YASLOGIST Move Smarter. See Further.
Request accessاطلب الوصول

Every handoff. One identity.

One shipment record across road, sea and air. Explore how its references connect.

Request access
Original conceptual logistics landscape showing a sea port, road gate, warehouse and cargo airport; not a real location
Original generated concept · schematic connections

Ocean gateway

Sea and air are alternative gateways. This fictional sample follows a sea-to-road corridor; the scene is not a geographic map or live tracking.

Every handoff changes the reference number. Keep one shipment record.

Building the Digital Infrastructure for the Movement of Goods.

One shipment moves under a booking, bill of lading, container number, ACID number, gate pass, truck plate, and delivery note. YASLOGIST links those identifiers into a single timeline so operations teams see where cargo sits and what holds it.

ACCESS STAGE Early access — Egypt & regional trade corridors
COVERAGE Road, sea, and air shipment records

Three operational functions on one shipment record.

CORE FUNCTIONS

Unify

01 // UNIFY

Link booking, bill of lading, container number, ACID number, gate pass, truck plate, and delivery note into one shipment record.

ONE SHIPMENT, ONE RECORD

Trace

02 // TRACE

Follow one ordered timeline across road, sea, and air, including inland haulage legs that carrier systems do not report.

ORDERED MULTIMODAL TIMELINE

Flag

03 // FLAG

Surface late milestones, missing documents, and open clearances as explicit exceptions before demurrage or detention accrues.

EXCEPTION SURFACING
Original generated concept of goods moving through a warehouse receiving dock
Original generated concept · schematic connections

Carriers report sea and air legs. Nobody reports the road leg unless it is captured at the gate and in the cab.

THE BLIND LEG

Once a container clears the port gate or cargo leaves the airport terminal, carrier feeds stop. YASLOGIST records gate-in, gate-out, truck plate assignment, and cab checkpoints directly so the inland leg stays attached to the same shipment record.

Original generated concept of a freight truck at a gate checkpoint
RECORDED AT GATE & CAB
REPORTING SOURCE BY LEG
Ocean Leg
Vessel departure, arrival, and discharge
CARRIER REPORTED
Air Leg
Air waybill flight manifest events
CARRIER REPORTED
Road Leg (Gate to Gate)
Truck plate, gate pass, and cab checkpoints
RECORDED AT GATE & CAB

How a shipment record is built and monitored.

OPERATIONAL WORKFLOW

Bind shipment identifiers

STAGE 01 BIND

Create the shipment record with the initial booking or ACID number and attach the bill of lading, container number, truck plate, gate pass, and delivery note as each document is issued.

Log sea, air, gate, and cab events

STAGE 02 CAPTURE

Combine sea gateway events and Cairo Cargo Village air milestones with gate-in, gate-out, and cab status updates from the road leg in chronological order.

Act on flagged holds

STAGE 03 RESOLVE

When a clearance remains open, a required document is missing, or a truck misses a gate window, the record flags the exception so the responsible party can clear the hold.

BKGB/LCNTRACIDGATETRKDNYSL-SHP-000482-EG

Seven references. One fictional record.

Three mode-specific surfaces connected to the same record.

OPERATING SURFACES

The links below open interactive simulation environments showing how each mode surface operates.

Ocean, Land and Air interfaces on yaslogist.com are coming soon. The .me links below are for demonstration environments.

Original generated concept of a ship unloading at a sea terminal

Ocean

Demo environment OCEAN

Container tracking through Egyptian sea gateways, linking bookings, bills of lading, ACID filings, terminal discharge, and port gate release.

Coming soonocean.yaslogist.com
Conceptual truck travelling on a desert highway during an inland freight leg
تصوّر بصري للنقل البري — ليس أسطولًا تابعًا للشركةInland leg concept — not company fleet

Land

Demo environment LAND

Road freight visibility from gate to gate, binding truck plates, driver dispatches, gate passes, and delivery notes across inland corridors.

Coming soonland.yaslogist.com
Original generated concept of cargo loading into an aircraft

Air

Demo environment AIR

Air cargo monitoring through Cairo Cargo Village, connecting air waybills, terminal handling milestones, clearance status, and tarmac release.

Coming soonair.yaslogist.com

The Air demo link was unavailable at review time.

Original generated concept · schematic connections

What YASLOGIST is not.

OPERATIONAL BOUNDARIES

YASLOGIST is a software visibility layer that maintains the shipment record across your existing logistics providers. It does not replace physical operators or regulatory intermediaries.

Not a freight forwarder

BOUNDARY 01

YASLOGIST does not book cargo space, operate trucks, charter vessels, or physically move or store goods.

Not a shipping agent

BOUNDARY 02

YASLOGIST does not represent ocean lines or airlines, issue bills of lading, or collect carrier freight charges.

Not a customs broker

BOUNDARY 03

YASLOGIST tracks ACID numbers and clearance milestones on the shipment record, but it does not file customs declarations or act as a licensed broker.

Frequently asked questions.

QUESTIONS & LIMITS

Request access or discuss a trade corridor.

DIRECT CHANNELS
Satellite photograph of the three Giza pyramids, plateau roads and the boundary between desert and dense urban neighbourhoods
Giza plateau · EgyptSatellite photograph

Talk to the founder

WHATSAPP // DIRECT

Direct WhatsApp line for supply chain leads evaluating YASLOGIST for their shipment operations.

+20 104 113 9910

Early access & onboarding

EMAIL // NEW ENQUIRIES

For new access requests, corridor assessments, and operational walkthroughs.

contact@yaslogist.com

Active shipment support

EMAIL // EXISTING SHIPMENTS

For teams already onboarded who need assistance with an active shipment record or reference update.

support@yaslogist.com

Giza plateau · Egypt

Crop from the supplied satellite photograph. Geographic context only; not live tracking.