Skip to content

Staples Inc. EDI
integration guide.

Plan your Staples Inc. EDI integration using 9 listed document types across 2 channels. Compare channels, map business records and test the operational handoff.

Book an EDI demo Explore EDI documents
Listed documents
9
Partner document references
Listed channels
2
Staples US (via Rithum) → Staples
Implementation
Plan
Map, validate and reconcile

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Implementation guide

Staples Inc.: EDI implementation plan

Build a reliable EDI workflow for Staples Inc.. Use 9 document types across 2 channels to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 860 Purchase Order Change Request Buyer InitiatedListed on 1 channel: Staples US (via Rithum) buyer order-change request

original purchase order, change revision and affected line
  • Apply a quantity reduction to the existing order instead of creating another order.
  • Test a cancellation arriving after allocation or shipment and route it to an exception owner.
X12 850 Purchase OrderListed on 1 channel: Staples US (via Rithum) purchase order or sales order

buyer purchase order, order line and trading-party identifiers
  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.
X12 855 Purchase Order AcknowledgmentListed on 1 channel: Staples US (via Rithum) purchase-order response

original purchase order, response revision and order line
  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 846 Inventory Inquiry AdviceListed on 1 channel: Staples US (via Rithum) inventory availability record

item, location, quantity type and snapshot time
  • Distinguish on-hand, available and reserved quantities before publishing availability.
  • Deliver an old snapshot after a new one and prevent stale stock from replacing current values.
X12 856 Ship Notice ManifestListed on 1 channel: Staples US (via Rithum) shipment notice (ASN)

shipment, order, package and item references
  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.
X12 990 Response To A Load TenderListed on 1 channel: Staples load-tender response

original load reference, carrier and response
  • Associate acceptance with the correct version of the load tender.
  • Test a declined tender and ensure it returns to dispatch for reassignment.
X12 204 Motor Carrier Load TenderListed on 1 channel: Staples load tender

load reference, pickup and delivery stop identifiers
  • Send an amended pickup appointment and retain the previous tender decision.
  • Test a multi-stop load whose stop sequence differs from address sorting.
X12 214 Transportation Carrier Shipment Status MessageListed on 1 channel: Staples shipment status event

shipment reference, event code, event time and location
  • Deliver an older status after a newer one and retain event history without moving the current status backward.
  • Send one milestone twice and avoid duplicate customer notifications.
X12 210 Motor Carrier Freight Details And InvoiceListed on 1 channel: Staples freight invoice

carrier invoice, shipment reference and charge line
  • Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate.
  • Test a second invoice for the same shipment and distinguish a revision from a duplicate.

Implementation steps

  1. Choose the trading account and channel

    Choose among Staples US (via Rithum), Staples. Confirm the business unit and account before copying a mapping from another channel.

  2. Map records and assign owners

    Start with buyer order-change request, purchase order or sales order, purchase-order response. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Staples Inc. production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using original purchase order, change revision and affected line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for Staples Inc.

9 transactions across 2 channels.

Document flow

Example document relationships for Staples Inc.

Where each document sits in its trading cycle, based on the 9 document types listed for Staples Inc. across 2 channels. These are example relationships; the trading agreement determines the required sequence.

Catalog & inventory

Some example steps listed
  1. 832 Price / Sales Catalog not listed for Staples Inc.
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not listed for Staples Inc.
  • 204 Motor Carrier Load Tender — is listed on 1 of Staples Inc.'s 2 channels
  • 210 Motor Carrier Freight Details And Invoice — is listed on 1 of Staples Inc.'s 2 channels
  • 214 Transportation Carrier Shipment Status Message — is listed on 1 of Staples Inc.'s 2 channels
  • 846 Inventory Inquiry Advice — is listed on 1 of Staples Inc.'s 2 channels
  • 850 Purchase Order — is listed on 1 of Staples Inc.'s 2 channels
  • 855 Purchase Order Acknowledgment — is listed on 1 of Staples Inc.'s 2 channels
  • 856 Ship Notice Manifest — is listed on 1 of Staples Inc.'s 2 channels
  • 860 Purchase Order Change Request Buyer Initiated — is listed on 1 of Staples Inc.'s 2 channels
  • 990 Response To A Load Tender — is listed on 1 of Staples Inc.'s 2 channels

Network context

Staples Inc. channel references for Rithum

These network names are derived from the listed Staples Inc. channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method.

LEGACY EDI MIGRATION FUND

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 fund
Migrate from SPS Commerce
Migrate from Cleo
Migrate from TrueCommerce
Migrate from OpenText
SECURITY

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

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

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:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more

Related references

Partners with related document listings

Compare document requirements for similar business processes.

The Home Depot 48 docs · 11 channels Walmart 32 docs · 8 channels Target 23 docs · 4 channels Costco 55 docs · 12 channels Rivian Automotive, Inc 11 docs · 1 channel Williams Sonoma 10 docs · 2 channels KeHE Distributors 18 docs · 5 channels United Natural Foods, Inc. (UNFI) 17 docs · 4 channels Aldi 16 docs · 2 channels Sysco 11 docs · 2 channels Shoe Carnival 10 docs · 2 channels White Cap 8 docs · 1 channel Starbucks Coffee Company 14 docs · 3 channels Boscov's Department Stores 13 docs · 2 channels Dick's Sporting Goods 10 docs · 3 channels Big Lots 7 docs · 2 channels Nordstrom 28 docs · 8 channels JCPenney 25 docs · 20 channels NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels Macy's 17 docs · 5 channels AAFES (Army and Air Force Exchange Service) 15 docs · 3 channels

Showing 21 of 48 references

Browse the full directory

FAQ

Staples Inc. EDI questions

Which EDI documents are listed for Staples Inc.?

X12 860 Purchase Order Change Request Buyer Initiated; X12 850 Purchase Order; X12 855 Purchase Order Acknowledgment; X12 846 Inventory Inquiry Advice; X12 856 Ship Notice Manifest; X12 990 Response To A Load Tender; X12 204 Motor Carrier Load Tender; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.

How should I choose the Staples Inc. EDI channel?

The directory lists 2 channels for Staples Inc., including Staples US (via Rithum), Staples. Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

Which identifiers should the Staples Inc. mapping preserve?

For X12 860 Purchase Order Change Request Buyer Initiated, plan around original purchase order, change revision and affected line. For X12 850 Purchase Order, use buyer purchase order, order line and trading-party identifiers. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Staples Inc. accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching Staples Inc. EDI?

Apply a quantity reduction to the existing order instead of creating another order. Test a cancellation arriving after allocation or shipment and route it to an exception owner. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Get started