Shopify store suspended, and you sell supplements. Migrate everything to a new Shopify store.
The notification lands without warning: your Shopify store has been suspended for violating the Acceptable Use Policy or Terms of Service. Support is unreachable or points you at a form with no reply. Here is what almost nobody explains, and it is the only thing that changes what you do in the next hour. This is a platform decision, not a payment processor problem. No gateway and no acquirer can override it. Shopify's Trust & Safety team made the call against your account under their own policy, and no external underwriting will change that verdict. But there is a second, harder deadline underneath. Admin access can be revoked at any moment, and with no admin there is no API. When that happens, your catalog, order history, consent timestamps and every metafield your theme renders from become unreachable — not deleted, just locked away with no way in. Merchants commonly report losing access within hours of suspension. So the only step with a deadline you do not control is this one: get a verified copy of your store data out, right now, while you can still log in.
Move all of it into a new store, from $247
One-time packages, no per-record metering, no quotes. The order form unlocks the moment you pay, counts are matched against your old store, and the entire migration then runs a second time — the second pass has to create nothing.
What you are looking at
- "Your store has been suspended for violating our Acceptable Use Policy" — with no detail on which part of your business triggered it
- Admin dashboard loads but checkout is disabled, or dashboard access is blocked entirely
- Support tickets remain unanswered for weeks, or auto-replies point to the Acceptable Use Policy document
- No explanation of what specific conduct violated policy, or what would need to change to appeal
- Shopify email confirms suspension but offers no timeline for review or reconsideration
The payment clock matters less than the access clock. You have a limited window to export data before admin login is revoked. That window has no published duration — it can close in hours. Once it does, API access dies and your catalog, order history and metafields vanish from your reach. That is the deadline that actually shapes what you do today.
Why it happened — specifically for supplements
Shopify Payments is underwritten by Stripe, which allows supplements but prohibits those that are 'not safe or make harmful claims'. The primary trigger is disease claims: anything stating or implying your product treats, prevents or cures a condition reads as marketing an unapproved drug. The secondary trigger is subscription refund disputes — when a customer cancels because the product 'did not work', the chargeback rate can spike, which is why free-trial-to-subscription models are a specific, well-documented decline reason across acquirers.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document a platform route for supplements — there is no attestation or pre-approval gateway. What merchants try first is connecting Shopify Payments and hoping the underwriting review misses the claims. It usually does not. If you are reading this, that review has already declined you. The honest move is to find an acquirer who specializes in ingestible categories and whose underwriting is built around the claims audit, not a blanket refusal. That is not faster, but it is the actual path.
It only helps if all of these are true:
- Your product descriptions contain no disease claims — only structure and function language.
- You use payment methods other than free trial to subscription, or you accept a higher chargeback reserve.
- Your current processing history shows a chargeback rate below the acquirer's stated threshold.
- You have documented supplier credentials and, where applicable, third-party testing results.
If any one of them does not hold, you are where everyone else on this page is: you need a store built around a gateway that will actually accept you — and everything you have built has to move into it without losing the catalog, the customers, the order history or the rankings.
What this means for a business like yours
💊 Sold to be swallowed, inhaled or applied — health claims and product-liability risk
Shopify suspension is catastrophic for health products because claims evidence lives in your store. Certificates of analysis, third-party test reports, disclaimer language—all of it is indexed to products in your catalog. If admin access is revoked before you move, that data becomes unreachable through the API, and you lose the exact wording regulators and underwriters will want to see. Export your product descriptions, images and all supporting documents to your own servers immediately. When you rebuild elsewhere, the claims language must be identical, word for word. A processor reviewing you later will compare old and new; any drift looks intentional.
🔁 Recurring billing is a large share of revenue
Subscription billing stops the moment the suspension takes effect, and stored payment methods held by Shopify cannot be exported or transferred to any other processor. Every active subscription becomes uncollectable immediately. Your revenue decay begins on day one. Before admin access is lost, extract every subscription customer record you can—email, billing address, product SKU, billing frequency. You will have to rebuild the subscription list on a new platform and contact every subscriber to restart billing, which never fully recovers. Start this before anything else, because the data window closes the moment Shopify locks you out.
📦 Thousands of SKUs, deep variant matrices, distributor feeds
The API becomes unreachable the moment admin is revoked, and metafields, variant matrices and distributor feed mappings are not portable through Shopify's standard CSV export. With thousands of SKUs and complex options, a manual rebuild is not possible. You have only one window to extract data: while login still works. Use the GraphQL API to pull every metafield, product variant, collection structure and custom field before the account locks. Standard CSV export will not capture any of this. Without it, your new catalog will be skeletal—flat products with no variant logic, no custom attributes, no distributor mappings. Rebuild only after you have extracted everything via API.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For supplements, these are the facts that move the decision:
Remove or rewrite every disease claim on your store
This is the single highest-yield fix. Anything that says or implies your product treats, prevents or cures a condition — anxiety, pain, sleep, inflammation, immunity — reads to an underwriter as a drug claim, which moves you from restricted to prohibited. Audit your product descriptions, your blog, customer reviews you display, your email flows and your FAQs. Reframe in terms of structure and function: 'supports joint health' instead of 'cures arthritis', 'promotes relaxation' instead of 'treats anxiety'. Check every claim against FDA guidance on dietary supplements.
Get product liability insurance and verify coverage for ingestibles
Most acquirers will not move forward without a current certificate. This is not optional. The policy must cover your specific product type — protein powders, botanical extracts, sports nutrition — and the certificate should state that clearly. Email your broker or insurer to confirm coverage for the formulations you actually sell. When you apply, provide the certificate with effective dates and policy limits visible. Underwriters will call to verify it before they approve anything.
Document your supplier chain and testing for every product SKU
Acquirers ask for formulation sheets, ingredient sourcing, and either third-party testing results or cGMP certification from your manufacturer. This matters especially if you use botanical extracts, proprietary blends or anything that requires batch verification. Organize this by SKU and have it ready to upload with your application. If you do not have it, ask your supplier for it now. A missing COA or sourcing sheet often stalls an underwriting review for weeks.
Fix your subscription billing model if you use free trials
Free trial followed by automatic subscription is a known chargeback trigger — customers cancel late and dispute the first paid charge. If you use this model, you have two options: switch to paid trial or add a charge-delay period with clear confirmation language before the first payment. Acquirers will ask about your cancellation rate and your refund process. Lower the friction to cancel and you lower the dispute rate, which makes underwriting easier. Disclose your actual chargeback percentage upfront when you apply.
What underwriting will ask you for
- Product liability insurance certificate (required for all ingestible categories and the single most common request).
- Complete product formulations and ingredient sourcing documentation.
- Copies of all marketing claims — product pages, email flows, social media and reviews displayed on your store.
- Testing certificates or cGMP documentation for manufactured products.
- Chargeback and refund history from your current processor for the past 12 months.
- Subscription terms and cancellation rates if you use recurring billing.
Getting underwritten for supplements
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite supplements. What none of them will tell you up front is the number that actually matters: what your business gets offered, once they have seen your volume, your claims and your history. Rate, reserve and settlement terms vary enormously between applicants in the same category.
Get real quotes from high-risk processors that accept supplements
Six taps and three details. We put it in front of the high-risk acquirers that actually underwrite your category and come back with what they will offer you — rate, reserve and settlement terms — so you are comparing real numbers instead of cold-emailing brokers for a fortnight.
The recovery playbook
- Read the suspension email for the specific policy citedShopify will have named at least one clause of the Acceptable Use Policy or Terms of Service you allegedly violated. Write down the exact text. If the email is vague — saying only that you violated policy without naming which one — make a note of that too, because a vague suspension is harder to appeal. This is the only thing Shopify has told you about why this happened. Everything else you do flows from understanding what the company thinks you did.
- Export your store data while you still have login access — todayThis is the step people skip, and it is the only one with a deadline you do not control. A store suspension is not the end of the process. It is the first thing that happened. Shopify can revoke admin access at any time after suspension, usually without notice. And if the store closes, admin access can go with it. That is the part that turns a bad month into a dead business, because with no admin there is no API — and with no API your catalog, order history, consent timestamps and every metafield your theme renders from are simply gone. Use Shopify's CSV export tool to pull products, customers, and orders. CSV export cannot carry metafields, metaobjects, videos, themes, discounts, menus or redirects, so it is incomplete — but it is faster than nothing. Then take a full backup using a third-party migration tool or service that can read the API before access is cut. Do this now, not tomorrow.
- Document your store's structure while you have timeWrite down or screenshot your theme name, app list, custom domains, store settings, and any menus or navigation structure. This takes an hour and it saves weeks of reconstruction later. Take screenshots of your discount codes, customer segments, and any automation or workflow you built. Shopify's CSV export does not carry discount rules, so you will need to recreate them by hand. Do the same for any custom pages, redirects or navigation changes you made. This is not a full backup — it is a map for rebuilding.
- Do not attempt to reopen on ShopifyShopify's Acceptable Use Policy applies to the person behind the account, not just to the account itself. Opening a new Shopify store under your name, as a new entity, or with a new email address does not reset what the platform knows. Shopify can and does suspend accounts with the same beneficial owner if it concludes the new store is reopening the same business under a different name. This is not a legal issue; it is a platform enforcement decision. The rebuilding move is to migrate your store to a platform and payment gateway that will underwrite your category.
- Apply to alternative platforms and gateways that accept your categoryIdentify payment processors and hosting platforms that publicly advertise support for your product category. Shopify Payments will not work (it is underwritten by the same company that rejected you at the gateway level). But dozens of alternative acquirers, payment facilitators and hosted platforms serve high-risk categories that Shopify rejects. You will need to provide bank statements, proof of business registration, and an honest explanation of why you left Shopify. Do not misrepresent your history. A new entity can be the right structural move for real business reasons, but it does not hide your past from underwriting — and anyone selling you a setup that does is selling you fraud. Honesty gets you underwritten faster than misdirection.
And then there is the part that actually loses businesses
If you do need a new store, the payments problem turns out to be the easy half. This is what is sitting in your current store right now, and what happens to each piece when someone tries to move it by hand:
Why this category in particular
A supplement store's data is dangerous to move by hand because compliance content lives in metafields. Batch numbers, testing certificates, ingredient sourcing notes and allergen flags are all reference or text metafields that a CSV export cannot carry — and if copied naively they keep pointing at files in the old store, so pages render but the compliance data is silently blank. On a regulated ingestible, that audit failure can trigger processor review even after onboarding.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,250images≈ 5 hrsbulk re-upload, ~15 sec each | By handthe CSV carries image URLs and alt text, but they point at your OLD store's CDN — so the moment the old store goes, every image 404s. Re-upload and Shopify appends a dedupe suffix to the filename, which breaks every theme section and product description that referenced the original URL | Automatedevery file re-uploaded through the API with its alt text and variant attachment intact, its content type preserved so image-restricted fields still accept it, and every reference to the old URL rewritten |
| Product descriptions | 250descriptions≈ 2 hrsone pass to repair inline image links — the CSV carries the text | By handdescriptions are full of inline images and links pointing at the old store's CDN. Paste them into the new store and the text survives perfectly while every embedded image quietly dies — which you usually discover from a customer, not from a report | Automatedbodies copied verbatim, then a second pass rewrites every source-CDN URL inside them to the re-uploaded file on the new store |
| Product attributes & variants | 2,000variants≈ 45 minthe CSV carries these; the time is verifying option order | By handoption ORDER is part of the product's identity. Rebuild "Size, Colour" as "Colour, Size" and every theme swatch, saved customer URL and app that keys on variant position breaks — silently, because the product page still renders | Automatedvariants upserted by SKU with option names and order preserved, so swatches, deep links and app data keep working |
| Metafields & metaobjects | 3,000metafields≈ 20 hrsonly the reference, JSON and metaobject fields, ~1 min each | By handthe product CSV carries simple text and number metafields — but not metaobjects, and not reference or JSON types, which is exactly where app data and theme content live. Reference fields are the real trap: copy the value and it still points at objects in the OLD store, so the page renders and the custom block is silently empty | Automatedwritten in dependency order after their targets exist, with embedded references re-pointed at the new store's objects — and any value whose reference cannot be resolved is dropped rather than written broken |
| SEO data & redirects | 433records≈ 3 hrsredirects one at a time, plus a handle audit | By handany handle that changes becomes a dead URL with no redirect, and existing 301s are not in the product CSV at all. Years of accumulated ranking and backlinks end up pointing at pages that no longer resolve — the most expensive thing on this page to get wrong, and the slowest to notice | AutomatedSEO titles, meta descriptions and handles carried across, and every existing 301 recreated, so nothing that used to rank starts 404ing |
| Your custom theme | 1theme≈ 6 hrs2–10 hrs depending on how customised it is | By handa theme is not just its files. The settings, section content and block ordering are stored against the store, so a file copy gives you the layout and none of the content. Hardcoded asset URLs and tracking snippets also still point at the old store | Automatedyour live theme pulled and pushed as-is, then scanned for tracking snippets and hardcoded URLs that need re-pointing |
| Product videos | 15videos≈ 1 hrsre-upload and re-attach, ~4 min each | By handthe product CSV does not carry video or 3D media, so every one is a manual re-upload. They also cannot be pulled straight from a remote URL — the bytes have to be downloaded and staged first, and a wrong content type lands the file as a generic attachment that media-restricted fields then reject | Automatedvideo bytes downloaded, staged through a proper upload target, re-attached to the right product, and verified as processed rather than silently failed |
| Customers | 8,000customers≈ 2 hrsCSV import, then cleaning up the rows that fail | By handthe importer works, but marketing consent is the exposure: the CSV carries the current opt-in state and NOT the timestamp or source behind it. Re-opting someone in is a compliance breach, dropping them burns list revenue you paid for, and you cannot prove which happened afterwards. Default-address designation is also lost | Automatedcustomers upserted by email with every address, the default-address designation, and email and SMS consent states and timestamps preserved exactly as they were |
| Order history | 12,000orders≈ 8 hrsa paid third-party importer, plus a day of mapping and reconciliation | By handShopify's own CSV importer cannot create orders at all, so the hours here assume you buy a third-party importer — key them in by hand instead and 9,400 orders is closer to 390 hours, which is why nobody does that and why order history is simply abandoned in most DIY moves. Then support cannot answer a warranty claim, repeat-purchase segments are empty, and every returning-customer flow starts from zero. Getting the mapping wrong duplicates orders or re-dates them to today, and both are worse than not importing at all | Automatedfull order history recreated through the API with line items, properties, customers re-associated, original dates and tracking numbers intact |
| Navigation menus | 4menus≈ 1 hrsabout an hour to rebuild and relink them all by hand | By handmenu items store resource IDs, not paths, so nothing about them is portable — every link has to be re-pointed at the equivalent collection, page or product on the new store | Automatedmenus rebuilt with their nesting, and every item re-pointed at the equivalent object on the new store |
| Discount codes | 85discounts≈ 1 hrsabout 1 hr via the discount CSV, or ~3 hrs rebuilt by hand | By handthe discount CSV covers basic codes, but automatic discounts, quantity breaks and combination rules are not in it and have to be reconstructed by hand. A subtly wrong rule is worse than a missing one, because nobody notices until it has been over-discounting for a fortnight | Automateddiscounts recreated through the API with their rules, usage limits and dates intact, including automatic and free-shipping types |
| Gift card balances | 200gift cardsno manual routecannot be moved by anyone | By handthis is the one thing on this page that truly cannot be moved by anyone. Gift card codes are unreadable through EVERY Shopify API, by design — no tool, ours included, can copy them. Those balances are real money you owe real customers, and abandoning the old store does not abandon the liability: the customers still turn up expecting you to honour it | Automatedwe re-issue each card with an identical balance, customer and expiry date, and hand you the new codes as a CSV with customer email copy ready to send — the only honest way to move them |
| Blogs & pages | 63articles & pages≈ 4 hrsrecreated one at a time, ~4 min each | By handno CSV route for either. Articles also have no SEO fields of their own — their title and description tags live in metafields — so a hand-rebuilt blog loses its SEO even when every word of the text is right | Automatedarticles and pages recreated with authors, tags and publish dates, their SEO written to the metafields Shopify actually stores it in, and inline image URLs rewritten |
| Apps & app data | 10apps≈ 10 hrsabout 1 hr per app to reinstall, reconfigure and re-test | By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed | Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
A new legal entity does not reset your processing history. MATCH — the database processors use to screen high-risk merchants — follows the beneficial owner for five years, so opening a new company and applying again will flag the same decline reason. The only genuinely useful reason to form a new entity is to separate a compliant product line from a non-compliant one, but only if the entity structures are fully separate. Otherwise, save the cost and fix the claims.
Frequently asked
Will a new gateway turn my payments back on?
No. Your payments are off because a processor declined you, not because the gateway is wrong. A new gateway by itself does not fix the underlying reason — usually disease claims or a subscription refund dispute rate that is too high. You need an acquirer built for ingestibles, which means their underwriting focuses on your claims audit and your chargeback history, not a blanket refusal. The gateway you use is secondary. Find the acquirer first, then they will tell you which gateway to connect.
What reserve should I expect?
Most acquirers in this category hold 5–10% of your monthly volume in a rolling reserve, released 90–180 days after the transaction. The exact number depends on your volume, your chargeback rate and your supplier credentials. Larger orders and lower dispute rates get you to the lower end of that range. If you have a history of chargebacks or refunds from customers claiming the product did not work, expect the higher end or a longer hold period. Ask the acquirer upfront what they charge for this specific profile.
Do my product descriptions survive a store move?
Yes, if you migrate them correctly. The risk is that your claims descriptions — the exact language that triggers processor review — move with them word-for-word, and your new processor sees the same compliance problem the old one did. A migration is a good moment to audit every product page and rewrite disease claims as structure-and-function language. Do not just copy your old store. Use the move as a chance to fix the thing that got you declined in the first place.
What happens if I just rebrand and start over?
MATCH, the database processors use to screen merchants, follows the beneficial owner, not the company name. Opening a new store under a new business name with the same owner will flag the same decline reason. So you cannot evade an underwriting decision by rebranding. The only way forward is to fix the compliance problem — remove the claims, get the insurance and documentation — and apply to an acquirer who specializes in supplements with that profile fixed. It is slower, but it is the honest path.
Can I appeal the suspension and get my store back?
Appeals go to Shopify Trust & Safety and must address the specific policy violation named in your suspension email. If the email does not name a specific clause, state that in your appeal. Appeals work rarely, only if Shopify made a procedural error or mistook your identity. You cannot appeal Shopify's policy itself, and you cannot negotiate an exception to it. Shopify does not publish timelines for appeal decisions, and merchants commonly wait weeks with no reply.
Will my money be released if I appeal?
Any balance held at the time of suspension follows Shopify's standard payout schedule unless Shopify suspects fraud or illegal commerce. If they do, holds can extend 120 days or longer. An appeal does not accelerate payouts. If your appeal succeeds and the suspension is reversed, payouts resume on the normal schedule. If it fails, the money is typically released after the hold period, but Shopify may withhold it if they believe chargebacks or legal claims are likely.
What happens if I lose admin access during the suspension?
Once admin login is revoked, you lose API access. At that point your product catalog, order history, consent timestamps and metafields become unreachable through any Shopify tool. You will have only what you exported before access closed. CSV export is the fastest option but it is incomplete — it cannot carry metafields, videos, themes, discounts, menus or redirects. This is why exporting immediately, while you still have login, is the only step with a hard deadline.
Can I open a new Shopify store instead?
Not effectively. Shopify's policy applies to the person or entity behind the account, not just the account name. A new store opened under your name or a new company you control will be subject to the same underwriting and policy review. Shopify can suspend a new account if it determines the store is a reopening of the same business. The legitimate move is to migrate your store to a different platform and payment processor that will underwrite your category.
Will you turn my Shopify store back on?
No. We cannot appeal Shopify's decisions or reverse platform suspensions. What we do is migrate your store — catalog, images, orders, customers, SEO data, theme, metafields, videos, discounts, menus, redirects — from Shopify to a new platform built around a gateway that accepts your category. That is a fixed-price service starting at 247 pounds, and it requires that you have exported your data while admin access still worked. The move is from misfit underwriting to fit underwriting, not from suspension back to Shopify.
Move everything, verified twice, from $247
Pick a package and the migration order form unlocks immediately. Your existing store is only ever read from — we never write to it, so nothing you still have can be made worse. How the migration runs, step by step →