Sign In
Book a Demo

DSW Designer Shoe Warehouse EDI Integration

Footwear and accessory suppliers to DSW run store purchase orders, dsw.com drop-ship orders, and the ship notices DSW checks against each order inside the same order operations as their other channels.
Book a demo
DSW Pipe17 Connector Icon

The Challenge of Designer Footwear EDI

Rewards Complexity and Omnichannel Demands

Stacked user icons, representing sub-accounts or team access

Two Programs, One Supply

DSW orders bulk for its stores and also runs dsw.com drop ship. Supplying both from separate stock counts invites oversells on one side and idle inventory on the other.

Icon of 3 stacked files next to 4 stacked database

Tight Vendor Specifications

DSW expects acknowledgments, ship notices, and labels to follow its vendor specifications, and drop-ship orders to ship within a day. Missing either standard can mean chargebacks.

Two-tone icon showing disconnected channels with broken link symbols and overlapping rectangles.

Omnichannel Size Availability

Shoppers expect their size online and in store. When size-level inventory is counted separately for each channel, the size a customer wants shows in stock after it has sold.

The Solution for DSW EDI Integration & Order Management

DSW Writes the Vendor Guide. Pipe17 Ships to It.

DSW trades store orders over EDI and drop ship through DSCO. Pipe17 can run both connections, or an existing provider can keep the EDI side. The gap is the legacy OMS and custom builds picking a warehouse per PO. Pipe17’s Order Operations Platform covers both, on one stock count.
iPaaS & Custom Builds Legacy OMS Pipe17
Native API-First Connectivity ✅ ❌ ✅
Pre-Built Commerce Connectors ❌ ❌ ✅
Custom Integration Mappings ✅ ❌ ✅
Advanced Order Orchestration ❌ ✅ ✅
Exception Management & Alerts ❌ ❌ ✅
Unified Inventory Management ❌ ✅ ✅
Rapid to Implement & Go-Live ❌ ❌ ✅
Easy to Add / Swap Channels & Flows ❌ ❌ ✅
Low Total Cost of Ownership (TCO) ❌ ❌ ✅

Leading Brands and Fulfillment Providers are Powered By Pipe17

Olly logo horizontal black svg
Follett Higher Education logo horizontal svg black
Mary Ruths horizontal svg logo black
CGK Linens Horizontal SVG Logo
Ryder horizontal svg black logo
AS Beauty logo horizontal svg black
Dude Wipes horizontal logo black svg
FedEx horizontal svg logo black
Wyze horizontal svg logo black
Melin horizontal svg logo black
Barrett Distribution Centers horizontal svg logo
Sacheu Beauty horizontal svg logo black
Made In Cookware horizontal svg logo black
Azalea Wang logo horizontal black svg
Radial fulfillment horizontal svg logo black
Black Rifle Coffee Company logo horizontal black svg

Elevate Your DSW Partnership with Pipe17

Supply DSW stores and dsw.com drop ship from one operation. Size-level inventory, routing, and order records are shared with your other channels, and each DSW order draws on stock you have.
Decision tree of rectangle boxes representing rules-based automation

Bulk and Drop Ship Together

DSW's bulk EDI orders and its drop-ship orders through DSCO arrive as orders in the same platform, each on its own connection and sharing one inventory pool.

Odometer turned up all the way over webpage representing immediate speed

Built to DSW Specifications

Documents are mapped to DSW's vendor specifications and tested through DSW's approval, and Pipe17 flags an order that risks missing its ship window.

Two-tone icon of a computer dashboard with charts controls and gears symbolizing visibility and system control.

Omnichannel Size Intelligence

Keep size-level availability current across stores, dsw.com, and your own storefront. The inventory DSW sees reflects every pair you can ship.

Automated DSW EDI Flows

DSW runs two supplier programs: bulk orders for its stores and distribution centers, traded as X12 EDI over its VAN, and dsw.com drop ship, which runs through DSCO. Pipe17 reaches the first through managed EDI and the second through its CommerceHub DSCO integration, as two separate connections.
  • Pull Orders from DSW. DSW transmits bulk purchase orders (850) in X12 version 4010, and only after your UPCs load from your online product catalog. Pipe17 creates an order from each one for your team to route, beside the drop-ship orders arriving from DSCO.
  • Push Order Confirmations to DSW. DSW’s bulk guide lists the purchase order acknowledgment (855) as a transaction set planned for later. Today vendors confirm receipt with a 997. Pipe17 can return an 855 with line-level accept, reject, or partial accept if a DSW program asks for one.
  • Push Fulfillments to DSW. DSW wants each advance ship notice (856) 48 hours before delivery, one per shipment and ship-from location, with the UPC and vendor style from the purchase order. Pipe17 assembles it from the shipment your warehouse or 3PL confirms.
  • Push Inventory to DSW. DSW refreshes dsw.com drop-ship availability once a day from its inventory feed and holds back 8 units per UPC as safety stock. Pipe17 sends that daily count through its DSCO connection over the API, not as an X12 846.
  • Push Invoices to DSW. DSW’s bulk program does not take the EDI invoice (810) yet. Bulk vendors bill through the Tungsten Network, and Pipe17’s DSCO connection carries no invoices. Pipe17 sends an 810 only where a DSW program takes EDI invoices.
  • Answer DSW With a 997. DSW asks for a functional acknowledgment (997) on each purchase order and change within 72 business hours. Pipe17 returns it automatically.
  • Take In DSW Order Changes. DSW sends each 860 as a full replacement of the purchase order. Pipe17 receives it and sends back a 997 to acknowledge it.
  • Carton Labels for DSW Receiving. Your warehouse or 3PL applies GS1-128 (UCC-128) labels from data Pipe17 serves through its API, scoped to the DSW program.
  • Send Each PO to One Ship Point. DSW receives a purchase order from a single location. Pipe17 routes the whole order to one warehouse or 3PL of your choosing.
  • Post DSW Orders to Your ERP. Each DSW purchase order can become a NetSuite sales order, or post to another connected ERP.
  • Work With a 3PL Over EDI. Pipe17 sends the warehouse shipping order (940) to a 3PL and takes back its shipping advice (945).
  • Surface DSW Exceptions. The Automation Engine brings orders that need attention, such as a line you cannot fill, to the person who owns the DSW account.

Connect DSW EDI to Your Designer Footwear Business

DSW is usually one account among many for a footwear brand. Pipe17 puts its purchase orders beside your storefront, marketplace, and wholesale orders, drawing on the same inventory and the same warehouses.

Work Toward DSW's ASN Window From the Same Order Flow

Bring your DSW vendor guide to the conversation. We will walk through how its purchase orders, ship notices, and drop-ship inventory feed would run on Pipe17 next to the channels you sell through today.
Book a demo

is better with

Pipe17 horizontal svg logo black

DSW Designer Shoe Warehouse EDI Integration FAQs

DSW bulk trades the purchase order (850), purchase order change (860), advance ship notice (856), and functional acknowledgment (997) in X12 4010 (see the DSW vendor EDI page). The required UPC catalog (832) is outside Pipe17's document set. Drop ship adds the invoice (810) and inventory advice (846). Pipe17 covers its core X12 set.

DSW needs the advance ship notice (856) 48 hours before goods arrive, and a late one risks a chargeback. Each ASN covers one shipment from one location and repeats the purchase order (850) UPC and style data. The advance shipping notice guide explains the document, and Pipe17's EDI order flow shows where it fits.

DSW's EDI requirements list chargeback triggers: a purchase order (850) or change (860) without a 997 inside 72 business hours, and an advance ship notice (856) that is late or does not match its order. The DSW vendor compliance documents hold the full policy. Pipe17's Order Operations Platform runs those orders alongside every other channel.

Yes, DSW's EDI FAQ says its compliance manager approves carton labels before production EDI. Your warehouse or 3PL prints each GS1-128 (UCC-128) label from data Pipe17 serves by API, scoped per DSW program. How Pipe17 handles GS1-128 label data covers requests, and DSW posts its ticketing and labeling requirements online.

The dsw.com drop-ship program runs through DSCO. Pipe17 connects via its CommerceHub DSCO integration, separate from DSW's bulk EDI. DSW asks for a daily inventory advice (846) and shipment within 24 hours, and holds back 8 units per UPC, so counts under 9 stay hidden online. Those orders draw on the same inventory as your online store, whether it runs on Shopify or another platform.

Yes, each DSW purchase order (850) can post to NetSuite as a sales order, and Acumatica works the same way. The EDI for your ERP section covers the general pattern. DSW bulk billing runs through the Tungsten Network rather than an EDI invoice (810), which finance handles outside EDI.

DSW asks vendors to report a new EDI ID or VAN and update its partnership with IBM Sterling, DSW's VAN, or risk a chargeback. Pipe17 handles setup, mapping to DSW's specifications, and testing through DSW's approval, as the EDI onboarding answer describes. If another EDI provider already serves DSW for you, that connection can stay, with Pipe17 working alongside your provider.

Pipe17's managed EDI comes with the Order Operations Platform. It suits a footwear or accessory brand that sells to DSW alongside its own site, marketplaces, or other wholesale accounts. If trading documents with DSW is the whole job, start with Pipe17's supplier fit notes for managed EDI.