How does Endless send inventory to Rithum, and why might a retailer’s site show different stock?

Endless sends inventory by DSCO Item ID, with a separate quantity for each mapped Rithum warehouse. Each warehouse receives the available stock from the Endless buildings mapped to it; the total quantity is their sum. Products need a saved DSCO Item ID and a push-enabled building connection with a Rithum warehouse code.

Enable Push Inventory to allow automatic or manual pushes. Inventory changes queue an update after a short delay, and the regular full push also runs. Push Inventory in the integration’s Actions menu starts an update on demand. Turning the setting off stops pushes; Rithum keeps its last quantities until changed there.

Endless checks Rithum’s results after sending. The Activity timeline reports applied, failed, and unconfirmed rows. A manual push also provides a CSV in your Inbox with the mapping status, quantity, warehouses, and result for each row. Review the reported reason when a retailer’s stock differs; submitting a request is not the same as Rithum applying every row.

Products without DSCO Item IDs are not sent. Sync Item IDs runs automatically every six hours and matches existing IDs, integration identifiers, or exact SKUs. It preserves saved mappings. Pull Product Data runs matching on demand and sends a CSV report to your Inbox; UPC matches are suggestions for review.

Map each building to the correct Rithum warehouse code. Warehouses without an Endless mapping are not updated. A retailer can also take time to read Rithum’s latest stock. Contact Endless support for help with missing mappings or rejected updates.