SureDone Integration: Catalog Sync, Orders & Refunds
Keep SureDone as your master catalog and add the storefront it was never going to give you. A streamed catalog import that keeps your variations and your category tree intact, storefront orders pushed into SureDone, fulfillment and refunds coming back, and a watchdog so the feed cannot go quiet without telling you.
Contact SureDone
Reach out to us for any inquiries or support, and
let’s connect!
-
Phone
(877) 773-6755 -
Website
suredone.com -
Email
hello@suredone.com
Get in touch with us
Reach out to us for any inquiries or support, and let’s connect!
Keep SureDone. Add the storefront it deserves.
SureDone is where your catalog lives and where eBay, Amazon and Walmart get fed. Your website is the one channel it does not run for you. Most stores bridge that gap with a nightly file drop: a CSV lands, an import runs, and everyone hopes. Web Shop Manager 6.0 replaces the file drop with a real integration. SureDone stays the master catalog. Your 6.0 storefront reads from it directly, keeps your own category tree and your variations intact, and pushes storefront orders back so every channel settles in one place.
Web Shop Manager stores have been selling from SureDone catalogs for years, on 5.0, over a nightly file drop. This is that connection rebuilt to full spec on SureDone’s current API: streamed bulk exports, v3 signed webhooks, and orders moving both ways. Connected live to a 1.46 million item SureDone production account in July 2026, where it imported 1,250 real products across three runs with no failures, pushed a storefront order in, and took a real shipment back as a storefront fulfillment. Sibling to our Rithum integration: same shape, same standard, different channel manager.
See the comparison · See what a silent import costs · Read the FAQ
Why a scheduled SureDone CSV import fails without telling you
The classic SureDone to website setup is a scheduled CSV. It works until it does not. An import pauses and nobody is told. One malformed row kills the rest of the file. Five hundred parts sit at zero dollars on the website while the prices are perfectly correct in SureDone. A create-only profile and an update-only profile drift apart for a month. The failure mode is always the same: silence that looks exactly like success. This integration was built so that class of problem surfaces instead of sitting silent.
Catalog import at real catalog size
The import is a bulk export, streamed. It asks SureDone for only the columns it actually uses, streams the compressed result row by row so the file is never held in memory, and re-orders the stream on disk so parent rows land before their variations. Worker memory stays bounded whether the catalog is five thousand products or the quarter million the benchmark runs. It has imported 1,250 real products from a live SureDone production account across three runs with no failures, on an account holding roughly 1.46 million items.
Unchanged products are never rewritten
Every product body is hashed before it is written. If the hash matches what was written last time, no call is made at all. On the 250,000 product benchmark, the second pass over an unchanged catalog produced zero writes against the 29,924 mutations the first pass took. Your sync window, your database and your rate limit are all left alone.
Variations arrive as variations
SureDone uses the eBay paradigm: members of a variation set share a sku, each row has its own guid, and the parent is the row where guid and sku match. The importer reads that structure and assembles real parent products with real variants, keeping each group whole in a single batch, instead of dumping a flat list of near duplicate products onto your website.
Your category tree becomes the storefront navigation
Your own taxonomy is already in the catalog, in the website category column, as a delimited path. The importer walks that path, creates any missing level, and files each product at its leaf, using the full path for the slug so the same leaf name under two different roots never collides. Categories that already exist are adopted rather than duplicated, and products with no path land in a fallback category you choose.
Orders both ways, proven on a live account
Storefront orders post into SureDone so your marketplace and website orders sit in one queue. A real order has been pushed into a live SureDone account and read back, and a real shipment recorded there came back as a storefront fulfillment carrying its tracking number. Partial shipments fulfill only the lines that actually went out, and the integration recognizes tracking it was already told about, so it never overwrites the carrier your shipper set. Cancelling on your side archives the order in SureDone.
Events arrive signed, and verified before they are read
Order and product events come in over SureDone’s v3 webhooks. Every delivery is checked against the Standard Webhooks scheme, with a five minute replay window and a constant time comparison, before the body is even parsed. Endpoints are provisioned for you and reconciled hourly, so a deleted or expired subscription heals itself. Real SureDone webhook deliveries have been received and cryptographically verified against this code.
Inventory changes arrive as events
A quantity or price change in SureDone raises an event, and the storefront picks it up then, rather than waiting for tonight’s file. If the event feed goes silent for an hour, polling takes over on a ten minute cycle so the store still converges. Pushing stock the other way, from the storefront into SureDone, is available and off until you turn it on, because on day one SureDone should win every disagreement.
Refunds flow both directions
A refund raised in SureDone creates a granted refund against the Web Shop Manager order, carrying line items when the payload has them, and requests that refund through your payment layer so your order totals stay right. A refund raised in your admin posts back to SureDone with per line refund sku and quantity. Both directions are on by default, and a redelivered refund event is recognized rather than granted twice.
See the cost before you spend it
Every sync mode has a dry run that executes the whole pipeline with the writer in preview mode. You get the create, update, skip and delete candidate counts with zero writes, before a single product moves. On the benchmark the dry run predicted the real run’s write count exactly, and it did the same against live catalog data.
Your images stay where they are
Images are referenced from their existing URLs and recorded in product metadata rather than copied into your store’s media library. A quarter million product catalog does not become a quarter million file downloads and a storage bill for pictures that already exist. Pulling them into the store’s own media is available as an option when a store wants it.
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, your SureDone user, token and webhook secrets are all encrypted at rest, and you connect it by pasting credentials into a settings screen and running a dry run. No middleware subscription and no separate vendor to call when a sync stops.
What a silent SureDone import costs you in one week
This is the week a scheduled file drop can cost you, and what this integration does at each step instead.
Monday A row in the file fails validation.
File drop: the rest of the file is abandoned.
This integration: that row is counted and
reported against the run with its reason.
Every good row carries on.
Tuesday The import stops running at all.
File drop: nothing happens. No email, no flag.
This integration: the run is stalled for two
hours, the watchdog raises it, and it appears
in your needs attention queue.
Thursday A customer orders a part you no longer stock.
File drop: the website sold what last night's
file said you had. You find out at pick and pack.
This integration: the quantity changed in
SureDone that morning and the storefront had it
as soon as the event arrived.
Friday Someone finally asks why the website is stale.
File drop: reconstruct the week from log files.
This integration: the run report was there on
Monday, with counts, errors and a timeline.
Your SureDone catalog on a Shopify store, and on Web Shop Manager 6.0
SureDone treats a shopping cart the same way it treats a marketplace: as a channel it pushes listings to. Shopify is the one most parts sellers reach for, so it is the honest thing to compare against. The right-hand column is what SureDone’s own public documentation says its Shopify channel does, read in July 2026 and cited below. The middle column is the current Web Shop Manager 6.0 integration. The difference is not speed. It is how much of your catalog survives the trip, and whether the aftermarket parts of it survive at all.
| What a parts seller actually feels | Web Shop Manager 6.0 | SureDone’s Shopify channel |
|---|---|---|
| Your catalog structure | ||
| Variation sets assemble themselves from your SureDone data | ●the guid and sku paradigm is read directly, nothing to declare per product | ◙mapping based, on a fixed set of variation fields you declare per product |
| A blank variation value does not silently cost you the listing | ●the row is counted and reported with its reason, the rest carry on | ○a blank value in a declared dimension stops the listing posting |
| Your own category tree becomes the storefront navigation | ●the website category path is walked and built for you, at any depth | ○collections are created inside Shopify first, then picked per product |
| Nested categories survive as a real hierarchy | ●full path, adopted rather than duplicated where it already exists | ○manual collections, no category tree documented |
| Fitment, the part aftermarket lives or dies on | ||
| Year, make and model arrives attached to the product | ●mapped onto the shared Web Shop Manager fitment convention | ○SureDone documents that it does not transfer fitment data to the cart |
| Vehicle search is part of the storefront, not glued onto it | ●fitment-native platform, it drives search and filtering | ◙a script added to your theme files, or a third-party app |
| Orders and money | ||
| Marketplace and website orders sit in one queue | ●storefront orders post into SureDone, idempotent | ●SureDone’s orders page shows every configured channel |
| Tracking goes back without anyone ticking a box | ●partial shipments fulfill only the lines that shipped | ◙tracking is not sent to the channel until the order is marked as shipped |
| Refunds handled in both directions | ●granted, then requested through your payment layer | ○no refund flow documented either way, you are sent to the payment processor |
| Freshness and ownership | ||
| Changes arrive as events, with a fallback when they stop | ●v3 signed webhooks, polling takes over after an hour of silence | ◙bounded by your Shopify plan’s API limits, and updates can take hours |
| An update that fails tells you it failed | ●attributed to the SKU, with the reason, in a needs attention queue | ◙SureDone notes that some updates may simply fail |
| No custom app for you to create and keep working | ●first-party app, you paste credentials into a settings screen | ◙a Shopify custom app you create, authorize and maintain |
● Live in the current WSM 6.0 integration ◙ Partial, manual, or bounded by plan ○ Not available, or not documented
- 1. The Shopify column describes what SureDone’s own public support documentation states its Shopify channel does, read in July 2026. SureDone treats Shopify as a channel alongside BigCommerce, Magento and its own storefront. Individual accounts vary. Where SureDone’s documentation is silent we have marked it as not documented rather than assumed a limitation, and said so in the note.
- 2. Variations: SureDone documents its Shopify variation management as mapping based with a fixed set of variation fields, declared per product, and states that if any item in the variation has a blank value in one of those fields the listing will not be posted. Web Shop Manager reads SureDone’s native structure instead, where members of a set share a sku and the parent is the row whose guid matches that sku.
- 3. Categories: SureDone documents that creating new collections is always done inside Shopify, and that it supports adding a product to a manual collection once that collection has been created there. No category tree or taxonomy mapping is documented.
- 4. Fitment: SureDone’s own module documentation states that it does not transfer fitment data to the cart, and that fitment is instead displayed by a script added to your theme. Its fitment automations are documented as export only, aimed at marketplace programs such as eBay Motors and Walmart.
- 5. Refunds: SureDone’s documentation describes no refund flow between Shopify and SureDone in either direction, and its own refund guidance is to process the refund in the payment processor or on the channel. That is an absence of documentation, not a tested limitation. On the Web Shop Manager side, refund settlement runs through your store’s payment provider, and we confirm yours on the demo call.
- 6. Tracking and freshness: SureDone documents that if an order is not marked as shipped, tracking information is not sent to the channel, and separately that updates may take a few hours to reflect on Shopify because of API throttling limits, and that some updates may fail.
- 7. Live account figures come from runs against a SureDone production account in July 2026: a catalog of 1,464,114 items counted through the API, three imports totaling 1,250 products with no failures, a storefront order pushed in and read back, and a shipment recorded on that account returning as a storefront fulfillment with its tracking. Signed webhook deliveries were received and verified against a SureDone demo account.
- 8. Scale figures come from a synthetic 250,000 product export used as the integration’s acceptance gate, 30 percent of it variation children. On that run the full cold sync completed in 124.6 seconds, the warm re-sync of the same unchanged catalog in 28.7 seconds with 0 writes and 0 mutations against the 29,924 mutations of the cold run, peak worker memory was 90.8 MB, and the dry run predicted the real run’s write count exactly. The benchmark catalog is synthetic by design, because the point of it is the memory ceiling and the write discipline.
- 9. The order timing is the outbound delivery of a live storefront order into a SureDone production account, measured at 1.1 seconds for the delivery task. The rest of the loop, the storefront event that triggers it, lands in the same second.
- 10. How the sync itself is built, the projected streaming export, the hash based diffing, the crash resume and the dry run cost preview, is described in the capability cards above and in the FAQ. Those are engineering mechanics rather than things a merchant feels day to day, which is why they are not rows in this table.
- 11. Event driven freshness depends on webhooks being provisioned on your SureDone account, which the integration does for you. Where they are not available, the polling fallback applies.
Score your current setup against this table, book 20 minutes
SureDone keeps the catalog. Web Shop Manager becomes the storefront.
SureDone is a multichannel listing and commerce platform: one product record, pushed out to eBay, Amazon, Walmart and the other channels it supports, with the resulting orders coming back into one place. It is built to be the system of record for your product data, and in this integration it stays exactly that. Web Shop Manager 6.0 reads from it and becomes the branded storefront on top, which is the one channel SureDone does not run for you. Nothing about your SureDone account, your channel settings or your listings has to change.
If you also run Rithum, that integration is a sibling of this one: different channel manager, same integration standard, same dashboard. See the rest of our platform integrations.
Web Shop Manager is a fitment-native platform built for aftermarket auto parts, where year, make and model decide whether a product is even relevant to the shopper. Fitment lives in the product data and already flows into our Meta, Google and Klaviyo integrations. This integration carries it across by mapping the SureDone columns you nominate onto that same shared fitment convention, so the vehicle data on the row arrives with the product instead of being rebuilt afterwards. Vehicle compatibility on the marketplace listings themselves stays governed by each marketplace’s own fitment program inside SureDone. For the wider picture, see automotive eCommerce.
SureDone and Web Shop Manager: what dealers ask
Straight answers for aftermarket and auto parts retailers weighing the connection between Web Shop Manager 6.0 and SureDone.
How do I connect SureDone to my Web Shop Manager website?
Three steps. Paste your SureDone API user and token into the integration’s settings screen, where both are validated against the live API and stored encrypted. Run a dry run, which reports exactly what a first sync would create, update and skip without writing anything. Start the sync when the numbers look right. Your SureDone webhooks are provisioned for you and reconciled hourly, so order and product events start arriving on their own. Nothing is created or migrated on the SureDone side, and your channel configuration is untouched.
Which marketplaces does this reach?
Whatever your SureDone account already reaches. SureDone is the hub that lists to eBay, Amazon, Walmart and the rest of its channel network, and Web Shop Manager connects to SureDone. Adding or removing a channel stays a SureDone decision, made in SureDone. We do not manage your channel listings, because that is the job you already pay SureDone to do.
Which system owns my product data?
SureDone does, and deliberately. The default flow is one way: SureDone into your storefront. Anything the storefront could push back, such as inventory and price, is off until you turn it on, so there is no ambiguity about which system wins and no risk of your website overwriting your catalog on day one. Orders and refunds are the exception, and those move in both directions by design.
Will my variations and categories survive the import?
Yes, both. Variation sets are read using SureDone’s own structure, where members share a sku and the parent is the row whose guid matches that sku, so they arrive as real parent products with real variants. Your category paths from the website category column are walked and recreated as a genuine category tree, which is what the storefront navigation is built from. Categories that already exist are matched and adopted rather than duplicated, and products with no category path land in a fallback category you choose.
How do orders and refunds actually work?
Storefront orders post into SureDone so your marketplace and website orders live in one queue, and they are idempotent, so a repeated event cannot create the order twice. Coming back, order events arrive over SureDone’s signed webhooks: a shipment fulfills the storefront order with its tracking number, and partial shipments fulfill only the lines that shipped. Refunds are handled in both directions and are on by default. A refund raised in SureDone creates a granted refund on the Web Shop Manager order and requests it through your payment layer, and a refund raised in your admin posts back with per line refund sku and quantity.
What does moving off my Web Shop Manager 5.0 CSV import look like?
Your 5.0 site keeps running while the 6.0 storefront is built alongside it, and your existing CSV job stays in place until you switch over. On the new store you paste your SureDone credentials, run a dry run against your real catalog, and compare the counts against what your nightly file is doing today. Your existing URLs are mapped and redirected as part of the launch, so the addresses Google already indexed keep working. Nothing changes inside SureDone at any point.
What happens to Year, Make and Model fitment?
You tell the integration which SureDone columns hold your fitment data, and it maps them onto the shared Web Shop Manager fitment convention, the same one our Google, Meta and TikTok feeds already read. That means the vehicle data on the row arrives attached to the product instead of being rebuilt afterwards. Fitment on your marketplace listings themselves continues to be handled inside SureDone by each marketplace’s own program.
How large a SureDone catalog can it sync?
It has run against a live SureDone account holding roughly 1.46 million items, importing a filtered slice of 1,250 real products with no failures. For scale it clears a 250,000 product benchmark before release, 30 percent of those rows being variation children: the full cold sync finishes in under 125 seconds, a re-sync of that same unchanged catalog takes 28.7 seconds and writes nothing at all, peak worker memory holds at 90.8 MB, and the dry run predicts the real run’s write count exactly. That benchmark catalog is synthetic by design, because the point of it is the memory ceiling and the write discipline. The behavior underneath it is covered by 586 automated tests across the sync, order, refund and reliability paths.
Bring your SureDone account. We will show you the dry run.
Book 20 minutes. We will connect to a copy of your catalog, run the preview, and show you exactly what a first sync would create, update and skip, before anything is written. Bring the last import that failed quietly, too.
Get Started Now: Replace the Nightly File Drop
Bring your SureDone account and the last import that failed quietly. We will run the preview against a copy of your catalog and show you exactly what a first sync would create, update and skip, before anything is written.
See SureDone 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.