Rithum Integration: Marketplace Catalog, Orders, Refunds & Returns
Most marketplace connectors stop at listings and orders. This one closes the loop: refunds in both directions that actually settle, and returns you approve or reject from your own dashboard. Catalog sync proven on a live 498,111 product export, tested end to end against a live Rithum account in July 2026.
Contact Rithum
Reach out to us for any inquiries or support, and
let’s connect!
-
Phone
1-844-482-4357 -
Website
https://www.rithum.com/ -
Get in touch with us
Reach out to us for any inquiries or support, and let’s connect!
The Rithum integration that finishes the job
Rithum, the platform you probably still call ChannelAdvisor, is where your Amazon, eBay, Walmart and Google listings live. Most connectors into it stop at two things: push a catalog, pull an order. Then the money moves backwards, a buyer returns a wheel or a marketplace issues a partial refund, and you are back in two admin screens with a calculator. Web Shop Manager 6.0 closes that loop. Refunds travel in both directions and actually settle. Returns are approved or rejected from your own dashboard. Nothing is left for you to reconcile by hand.
Web Shop Manager has connected stores to ChannelAdvisor for years, all the way back through 5.0. This is that integration rebuilt to full spec on Rithum’s current REST API, and validated end to end against a live Rithum account in July 2026: catalog, orders, webhook signatures, refund settlement and returns. The catalog side was exercised against that account’s own production export, 498,111 products across 527 columns and 3.92 GB uncompressed, streamed and parsed rather than loaded into memory.
Listings and orders are the easy half. The money coming back is the half that breaks.
Every marketplace connector can create a listing and drop an order into your admin. The trouble starts after the sale. A buyer opens a return. Amazon refunds a shipping charge. A line item goes back but the rest of the order ships. If your integration only understands orders flowing one way, every one of those events becomes manual work, and the two systems quietly drift apart until month end, when someone has to find the difference. This integration was built for the second half.
Full catalog sync, at real catalog size
Products, variants, pricing, quantity and attributes move between Web Shop Manager and Rithum in both directions. The bulk path uses Rithum’s own product export: we pulled a 498,111 product, 527 column export, 3.92 GB uncompressed, and parsed it in a streaming pass. Nobody has to trim their catalog to fit the connector.
Unchanged products are never resent
Every product body is hashed before it is written. If the hash matches what was sent last time, the write does not happen. A full re-sync over an unchanged catalog makes essentially zero calls: on a 500,000 product scale run, the warm pass mutated nothing at all. That is your API quota, your database, and your sync window, all left alone.
Orders arrive over signed webhooks
Marketplace orders come in over Rithum’s webhooks with the HMAC signature verified on every request, timing-safe, with key rotation handled. Installs without a live webhook fall back to polling, so an order never sits waiting for a subscription somebody forgot to register. Shipments, cancellations and fulfillment updates push back the other way.
Refunds in both directions, with real settlement
A refund raised in Rithum does not just leave a note on the order. It creates a granted refund against the Web Shop Manager order and requests the refund through your payment layer, line items and all, so the customer’s money actually moves and your order totals are correct. A refund raised in your admin posts back to Rithum as an order adjustment.
Returns and RMAs you can act on
Return requests are pulled from Rithum and surfaced in your dashboard, where you approve or reject them. Rejections use Rithum’s own closed list of rejection reasons, so a reject cannot be silently refused for a reason the API does not accept. Return shipping labels are retrievable through the same connection.
Your images stay where they are
Product images are referenced from Rithum by URL, not copied into your store’s media library. A half million product catalog does not become a half million file downloads, an import that runs for days, and a storage bill for pictures that already exist somewhere else.
Multiple distribution centers, bundles, promotions
Inventory is read per distribution center, including fulfillment-by-marketplace locations, rather than flattened into one number that is wrong for everybody. Product bundle components, order item bundles, and order level promotions are read through too, so a bundled or discounted order does not arrive as a mystery.
Built into the platform, not bolted on
This is a first-party Web Shop Manager 6.0 application. Long syncs run on the platform’s background workers, credentials are stored encrypted, failures raise a visible needs-attention event instead of disappearing into a log, and you connect it by pasting credentials into a settings screen. No middleware subscription, no separate vendor to call when a sync stops.
What happens when a buyer sends the wheel back
This is the sequence a typical connector leaves to you, and what this one does instead.
1. Buyer opens a return on the marketplace. 2. Rithum records the return request against the order. 3. WSM pulls the request and shows it in your dashboard. 4. You approve, or reject with a reason from Rithum's own list. 5. On approval, the refund is granted against the WSM order, line by line, and requested through the payment layer. 6. Order totals, refunded amount and audit trail update on both sides. Nothing left in a spreadsheet.
Your Rithum catalog on a Shopify store, and on Web Shop Manager 6.0
Rithum files a shopping cart under Webstores, one row down from Marketplaces, and drives it from the Rithum side. Shopify is the cart most parts sellers reach for, so it is the honest thing to compare against. The right-hand column is what Rithum’s own published documentation says its Shopify connection does, read in July 2026 and cited below. The middle column is the current Web Shop Manager 6.0 integration. Web Shop Manager is listed in that same Webstores category in Rithum’s own knowledge base, and has been for years. What changed is how much of the job the integration finishes.
| What a parts seller actually feels | Web Shop Manager 6.0 | Rithum’s Shopify connection |
|---|---|---|
| Where your catalog lives | ||
| Product data can move in both directions | ●products, variants, pricing, quantity and attributes sync both ways | ○Rithum states it sends product data to Shopify and cannot import it back |
| Your category paths become a real nested category tree | ●the path is walked and each level created for you | ◙smart collections only, manual collections are not assigned |
| No ceiling on how many variations a product can carry | ●the integration sets no per-parent variation limit | ◙99 variations per parent |
| No listing cap to design your catalog around | ●a 498,111 product export and a 500,000 product acceptance run | ◙Rithum’s terms state up to 200,000 listings for each online store |
| Images can stay where they already are | ●referenced by URL, never copied into your media library | ◙images must be hosted with Rithum or another third party |
| How fresh the storefront is | ||
| Catalog changes arrive as they happen | ●signed webhooks, with a polling fallback | ◙product and variation details updated approximately every hour |
| Orders land without waiting on a cycle | ●HMAC verified webhooks, key rotation handled | ◙Shopify orders import every 15 minutes, and only once paid |
| The money coming back | ||
| Refunds move in both directions | ●granted and settled in your store, and posted back to Rithum | ◙a refund issued in Rithum is reflected on Shopify, nothing documented coming back |
| Partial refunds keep their line items | ● | ○not documented |
| Return requests approved or rejected from your own dashboard | ●rejection reasons validated against the API, labels retrievable | ◙returns are listed among what the app manages, mechanics not published |
| Duplicate refund events cannot pay out twice | ●deduplicated before they act | ○not documented |
| Aftermarket fit | ||
| Year, make and model drives the storefront your buyers use | ●fitment-native platform, it drives vehicle search and filtering | ○no fitment documented for webstores, it appears only under eBay Motors |
| A storefront built for parts, not a general cart theme | ●the platform is built around vehicle fitment end to end | ◙whatever your Shopify theme and third-party apps provide |
| Ownership | ||
| First-party app in your platform, no middleware subscription | ● | ◙a connector app plus whatever your storefront needs on top |
| Sync failures raise a visible needs-attention event | ● | ◙not documented publicly |
● Live in the current WSM 6.0 integration ◙ Partial, capped, or varies by setup ○ Not available, or not documented
- 1. The Shopify column describes what Rithum’s own published documentation and service terms state about its Shopify connection, read in July 2026. Rithum classes Shopify as a webstore alongside BigCommerce, Adobe Commerce, Yahoo! Stores and Web Shop Manager. Individual accounts vary. Where Rithum publishes nothing on a capability we have marked it not documented rather than assumed a limitation, and said so in the note.
- 2. Direction of sync, images, collections, variation and SKU limits, sync cadence and paid-order behavior are all stated in Rithum’s own Shopify capability overview, including that Rithum sends product data to Shopify and cannot import product data from Shopify, that product and variation details update approximately every hour, that Shopify orders import every 15 minutes, that only paid orders are imported, that images must be hosted with Rithum or another third party, that the integration supports smart collections and does not assign products to manually created collections, and a limit of 99 variations per parent.
- 3. The listing cap is from Rithum’s published webstore service description, which states the module supports quantities of up to 200,000 product listings for each online store. Rithum’s Shopify overview separately cites a 250,000 SKU cap per label. The two are stated in different units, so we have quoted the service description.
- 4. Refunds: Rithum documents that orders refunded in Rithum will be refunded on Shopify. It publishes nothing about a refund raised on the store side reaching Rithum, and nothing about how settlement is performed. That is an absence of documentation, not a tested limitation. On the Web Shop Manager side, refund settlement depends on your store’s payment provider supporting refunds through the platform’s payment layer, and we confirm yours on the demo call.
- 5. Returns: Rithum’s own app listing states it lets you manage order cancellations, returns and shipping updates from the Rithum platform, but no public documentation describes the mechanics, and its knowledge base carries no returns category. We have marked it partial on that basis rather than claiming it absent.
- 6. Fitment: Rithum publishes no vehicle fitment capability for webstores. Fitment appears in its documentation only in connection with eBay Motors. On the Web Shop Manager side, vehicle compatibility on the marketplace listings themselves is governed by each marketplace’s own fitment program and is not part of what this integration writes today.
- 7. Catalog figures come from a real product export pulled from a live Rithum account: 498,111 rows, 527 columns, 3.92 GB uncompressed, streamed and parsed rather than loaded into memory.
- 8. The 500,000 product acceptance run is a synthetic export used as the integration’s scale gate before release. The cold pass wrote 490,000 products in 571 seconds, the warm pass over the same unchanged catalog wrote nothing at all, 0 mutations against the cold run’s 107,800, and peak worker memory held at 85.4 MB.
- 9. Category tree creation is a setting you turn on, so that a first sync cannot reshape a storefront navigation you have already built by hand.
Score your current setup against this table, book 20 minutes
Rithum, if you know it as ChannelAdvisor
Rithum is the current name for ChannelAdvisor: the marketplace and channel platform that connects a single product catalog to Amazon, eBay, Walmart, Google Shopping and the rest of the channels in its network, then routes the resulting orders back to you. Same platform, same accounts, new name. Web Shop Manager connects to it through Rithum’s REST API using credentials you already have, so if you are running a Rithum account today, nothing about it has to change.
Web Shop Manager is a fitment-native platform: year, make and model live in the product data, drive the storefront’s vehicle search, and already flow into our Meta, Google and Klaviyo integrations. The catalog this integration syncs to Rithum is that same fitment-aware catalog. Vehicle compatibility on the marketplace listings themselves is governed by each marketplace’s own fitment program, and is not part of what this integration writes today. For the wider picture, see automotive eCommerce.
Rithum and Web Shop Manager: what dealers ask
Straight answers for parts sellers weighing the connection between Web Shop Manager 6.0 and Rithum.
Does this work with my existing ChannelAdvisor account?
Yes. Rithum is ChannelAdvisor renamed, and the integration authenticates against the same account over Rithum’s REST API. You paste in the credentials from your Rithum developer console, we validate the connection, and your existing profile, distribution centers and channel setup are read as they already are. You do not create a new account or migrate anything on the Rithum side.
What marketplaces does this reach?
Whatever your Rithum account already reaches. Rithum is the hub that connects to Amazon, eBay, Walmart, Google Shopping and the rest of its channel network, and Web Shop Manager connects to Rithum. Adding or removing a channel stays a Rithum decision, made in Rithum, and the integration follows it.
Do I have to re-list everything?
No. The first sync reconciles rather than recreates. Products are matched against what already exists in your Rithum catalog by SKU, and existing listings are mapped to your Web Shop Manager products instead of being duplicated. From then on, only genuinely changed products are written, because every product body is hashed and compared before anything is sent.
How do refunds actually work?
In both directions, and they settle. When a refund or return credit is raised on the marketplace side, the integration creates a granted refund against the matching Web Shop Manager order, carrying the specific line items and amounts, and then requests that refund through your store’s payment layer, so the customer’s money moves and your order totals are right. When you issue a refund in your own admin, it posts back to Rithum as an order adjustment. Repeated webhook deliveries are recognized and will not refund twice.
Is my catalog copied into Rithum, or images duplicated into my store?
Product data syncs, images do not get duplicated. Images are referenced from Rithum by URL and recorded in the product’s metadata, rather than downloaded into your store’s media library. That is what makes a catalog in the hundreds of thousands of products practical: the sync moves text and numbers, not gigabytes of pictures that already exist.
What does migrating from Web Shop Manager 5.0 look like?
It is a genuine change of direction, and worth understanding before you plan it. On 5.0, ChannelAdvisor called into Web Shop Manager: your store was the server, waiting to be asked. On 6.0, Web Shop Manager calls out to Rithum’s REST API, which is what makes webhooks, bulk export, refunds and returns possible at all. Practically, that means new credentials from your Rithum developer console, a first reconcile pass to map your existing listings, and no change to your channel setup inside Rithum. We walk through it with you on a screen share.
How large a catalog can it handle?
We built and tested it against a real one. The bulk path was proven on a live 498,111 product export, 527 columns and 3.92 GB uncompressed, parsed in a streaming pass rather than loaded into memory, and a synthetic 500,000 product scale run stayed under 100 MB of memory with the warm re-run producing no writes at all. There is no catalog trimming step and no per-product ceiling to plan around. If you also sell through SureDone, the same catalog feeds both.
See your own catalog, your own orders, and a refund that closes itself
Book 20 minutes. Bring your Rithum account and a recent return that cost your team an afternoon. We will show you what the same event looks like when the integration handles it end to end, and what your first reconcile pass would actually touch.
Get Started Now: Close the Loop on Marketplace Orders
Bring your Rithum account and a recent return that cost your team an afternoon. We will show you what the same event looks like when the integration handles it end to end, and what your first reconcile pass would actually touch.
See Rithum Integrated On Your Store
Ready To Grow Your Business?
Ready to grow your aftermarket eCommerce presence and lift conversions across auto, truck, powersports, marine, and more? Connect with
Web Shop Manager for tailored solutions: strategy, platform, and performance in one team.