---
title: LS Wholesale: SPS Commerce EDI and Katana Case Study
url: https://dataautomation.com/case-studies/ls-wholesale/
description: LS Wholesale connected SPS Commerce document flows with Katana, bringing retail purchase orders and their required responses into the operating process.
---

[← All case studies](https://dataautomation.com/case-studies/) LS Wholesale

# Retail EDI connected to the inventory and production workflow.

LS Wholesale connected SPS Commerce document flows with Katana, bringing retail purchase orders and their required responses into the operating process.

EDI integration Document transformation Order mapping Katana integration

**Retail document requirements connected to operations** Implementation outcome

## Client

LS Wholesale

## Engagement

Retail EDI and Katana integration

## Systems and workflows

- SPS Commerce
- [Katana](https://dataautomation.com/katana/)
- Retail trading-partner documents

Retail purchase orders and changes -> Operational order handling -> Acknowledgments, shipment notices and invoices

## 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.

[PreviousClinuvel](https://dataautomation.com/case-studies/clinuvel/) [All case studies](https://dataautomation.com/case-studies/) [NextJSW Media](https://dataautomation.com/case-studies/jsw-media/)

## Audited every year.

Deloitte and Amazon SP-API audits in 2026. PwC and Amazon SP-API in 2025. Shadow AI was involved in 43% of the breaches [IBM studied for its 2026 report](https://www.ibm.com/reports/data-breach); we keep your data out of it. And if something we run goes wrong, we own the fix.

[See the latest AI incidents](https://dataautomation.com/ai-security/) [See our audits](https://dataautomation.com/audits/)

## Bring us the complicated part.

[See what changed for our clients ->](https://dataautomation.com/case-studies/)

[Book a free call](https://meet.dataautomation.com/meet-with-dataautomation) [Describe your setup](https://dataautomation.com/#describe)
