The cockpit your forwarders work in. Branded for your operations.

The operator pays for TradeOS; the Logistics Portal is free for the forwarders, brokers, and carriers they invite. Operators on different tiers see different features show up in your workspace for them: carrier API integration on Solo+, automated customs documentation on Business+, direct US ABI/ACE filing on Business+. Logistics providers never see a paywall on TradeOS.

No. One global users row, one login, ten operator workspaces. The platform’s external_memberships table joins one user to multiple external_organizations; switch operators with one click in the workspace switcher. Each operator’s data is fully isolated — your bookings, rates, milestones, invoices for operator A are invisible to operator B, enforced by per-connection scope at the service layer (not the UI).

Set up once at your external_organization level, reused across every operator workspace you serve. Credentials are encrypted via the KMS plugin; the same Maersk / MSC / CMA CGM / ONE / HMM / project44 setup feeds every operator. v1 ships the credentials store and the project44 integration; broader carrier-API coverage (direct ocean carrier integrations, IATA Cargo IQ for air, FedEx / UPS / DHL for express) lands as those integrations are built. The schema is carrier-agnostic — adding a new carrier doesn’t require schema changes.

Incoterm-driven. The connection’s visibility_config JSON sets per-incoterm visibility — origin can render as country, port, city, factory name, or factory address; destination similarly. Under DDP / CIF / CFR the operator is the legal shipper of record and the factory identity is abstracted (typically rendered as the operator’s address). Under FOB or EXW the factory is the legal BOL shipper; the factory name has to appear because it has to be there legally. The platform makes this explicit and configurable, not negotiated.

Yes via PWA — installs to the home screen on Android and iOS, works offline, captures milestones with GPS lat/lng and photo uploads. Driver-role users see only their own dispatch assignments — no rates, no invoices, no other shipments. POD capture (signature on canvas, photo, signer name/title) is a gating requirement before the dispatch state can advance to completed. Native iOS / Android driver apps and geofence-driven auto-transitions are post-launch.

For US import/export, yes — direct ABI/ACE submission for licensed brokers is on the Business+ tier. For other jurisdictions (EU ICS2, UK CDS, China Single Window, India ICEGATE) we integrate with your existing broker and surface filing status. Customs filings move through a 7-state machine: draft → submitted → accepted / held / queried → cleared (or rejected). Per-jurisdiction (ISO 3166-1 alpha-2 country code), per-declaration-type (import / export / transit). Schema-less declaration_data JSON accommodates per-jurisdiction differences without schema changes.

It’s the structured-response queue for operator-initiated work, the largest single page in the portal (1252 lines). Three sub-tabs combine three workflow types that all share the same “I owe a response, this is time-pressured” pattern: /inbox/bookings (booking requests · accept, counter-quote, or decline inline), /inbox/quotes (RFQs · submit quote with rate/currency/transit-days/expiry, or decline inline), /inbox/disputes (invoice disputes · respond inline). Each tab has three sections: Needs Action (Rachel owes a response — inline forms), Awaiting Response (read-only), Recently Decided (last 7 days, collapsed). Counter-quoted bookings the operator hasn’t acted on in 48+ hours surface in Needs Action with a “STALE · FOLLOW UP” eyebrow.