# Turn Rithum OrderStream into an API

> Read the Order Summary for each retailer, the orders waiting in Open/No Activity and each PO's line items with one API call each. A workflow can check every retailer each morning and hand new POs to your order system.

Page: https://fous.com/automate/rithum-orderstream
Updated: 2026-11-12

Works with your own Rithum OrderStream account. Fous is an independent product.

## What you can build on OrderStream

### Get the Order Summary by retailer

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

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

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

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](/product/workflows) 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

Starts: Every weekday at 7:00

1. Get the Order Summary for every retailer.
2. Keep the retailers with orders in Open/No Activity.
3. For each of them, list the orders in Open/No Activity.
4. Email you the count per retailer, with the PO numbers listed for each one.

### New POs handed to your order system

Starts: Every hour, on weekdays

1. For each retailer you name, list the orders in Open/No Activity.
2. Keep the PO numbers that were not there on the last run.
3. Get each new PO's details.
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

Starts: Every Monday at 8:00

1. Get the Order Summary for every retailer.
2. Compare each retailer's counts by status with the last run.
3. Have an AI step write a short summary of where open orders stand.
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](/product/methods), 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.

Example request:

```
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"
    }
  }'
```

Example response:

```
{
  "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.

| Option | What it covers | What it takes |
| --- | --- | --- |
| XML and delimited files | Files such as .neworders, .confirm, .invoice, .canreq, .return, .fa and .status, exchanged with Rithum. | Confirm each file extension with your Onboarding Representative before using it. |
| Manifest integration | Uploads a shipment confirm file from select shippers straight to the platform. | An account configured for manifest integration. |
| OrderStream by hand | Order Summary, quick action pages and Order Detail, one retailer at a time, plus the order.csv download for your shipping application. | A user account with authority to confirm orders, and authority to download files for order.csv. |

Read on November 12, 2026: [XML and Delimited file extensions](https://knowledge.rithum.com/s/article/XML-and-Delimited-file-extensions), [Confirming shipment of an order](https://knowledge.rithum.com/s/article/Confirming-shipment-of-an-order), [Viewing orders by fulfillment status](https://knowledge.rithum.com/s/article/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](https://fous.com/automate/syndigo-cxh.md)
- [1WorldSync Item Management](https://fous.com/automate/1worldsync-item-management.md)
- [Scintilla](https://fous.com/automate/scintilla.md)
- [AlbertsonsNet for Suppliers](https://fous.com/automate/albertsonsnet-for-suppliers.md)
- [CVS AP Vendor Portal](https://fous.com/automate/cvs-ap-vendor-portal.md)
- [Home Depot Supplier Hub](https://fous.com/automate/home-depot-supplier-hub.md)
- [Kroger Partner Pass](https://fous.com/automate/kroger-partner-pass.md)
- [Lowe's Vendor Gateway](https://fous.com/automate/lowe-s-vendor-gateway.md)
- [Target Partners Online](https://fous.com/automate/target-partners-online.md)
- [Wayfair Partner Home](https://fous.com/automate/wayfair-partner-home.md)
- [Traverse Portal](https://fous.com/automate/traverse-portal.md)
- [myUNFI](https://fous.com/automate/myunfi.md)

Other industries: [Asda Supplier Portal](/automate/asda-supplier-portal), [AT&T Premier](/automate/at-and-t-premier), [Travis Perkins](/automate/travis-perkins), [Petronect](/automate/petronect), [CONTPAQi](/automate/contpaqi), [Meta Business Suite and Ads Manager](/automate/meta-business-suite-and-ads-manager).

## Frequently asked questions

### Does Rithum OrderStream have an API?

The integration that Rithum's OrderStream articles describe is file exchange: XML or delimited files such as .neworders, .confirm and .invoice, set up with your Onboarding Representative. Accounts with manifest integration can upload confirm files from select shippers. Otherwise you work in the web application.

### How do I confirm shipment of many orders at once in OrderStream?

Use the Quick Action page: open the retailer's Order Summary, click Open/No Activity, fill in the fields and click Submit. It only takes orders whose line items all ship under one tracking number, and it times out after 60 minutes. Other orders are confirmed from their Order Detail page.

### Can I undo a shipment confirmation?

No. Rithum's help centre says a shipment confirmation is final and cannot be reversed or altered, so review the information before you submit. With Fous, a method that confirms shipments runs only when you or your own system call it with the data.

### Where do I log in to OrderStream?

Live orders are at dsm.commercehub.com, also reached from Login on rithum.com by choosing OrderStream. Testing, recertifying and onboarding use test.commercehub.com. Both ask for your email address and then your password.

### Is Fous affiliated with Rithum?

No. Fous is an independent product. You use it with your own OrderStream account, and a method reads and does only what that account can.

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Rithum OrderStream (Rithum). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.