Rithum

Rithum brings channel orders into a central view and routes them using the brand's fulfillment rules. The destinations can include owned warehouses, third-party logistics providers and marketplace fulfillment services. Shipment and status updates return to the connected operation.

Map warehouses, channel accounts and the ERP or warehouse-management system before implementation. Onboarding covers those connections, fulfillment locations and the order and inventory data they exchange. Decide which activities your team will run and which belong in a managed-service agreement.

Define the fee and service boundaries

Commerce Core terms describe a recurring subscription or managed-service fee, possible setup charges and a variable fee based on gross merchandise value, subject to the order form. Transactions on a contracted destination may count toward that value even when they were not processed through Rithum.

The standard terms include two product feeds unless the agreement says otherwise. Those feeds have a different scope from transactional marketplace connections. Specify both requirements in the proposal.

Where Rithum manages a destination, self-service access is limited to the other agreed destinations or features. Confirm who owns changes before editing connected accounts.

Team access

Users need individual platform accounts. In OrderStream, administrators invite colleagues and set their permissions. Admin > My Admins identifies the people responsible for that organization's access and setup.