11 required · 8 present · 1 in progress · 2 to generate
Requirements derived fromCIF Hamburg + 🇩🇪 DE destination + medical Cat III + Meridian standard terms + LC drawing terms
PRODUCT · ORDERS · DOCUMENTS COLLECTION
Trade is paperwork pretending to be commerce. A single order to Germany generates a Commercial Invoice, a Packing List, a Bill of Lading, a Certificate of Origin, an EUR.1, an Insurance Certificate, an AQL Inspection Report, an LC Document Set, customs declarations on both ends, and product certificates. TradeOS treats documents as first-class data — generated from order data where possible, collected from counterparties where not, and stored once with full lineage.
11 required · 8 present · 1 in progress · 2 to generate
Requirements derived fromCIF Hamburg + 🇩🇪 DE destination + medical Cat III + Meridian standard terms + LC drawing terms
THE PROBLEM
The Commercial Invoice is in QuickBooks. The Bill of Lading is in the freight forwarder's portal. The CE certificate is in an email from the manufacturer's QA. The Packing List is in someone's Excel template. The Customs Declaration is being typed by the customs broker right now. The LC document set is being assembled in a Dropbox folder. None of them know about each other. None of them update the order they belong to. The audit trail of who provided which document when lives in someone's inbox.
FIVE LAYERS, ONE CHECKLIST
EDMA derives the document list from five layers of data on every order: the Incoterm (CIF, FOB, DDP — each requires different shipping documents), the destination country (different customs paperwork per country), the product compliance class (medical CE Cat III pulls test reports a textile shipment doesn't), the client's specific commercial terms (LC drawing terms, particular certificates the buyer requires), and any letter of credit requirements layered on top. The list updates as the order's parameters change.
AUTO-GENERATION FROM ORDER DATA
Commercial Invoice, Packing List, Certificate of Origin, and Customs Declaration are all derivable from data the platform already has — line items, container manifests, lot lineage, declared values, currency conversions, HS codes. EDMA generates them automatically from order data, surfaces them for operator review and signature, and re-generates them when the order changes. Saves typing, eliminates copy-paste errors, and creates a complete audit trail of what was on the document at the moment of issuance.
| Description | HS code | Qty | Unit price | Total |
|---|---|---|---|---|
| Protect-M Nitrile Gloves, Size M | 4015.19.10 | 4,000,000 | $0.070 | $280,000 |
| Protect-M Nitrile Gloves, Size L | 4015.19.10 | 3,000,000 | $0.070 | $210,000 |
| Protect-M Nitrile Gloves, Size XL | 4015.19.10 | 1,000,000 | $0.070 | $70,000 |
AUTO-COLLECTION FROM COUNTERPARTIES
Bill of Lading from the carrier. CE Certificate from the manufacturer. AQL Inspection Report from the third-party inspector. Insurance Certificate from the broker. EDMA monitors counterparty channels — carrier APIs, the supplier portal, the freight forwarder's portal, broker email feeds — and pulls in documents as they're issued. When a document arrives, the platform tags it to the right shipment, runs a basic validity check (right reference number, right vessel, right dates), and notifies the operator. No more chasing.
Auto-collection activity · last 7 days · all orders
All sources ▾Counterparty channels supported include carrier APIs (COSCO, MSC, Maersk, CMA CGM, Hapag-Lloyd), supplier portals, freight forwarder integrations, broker email feeds, and government certificate systems where available.
THE UNIVERSAL STORE
Every document in EDMA — generated, collected, or uploaded — lives in one universal store. Every document has a version history, a chain of custody, and an immutable audit trail. Documents are searchable by content, by reference number, by HS code, by date, by counterparty. When a document is superseded by a newer version, the old version is preserved with a "superseded by" link. The audit trail is read-only; even admins can't edit it.
CE Certificate Cat III · CE-2024-9912
uploaded by Crescent Manufacturing
Metadata
Version history
Used in
+ 8 earlier orders →
Download history · 14 downloads by 6 users in the last 90 days · last accessed 2 hr ago by Sarah Chen.
TEMPLATES AND SIGNATURES
Generated documents pull from per-tenant templates: your company letterhead, your bank details for invoices, your standard terms and conditions, your authorized signatories. Configure once, applied automatically. Signatures are embedded — upload a signature image, and the platform applies it to the right field on the right document with a date stamp and an audit trail entry. Multiple signatories can be configured per role (commercial signatures from sales, compliance signatures from QA).
Document templates · EDMA Group LLC
Per-tenant defaults applied to all generated documents
Templates are versioned. Changes apply to new documents only; existing documents preserve the template version they were generated with.
Authorized signatories
Configure who signs which document type
COMPLIANCE AND EXPIRY
Every certificate in the platform has an expiry date — CE certificates renew every 1-5 years, ISO certifications every 3, FDA registrations annually. EDMA tracks expiry dates per certificate, surfaces 90-day and 30-day warnings, and prevents shipments where the underlying certificate would expire mid-transit. Compliance is one less thing falling through.
Compliance overview · all manufacturers, all certificates
47
active certificates
3
expiring within 90 days
0
expired
0
shipments blocked
Renewal reminders sent automatically at 90 and 30 days. Operators can request renewal directly from the platform — sends a structured request to the manufacturer's QA contact and tracks the response.
ONE MISSING DOCUMENT, FIVE EFFECTS
When a required document is missing or invalid, the impact ripples through the order. The shipment can't clear customs at destination. The buyer can't draw on the letter of credit. The order's expected delivery shifts. Demurrage forecasts kick in. The customs broker's slot is wasted. EDMA traces the chain so the operator sees the consequence before it lands.
Five sections of the platform respond to one event. The operator sees the impact before it materializes — and a [Generate now] button on the missing document is one click away.
VS. THE TOOLS YOU MIGHT BE USING
| Capability | Google Drive | DocuSign | CargoWise | TradeOS |
|---|---|---|---|---|
| Auto-generate documents from order data | — | — | partial | ✓ |
| 5-layer requirements engine (per order) | — | — | — | ✓ |
| Auto-collect from carriers + suppliers | — | — | partial | ✓ |
| Embedded signature flow | — | ✓ | partial | ✓ |
| Per-tenant templates and letterhead | manual | partial | ✓ | ✓ |
| Certificate expiry tracking + alerts | — | — | partial | ✓ |
| Cascade into order, shipment, finance | — | — | — | ✓ |
Generic file storage holds files. eSignature platforms sign them. Forwarder document systems handle freight paperwork. None of them know which documents your order needs, where to get them, or what happens when one is missing. EDMA does.
FREQUENTLY ASKED
Commercial Invoice, Proforma Invoice, Packing List, Certificate of Origin, Customs Declaration (per destination country), and the LC Document Set assembly. New types can be added per tenant — operators with custom commercial documents (debit notes, freight invoices, broker invoices) can configure templates and have them auto-populate.
Book a 30-min demo and we'll set up your templates, your signatories, and walk through a real order's document collection from confirmation to closure.