Turn Rithum OrderStream into an API

What you can build on OrderStream

• Get the Order Summary by retailer

  Build this

  Reads the Order Summary page: your retailers and, for each one, how many open orders sit in each status, such as Open/No Activity.

  Takes

  Retailer (optional)

  Returns

  Retailer, status, number of orders

• List orders in one status

  Build this

  Opens a retailer's Order Summary, clicks one status link and reads the orders listed on the quick action page.

  Takes

  Retailer, status

  Returns

  PO number, basic order information shown, status

• Get a PO's details

  Build this

  Opens the Order Detail page for one PO number and reads its line items, ship-to address and ship method.

  Takes

  Retailer, PO number

  Returns

  PO number, line number, vendor SKU, merchant SKU, item description, quantity, unit price, ship-to address, ship method

• Confirm shipment of an order

  Build this

  On a PO's Order Detail page, selects Ship from the Action menu, fills in the Shipment Confirmation page and submits it.

  Takes

  Retailer, PO number, tracking number, ship date, ship method, quantity per line

  Returns

  PO number, tracking number, confirmed lines, confirmation message

Automate OrderStream with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Orders waiting in Open/No Activity, every retailer

  Build this

  Starts

  Every weekday at 7:00

  Step 1

  Get the Order Summary for every retailer.

  Step 2

  Keep the retailers with orders in Open/No Activity.

  Step 3

  For each of them, list the orders in Open/No Activity.

  Step 4

  Email you the count per retailer, with the PO numbers listed for each one.

• New POs handed to your order system

  Build this

  Starts

  Every hour, on weekdays

  Step 1

  For each retailer you name, list the orders in Open/No Activity.

  Step 2

  Keep the PO numbers that were not there on the last run.

  Step 3

  Get each new PO's details.

  Step 4

  Post the PO number, lines, SKUs, quantities, ship-to address and ship method to your order system's webhook.

• Weekly open-order report by retailer and status

  Build this

  Starts

  Every Monday at 8:00

  Step 1

  Get the Order Summary for every retailer.

  Step 2

  Compare each retailer's counts by status with the last run.

  Step 3

  Have an AI step write a short summary of where open orders stand.

  Step 4

  Email you the summary with a table of retailer, status, number of orders and change.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get the Order Summary by retailer” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "dsm.commercehub.com/get_order_summary",
    "input": {
      "retailer": "Acme Home"
    }
  }'

{
  "status": "completed",
  "data": {
    "retailers": [
      {
        "retailer": "Acme Home",
        "statuses": [
          {
            "status": "Open/No Activity",
            "orders": 14
          }
        ],
        "open_orders": 22
      }
    ],
    "checked_at": "2026-11-12T07:00:00-05:00"
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

OrderStream’s own options

The integration that Rithum's OrderStream articles describe is file exchange: XML or delimited files for new orders, confirmations, invoices, cancellations, returns and status, with each file extension confirmed with your Onboarding Representative. Accounts configured for manifest integration can upload a confirm file from select shippers. In the web application you work retailer by retailer from the Order Summary.

Read on November 12, 2026: XML and Delimited file extensions, Confirming shipment of an order, Viewing orders by fulfillment status.

Signing in to OrderStream

OrderStream asks for your email address and password at dsm.commercehub.com, then a one-time code: by email, which is always on, or by text message or authenticator app if you add them. With Fous you sign in once through OrderStream's own sign-in with your own account: the login is sealed with AES-256, emailed codes are handled, and an expired session is signed back in.

Worth knowing

Statuses differ from retailer to retailer

The Order Summary lists open orders by status for each retailer, and the statuses shown vary by retailer. A method takes the retailer as an input, and a workflow loops over your retailers.

A shipment confirmation is final

Submitting a ship confirm cannot be reversed or altered. Your retailer may also require you to acknowledge the order first.

Quick Action page limits

The Quick Action page confirms many orders at once, but only orders whose line items all ship with a single tracking number. It times out after 60 minutes.

Sandbox and production are separate sites

Testing, recertifying and onboarding happen at test.commercehub.com, and live orders at dsm.commercehub.com. Build methods for live orders on dsm.commercehub.com.

More in Retail: vendor portals (North America)

• Syndigo CXH
• 1WorldSync Item Management
• Scintilla
• AlbertsonsNet for Suppliers
• CVS AP Vendor Portal
• Home Depot Supplier Hub
• Kroger Partner Pass
• Lowe's Vendor Gateway
• Target Partners Online
• Wayfair Partner Home
• Traverse Portal
• myUNFI

Other industries: Asda Supplier Portal, AT&T Premier, Travis Perkins, Petronect, CONTPAQi, Meta Business Suite and Ads Manager.