How do Rithum orders come into Endless, and why might one be missing?

Endless checks Rithum’s order stream every minute and turns each new order into a Pending sales order on the integration’s Sales Channel. Once an hour it also asks Rithum for newly created orders, to catch any the stream missed.

If a drop-ship order is missing:

• “Ingest Orders” must be on.
• With “Trading Partner ID” set, Endless ignores orders from every other trading partner.
• Import an order by hand when Rithum has already moved it past its created state.

To import one order, use Import from integration on the Orders page, choose the Rithum integration, and enter the exact PO number or DSCO order ID. Endless searches by PO number first, then by DSCO order ID. An order already in Endless shows as Already in Endless.

To bring Rithum changes into an order that is already in Endless, make them on the order in Endless yourself instead of using Reload order. Contact Endless support for help with changed Rithum orders.

Endless acknowledges the order in Rithum when its first fulfillment order is allocated, not when it arrives. It acknowledges each order once, and the order’s timeline shows the result. “Rithum AcknowledgeOrder: order … failed” means Rithum rejected the acknowledgment, and the message includes Rithum’s response. Endless tries again the next time a fulfillment order on that order is allocated.

Endless matches Rithum lines to products by SKU. When a line has no SKU, Endless uses its product group or UPC in its place, which matches only a product whose SKU is that value. A line that matches no product comes in without one.