The challenge
Retail trading relationships require a chain of related documents. The incoming purchase order is only the start: acknowledgments, changes, shipment notices and invoices must retain the identifiers and line-level meaning required by the trading partner.
LS Wholesale needed retail trading requirements connected to its Katana workflow. Buyer and vendor item identifiers, case quantities and pack details had to retain their meaning as an incoming purchase order became an operational record.
The implementation
Map the retail document chain
DataAutomation developed client-specific transformations for SPS Commerce data and the corresponding Katana records. The configuration set covers incoming purchase orders and order changes, plus outgoing acknowledgments, shipment notices and invoices.
Preserve item, quantity and reference meaning
The implementation mapped supplier-facing and retailer-facing order data, including differences in SKUs, quantity conventions and field meanings. The transformations preserved the identifiers and line relationships needed to connect one document to the next.
Connect document exchange to operating events
This work positions EDI as part of the operating process: the order enters the production and inventory system, while the required responses are generated from the corresponding business events.
What changed
LS Wholesale gained an integration connecting retail document requirements with operational order handling. The work translated trading-partner data into the records and responses used by the business.
The implementation addressed the details that make EDI operationally useful: item identifiers, quantity conventions, line references and document relationships. Those meanings were mapped into the integration rather than left for staff to interpret from incoming files.
The scope of the engagement
Retail integration across a trading network, document standards and the business platform used to fulfill orders.
Business outcomes and timelines reported by DataAutomation.