PLATFORM · ORDERS

Find out where your order actually stands. In four seconds, not twenty minutes.

Every cross-border order lives in six tools at once — your accounting system, your spreadsheet, a WhatsApp thread, the forwarder's portal, a Dropbox folder, and somebody's head. When the client emails for an update, the answer takes a reconstruction. When something changes — a quantity, a manufacturer, a shipment delay — the cascade has to be redone by hand.

Orders in TradeOS runs the whole thread on one record. PO, production, QC, shipping, documents, invoicing, payment — same row, every state visible, complete history.

Book a demoSee pricing →

Order RD-2026-077 — every dependency, every dollar, in one record.

WHAT GOES WRONG WHEN THE ORDER LIVES IN SIX TOOLS

Three moments every cross-border operator already knows.

The twenty-minute status update

The hospital distributor in Frankfurt emails Tuesday morning asking when their order of nitrile examination gloves will ship. You open the spreadsheet — production was supposed to start Monday. You open WhatsApp — the manufacturer says one of two lots is at 18% versus the 60% expected. You open the forwarder portal — the slot is booked but the manufacturer hasn't confirmed ready-to-ship. You open accounting — the deposit cleared three weeks ago. Twenty-three minutes later you reply with a partial answer. By the time you send it, two of those four data points have already changed.

The amendment that cascades for three days

The buyer on a stainless steel order increases the quantity by 30% on Friday afternoon. By Monday you've updated the production plan with the mill, the freight booking with the forwarder, the invoice on accounting, the customs declaration on the broker portal, the insurance certificate, and the LC amendment with the bank. Every system is its own update. The HS code is the same — but it's typed five times across five tools. One of them is wrong. You won't find out which until customs holds the shipment.

The split shipment nobody can price

A power IC you've ordered for a customer is on allocation. The supplier confirms 70% available this month, 30% in six weeks. The customer wants both legs to ship — partial now, balance later. Now you need two invoices, two freight bookings, two customs entries, two sets of documents, and a recomputed margin per leg because air freight on the second tranche kills the unit economics. The order management tool doesn't do partial shipments. So it gets done in a spreadsheet. The actual margin is found out at month-end.

PORTFOLIO VIEW

See what needs your attention across all orders — without opening any of them.

The detail page answers what's happening with this order? The Overview answers what across the whole book needs me right now? Six role-adaptive KPIs at the top, six live cards underneath that surface what's behind, what's shipping, what's stuck, and what needs documentation. The orders that need attention rise. The orders that are fine stay quiet.

Overview tab · Apr 30, 2026 · 38 active orders, $6.4M total value, 3 flagged.

CAPABILITIES

What the Orders module does

4.1 · Three views

Same orders, three lenses — depending on the question you're asking.

Board view is a kanban across three lifecycle stages, with order count and $ in flight per lane — the lens for "what stage is everything in." Timeline is a Gantt with weekly columns and a bar per order, color-coded by status — the lens for "where are the bottlenecks." List is a sortable table across every dimension — status, lots, shipments, invoice state, priority, delivery, margin — the lens for bulk review and export. The data doesn't change. The question does.

Board · Timeline · List

BoardTimelineList

Sales $520K1

RD-2026-072

🇨🇳 CN consumer electronics

$520K

DRAFT0d
→ Confirm

Operations $2.5M16

RD-2026-038

🇸🇬 SG industrial controls

$85K

CONFIRMED0d
→ Production

RD-2026-077

🇩🇪 EU healthcare distributor

$560K

IN PRODUCTION14d
→ Ready to Ship

Delivery $3.4M21

RD-2026-026

🇦🇺 AU hospital network

$115K

SHIPPED3d
→ Delivered

RD-2026-068

🇮🇹 IT pharmacy chain

$445K

DELIVERED28d

Timeline (W14 — W27, weekly)

ORDERW14W16W18W20W22W24W26
RD-2026-064IN PRODUCTION
RD-2026-077IN PRODUCTION
RD-2026-068DELIVERED
RD-2026-072DRAFT

List

OrderClientValueStatusMargin
RD-2026-077🇩🇪 EU healthcare distributor$560KIN PRODUCTION21.2%
RD-2026-064🇬🇧 UK clinic group$312KIN PRODUCTION18.7%
RD-2026-068🇮🇹 IT pharmacy chain$445KDELIVERED23.4%
RD-2026-072🇨🇳 CN consumer electronics$520KDRAFT—

4.2 · Lifecycle

Approval rules and deposit gates that move orders along automatically.

Thirteen states from Draft to Closed, surfaced as six milestones on the order detail page. The full state machine drives transitions underneath: orders above a value threshold or assigned to a new manufacturer route to a manager for sign-off. Deposit terms gate the move into production. Client approval workflows formalize the proforma sign-off. Every transition is logged in an immutable audit trail.

State machine — 13 states

Happy pathCancelled w/ reversalOn hold (any state)

4.3 · Documents

The document checklist generates itself — for this order, this Incoterm, this destination.

CIF Hamburg pulls a different list than FOB Long Beach. A medical glove shipment to the EU pulls one set of certificates; a chemical drum shipment to Singapore pulls another. The checklist updates as the order's parameters change. Documents present, missing, and expiring are visible from the order detail page — no chasing the operator to remember what's required.

Document checklist · CIF Rotterdam · stainless steel coils

RD-2026-20311 required · 5 present · 4 pending · 2 to generate
✓ Commercial Invoice
✓ Packing List
✓ Mill Test Certificate (EN 10204 3.1)
✓ RoHS Material Declaration
✓ Insurance Certificate
… Bill of Lading awaits shipment
… EUR.1 Movement Certificate request from mill
… SGS Inspection Report at load port
… LC Document Set in progress
− Certificate of Origin auto-generate →
− Customs Declaration (NL) auto-generate →

4.4 · Profit & loss

Know the margin on every order while it's still alive, not at month-end.

Revenue, manufacturer cost, freight, customs, insurance, inspection fees, packaging, rework, expedite charges — all attached to the same order record. Net profit and margin update in real time as costs accrue. Finance sees the orders running below threshold before they close, not after. The reason TradeOS can compute this where most tools can't: the costs and the revenue live on the same row, not in separate systems that need reconciling.

Order P&L · RD-2026-147 · live

RD-2026-147 · KR EMS customer · power ICs▲ 9.4% margin
Revenue (invoice total)$340,000
Component cost−$248,500
Air freight (split shipment)−$38,200
Customs & duties−$14,400
Insurance + other−$6,800
Total costs$307,900
Net profit$32,100

4.5 · Atlas on Orders Coming with AI services

Atlas will read every order so you don't have to.

When the AI services module ships, Atlas runs alongside every order: detects risk before it lands by watching production progress against the milestone schedule, digests supplier threads across WhatsApp, email, and portal so you know operational state without reading every message, drafts documents from order data — Commercial Invoice, Packing List, Certificate of Origin — for human sign-off instead of typing.

Atlas-on-Orders ships with the AI services module after the four operator portals are complete. The platform today is fully functional without it.

Atlas signals · Preview of the planned UI

Risk · RD-2026-064

Factory B production at 18% — expected 60% by today. Material shortage cited in supplier thread.

Surfaced 3 days early · partial-fulfillment split suggested

Thread digest · RD-2026-077

Factory A confirmed lot PL-2026-0138 ready for QC. Factory B delayed 4 days on lot PL-2026-0142.

7 messages summarized · 1 needs reply

Doc draft · RD-2026-068

Commercial Invoice draft generated from line items, CIF Hamburg, USD. Ready for operator review.

Drafted from order data · sign-off required

DATA MODEL

Update one fact about an order. Every other section already knows.

Orders is the row that ties the data model together. Products references it for line items and prices. Manufacturers references it for production allocation. Shipments references it for what's moving. Documents references it for the checklist. Finance references it for invoices and payments. Change a manufacturer on the order, the production plan updates. Change the destination, the document checklist regenerates. Nothing copies anywhere.

SectionWhat flowsWhat you see
ClientsClient terms, addresses, deal pipeline conversionClient name clickable; one-click deal-to-order
ProductsCatalog → line items, pricing, compliance classProduct name clickable to detail
ManufacturersAssignment per line, capacity, lead time, costManufacturer name clickable to profile
ProductionOrder generates lots, QC results returnLot reference clickable; embedded production status
ShipmentsOrder spawns shipments, tracking returnsShipment number clickable; embedded position
FinanceOrder → invoice → paymentInvoice and payment status on every order
DocumentsAuto-generated checklist + linked uploadsRequired, present, missing visible inline

DEPTH

Where it goes deeper

6.1 · Pipeline conversion

Close a deal in Sales. The order is already drafted in Ops.

When a deal moves to Won in Clients > Pipeline, one click generates a Draft order pre-populated with everything the deal already knew — client, products, quantities, accepted pricing, shipping address, payment terms, currency, Incoterm, notes. The operator reviews, adjusts if needed, confirms. CRM and order management collapse into one motion.

Deal → draft order · auto-populated

Pipeline · Won

● Won — Apr 08, 2026
ClientNL infrastructure contractor
ProductStainless steel coils 304L · 4mm
Quantity180 tonnes
Quote$2,180 /tonne
Total$392,400
Terms30/70 LC
IncotermCIF Rotterdam
OwnerMira S. (Sales)
⟶

Order · Draft (auto-populated)

● Draft — generated Apr 12
Order IDRD-2026-203
ClientNL infrastructure contractor
Line itemsStainless steel coils 304L · 180t
Unit price$2,180 /tonne
Total$392,400
Terms30/70 LC
IncotermCIF Rotterdam
HandoffMira S. → Ops

6.2 · Amendments

When the order changes, the cascade is automatic — not three days of cleanup.

Quantity changes, manufacturer swaps, destination changes, Incoterm changes, payment term changes — every amendment writes through to production, shipping, documents, invoicing, and the audit trail in one move. The customs broker sees the new HS code. The forwarder sees the new freight booking. The bank sees the LC amendment. Nobody retypes.

Amendment · impact assessment

Amend order — quantityRD-2026-077

Requested change

Quantity:
8,000,000 → 9,600,000 units (+20%)

Reason:
Client follow-up order absorbed into open PO

Impact

Prod AFactory A capacity OK · +960KOK
Prod BFactory B capacity tight · +640KWARN
Freight+1 container · +$2,400OK
Delivery+2 days (Jul 23 vs Jul 21)WARN
Docs3 to regenerate (CI, PL, CoO)OK
CancelApprove amendment

A DAY IN OPERATIONS

A day in the life

Mira runs trade operations for an 18-person medical-grade glove importer based in Chicago, shipping to healthcare distributors across the EU. Her morning starts with the Orders board.

She opens the kanban view and the column "In Production" has 14 orders in it. One has a red risk indicator — order RD-2026-064, due to ship in 6 days. She clicks in. The production tab shows two lots, one at Factory A (on track) and one at Factory B (behind schedule, 18% complete versus 60% expected by today). The manufacturer thread shows yesterday's message from Factory B citing a material shortage. She replies with a question, then opens the impact assessment: if Factory B finishes a week late, the order ships partial — 70% on the original schedule, 30% in a follow-up. She approves the partial fulfillment split, which auto-creates a child order for the remaining 30% and updates the document checklist for the partial shipment.

She moves to a Pending Client Approval order — the proforma was sent to a new client three days ago. She nudges via the per-order communication thread. She opens the financial summary on a recently-closed order and sees the actual margin came in 2.1 percentage points higher than projected; the variance was lower freight cost than estimated. She tags the cost type so the next quote builder knows to use the better rate.

By 9:45 she's done with Orders for the morning. Without the platform, this would have been six tabs, three messages, and a spreadsheet update.

WHERE IT FITS

Keep your accounting system. Keep your forwarder portal. Run the order on TradeOS.

Most operators arrive with a working stack — accounting for the books, a freight forwarder portal for shipments, spreadsheets for production allocation, messaging for supplier conversations. TradeOS Orders is the layer above. It runs the order itself end-to-end and connects to the rest. Nothing to rip out.

Accounting & finance system

Stays where it is.

TradeOS Orders pushes invoices and payment events into your accounting system through native integration. Your books stay the source of truth for accounting; your orders stay the source of truth for the operation. Same data, no re-keying.

Freight forwarder portals

Connects in.

Carrier APIs and forwarder portals feed shipment milestones (BL issued, departed, in transit, arrived) directly onto the order record. The forwarder keeps their TMS for their workflow; you see the milestones in context of your order, your client, your delivery promise.

Inventory / warehouse system

Stays where it is.

If you hold stock domestically, your WMS keeps running the warehouse. TradeOS Orders covers the upstream layer — the months between PO and goods landing — that warehouse systems don't track. The handoff is automatic when goods arrive.

Supplier messaging (WhatsApp · email · WeChat)

Connects in.

Per-order communication threads pull from email, WhatsApp, and (coming) WeChat. The supplier keeps using their channel; the operator sees the messages alongside the order they belong to. Atlas summarises threads and flags what needs a reply.

TradeOS Orders

Runs the thread.

The one record everything else attaches to: the PO, the production plan, the QC outcome, the shipment, the documents, the invoices, the margin, the conversation history. Months of activity, every party, one trail.

The tools in your existing stack are good at their slices. None of them tracks the full cross-border trade transaction from purchase order to payment — that's a different problem with a different shape. TradeOS Orders is built for that shape. It doesn't replace your stack; it runs the layer above it that has been a spreadsheet until now.

FAQ

Frequently asked questions

Eight questions operators ask when evaluating TradeOS Orders.

The Orders module is the central hub of TradeOS where every commercial trade transaction lives from the moment a deal is won through to the moment it's invoiced and paid. Each order is a single record that references the products being shipped, the client buying them, the manufacturers producing them, the production lots, shipments, invoices, and documents — connecting every other section of the platform.

Bring us one of your active orders. We'll run it through TradeOS in 30 minutes.

The messiest one is the most useful — the one with the amendment, the document chase, the split shipment, the manufacturer that went quiet. We'll show you what it looks like when production, shipping, documents, and finance are all on the same record. No demo data. Your data.

Book a demoTalk to sales

See pricing →

PRODUCTIONProductionMulti-manufacturer planning, AQL inspections, yield tracking.Open module →SHIPMENTSShipmentsBooking through customs to delivery in one record.Open module →FINANCEFinanceInvoicing, payments, profitability with landed cost.Open module →
Order management for global trade operators | TradeOS