Back to All Case Studies
e-commerceFull Access Unlocked

Customs Paperwork That Files Itself, in 31 Countries

Every cross-border order needs the right customs form, the right Incoterm and the right return route — and the rules differ per destination. We built the system that decides all three and files the paperwork before the parcel moves.

Cross-border DTC operator · EU, UK, Switzerland, US, Canada

e-commerce
31
countries
auto
customs Forms
2
return Routes

!The Need

Selling physical goods from Europe into the US, Canada, the UK and Switzerland means every order leaves the single market and meets a different rulebook. A US shipment may need an FDA form; anything crossing a customs border needs a proforma invoice with HS codes, country of origin, declared values and an EORI number; the Incoterm decides who pays the duty and gets it wrong at the customer's expense. Returns split the same way — the European carrier network cannot handle a US return, which runs through a third-party warehouse on a different process entirely. Done by hand this is a per-order research task, and the failure mode is not a bad form but a parcel held at the border with a customer waiting.

The Approach

We built an order management system where destination drives every downstream decision. On order creation the system derives the Incoterm (DDP, DAP or DDU) from the destination, generates the proforma invoice with HS codes, origin and declared values, and produces an FDA 2877 for US shipments that require one — then submits the customs documents to the carrier's paperless trade API automatically when the carrier supports it, rather than attaching PDFs by hand. Shipping labels are created through a multi-carrier aggregator, with carrier detection deciding which orders qualify for paperless processing. Returns are routed by the order's own country: European, UK, Swiss, Norwegian and Canadian returns get a label immediately, while US returns go to a third-party logistics provider on an asynchronous, admin-approved path that is created without a label and must be polled before the customer is told anything. Every state change writes to an activity log, so a disputed shipment can be reconstructed after the fact.

Technologies Used

Next.jsSupabaseStripepdf-libCarrier paperless-trade APIsMulti-carrier label aggregator

The Output

Incoterm selected automatically per destination across the EU 27, the UK, Switzerland, the US and Canada
Proforma invoices generated with HS codes, country of origin, declared values and EORI number
FDA 2877 produced and attached automatically for the US shipments that require it
Customs documents submitted straight to the carrier's paperless trade API, with carrier detection deciding eligibility
Shipping labels and tracking through one multi-carrier integration rather than per-carrier portals
Returns routed by country — immediate labels for Europe, UK, Switzerland, Norway and Canada; an asynchronous approved path via a third-party warehouse for the US
A full activity log on every order, so a disputed shipment can be reconstructed

The Impact

Customs paperwork stopped being a per-order research task and became a property of the destination
The two failure modes that cost most — wrong Incoterm billing duty to the customer, missing FDA form holding a parcel — are now decided by code rather than recall
US returns can no longer be promised to a customer before the third-party warehouse has approved them, because the flow refuses to produce a label that does not exist
One operator can run shipping across 31 countries without knowing each country's rules by heart
Disputed shipments are answerable from the activity log instead of from memory

Ready to achieve similar results?

Contact Us
Supalabs AI solutions