What can I do with a Rithum order after it comes into Endless, and when does Endless send shipments, tracking, and invoices to Rithum?

You fulfill a Rithum order in Endless like any other order. With “Orders Locally Managed” on, the default, Endless creates a draft fulfillment order when the order arrives, at the building whose Rithum connection has the order’s warehouse code as its External Location ID, or by your routing strategy. With it off, Endless does not create that fulfillment order. Endless does not lock Rithum orders beyond the usual editing rules, such as not changing the product on a line that is on an active fulfillment order. Edits are not sent to Rithum.

Endless sends acknowledgments and shipments, so you do not need the Rithum portal for those. When a retailer changes or cancels a Rithum order after import, make the change or cancel the order in Endless yourself. Contact Endless support to discuss syncing later Rithum changes and cancellations, or sending invoices through Rithum.

The requested carrier service comes from Rithum’s carrier, ship method, and service level code, matched against the carrier mappings on the integration’s Data mapping tab, and the order keeps Rithum’s original text. Your warehouse receives that carrier service as for any order. Without a matching mapping, the order has no requested carrier service.

Endless sends each shipment to Rithum automatically when it is recorded as shipped or its fulfillment order becomes Fulfilled, including partial shipments. Send shipments on the order sends any that were missed. Each shipment is sent once, with the tracking number, carrier, ship method, ship date, weight, warehouse code, and shipped lines. The carrier names come from your carrier mapping, otherwise from the shipment, with “Standard” as the ship method.

“Rithum: failed to send shipment for fulfillment …” means Rithum rejected it, and the message includes Rithum’s response. Fix the cause and select Send shipments.

“Send Tracking Number as SSCC” also puts each tracking number in the SSCC barcode field, for partners such as AAFES that reject shipments without one.