Integrations
Carriers, forwarders, ERP and retail, on one spine.
Shipeezi connects to the systems already in the chain through one adapter model, and normalises everything onto a canonical event spine. No bespoke integration is a domain change.
One adapter model
Retailer onboarding is a config, not a deploy.
Every external system lands on the same canonical event spine. Mapping happens at the adapter boundary, so a carrier integration or a retailer feed never reaches into the domain model.
API
Client credentials map to a tenant. Clean request and response shapes for retailers and LSPs that can push.
SFTP
Scheduled file drops for retailers running on overnight batches, parsed and mapped per tenant.
EDI over AS2
850, 855, 856 and 810 as a first-class channel, alongside API, for the big retailers. AS2 certificates and receipts are onboarding, not a separate product.
Email intake
A sender allowlist, a schedule and a per-tenant parser map an inbox into POs, replacing hardcoded filename routing.
Upload
A manual path for the long tail, with the same validation the automated channels get.
Webhooks and public API
A DCSA-shaped public track-and-trace surface so a customer's other systems plug in without a rip-and-replace.
Carriers and forwarders
Track by whatever reference the carrier accepts.
A carrier catalog carries each carrier's SCAC, its type, and the references it can be tracked on: booking reference, bill of lading, or container number. That metadata is what decides how a tracking query is issued.
Ocean
Ocean transport adopts the DCSA track-and-trace taxonomy and reference data: UN/LOCODE locations, IMO vessel numbers, ISO 6346 container numbers and SMDG facility codes. First-class carrier support and DCSA alignment are the same work.
Forwarder and air
Self-serve air freight runs from the same front door: quote, book, document and track, with CargoWise as the ops backend. Status flows back onto the same event spine, so an air leg looks like any other leg.
Interoperability as a wedge
The opposite of a lock-in platform.Plug in without a rip-and-replace.
A carrier or ERP integration should be a config, not an architecture negotiation. Retailers, suppliers, CFS operators and LSPs all connect to the same canonical spine.
Retail and ERP
The retailer's system of record stays the system of record.
Inbound POs
API, SFTP, EDI 850 or email intake, mapped once per trading relationship.
Outbound events
856, 810 and webhook events for the retailer's ERP, with the SSCC that was minted here.
CRM and onboarding
A CRM company with the required fields complete provisions a tenant, so the retailer or LSP onboarding funnel is ready-made.
Map your integrations.
Tell us the carriers, forwarders and retailer systems you run, and we will show you the adapter shape.