Customs and regulatory compliance
The compliance record, emitted from the layer that wrote it.
Shipeezi turns customs and regulatory obligations into data captured once at execution: pre-ship ASN validation, HS and origin at the line, emissions at the leg, and a title chain for the document.
Vendor compliance and ASN
Kill the chargeback before the container sails.
Retail import chargebacks and OTIF penalties run a few percent of revenue, and most OTIF fines are really ASN timing or data mismatches and SSCC or label errors. Shipeezi can run the checks that decide them pre-ship, because it mints the SSCC and sees the SKUs inside it.
Pre-ship validation as rules, not a form builder
The retailer's routing guide is loaded as data: ASN lead time, label spec, required identifiers and tolerance. Each check is a predicate over the booking, its cartons and its lines, and each finding carries a code, a message and the field it concerns.
- Every carton's SSCC is well formed and check-digit valid
- Packed quantity per line matches the PO within tolerance
- Every packed line resolves to a GTIN
- The ASN would land inside the retailer's window
- SCAC is present on the shipment
- The SSCC on the label equals the SSCC on the record
The 856 is a pure function of the data
An 856 is hierarchical: shipment, order, tare, pack, item. Shipeezi builds it from the leg spine and the carton tree, so its correctness is testable without any EDI transport. Sending it is an integration; generating it correctly is the product. EDI over AS2 sits alongside API, SFTP and email as a first-class channel.
EDI transport and the first retailer are onboarding decisions, not product gaps. The generated document works from day one.
Compliance as data
A fact attaches to the narrowest node that can answer it.
Origin is a property of goods, so it lives at the SKU line. Emissions are a property of movement, so they live at the leg. Title is a property of the document, so it has its own append-only chain. Shipeezi emits the compliance record from the execution layer that wrote it.
Customs and duty
HS code per line, overridable per destination because the same SKU can classify differently, with an attributed source and a confidence score.
CBAM
Goods category and embedded emissions at the leg, distinct from transport CO2e, reported per import.
UFLPA
Pre-import due diligence: supplier declarations, mill or farm identifiers, certificate references, held against the line.
EUDR
Geolocation-to-plot and the Due Diligence Statement reference for in-scope commodities, from December 2026.
CO2e per leg
GLEC and ISO 14083 factors by mode, carrying the method and the factor version so a number can be reproduced.
eBL title chain
An append-only sequence of transfers, not a status column, so electronic bill of lading issuance is additive when a customer forces it.
Emit, do not retrofit
The dates are already here.Store the fields at the nodes that write them.
CBAM is in force, UFLPA asks for pre-import due diligence, EUDR applies in December 2026, and DCSA carriers are committed to electronic bills of lading. Modelling the fields before intake goes live is one migration; doing it after is a backfill against real retailer data.
Documents
Generate the paperwork from the same record.
Commercial invoice and packing list
Built from the PO lines and carton contents, with HS codes and origins already on the record.
Customs and trade forms
A template to filled-PDF engine, retargeted from the same pattern that already shipped a customs form.
ASN and labels
The 856 and the GS1 SSCC labels, minted and printed by the label authority itself.
Map your routing guide.
Bring a retailer's guide and we will show you the pre-ship checks running against it.