For forwarders
Self-serve air and ocean, with CargoWise as your backend.
Shipeezi is not here to replace the forwarder system of record. It gives you a self-serve front door to quote, book, document and track, and hands the ops to CargoWise while status flows back onto the same event spine.
The problem
The front door is manual and the status is trapped.
The front door is manual
Quoting and booking air and ocean still run through email and spreadsheets, with no self-serve path for the shipper.
Two systems, two truths
The ops system is the record, but the customer wants status the ops system was never built to expose.
Mode is treated as a product
Air and ocean are often separate tools, when both are legs on one shipment.
How Shipeezi fits
Integrate, do not rip and replace.
Shipeezi is the shipper-facing front door and the normalised status surface. Execution stays with the forwarder and CargoWise.
CargoWise as the ops backend
Execution is handed to CargoWise. Shipeezi takes the shipper-facing work: the quote, the booking and the status the customer asks for.
Air and ocean on one model
Both are leg modes. A shipment is an ordered chain of legs, so a sea-then-air move is one record, not two.
Status back on the same spine
Carrier, DCSA and ops events normalise onto the leg as planned, estimated and actual, whatever their source.
Capabilities
What a forwarder gets.
- Self-serve quote, book, document and track
- CargoWise as the ops backend
- Air, ocean, road and rail on one leg model
- DCSA track and trace for ocean
- Carrier catalog with per-carrier references
- Webhooks and a public read API
Bring a lane.
Give us an air or ocean lane and we will show the booking, the leg chain and the status feed.