EDI in Plain Terms
EDI replaces the paper and email version of doing business — purchase orders, invoices, shipping notices — with a structured, standardized digital exchange between two companies' systems. No faxing, no PDFs, no manual re-typing of order details into a spreadsheet. Once a retailer and a supplier are exchanging documents this way on an ongoing basis, they're considered trading partners.
Why Scheels Requires It
Scheels operates roughly 30 stores across more than a dozen states, and each location carries an enormous number of active SKUs — reportedly over two million per store. Thousands of vendors feed that assortment. Historically, Scheels managed much of that volume through phone and fax orders, but that approach couldn't keep pace as the vendor base grew. Moving to EDI gave Scheels:
- Faster, more accurate order processing without manual data entry
- Real-time visibility into what's shipping and when
- Fewer receiving errors, since a good ASN and label combination lets cartons scan straight into inventory
- A more reliable foundation for scaling vendor relationships without scaling headcount
How Scheels and Its Suppliers Connect
Unlike retailers that require a direct AS2 handshake with every vendor, Scheels runs its EDI program largely through established Value Added Networks (VANs) — most notably SPS Commerce and TrueCommerce, which together handle a large share of Scheels' vendor connections. That means most suppliers aren't standing up their own AS2 server from scratch; they're connecting through a VAN that already has a mapped relationship with Scheels, or working with an EDI provider that manages that connection on their behalf. Direct AS2 or SFTP connections are also supported for suppliers who prefer to manage their own infrastructure.
Which EDI Standard Does Scheels Use?
Scheels transacts on ANSI X12, primarily on the 4010 version of the standard. As with most retail EDI programs, the underlying goal isn't the format itself — it's making sure your internal order and shipment data maps cleanly into that structure so nothing gets lost or misread on either end.
The Two Building Blocks: Translation and Transmission
Every EDI document you send or receive with Scheels comes down to two steps. Translation converts your internal purchase order, invoice, or shipment data — whatever your ERP, WMS, or accounting system produces — into the X12 format Scheels' systems expect. Transmission then delivers that translated document through your VAN or direct connection, with confirmation that it arrived intact. Get either step wrong — a bad map or a dropped connection — and orders, ASNs, or invoices simply don't make it through.
Step-by-Step: Becoming an EDI-Ready Scheels Supplier
- Confirm you're EDI-capable. You'll need the ability to generate, send, and receive core documents automatically — no manual workaround once you're live.
- Choose your connection method. Most suppliers connect through a VAN like SPS Commerce or TrueCommerce rather than building a direct AS2 link; either path works, but the VAN route is typically faster to stand up.
- Get your trading partner setup started. Your EDI provider or VAN will coordinate the technical setup — connection details, qualifiers, and IDs — directly with Scheels.
- Confirm your items are set up correctly. As with most retailers, you can't validate order and invoice transactions without active, correctly identified product data behind them.
- Complete compliance testing. Scheels requires vendors to pass testing before go-live, typically run through the SPS Commerce portal (or coordinated by your VAN of choice if they're handling testing for you).
- Acknowledge every purchase order. Once live, functional acknowledgments (997s) need to go out promptly after each 850 is received — leaving orders unacknowledged risks delays and compliance issues.
The EDI Documents You'll Actually Use
The exact document set can vary by vendor program, but suppliers working with Scheels should expect to handle:
- 850 — Purchase Order: the order itself, sent from Scheels to you
- 855 — Purchase Order Acknowledgment: your confirmation of receipt, acceptance, or changes
- 856 — Advance Ship Notice (ASN): shipment contents and carton-level detail, tied directly to your shipping labels
- 860 — Purchase Order Change: modifications to a previously issued order
- 810 — Invoice: your request for payment, which needs to reconcile cleanly against the PO and ASN
- 812 — Credit/Debit Adjustment: used for chargeback and adjustment activity
- 997 — Functional Acknowledgment: confirms a transmission was received and readable
Labeling: Where Most Chargebacks Start
The 856 doesn't stand alone — it has to match the physical shipment exactly. Scheels requires GS1-128 (formerly UCC-128) shipping labels with a unique SSCC-18 code on every carton, and that code has to align precisely with what's transmitted in the ASN. A mismatch between the label and the ASN data — or a label that simply won't scan — is one of the fastest ways to trigger a rejected shipment or a chargeback. Clean, correctly placed UPC barcodes and proper pallet configuration matter just as much; Scheels' receiving process is built around scanning cartons straight into inventory, so anything that breaks that flow creates friction on both sides.
Choosing the Right EDI Approach
Whether you connect through SPS Commerce, TrueCommerce, or another EDI provider, the job is the same: reliably translate your internal data into compliant X12 documents going out, and back into your own systems coming in. Given how central the VAN relationship is to Scheels' vendor network, working with a partner who already understands Scheels' specific setup — qualifiers, testing process, label requirements — tends to save suppliers a meaningful amount of onboarding time.
How SBSA Technology Can Help
Getting your document mapping and label compliance right on the first pass isn't automatic, and mistakes here cost you time during onboarding or, worse, delays getting paid once you're live. SBSA Technology helps suppliers plan and validate their Scheels EDI setup — from connection through compliance testing — so you're not troubleshooting label and ASN mismatches after you're already shipping.
Frequently Asked Questions
Does Scheels require EDI from every supplier? The large majority of Scheels' vendor base now transacts via EDI, and it's the expected standard for any ongoing supplier relationship of meaningful volume.
Which EDI documents matter most? The 850, 855, 856, 810, and 997 form the core of the relationship, with the 860 and 812 used as needed.
Do I need to build a direct AS2 connection? Not necessarily. Most Scheels suppliers connect through a VAN such as SPS Commerce or TrueCommerce rather than standing up their own AS2 infrastructure.
What causes the most compliance issues? Label and ASN mismatches — incorrect SSCC-18 codes, labels that won't scan, or shipment data that doesn't match what's on the carton — are the most common source of chargebacks.
Conclusion
Scheels' EDI program reflects the same operational discipline as any national retailer, even with its smaller, family-run footprint. Get your connection, document mapping, and label compliance right before you go live, and the day-to-day flow of orders, shipments, and invoices runs largely on its own. Skip a step, and you'll be chasing chargebacks and delayed payments instead of shipping product.
Connect with SBSA Technology
Ready to get compliant with Scheels — or want a second opinion on your current EDI setup? SBSA Technology works with retail suppliers, distributors, e-commerce brands, and 3PL providers to automate EDI, order processing, and retailer compliance.
- Book a demo: sbsatech.com/consultancy
- Talk to the team: sbsatech.com/contact
- Explore the platform: sbsatech.com
- More insights: sbsatech.com/blog