Rithum (ChannelAdvisor) marketplace integration for ecommerce

iWeb builds a feed or API bridge from your PIM into Rithum, transforming product attributes into each channel's format and cadence. We map variant names, sizing, materials and other dimensions so that Amazon sees different attributes than eBay, each correct and consistent with your source of truth.

Rithum does not version attribute mappings or pricing rules by default. iWeb implements a configuration-as-code approach so that all rule changes are tracked, tested in a staging environment and rolled back if needed. This prevents silent failures and allows you to audit who changed what and when.

iWeb designs stock allocation rules that reserve inventory for each channel based on picking and dispatch timescales. We sync stock from ERP or OMS into Rithum at a frequency that matches your fulfilment speed (usually every 15 or 30 minutes). We also reconcile actual picks and shipments back into ERP so that the true free stock is always known.

If Rithum ingests an order but the acknowledgement callback from your ERP does not fire, the marketplace dashboard will show the order as unconfirmed, causing customer anxiety. iWeb monitors this flow and alerts you to unacknowledged orders that are older than a threshold. We also build fallback logic to requeue acknowledgements if the first attempt fails.

iWeb connects return requests from Rithum to your RMA or returns system, tracks approval and reconciles refunds to your finance ledger. We ensure that every return is visible in a queue, no refund is approved twice, and customers see status updates in their marketplace account.

This depends on your fulfilment speed and picking batch frequency. If you pick and dispatch every 2 hours, syncing stock every 30 minutes is usually safe. If you pick multiple times per hour, 10-15 minute refreshes are better. iWeb helps you choose the right cadence and monitors whether Rithum's stock view is drifting from ERP.

Yes. iWeb designs channel-specific pricing rules in Rithum that apply margin, discount or promotional adjustments to your base price from ERP. These rules are version-controlled and gated, so you can test changes before they go live and roll back if margin is impacted.

If Rithum is unavailable, new product syncs and stock updates will queue until it recovers. Existing listings and stock levels on the channel remain in place, but cannot be updated. iWeb monitors Rithum availability and alerts you to outages; we help you decide whether to pause order acceptance on channels or let orders queue for manual processing.

iWeb builds a flow so that cancellation requests from Rithum flow into your OMS or ERP, reverse the original order and trigger a stock adjustment. If the order has already picked or shipped, we route the cancellation to customer service with full order context so they can decide how to handle it (refund, reship, etc.).

Yes, if the change came through iWeb's configuration-as-code pipeline. iWeb logs all attribute mapping changes, pricing rule updates and channel rule edits with timestamps and ownership. If a change was made directly in Rithum's UI, we recommend disabling direct editing and requiring all changes to flow through your PIM or a controlled system.

iWeb defines a rule set (e.g. 'if qty > on-hand, hold order in exception queue') and logs the reason. An exception team can then investigate (check if on-hand was miscounted, if there is substitute stock, if the order should be split between warehouses). Until the order is manually resolved or a rule is overridden, it does not flow into picking.

This depends on the marketplace's integration method (API, FTP, EDI, punchout). Rithum usually has a pre-built connector. iWeb's integration work is to map your product data and pricing rules into Rithum's format for that marketplace, test stock and order flows, and add the marketplace to your monitoring dashboards. Typically 2-4 weeks for a well-scoped integration.

iWeb implements daily or per-sync reconciliation reports that compare Rithum inventory to ERP inventory. If variance exceeds a threshold (e.g. > 5 units or > 2%), we alert you to investigate. Common causes are picks that have been registered in ERP but not yet synced to Rithum, or safety-stock reserves that are not being tracked consistently.