Skip to content
EDI Saks Fifth Avenue & Saks OFF 5th Saks OFF 5TH (Dropship) (via DSCO (dba Rithum))

Channel

Saks Fifth Avenue & Saks OFF 5thSaks OFF 5TH (Dropship) (via DSCO (dba Rithum))

Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) is one of Saks Fifth Avenue & Saks OFF 5th's 10 EDI trading channels. It supports 5 document types including X12 856, X12 810, X12 846, X12 850, X12 870.

Documents
5 transactions
Standards
X12 + EDIFACT
Transport
AS2 · SFTP · API

Document catalog

EDI documents we support for Saks Fifth Avenue & Saks OFF 5th Saks OFF 5TH (Dropship) (via DSCO (dba Rithum))

5 EDI transactions ready to integrate.

Document flow on this channel

How documents flow on Saks OFF 5TH (Dropship) (via DSCO (dba Rithum))

This channel carries 5 of Saks Fifth Avenue & Saks OFF 5th's 7 document types; the rest run on other Saks Fifth Avenue & Saks OFF 5th channels (listed below).

Catalog & inventory

Partial on this channel
  1. 832 Price / Sales Catalog not on Saks OFF 5TH (Dropship) (via DSCO (dba Rithum))
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not on Saks OFF 5TH (Dropship) (via DSCO (dba Rithum))

Only available on other Saks Fifth Avenue & Saks OFF 5th channels

Network onboarding

Saks OFF 5TH (Dropship) (via DSCO (dba Rithum)) is routed through Rithum

Stacksync maintains a certified Rithum connection covering 23 trading partners across 25 channels. Onboarding with Saks Fifth Avenue & Saks OFF 5th 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

Ready to automate your Saks Fifth Avenue & Saks OFF 5th EDI?

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