Bills of lading, commercial invoices, packing lists, customs filings, certificates of origin, freight invoices — auto-organized by shipment, version-controlled, and downloadable. No more email attachment archaeology.
Documents arrive from four sources: the supplier (CI, PL, CO), the carrier (BL, AWB, DG declaration), our customs desk (7501, ISF filing, FDA prior notice, FTA cert), and your finance team (PO, payment remittance). Every file is parsed, versioned, tagged with the shipment ID, and placed in the folder it belongs to within minutes of arrival.
Version control is conservative by default. An updated BL or revised CI doesn't overwrite the previous version — it stacks on top, with a diff so your team can see what actually changed (quantity, value, consignee, notify party). Previous versions stay downloadable for the full retention window.
Walk through the document flow →
Every document your shipment might need, mapped to the leg it applies to. Not every shipment uses every document — the folder only surfaces the types that actually exist for that record.
Ocean master BL and house BL, or sea waybill where the shipper has released the cargo without a physical negotiable document. Draft BL circulated for shipper approval before the master is cut; amendments captured as new versions.
Fields parsed on upload: consignee, notify party, vessel/voyage, container numbers, marks, description, weights, measurements.
Master AWB and house AWB, with the flight number and ULD allocation. Pre-alert generated at wheels-up; arrival notice produced at wheels-down. Linked to the FDA prior notice and any DG declaration for the same shipment.
For integrator traffic (FedEx, UPS, DHL Express), tracking numbers and status events replace a formal AWB document.
Shipper's invoice to consignee, the single most audited document in the folder. Line-level parsing picks up quantity, unit value, extended value, HTS code, country of origin, and incoterms. Discrepancies against the PO flagged to your buyer before entry is filed.
Cartons, gross and net weights, dimensions and marks, per line of the CI. Used at customs exam, at deconsol and at warehouse receiving. PL anomalies (over-pack, under-pack, PL value not matching CI) raise an alert before the container hits the port of loading.
Chamber-of-commerce certificate of origin and free-trade-agreement certificates (USMCA, UK-EU, CPTPP, EU-KR, India GSP). Each FTA cert carries the specific rule-of-origin citation our brokerage used to claim the preference — so CBP's questions have answers ready.
The actual entry our licensed broker (or a partner broker) filed with the destination customs authority. CBP form 7501 in the US, SAD across EU customs, ATLAS in Germany, CDS in the UK. Stamped "released" copy returned to the folder once clearance completes.
US importer security filing (10+2), automated manifest system, EU entry summary declaration, Canadian advance commercial information. All filed before loading at origin; confirmation numbers posted back to the folder as soon as the authority issues them.
FDA prior notice for food and drugs, FSVP supplier records, USDA APHIS for plant and animal products, EPA TSCA for regulated chemicals, FWS for wildlife products. PGA message sets filed via ACE in the US with confirmation numbers archived.
IMDG Dangerous Goods Declaration for ocean, IATA DGD for air, with UN numbers, class, packing group, and proper shipping name. Lithium battery variants (UN3480 standalone, UN3481 in equipment / packed with) carry a copy of the most recent battery test summary.
One consolidated invoice per shipment (or per month, if you prefer), breaking out every charge line — ocean, air, local, drayage, customs, accessorials. Every line references the underlying vendor invoice so your AP team can audit back to source without emailing us.
Payments to suppliers out of our trust-account structure, stored against the originating PO and CI. SWIFT references, FX rate used, and settlement batch ID all visible to your finance team. Bank-statement-grade for annual audits.
For retail-distribution shipments: 856 ASN, 810 invoice, 945 warehouse shipment advice, 997 functional acknowledgments. EDI events replay into the shipment folder as human-readable summaries, so your ops team doesn't need to read X12.
Document retention is set by jurisdiction, not by our whim. We retain for the longest applicable window across the shipment's origin, destination and trans-shipment authorities, so your audit trail outlasts any single regulatory cycle.
| US customs records |
Retained 5 years from entry date (19 CFR 163.4). All documents supporting the entry — CI, PL, BL, HTS rationale, FTA cert, exam record — downloadable by your compliance team, CBP-audit-ready. |
|---|---|
| EU & UK customs records |
Retained 10 years (UCC Article 51 / UK Taxation (Cross-border Trade) Act). Covers SAD, CDS, ENS, T1 transit, and proof-of-origin evidence. |
| FDA / USDA / OGA records |
2 years for FDA food records (21 CFR 1.337), longer for FSVP and drug records. Retention window flagged per document type; auto-renewed when a live FDA/USDA hold references the shipment. |
| Freight invoices & payments |
7 years for tax and finance records by default, configurable per tenant. Exportable to CSV, Parquet or direct API pull for your ERP. |
| Role-based access |
Users see only the documents their role entitles them to. Finance sees invoices and remittance, compliance sees customs entries and FTA certs, buyers see POs and CIs. Role templates configurable per tenant; audit log captures every view and download. |
| External share |
Shareable document links with expiry, watermark and single-document scope. For sharing with auditors, retail compliance teams, or factoring providers — without a full portal seat. |
Bring a real shipment to the walkthrough — any recent BL, CI and packing list — and we'll show you the folder structure populated with your own documents. You'll leave the call with a tenant URL you can use the same day.
Book a documents walkthrough →The folder is only useful because every document is tied to the order, the tracking record, and the API. The other three modules close the loop.
POs and line items carry the IDs every document later references.
Live TrackingWhen documents arrive.Every tracking event can be tied to the document that supports it.
API & IntegrationsStream docs out.Pull the folder into your ERP, DMS or compliance system on event.