Shopify store suspended, and you sell research peptides. 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 research peptides
Shopify Payments is underwritten by Stripe, and Stripe explicitly prohibits the sale of research chemicals and drug analogs. The primary trigger is that research peptides occupy a legal grey zone: their entire commercial viability depends on the RUO (research use only) disclaimer. The secondary trigger is enforcement risk — any language suggesting human consumption, health benefit or therapeutic use converts your listing from a regulated-but-legal product into an unapproved pharmaceutical claim, which moves you from restricted to prohibited. FDA enforcement activity in this category is documented and rising.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document an official route for research peptides the way it does for hemp. Most merchants try to apply through the standard high-risk merchant form and get declined at the Stripe level without appeal. The honest equivalent is that you need a high-risk acquirer willing to underwrite the category explicitly — one that accepts the RUO model and has evaluated the regulatory environment. That underwriting is separate from Shopify's approval, and the acquirer will scrutinise your exact copy, your customer acquisition channels and your compliance documentation before deciding whether to take you.
It only helps if all of these are true:
- Your product pages must state research use only and exclude all human consumption language
- You must hold liability insurance that covers the RUO product category explicitly
- Your ads and marketing materials cannot imply or suggest any health benefit or therapeutic use
- You need documented evidence of compliance with any applicable state or local research chemical rules
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.
⚖️ Legal status is genuinely contested or actively changing
Shopify's suspension decision is not made by a payment processor; Shopify Trust & Safety makes it, and no payment acquirer anywhere can override it. If the legal status of what you sell is actively contested or changing, Shopify's risk appetite for that category may have simply shifted. An appeal to Shopify can take weeks or be denied. Moving to a new gateway does not help you—you have no store to send traffic to. Your only path is either to rebuild the entire store on a platform that has not suspended you, or to win the appeal. This is a platform problem, not a payments problem. No processor fix exists.
💎 High average order value, so fraud and disputes cost more per event
A single fraud dispute or chargeback on a high-ticket order is material to your reserve and your underwriting profile. Suspension isolates you from payment data at the worst moment—you cannot download transaction details, dispute evidence or customer communication logs while locked out. Download all order history, customer notes, payment processor reports and any evidence of fulfillment or delivery confirmation before access closes. High-AOV processors will ask for a complete dispute history and proof of fraud controls. If you cannot produce that history because you were locked out, underwriters will price you as higher risk.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For research peptides, these are the facts that move the decision:
Remove every phrase that implies human consumption or health benefit
This is the single highest-yield fix and where most applications fail. Any statement that your peptides treat, prevent, cure or manage a condition — inflammation, muscle recovery, cognitive function, anything — converts your offer into an unapproved drug claim. Audit your product descriptions, FAQs, testimonials, email sequences, blog posts and customer reviews for therapeutic language. Even indirect claims like 'supports recovery' or 'enhances performance' trigger automated flagging. RUO language must be plain and unqualified: 'for research purposes only' with no implication of end use.
Obtain and display current product testing documentation
Processors in this category ask for laboratory analysis showing exactly what is in each peptide and at what purity. You need COA (Certificate of Analysis) from an accredited third-party lab for every SKU you sell. This becomes part of your underwriting file and is often requested during periodic compliance reviews. Store these securely and be able to produce them on demand. Testing gaps are the second reason applications get declined.
Document your RUO liability insurance explicitly
High-risk acquirers require proof that your insurance covers research-use-only products and your specific liability exposure. A standard general liability policy often excludes chemical or pharmaceutical products. You need an endorsement or a dedicated RUO product liability policy. Bring the certificate to your underwriting call and highlight the coverage limits and the RUO language.
Build a compliance dossier covering sourcing and storage
Acquirers will ask where you source peptides, how you verify supplier credentials, how you store them and what your return or destruction policy is. This should be written down, dated and available to send to underwriting. The detail here signals that you understand the regulatory environment and are not running a grey-market operation. Include any state-level registrations or licenses if applicable in your jurisdiction.
What underwriting will ask you for
- Research use only attestation signed by your company officer
- Product liability insurance certificate naming the RUO peptide category
- Customer acquisition and marketing examples (ads, emails, landing pages)
- Laboratory certification or third-party testing results for each peptide
- Detailed description of your quality control and storage protocols
- Financial statements for the last 12 months
- List of all suppliers and their certifications
Getting underwritten for research peptides
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite research peptides. 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 research peptides
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 research peptide store's data is uniquely dangerous to move by hand because compliance metadata lives in metafields. Batch numbers, Certificate of Analysis file links, purity percentages, chain-of-custody data and storage condition records are all stored as reference or file metafields that a CSV export cannot carry. If you copy them naively, they persist as pointers to the old store's files, so product pages render but compliance documentation silently fails to load. On a regulated product category under active FDA scrutiny, that is a compliance failure, not a cosmetic bug.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,800images≈ 8 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 | 450descriptions≈ 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 | 1,350variants≈ 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 | 8,100metafields≈ 54 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 | 620records≈ 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 | 12videos≈ 48 minre-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 | 2,800customers≈ 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 | 8,500orders≈ 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 | 3menus≈ 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 | 18discounts≈ 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 |
| Blogs & pages | 50articles & pages≈ 3 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 | 12apps≈ 12 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?
You do not need a new legal entity to process research peptides. Many merchants think a fresh company will reset their profile — it will not. MATCH filing on a business owner persists for five years, and Stripe and other processors check it. A new entity does not erase your history and usually signals to underwriters that you are trying to evade the prior decline, which makes approval less likely, not more.
Frequently asked
Will Shopify Payments process research peptides?
No. Stripe, which underwrites Shopify Payments, prohibits the sale of research chemicals and drug analogs explicitly. You must use a third-party payment processor that has explicitly agreed to underwrite high-risk RUO peptide merchants. Approval is not guaranteed — it depends on your product claims, your compliance documentation and your processing history. The processor will run its own underwriting even after you connect it to Shopify.
Which payment gateway will actually work for me?
Several high-risk acquirers publicly underwrite research peptides: Authorize.net on a high-risk merchant account, PaymentCloud, Soar Payments and Easy Pay Direct. But which one will accept your application, at what rate and with what reserve, depends on your volume, your specific peptides, your marketing channels and your underwriting profile. Rather than cold-contact each one, the quote form on this page will help you match with brokers who know this category.
Will my peptide test results and batch data survive the store move?
No, if you move by hand. COA files, batch numbers and compliance metadata live in product metafields, and Shopify's CSV export cannot carry metafields at all. A migration service using the Shopify API can copy them, but you must verify the file links work in the new store. Always download and re-upload your lab documentation rather than relying on file pointers from the old store.
What reserve should I expect?
High-risk acquirers typically hold 10–25 per cent of your monthly volume in rolling reserve for 180 days or longer, depending on your chargeback rate and processing history. Some hold a lump-sum reserve upfront. This varies by processor and your individual underwriting. Budget for 90 days of operating costs not held in your main account before signing a merchant agreement.
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 →