Order-to-cash
Partial on this channel- 850 Purchase Order
- 855 Purchase Order Acknowledgment not on Best Buy via CommerceHub
- 856 Ship Notice Manifest
- 810 Invoice
Channel
Best BuyBest Buy via CommerceHub
Best Buy via CommerceHub is one of Best Buy's 3 EDI trading channels. It supports 4 document types including X12 850, X12 856, X12 846, X12 810.
- Documents
- 4 transactions
- Standards
- X12 + EDIFACT
- Transport
- AS2 · SFTP · API
Document catalog
EDI documents we support for Best Buy Best Buy via CommerceHub
4 EDI transactions ready to integrate.
Document flow on this channel
How documents flow on Best Buy via CommerceHub
This channel carries 4 of Best Buy's 5 document types; the rest run on other Best Buy channels (listed below).
Catalog & inventory
Partial on this channel- 832 Price / Sales Catalog not on Best Buy via CommerceHub
- 846 Inventory Inquiry Advice
- 852 Product Activity Data not on Best Buy via CommerceHub
Only available on other Best Buy channels
- 860 Purchase Order Change Request Buyer Initiated on Best Buy Canada →
Network onboarding
Best Buy via CommerceHub is routed through Commercehub
Stacksync maintains a certified Commercehub connection covering 1 trading partner across 1 channel. Onboarding with Best Buy on this channel reuses that connection — no separate VAN contract or certification cycle.
CommerceHub, now operating as part of Rithum, is the commerce network that large retailers use to run dropship ecommerce programs. Retailers connect to the network once and onboard their suppliers through it, so suppliers exchange orders, shipment notices, invoices, and inventory updates with the retailer via CommerceHub instead of point-to-point EDI. Suppliers can integrate through the hosted portal, EDI or XML file exchange, or Rithum's APIs.
Connecting via Commercehub
- Get sponsored into the network by the retailer running the dropship program, then complete account setup with the CommerceHub/Rithum partner setup team.
- Choose an integration method: hosted portal, X12 EDI or XML file exchange over SFTP/FTP, or Rithum's REST APIs (recommended at scale), and obtain test credentials from CommerceHub.
- Request the retailer-specific supplier test plan and message guides, and map order (850), ship notice (856), invoice (810), and inventory (846) flows to the required formats.
- Execute the scripted test plan in the CommerceHub test environment (test.commercehub.com) and let CommerceHub review the test transactions.
- After test sign-off, switch from test to production credentials and endpoints to begin live trading with the retailer channel.
Testing: CommerceHub requires scripted testing per retailer channel before go-live. The supplier obtains the retailer-specific supplier test plan and message guides, processes test orders in the test environment (test.commercehub.com), returns shipment confirmations and invoices, and CommerceHub reviews the results before production is enabled. Failed documents trigger additional test rounds.
Timeline: No official timeline is published. Custom EDI integrations with CommerceHub have historically taken roughly two to three months; pre-built connectors and the API route are faster, and each additional retailer channel adds its own test-plan cycle.
Most-traded documents on Commercehub
- 810 1 ch
- 846 1 ch
- 850 1 ch
- 856 1 ch
Trading partners
2+ 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.
Ready to automate your Best Buy EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
