Guide · Switching from Rithum
Leaving ChannelAdvisor, now sold as Rithum, does not have to mean a hard switch date, a quarter of onboarding, or a gap in orders. InfiPlex runs alongside Rithum while your sales channels move one at a time: Amazon this week, Walmart next, the Shopify store after that. Each moved channel lands in one order queue, routes to the warehouse or 3PL that ships it, and pushes to your ERP once. Clients who make this move report two things immediately: the monthly bill drops to a flat published rate with no revenue share and no per-message EDI fees, and the changes they had been waiting on, a new connection, a custom rule, a field mapping, get built in days instead of sitting in a queue or being turned down.
Why people leave
The first is the bill. Rithum does not publish pricing; reported costs start above $2,000 a month plus a 2 to 3 percent revenue share, with EDI transactions billed individually on top. Every dollar of growth raises the fee. The second is turnaround. A client asks for a new connection, a custom routing rule, or a field that needs to land in their ERP a certain way, and the answer is a long project timeline, or that it is not on the roadmap at all. InfiPlex is priced flat and published, from $49.99 a month with unlimited connections on every plan, and it is built to be adapted: a connection not yet in the integration directory is built by InfiPlex at no development cost on any Growth plan, and custom rules, mappings, and SKU maps are configured directly through Order Automation. The InfiPlex vs Rithum page lays the two side by side; this guide covers how the move actually happens.
The risk
Two things break during a connector migration, and both come from having two systems touch the same marketplace at the same time. The first is duplicate fulfillment: Rithum and the new system both see an Amazon order and both send it to the warehouse or the ERP. The second is inventory: the new system starts pushing quantities to a channel before it has a complete, current picture of what your warehouses and 3PLs hold, and listings show stale numbers on day one. A cutover plan that avoids both does not need a hard switch date. It needs each channel to have exactly one system pulling its orders at any moment, and an inventory pull that has already been running before any channel starts receiving quantities. Both are how InfiPlex is set up by default.
Cutover sequence
InfiPlex runs in parallel with Rithum. Most clients pick a single channel to start, often the one costing the most under revenue share: order pulls for that channel are switched off in Rithum and switched on in InfiPlex, its orders begin landing in the InfiPlex order queue and routing to the warehouse or 3PL that ships them, and once the team is comfortable the next channel follows. Amazon can move this week, Walmart next week, the Shopify store after that, in whatever order matches your volume and your contract timing. Every moved channel lands in the same queue alongside the channels still on their way over, with the same multi-warehouse order routing rules and the same ERP push, so the last channel to move behaves exactly like the first.
Duplicate prevention
A marketplace order carries one order ID, and InfiPlex keys every imported order on it, so a re-pull, a retry, or a manual re-import does not create a second copy. During the switch, the channel is turned off in Rithum as it is turned on in InfiPlex, which keeps one system responsible for that channel's orders at every moment. The handful of orders that arrive in the gap between the two switches can be pulled into InfiPlex once the channel is live, under the same rules that apply on schedule, so nothing skips your filters because it came in during the changeover. Listings are unaffected the entire time: they live on the marketplace, not in the connector, so moving order flow does not delist anything.
Inventory during the switch
InfiPlex pulls inventory from every warehouse, 3PL, and ERP location you map from the moment the connection is live, independent of whether any channel is receiving quantities yet. Sending inventory to a sales channel is a separate switch, enabled or disabled channel by channel. That separation is what lets a channel move its orders first: you confirm orders are routing the way you expect, then enable inventory sends for that channel and the number it receives is already current. One pool across every warehouse feeds every channel, with per-channel warehouse mapping, per-SKU buffers, and set-to-zero thresholds so a channel never sees stock you cannot ship; the multichannel inventory sync guide covers each control. In InfiPlex, inventory is the foundation everything else runs on, not a feed maintained in another system.
Retail dropship programs
Rithum's CommerceHub half runs retailer dropship programs, and suppliers connected to Home Depot, Best Buy, or another retailer through it are billed per EDI transaction on top of the platform fee. Those programs move to InfiPlex the same way a marketplace does: the retailer connection comes up in InfiPlex, purchase orders in, acknowledgments, ship notices, and invoices out are handled inside the platform through the EDI integration bridge and delivered as normal API data, and the retailer is switched off in Rithum once the first orders confirm. There is no per-message charge. The InfiPlex Bridge page covers how EDI documents become API data.
Configuration
Routing rules, SKU maps, and ERP mappings are configured on the InfiPlex side rather than exported from Rithum, which is usually the point of the switch. Channel SKUs reach your warehouse and ERP through SKU maps: each row carries a source SKU, a destination SKU, and a destination quantity, so a marketplace SKU ships under the SKU your 3PL knows and pushes under the item your ERP knows, with tracking and inventory reverse-mapped without a second configuration. Bundles and kits are handled by the bundle tool; the SKU groups, bundles, and SKU maps guide covers which tool fits which case. ERP pushes to NetSuite, QuickBooks Online, or Dynamics 365 map any custom field in either direction; the custom field mapping and order rules guide walks through each rule type. None of this is a scoped project: it is configuration a client can see and change, and when a real operational need is not already covered, InfiPlex builds it.
Timing the contract
Rithum contracts are typically multi-year, so the cutover order should follow the money and the calendar. Start with the channels carrying the most revenue share, move the retail dropship programs once the marketplace flow is proven, and time the last channel to your contract's notice window. Because InfiPlex runs in parallel, you do not have to wait for the term to end to start moving, and you are not paying two full platforms for long: Basic Starter is month-to-month and Growth plans require a 3-month commitment, so the overlap is a few hundred dollars a month, not a second enterprise contract. Ask Rithum for the specific termination clause and notice period in writing before you set the final channel's move date.
Frequently asked
Yes. InfiPlex runs in parallel with Rithum while sales channels move one at a time. A channel's order pulls are turned off in Rithum and turned on in InfiPlex, then the next channel follows. Nothing has to switch on the same day, and listings stay live on each marketplace the whole time.
Two ways. Each channel is turned off in Rithum as it is turned on in InfiPlex, so one system is pulling that channel at any moment. And every order InfiPlex imports is keyed on the marketplace's order ID, so a re-pull, retry, or manual import does not create a second copy.
No. The cutover unit is a single sales channel or retailer program. Move Amazon this week, Walmart next week, the Shopify store after that, in whatever order matches your revenue share exposure and your contract timing.
No. Listings live on the marketplace, not in the connector. Moving order and inventory flow from Rithum to InfiPlex does not delist, unpublish, or change a listing.
Yes. InfiPlex pulls inventory from every mapped warehouse, 3PL, and ERP location from the moment the connection is live, so quantities are already current whenever you enable inventory sends for a channel. You are turning on an outbound feed to a number that has been kept current, not starting a sync from scratch.
They move the same way a marketplace does. The retailer connection comes up in InfiPlex, purchase orders in and acknowledgments, ship notices, and invoices out are handled inside the platform through the EDI-to-API bridge, and the retailer is switched off in Rithum once the first orders confirm. There is no per-message EDI charge in InfiPlex.
Rithum does not publish pricing; reported costs start above $2,000 a month plus a 2 to 3 percent revenue share, with EDI transactions billed individually. InfiPlex is flat and published: Basic Starter at $49.99, Growth Starter at $499.99, Growth Pro at $999.99, and Growth Enterprise for 50,000+ orders a month, with unlimited connections and no revenue share on every tier. The Cost of One Connection page models the gap at your volume.
Custom routing rules, field mappings, SKU maps, and order filters are configured directly in InfiPlex through Order Automation, and a connection not yet in the integration directory is built by InfiPlex at no development cost on any Growth plan. If there is a real operational need the platform does not already solve, it gets built, in days, not scheduled for a future release.
No. Because InfiPlex runs in parallel, channels can start moving now and the last one can be timed to your notice window. The overlap cost is an InfiPlex plan for a few months, not a second enterprise contract. Get the termination clause and notice period from Rithum in writing before setting the final move date.
No. InfiPlex is order management, inventory sync, and fulfillment routing. Advertising stays with the marketplace's own tools or a dedicated platform. Clients making the move keep those tools and replace the order and inventory layer, which is where the revenue share and the turnaround problems were.
Resources
Parallel run, one channel at a time, listings untouched, inventory already current when you turn it on, and a flat published bill with no revenue share. Most connections live in days.
We move marketplace channels and retail dropship programs onto InfiPlex from Rithum regularly. Tell us which channels you run, what your current bill looks like, and which changes you have been waiting on, and we will map out the channel order and the contract timing with you. Contact us, email info@infiplex.com, or call 888‑770‑0857.
InfiPlex™ is a trademark of InfiPlex. Rithum, ChannelAdvisor, and CommerceHub are trademarks of Rithum Holdings, Inc. InfiPlex is an independent order management provider and is not endorsed by or affiliated with Rithum. Rithum does not publish a rate card; cost and contract figures are as publicly reported as of September 2026, so verify current specifics with Rithum before relying on them. ©2026 InfiPlex. All rights reserved.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License