Blog
Field notes on import execution.
Chargebacks, carton trace and the compliance dates that are already here. Written for the teams who carry the fine and the deadline.
The execution gap: visibility reads, execution writes
Every visibility product is a reader. The record it reads is written somewhere else, usually by people. Why the first mile is an execution problem.
Read the postThe portal tax
Every portal you ask a supplier to use is a tax paid in stale data, late bookings and phone calls. The portal is not the problem. The second copy is.
Read the postThe handoff is the product
ERP, WMS and TMS each do their job. The handoffs between them are where the first mile breaks, and no one owns the handoff.
Read the postAn agent you cannot audit is a liability
Agents that act on supply chain records need a ledger before they need autonomy. The audit trail is the feature.
Read the postWhat actually causes a retail import chargeback
Most OTIF fines are ASN timing and data mismatches plus SSCC and label errors. Where those failures start, and why pre-ship validation catches them before the invoice.
Read the postYour 856 is a pure function of your data
An EDI 856 is a deterministic projection of your carton records, not a document you maintain. Why separating generation from transport stops ASN-driven chargebacks.
Read the postThe 2026 compliance deadlines, and where the fields belong
CBAM, UFLPA and EUDR each ask for a field at a specific node. Origin and plot geometry belong at the SKU line, emissions at the leg, and the node is the whole game.
Read the postWhy we integrate with CargoWise instead of replacing it
CargoWise is the forwarder's system of record. Shipeezi is shipper-side execution and compliance. Why the right interface is the boundary, not a fight over the middle.
Read the postOne workspace, many retailer clients
Managed accounts, per-client branding and grant scoping let one LSP team operate a book of retailers without a bespoke instance per client, and graduate a client without a migration.
Read the postMint the SSCC and own the trace
A reader-only system can scan a carton but cannot guarantee what went into it. Owning the GS1 prefix and minting at packing makes the trace structural rather than best-effort.
Read the postGet the next field note.
Tell us which problem is closest to yours and we will point you at the post that covers it, or write it next.