PLATFORM · DOCUMENTS
Every trade shipment ships with a stack of paperwork — commercial invoice, packing list, BOL, certificate of origin, certificate of analysis, customs declaration, plus client- and regulator-specific certificates. The same five fields — consignee name, vessel name, port code, HS code, weight — get retyped onto document after document. Each retype is another chance for the typo that gets the LC presentation rejected. Each PDF lives in a Dropbox folder named “QC reports 2026-Q3,” forgotten by Friday, asked for by customs on Tuesday.
Documents in TradeOS templates the documents you generate, populates them from your connected order/production/shipment data, tracks coverage per shipment so you see what’s missing before the vessel sails, and surfaces the right documents to each external party — clients in their portal, manufacturers in theirs, your team in yours. Generated, not retyped.
Coverage — every shipment’s document set, what’s present, what’s missing, what’s expiring. Click any document to view, edit, or request a new version.
WHAT BREAKS WHEN DOCUMENTS LIVE IN FOLDERS, NOT ON RECORDS
The commercial invoice you sent to the LC bank says “Bremerhaven” — the LC says “Hamburg.” The vessel name in the BOL says “COSCO Rose v047E” — the LC reference says “COSCO Rose v0047E.” Both wrong by one character. The bank rejects the presentation. The wire that was supposed to land Friday lands the following Thursday. You retype, resubmit, and discover the packing list now has a different gross-weight number than the BOL — round two.
The container has arrived at the destination port. The customs officer needs the EUR.1 preferential origin certificate. It exists — your supplier issued it three weeks ago and emailed it to procurement. Procurement is on PTO. The email is in their personal inbox. Three hours of search-by-attachment-name across four Drive folders before someone finds it. Demurrage starts accruing at hour two.
The packing list was amended on Tuesday after a count discrepancy — 1,800 cs corrected to 1,820 cs. The amended version was sent to the forwarder. The customs broker has the original from Monday’s email. The auditor pulls the original from a shared folder where someone backed up the Monday version. Three documents, three numbers, one shipment. Six months later, an audit finding: which packing list was the one of record?
WHAT IT DOES
The Templates & Generation tab ships with six core trade-document templates — commercial invoice, packing list, proforma invoice, certificate of origin, customs declaration, shipping instructions. Each template knows which fields go where and which section of the platform supplies them. Open the commercial invoice for shipment SH-2026-088 and most fields are pre-filled — consignee from Orders, vessel from Shipments, lot composition from Production, HS code from Products, LC reference from the order’s LC record. A handful of free-text fields remain — the operator reviews, fills them, issues. Templates are fully customizable in the document editor, and event-based triggers (order confirmed, shipment booked, payment received) can auto-generate the next document in the chain so it lands as a draft ready for review.
COMMERCIAL INVOICE TEMPLATE · INV-2026-077
What documents does a shipment actually need? It depends on the incoterm (CIF needs the insurance certificate, EXW doesn’t), the destination country (EU needs an EUR.1, Singapore doesn’t), the product (medical Cat III needs CE certificates and EN test reports, basic apparel doesn’t), the client (some buyers require a Beneficiary Certificate, some don’t), and the LC terms (the bank may require a specific list of documents in the presentation set). TradeOS captures all of this as five layers of rules — Incoterm, Destination, Product, Client, LC Terms — and the Requirements builder unions them: pick the values for a shipment, the system returns the exact list of documents you owe, with the source layer tagged on each one. Add a new client with quirky paperwork demands? Add a Client-layer rule. Open a new destination market? Add the destination rules once, every future shipment to that market inherits them.
REQUIREMENTS BUILDER · SH-2026-088
Trade documents don’t live in one bucket. Shipments need transport docs, orders carry commercial docs, manufacturers carry their certifications, clients carry their compliance demands. The Coverage tab groups documents by the entity they belong to — Shipments, Orders, Manufacturers, Clients — and tracks completeness against the requirements engine, so you see at a glance which shipment is short two documents, which manufacturer has a certificate expiring next month, which order is ready for invoicing and which is blocked. Click into any card to see each document with status (Complete, Draft, Missing, In Progress, Expiring) and the actions available — Edit, Finalize, New version, Upload, Request from supplier.
COVERAGE · 4 ENTITY TYPES
Standard templates cover the common cases. The Document Editor handles everything else. Open any template from Templates & Generation and the editor loads with the rendered document on the left and a block library on the right — text, headings, addresses, info fields, tables, dividers, images, spacers, signatures, notes, total-due. Edit any field, add blocks, change the layout, restyle to match your brand. The editor merges connected data live: pick an order from the sidebar and the consignee block, invoice number, line items, vessel, ports populate from the order, production lot, and shipment in one pass. Save Draft to keep iterating, Issue Document to finalize, Export PDF to get the file. No re-typing. No format drift between documents. No abandoned Word file on someone’s desktop.
DOCUMENT EDITOR · COMMERCIAL INVOICE INV-2026-077
HOW IT CONNECTS
A document is a snapshot of the data underneath. Documents reads from every other section to populate templates, and every other section reads back from Documents to surface what’s been issued, received, or required.
| Section | What flows | What you see |
|---|---|---|
| Orders | Consignee, Incoterms, LC reference, presentation deadline | All commercial documents pre-filled |
| Production | Lot composition, QC results, AQL inspection report | Quality docs auto-attached to shipment |
| Shipments | Vessel, voyage, BOL, container, sailing dates | Transport documents wired automatically |
| Manufacturers | Factory certifications, audit reports, signatory authority | Certificate library per manufacturer |
| Products | HS code, CE/FDA/PMDA refs, EN/ISO test reports | Regulatory docs per product per market |
| Finance | Invoice amounts, AP/AR posting, payment status against documents | Issued invoices and bills land in Finance ledger |
| External portals | Document visibility for client (buyer) and supplier (manufacturer) | Each role sees only what they should |
WHERE IT GOES DEEPER
Trade documents need an audit trail you can defend, and external parties — your clients at the destination, your manufacturers at origin — need access without seeing what they shouldn’t.
Every document keeps an immutable history: who created it, who edited which field, who finalized it, who downloaded it. When a client questions a vessel name on the invoice three weeks after delivery, the audit trail shows it was generated at 09:14 from the commercial-invoice template, edited at 11:22 by Carmen to fix a hyphenation against the LC, finalized at 11:40 by James (ops manager), downloaded at 11:42 for the buyer’s records. Immutable audit logs, queryable by document, exportable for any regulator who asks. The fragility of trade-document compliance is the gap between what was sent and what’s in the file folder. The audit trail closes that gap.
AUDIT TRAIL · INV-2026-077 · 5 EVENTS
Trade documents have to be visible across the operation — to your buyer at the destination, to your manufacturer at origin — without exposing the operator’s internals. Most operators handle this by emailing PDF attachments and CC’ing themselves, which is slow, lossy, and unauditable. TradeOS gives each external party a role-scoped portal. The Client portal shows the buyer the documents they need on their end — commercial invoice, packing list, BOL, certificates, customs declaration — read and download, no edit. The Supplier portal shows the manufacturer the documents required from them on each PO — AQL reports, test certificates, mill certs, factory audit reports — with upload affordances on the missing ones. Each role sees only what they should — the buyer doesn’t see your manufacturer cost or margin, the supplier doesn’t see other suppliers’ POs or the buyer’s contract terms. The cost of the wrong eyes on the wrong document is removed by design.
EXTERNAL PORTAL ACCESS · SH-2026-088
BUILT INTO YOUR OPERATIONS
Carmen runs logistics for EDMA Group. The vessel for order RD-2026-077 sails in 5 days, and the buyer Brevin Health EU expects the full document set on their client portal the day before departure. She has a meeting at 11:00 and three other shipments to look at.
09:14 UTC. Carmen opens Documents > Coverage, filters by Shipments, picks SH-2026-088. The Coverage card shows 8 of 11 documents complete — the 3 missing are the commercial invoice (she needs to generate it), the beneficiary certificate (auto-generated, awaiting her signature), and the EN 455 test report (requested from Crescent Manufacturing via the supplier portal, still pending).
09:16. She clicks across to Templates & Generation, selects the Commercial Invoice template, clicks Generate Now. The modal asks her to pick the order — she selects RD-2026-077 — and the shipment — SH-2026-088. The editor opens with 22 of 24 fields auto-filled: consignee, vessel, voyage, ports, manufacturer, HS code, line items, totals, LC reference all pulled from the connected order, lot, and shipment records. The two free-text fields remain — special markings, additional remarks.
09:22. Carmen fills “Medical examination gloves · do not freeze · keep dry” in special markings, reviews the line items against the LC’s bill of materials, and clicks Save Draft. The PDF is generated and stored. INV-2026-077 v1 appears on the Coverage card as a Draft.
10:15. She returns to v1, refines the remarks to add a freeze-protection clause Brevin Health EU asked about last week. Save Draft increments to v2. Audit trail records “edited special markings.”
10:42. The supplier portal pings: Crescent Manufacturing has uploaded the EN 455 test report against PO RD-2026-077. The doc lands as Final in the Coverage view, linked to both the shipment and to the manufacturer’s certificate library. 9 of 11.
11:08. Carmen drafts the beneficiary certificate from the same template flow, signs it digitally in the editor’s signature block, clicks Issue Document. Audit trail records “finalized: status → Complete · linked to order RD-2026-077”. 10 of 11.
11:18. She opens Documents > Requirements, picks the shipment’s parameters (CIF · Hamburg · Nitrile Cat III · Brevin Health EU · DBS LC), and the engine confirms: 11 required documents, 10 currently present, 1 still required — the EN 374 test report. She sends another request to Crescent through the supplier portal.
11:40. James (ops manager) reviews the commercial invoice v2, opens it in the editor, makes a small formatting fix on the vessel name (per the LC’s exact-casing rule), clicks Issue Document. v3 saves with status Final. Coverage card now shows 10 of 11.
14:02. The remaining EN 374 test report lands from Crescent. 11 of 11 · 100% complete. Coverage badge flips from amber to green.
Three days later, the vessel sails. Brevin Health EU sees the full document set in their client portal — 6 documents visible (invoice, packing list, BOL, EUR.1, CE+EN, customs), with internal cost and margin data masked. Six weeks after delivery, the buyer questions the vessel-name format on the invoice. The audit trail answers in one screen: generated 09:14 from template, edited 11:22 by Carmen, finalized 11:40 by James, downloaded 11:42. No one had to remember anything.
VS. ALTERNATIVES
| Capability | Dropbox / Box | SAP GTS | Tradeshift | Bill.com | TradeOS |
|---|---|---|---|---|---|
| Trade document templates (core 6 + custom) | ✓ | — | ✓ | partial | — |
| Auto-fill from order, production, shipment data | ✓ | — | partial | — | — |
| 5-layer requirements engine (incoterm · destination · product · client · LC) | ✓ | — | partial | — | — |
| Coverage tracking by shipment / order / manufacturer / client | ✓ | — | partial | — | — |
| WYSIWYG document editor with PDF export | ✓ | — | partial | — | — |
| Version history with audit trail | ✓ | partial | ✓ | partial | partial |
| Role-scoped Client + Supplier portals | ✓ | partial | partial | ✓ | — |
| Connected to order, lot, shipment data | ✓ | — | ✓ (within SAP) | — | — |
| Setup time | 1–2 weeks | 1 day | 9–18 months | 3 months | 1 week |
| Pricing fits SMB shipper | ✓ | ✓ | — | — | partial |
This isn’t a takedown. SAP GTS is the comprehensive enterprise solution for global trade document management — it works, it scales, and it costs hundreds of thousands a year with implementation timelines measured in fiscal quarters. Tradeshift is a credible supplier-collaboration platform for AP-heavy enterprises. Bill.com is best-in-class AP automation. Dropbox and Box are file storage. None of them generate the core trade documents from connected order, production, and shipment data, compute requirements from a five-layer rule engine, track coverage per entity, surface a WYSIWYG editor for custom templates, and expose role-scoped client and supplier portals — at a price point a $50M trader can afford. TradeOS Documents is built for that gap.
FAQ
The Documents module is the single store for every document a trade operation produces, receives, or has to present — commercial invoice, packing list, BOL, certificate of origin, EUR.1, certificate of analysis, AQL inspection report, test reports, insurance certificate, LC, customs declaration, and 30+ more. Documents are templated, auto-generated from connected order, production, and shipment data, version-controlled with full audit trail, validated against destination requirements, and organized as shipping document sets ready for the bank presentation, customs broker, or client portal.
Send the commercial invoice, packing list, BOL, and any certificates from a real shipment. We’ll show you how those fields populate from your order/production/shipment data, what coverage looks like across the shipment, and which docs are missing for the destination market. No demo data. Your shipment.