DSW (formerly Shoes.com) EDI
across every channel.
Stacksync wires the full DSW (formerly Shoes.com) trading-partner footprint, DSW (formerly Shoes.com) (Dropship) (via DSCO (dba Rithum)), into your ERP, WMS, or warehouse from one workspace.
Adopted by fast-scaling companies moving mission-critical data in real time
Document catalog
EDI documents we support for DSW (formerly Shoes.com)
5 transactions across 1 channel.
Document flow
How EDI documents flow with DSW (formerly Shoes.com)
Where each document sits in its trading cycle, based on the 5 document types DSW (formerly Shoes.com) trades across 1 channel.
Order-to-cash
Partial cycle- 850 Purchase Order
- 855 Purchase Order Acknowledgment not required by DSW (formerly Shoes.com)
- 856 Ship Notice Manifest
- 810 Invoice
Catalog & inventory
Partial cycle- 832 Price / Sales Catalog not required by DSW (formerly Shoes.com)
- 846 Inventory Inquiry Advice
- 852 Product Activity Data not required by DSW (formerly Shoes.com)
Network context
DSW (formerly Shoes.com) trades through Rithum
EDI traffic with DSW (formerly Shoes.com) is routed over this network. Stacksync maintains certified connections to each, so one integration covers every partner reachable on them.
Rithum
25 channels · 23 trading partners on Stacksync
Rithum, the network formerly known as CommerceHub, is a commerce platform large retailers use to run dropship and marketplace programs; supplier connectivity runs on its Dsco and OrderStream platforms. Retailers that mandate the network have suppliers exchange orders, shipments, invoices, and inventory data, carried as EDI 850, 856, 810, and 846 or as XML, JSON, or delimited files over the same connections.
DSW (formerly Shoes.com) channel on this network: DSW (formerly Shoes.com) (Dropship) (via DSCO (dba Rithum))
- 850 25 ch
- 856 25 ch
- 846 24 ch
- 810 20 ch
- 870 10 ch
How it works
Three steps to live DSW (formerly Shoes.com) EDI.
Stacksync handles the complexity of DSW (formerly Shoes.com) EDI so your team doesn't have to. Connect your ERP, WMS, or database through a simple API, we translate, validate, and deliver every transaction automatically.
- 01
Connect your systems
Plug Stacksync into your ERP, WMS, or database with a no-code connector. We handle authentication, schema discovery, and field mapping.
- 02
Map to DSW (formerly Shoes.com) guidelines
We ship pre-built mappings for every DSW (formerly Shoes.com) document type. Override any field, add custom validation, or extend with custom code.
- 03
Send & receive in real time
Stacksync translates, validates, and delivers every transaction over AS2, SFTP, or API. Watch every document flow live in the dashboard.
Why Stacksync
Built for EDI suppliers, not enterprise legacy.
From pre-built DSW (formerly Shoes.com) mappings to real-time compliance checks, Stacksync removes the friction from EDI, so you can focus on growing your business.
-
Pre-built mappings
Stacksync ships native mappings for every DSW (formerly Shoes.com) document type. No more 6-week field-mapping projects.
-
Real-time monitoring
Every transaction shows up in the dashboard the second it lands, with retry, revert, and replay built in.
-
No vendor lock-in
Your data lives in your ERP/WMS/database. Stacksync is the translation layer, not the system of record.
-
Days, not months
Most DSW (formerly Shoes.com) suppliers go live in under a week. We migrate from SPS Commerce, TrueCommerce, Cleo and IBM Sterling.
Still with a legacy EDI vendor? We cover the buyout.
Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.
Check your eligibility for the EDI migration fundSecurity teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Trading partners
5,000+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
FAQ
DSW (formerly Shoes.com) EDI questions
How long does it take to set up DSW (formerly Shoes.com) EDI with Stacksync?
Most suppliers are fully connected and processing live DSW (formerly Shoes.com) EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.
What is DSW (formerly Shoes.com) EDI?
DSW (formerly Shoes.com) accepts EDI for 5 document types across 1 channel. Trading partners use EDI to exchange purchase orders, invoices, shipping notices, and acknowledgements with DSW (formerly Shoes.com) programmatically, Stacksync handles the entire EDI exchange, validation, and translation into your ERP, WMS, or database.
Which EDI standards does DSW (formerly Shoes.com) use?
DSW (formerly Shoes.com) uses X12. Stacksync supports both X12 (the dominant North American standard) and EDIFACT (the dominant European and global shipping standard) for every connected trading partner. Channel-specific implementation guidelines from DSW (formerly Shoes.com) are pre-built into the Stacksync connector and validated on every outbound transaction.
Which transaction codes does DSW (formerly Shoes.com) support?
DSW (formerly Shoes.com) supports 5 transaction codes in total. The most common include: 850, 856, 810, 846, 870. Each code is mapped to its business-record equivalent (purchase order, ASN, invoice, etc.) inside Stacksync, so EDI exchanges land directly in your ERP or warehouse without manual translation.
How long does DSW (formerly Shoes.com) EDI integration take with Stacksync?
Most DSW (formerly Shoes.com) EDI integrations go live in 3 to 10 business days. The Stacksync team handles partner enrolment, channel certification, transaction-set mapping per DSW (formerly Shoes.com)'s implementation guide, and end-to-end testing. Complex multi-channel deployments or custom transaction sets take 2 to 4 weeks. Cutover is zero-downtime and parallel-run validated.