Integrations and data
Field notes on ERP versus WMS data ownership, carrier API changes, EDI 856 ship notice structure, EDI 214 versus APIs and item master data.
Scope a project
Most logistics software problems that look like bugs are integration problems: two systems that each believe they own a number, a ship notice that describes a different pallet from the one on the truck, a carrier interface that changed under you. The notes in this section deal with data ownership, message structure and the master data that every interface depends on.
Where to start
- The featured note, ERP or WMS: which system should own each inventory number?, assigns ownership field by field and explains how the two systems should exchange changes.
- UPS, FedEx and USPS API changes your integrations must handle covers authentication and interface changes that break shipping integrations.
- EDI 856 ship notices explains how to choose a hierarchy that matches the freight and what receivers check.
- EDI 214 or carrier APIs for shipment status compares status sources and how to normalize them into one set of milestones.
- Item master data to fix before go-live lists the dimensions, weights and unit conversions that integrations and labels rely on.
Tools for this section
List every interface with its trigger, method, volume and owner in the integration inventory worksheet, and check parcel and freight cost inputs with the dimensional weight and freight density calculators.
When you need the interfaces built, tested with trading partners and monitored, see ERP and WMS integration.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.