Guides

Disconnecting a sync app: the question to ask before you install

Uninstalling a sync app is not a clean exit. Products it created stay behind, counts can be zeroed, and the worst damage lands during the uninstall itself.

Updated 20 September 2026

Everyone evaluates sync apps on how they behave when they are working. Almost nobody asks what they do on the way out — and in this category that is the question with the most expensive wrong answer.

We read 2,603 public reviews across nine sync apps. Nineteen of them mention disconnecting, uninstalling or unsyncing. Ten of those nineteen are one-star reviews. That ratio is the point: merchants rarely mention the exit, and when they do it is usually because it went badly.

Why leaving is dangerous at all

A sync app is not a passive observer. Depending on what you enabled, it may have created products in the store it syncs into, written quantities on a schedule your store now depends on, and registered webhooks that stop firing the moment access is revoked. Disconnecting raises a question with no obviously correct answer: who owns the things the app made?

Every vendor answers it differently, and the answer is usually undocumented. Four models exist in practice:

That last row is not hypothetical. A merchant reviewing Multi-Store Sync Power in November 2025 reported that after correctly nominating their main store as the source, the app “set my entire inventory quantity to zero (0) across all products and variants in my primary shop”, costing over three hours of manual restoration from the Inventory Adjustment History plus the lost sales while the store showed empty. An earlier reviewer of the same app reported roughly 2,000 variants going to negative quantities before they uninstalled.

The case that should change how you test

The most instructive report in our dataset comes from a merchant running a retail store and a wholesale store, reviewing Tipo Multistore Sync in September 2025. They connected the two, thought better of it, and uninstalled from both stores within two minutes.

It did not help. By their account the sync had already run: inventory pushed back and forth between source and destination, collections removed from online visibility, destination-store banners appearing on source products, duplicate collections created, product tags altered — and theme templates they had built by hand “permanently d[eleted]”.

Two minutes. The lesson is not that this app is uniquely dangerous — it holds a 4.7 average and this is one review among 134. The lesson is that uninstalling is not an undo button. Whatever a sync app does, it does immediately, and removing it afterwards does not reverse it.

Which is why the meaningful test is not “can I uninstall it” but “what does it write, and can I see that before it writes”. That is what a dry run against your real catalogue is for.

Billing does not always stop either

A separate failure worth checking: one QuickSync reviewer reported still being charged a month after uninstalling, and was refunded once they raised it. Shopify app charges live on the subscription rather than on the install, so confirm the charge is cancelled in your Shopify admin, not just that the app is gone.

The honest framing

Nineteen mentions across 2,603 reviews is a small number, and every app named here holds a strong overall rating. These are minority reports.

But they are minority reports about the failure mode with the longest tail. A sync that gets a quantity wrong costs you one order; a disconnect that zeroes your source store or deletes your theme templates costs you a weekend and, in one of the accounts above, thousands. Low probability, high cost, and entirely knowable in advance — which is an unusual combination, and the reason to spend ten minutes on it before installing anything.

What to ask before you install

Send this to the vendor and keep the reply:

1. When I disconnect a store, what changes in each store? Anything other than “nothing changes, sync stops” needs a follow-up.
2. Do you create products in the store you sync into? If yes, what happens to them on disconnect — kept, deleted, or my choice?
3. Do you ever set quantities to zero? On which store, and under what conditions?
4. Is disconnecting reversible? If I reconnect tomorrow, what state am I in?
5. How do I cancel billing, and is it separate from uninstalling?

Then read the app’s one-star reviews for deleted, wiped, uninstalled and zero. Disconnect behaviour is documented in reviews far more often than in documentation.

The exit runbook

When you do leave an app — and eventually you will leave every app:

1. Export products from every connected store first. Not ceremony: it is the only cheap rollback you have, and it doubles as a duplicate-SKU audit for whatever comes next.
2. Disconnect inside the app, not from the Shopify admin. Uninstalling from the admin revokes access before the app can run its own tidy-up, which is how people end up with orphaned live products.
3. Resolve synced products deliberately — keep or delete, per product, rather than accepting a default.
4. Set anything ambiguous to draft rather than leaving it live with stock that will never update.
5. Reconcile quantities by hand against the store that holds physical reality, before you resume selling.
6. Confirm the subscription is cancelled in the Shopify admin.
7. Only then uninstall.

If you are switching rather than stopping, run the new app in a read-only or dry-run mode alongside the old one first and compare what each believes is paired. Disagreements between two apps on the same catalogue are the most informative signal you will get. Read-only is the load-bearing word. If the new app is allowed to write while the old one is still running, each will read the other’s writes as fresh sales and both sets of numbers will be wrong before you have finished comparing them.

What StockUnison does

Disconnecting stops the sync and changes nothing else. Every product in every store keeps the quantity it last had. No product is set to zero, in either direction. Nothing is deleted.

It can promise that because of a decision made earlier in the design: StockUnison never creates a product in a connected store. A SKU that exists in the main store and not in a connected one is reported as unmatched, not invented. With nothing created, there is nothing orphaned, and the whole keep-or-delete question never arises.

Two honest limits. First, the open-window risk in row one of that table applies to us too: after you disconnect, the store that was following keeps selling from a number that no longer updates, and it is on you to reconcile it — no app can fix that, which is why step 5 of the runbook exists. Second, StockUnison launched in August 2026 and has no review record, so this section is a claim rather than a track record. The way to test it costs nothing: connect a development store on the free plan, run a preview mode, disconnect, and look at what changed.