Shipment Tracker
IN TRANSIT
2 2 active
DELAYED
1
NEXT ARRIVAL
Jun 22
FREIGHT THIS MONTH
$128K
PLATFORM · SHIPMENTS
Find out the container is held in customs before your client does.
The forwarder runs their TMS. The carrier has their own tracking. The customs broker emails when something is wrong. The accounting system books the freight invoice three weeks later. Each tool is excellent at its slice — none of them sees what the operator actually needs to see: which production lot is in which container, why customs is asking about the EN 455-2 report, what the landed cost will be when the box hits Hamburg.
Shipments in TradeOS is the layer above all of it. Multi-modal tracking with the production lot, the certificates, the customs documents, and the landed cost on the same record as the order. So when something goes sideways at a transshipment port, you're the one telling the client — not the other way around.
Tracking — every shipment, every milestone, every exception, on one canvas.
WHAT BREAKS WHEN YOU’RE THE SHIPPER, NOT THE FORWARDER
Three shipment moments every international operator already knows.
Demurrage on a coffee container
A 25-tonne container of green coffee beans from Buenaventura arrives in Hamburg on a Friday. The customs broker emails Monday morning — the phytosanitary certificate references an inspection date 11 days before loading, and the regulator wants a fresh certificate. The container sits at the terminal. Demurrage starts ticking on day 5: $180/day on day 1–5, $360/day after. By the time you locate the right certificate in a 47-message email thread and the broker re-files, you’ve eaten 9 days at $360. The margin on the shipment was 11%.
The hazmat hold on a chemical drum
A 20-foot reefer container of specialty resin leaves Yokohama on Tuesday. On Thursday, the carrier flags a missing UN dangerous goods declaration — your shipper didn’t classify the resin correctly on the manifest. The container is offloaded at the next port and held pending re-classification. You’re now two weeks late, the customer’s production line is waiting, the carrier wants $12,400 in handling fees, and the insurance underwriter wants to know why the MSDS in the email thread doesn’t match the manifest. You don’t have one place to show them all the documents together.
The split shipment for an EMS customer
Your customer in Querétaro needs 80,000 power IC units to keep their automotive line running. The Shenzhen supplier has 50,000 ready to ship — the other 30,000 are six weeks out. The customer wants both legs to ship — sea freight for the first 50K, air freight for the 30K when ready. Now you need two BOLs, two customs entries at two different ports, two freight invoices, a recomputed landed cost per leg (because air freight on the second batch eats your 8% margin), and a way to keep the customer updated on both legs from one place. Your existing tools see one shipment at a time.
WHAT IT DOES
What the Shipments module does
When the client asks “where is my order,” answer in one screen — not after checking three portals.
Every shipment moves through a nine-milestone timeline — Booked, Docs Ready, Loaded, Departed, In Transit, Arrived, Customs, Cleared, Delivered — with each event recording date, time, location, and source. For multi-modal shipments, the detail breaks the journey into three legs: origin trucking from factory to load port, ocean freight with carrier and vessel tracking, and destination trucking from discharge port to the client’s warehouse. Each leg shows its own status so the operator sees at a glance which leg is the bottleneck. Same data feeds the client portal — when the client asks “where is my order,” the answer is one screen, not a Slack thread.
SHIPMENT DETAIL · TRACKING + TRANSPORT LEGS
SH-2026-088IN TRANSIT
🇩🇪 EU healthcare distributor · COSCO · COSCO Shipping Rose
Cargo
| LOT | PRODUCT | QTY | CTN | KG | CBM |
|---|---|---|---|---|---|
| PL-2026-0138 | Nitrile exam gloves · Cat III | 36,000 | 336 | 5,400 | 36.0 |
| PL-2026-0142 | Nitrile exam gloves · Cat III | 28,000 | 224 | 4,200 | 32.0 |
Tracking
Jun 12
06:18
🚢 Vessel Departed
📍 Port Klang, MY · COSCO Shipping Rose
Jun 18
14:02
⚓ Transshipment Arrival
📍 Singapore · COSCO Shipping Rose
Jun 22
09:47
🌊 In Transit Update
📍 Indian Ocean · COSCO Shipping Rose
Jun 28
11:30
🏁 Vessel Arrived
📍 Hamburg, DE · COSCO Shipping Rose
Transport Legs
Leg 1 · Factory → Port KlangCOMPLETE
Leg 2 · Port Klang → HamburgIN TRANSIT
Leg 3 · Hamburg → Client warehousePENDING
Pack containers from the lots you actually have — not the spec sheet of what fits in a 40HC.
Container planning starts with what you have, not what you want to fit. The operator picks a client, then selects which production lots — across factories, across orders — are ready to ship together. The planner aggregates total volume, weight, and unit count, then compares 20GP / 40GP / 40HC side by side: how many of each are needed, what the utilization looks like color-coded green (≥85%), amber (60–84%), or red (under-filled), and which type is flagged BEST FIT. The recommendation isn’t a black box — the operator sees the math and decides. Confirmed lots create the shipment with allocations preserved for the rest of the lifecycle.
CONTAINER PLANNING · STEP 3 · CONTAINER TYPE RECOMMENDATION
Container Planning
Step 3 of 3 · Plan Containers
🇲🇽 MX automotive EMS · 3 lots selected
TOTAL UNITS
140,000
TOTAL CBM
140.0
TOTAL WEIGHT
21,000 kg
20GP
5
containers
84% utilization
140.0 / 166 CBM
40GP
3
containers
69% utilization
140.0 / 203 CBM
★ BEST FIT
40HC
2
containers
92% utilization
140.0 / 153 CBM
DATA MODEL
A shipment knows which order it fulfills, which lots it carries, and what it actually cost — without anyone re-keying.
Shipments sits at the intersection of physical movement (production lots becoming cargo) and financial outcome (freight costs becoming landed cost). Every other section either feeds into a shipment or reads from one — and the cross-references are live, not copied.
| Section | What flows | What you see |
|---|---|---|
| Production | Released lots become shipment cargo with carton/weight/CBM | Lot reference clickable; QC results visible on shipment |
| Orders | Order references on every shipment; consolidation supported | Order number clickable; shipment status on order |
| Manufacturers | Origin factory address, contact, certifications | Factory profile clickable from shipment origin |
| Documents | Required docs auto-populate by Incoterm; missing docs flagged | Incoterm-based document checklist (CIF requires 7) |
| Finance | Freight costs feed landed cost and order P&L | Cost waterfall on shipment + on order detail |
| Customs & Compliance | Declarations, HS verification, duty estimation, broker tracking | 6 sub-tabs in one customs workspace |
| Inventory | Delivered shipments trigger inventory Receipt automatically | Stock level updates without re-entry |
WHERE IT GOES DEEPER
One capability most teams leave on the table.
Most shipment tools stop at tracking. TradeOS keeps going — into the duties left on the table.
Find the duty money sitting on import shipments that already re-exported — automatically.
When imported goods are subsequently re-exported — common for distributors and trading companies — the original import duties are partially or fully recoverable. Most operators leave this money on the table because matching drawback-eligible pairs across import and export shipments takes reconciliation work nobody has time for. TradeOS surfaces the candidates automatically: every import shipment with a duty paid record can be paired with an export shipment containing those products, and the platform tracks the claim from Identified → Filed → Approved → Received, with the recovered amount flowing back into the order’s P&L.
COSTS & FREIGHT · DUTY DRAWBACK
TOTAL DUTIES PAID
$184,400
ELIGIBLE FOR RECOVERY
$152,360
RECOVERED
$60,768
PENDING CLAIMS
$91,592
All Status ▾12 entries+ New Drawback Entry
| IMPORT | EXPORT | PRODUCT | HS CODE | DUTY PAID | ELIGIBLE | STATUS |
|---|---|---|---|---|---|---|
| SH-2025-419 | SH-2026-203 | Green coffee · Arabica washed | 0901.11.00 | $32,580 | $28,344 | FILED |
| SH-2025-387 | SH-2026-122 | Roasted coffee · ground · whole-bean | 0901.21.00 | $48,920 | $44,028 | RECEIVED |
| SH-2025-491 | Not matched | Specialty single-origin · Ethiopia | 0901.11.00 | $24,700 | $22,230 | IDENTIFIED |
| SH-2025-455 | SH-2026-178 | Decaffeinated green coffee | 0901.12.00 | $18,600 | $16,740 | APPROVED |
BUILT INTO YOUR OPERATIONS
A shipment, end to end.
Carmen runs logistics for an importer of medical-grade supplies. Today is the day shipment SH-2026-088 — carrying lots PL-2026-0138 from Factory A and PL-2026-0142 from Factory B against order RD-2026-077 — leaves Port Klang for Hamburg.
Morning: Carmen opens Shipments > Tracking and SH-2026-088 sits at the top of the active list, status Loaded. She clicks in. The CIF document checklist shows complete — proforma invoice, purchase order, commercial invoice, packing list, BOL, certificate of origin, insurance certificate — plus the medical-grade certifications uploaded against the shipment: CE Cat III, EN 455-1/2/3 test reports, EN 374 test report, AQL inspection. The container CMAU 8473521-9 is sealed. She clicks Confirm departure. Status moves to Departed. The client portal updates instantly; EU healthcare distributor sees their order is on its way.
Day 14: Carmen gets a Slack notification from the platform — Atlas AI flagged that the Singapore transshipment took 2 days instead of the planned 1, and the new ETA at Hamburg is July 12 instead of July 10. The platform has already drafted a notification to the client. Carmen reviews, edits one line, and sends.
Day 30: The container arrives at Hamburg port and clears discharge. Six hours later the customs declaration goes in. Twelve hours after that, an exception fires — Major severity, customs hold, HS code clarification request. The customs inspector is asking for the EN 455-2 test report. Carmen opens the exception detail. The platform has already located the EN 455-2 report in the Documents module and prepared a customs response. She reviews, approves, the response submits at 09:18. By 10:18 the next morning, customs has cleared the container. The hold added 18 hours. No demurrage was charged because the container was still inside the 5-day free-time window.
Day 32: The container arrives at EU healthcare distributor’s warehouse in Hamburg. The driver scans the BOL barcode on his mobile app and captures POD with a photo. Inventory section auto-creates a receipt for 8,000,000 units of Nitrile exam gloves · Cat III. Order RD-2026-077 status moves to Delivered. Finance section sees the delivery event and queues the final 70% LC presentation to the bank.
The whole shipment lived in one record. Five sections updated each other automatically. Carmen handled it from one screen.
WHERE IT FITS
Keep your forwarder. Keep your carrier portal. Keep your broker. Run the layer above them.
Most operators already have shipment tooling in place — the forwarder runs a TMS, the carrier has their own tracking, the customs broker uses their own software, sometimes a visibility layer sits on top. TradeOS Shipments doesn’t replace any of it. It owns the shipper’s order record — where the production lot, the cargo, the documents, and the landed cost live together.
Forwarder TMS / portal
Stays where it is.
Your forwarder keeps running their TMS for their workflow — bookings, manifests, container tracking, milestone updates. TradeOS Shipments reads from their portal or their API and pulls the milestones into the order record. The forwarder doesn’t change tools; you stop checking three portals.
Carrier tracking (Maersk, MSC, CMA CGM…)
Connects in.
Carrier APIs feed shipment milestones — BL issued, departed, in transit, transshipment, arrived — directly onto the order record. Carriers keep doing what they do; you see their data in the context of your order, your client, and your delivery promise.
Customs broker software
Receives the handoff.
When a shipment approaches arrival, the platform surfaces the documents the broker needs and flags anything missing pre-departure. The broker files; the filing status comes back onto the shipment record. You stop being the email relay between origin and destination.
Visibility layers & spreadsheets
Absorbed.
The third-party visibility layer that watches your containers, the spreadsheet tracking freight cost variance, the WhatsApp thread with the forwarder about a customs hold — all collapse into the shipment record. The data was never meant to live in a separate tab; it just had nowhere else to go.
TradeOS Shipments
Runs the shipper-side thread.
Production lots → containers → vessels → customs → inventory receipts — all on one record, linked to the order they fulfill and the P&L they affect. Multi-modal legs, lot-level container planning, customs and compliance, duty drawback identification, insurance management. The layer above the freight, owned by the company shipping the goods.
Forwarder TMS platforms and carrier-aggregation suites were built for the company moving the freight — not for the company shipping the goods. TradeOS Shipments fills the gap nothing else owns: the operator-side thread that connects production lots (with QC) to shipments (with tracking) to inventory receipts to landed-cost-aware order P&L. It doesn’t replace your forwarder, your carrier, or your broker; it runs the layer above them where the shipper actually works.
FAQ
Frequently asked questions
The Shipments module manages the logistics lifecycle of cross-border trade shipments from booking through delivery. Each shipment is a single record connected to the orders it fulfills, the production lots that filled it, the documents customs will require, and the freight costs that determine landed margin. Trade operators use it to track multi-modal legs, plan container utilization with production lot granularity, run pre-departure compliance checks, manage 600+ exception types with severity-based actions, score carrier performance per route, and identify duty drawback opportunities.
Bring us one of your active shipments. We’ll trace it end-to-end in TradeOS in 30 minutes.
The one held in customs, the one that ate demurrage, the split shipment with two BOLs, the import that should have triggered a drawback claim. We’ll show you what it looks like when the production lot, the documents, the milestones, and the landed cost are all on the same record. No demo data. Your data.