Skip to content
EDI QVC QVC (Dropship) (via Rithum)

Channel

QVCQVC (Dropship) (via Rithum)

QVC (Dropship) (via Rithum) is one of QVC's 1 EDI trading channels. It supports 4 document types including X12 846, X12 850, X12 856, X12 860.

Book a demo ← All QVC channels
Documents
4 transactions
Standards
X12 + EDIFACT
Transport
AS2 · SFTP · API

Document catalog

EDI documents we support for QVC QVC (Dropship) (via Rithum)

4 EDI transactions ready to integrate.

Document flow on this channel

How documents flow on QVC (Dropship) (via Rithum)

This channel carries all 4 of QVC's document types.

Catalog & inventory

Partial on this channel
  1. 832 Price / Sales Catalog not on QVC (Dropship) (via Rithum)
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not on QVC (Dropship) (via Rithum)

Network onboarding

QVC (Dropship) (via Rithum) is routed through Rithum

Stacksync maintains a certified Rithum connection covering 23 trading partners across 25 channels. Onboarding with QVC on this channel reuses that connection — no separate VAN contract or certification cycle.

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.

Connecting via Rithum
  1. Accept the retailer's program invitation and create a Rithum supplier account.
  2. Choose a connection method: supplier portal, SFTP or FTPS file exchange, AS2 (carrying EDI, XML, or delimited messages), or the API.
  3. Set up connectivity against Rithum's test environments; AS2 uses a dedicated staging endpoint (staging AS2 ID RITHUMAS2-STAGING) separate from production, and TLS 1.2 or later with SNI support is required.
  4. Map and validate inventory, order, shipment, and invoice flows, then contact Rithum software support to validate bidirectional message transmission.
  5. Cut over to the production endpoints (production AS2 ID RITHUMAS2, as2.rithum.com) once the retailer signs off.

Testing: Rithum maintains separate test and production environments (dedicated vendor test and retailer test tiers, and a staging AS2 identity distinct from production). Suppliers validate inventory, order, shipment, and invoice flows in test, and Rithum software support confirms bidirectional message transmission before production cutover. AS2 clients must support SNI and TLS 1.2 or later.

Timeline: Rithum states that onboarding suppliers to a dropship program traditionally takes three to six months and claims a 66 percent reduction using its platform and onboarding team; actual duration depends on the connection method chosen and the retailer's test requirements.

Most-traded documents on Rithum
  • 850 25 ch
  • 856 25 ch
  • 846 24 ch
  • 810 20 ch
  • 870 10 ch
  • 855 8 ch
Other partners reachable via Rithum

Ready to automate your QVC EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a QVC EDI demo Tour the platform on your own