Shopify banned vape sales with two weeks' notice. Whose store is it, really?

On June 24 Shopify notified merchants that it no longer supports the sale of Electronic Nicotine Delivery Systems, and gave them until July 8 to pull the listings. Reuters reported it, Shopify confirmed the notice on July 10, and stores started disappearing. If you sell vape hardware or e-liquid on Shopify, this is not a rumor and there is no appeal process. And if you don't sell vapes at all, it's still worth five minutes of your attention, because the mechanism that just removed those stores applies to every catalog on a hosted platform, including yours.

What actually happened?

Here's what is confirmed as of this writing, and it's worth separating that from the noise, because there's a lot of noise:

• June 24, 2026 - Shopify sends merchants a notice: "Due to changes in legal restrictions on the sale of Electronic Nicotine Delivery Systems (ENDS), Shopify no longer supports the sale of these products." Removal deadline given as July 8. Some merchants in the community thread report being told July 7.
• Early July - Merchants start reporting stores closed or products removed. Non-compliance means account suspension or termination.
• July 10, 2026 - Reuters reports the story and Shopify confirms the notice publicly.

The background is regulatory pressure, not a change of heart. A coalition of U.S. state attorneys general and city law enforcement had been pushing Shopify over illegal vapes sold through stores on its platform. Shopify made a business decision about its own exposure, and every merchant in the category paid for it.

The part that made this harder than it needed to be: for days there was no clear guidance in Shopify's Help Center or Acceptable Use Policy. Merchants were piecing together a compliance deadline from a notice email, a community forum thread, and news coverage. Scope questions went unanswered. Is empty hardware in? Batteries, vaporizers, empty cartridges, empty pods? Is this U.S. only or global? Merchants were asking each other, because there was nobody else to ask.

If you're affected and still reading: contact Shopify Support directly, watch your admin notices and the email on the account, and don't rely on a blog post (including this one) for your compliance timeline. Get it in writing from them.

Why this matters even if you've never sold a vape

Strip out the product category and look at the shape of what happened. A platform changed its acceptable use policy. Thousands of businesses had two weeks to remove their inventory or lose their store. The policy applied to FDA-authorized products too, so being legal and compliant wasn't the deciding factor. The deciding factor was the platform's own risk calculation.

That's not Shopify being uniquely villainous. Any hosted platform would do the same thing, and most have. It's the deal you sign when you rent your storefront: you get someone else's uptime, someone else's PCI scope, someone else's checkout, and in exchange they get a veto over what you sell. Most of the time the veto is invisible. It's invisible right up until the week it isn't.

Ask yourself which of these you could survive with two weeks' notice: your category becomes restricted, your payment processor decides your risk profile changed, an app you built a workflow around gets acquired and sunset, or your checkout customization stops being possible because the platform closed that surface. None of those are hypothetical. All of them have happened to real merchants, and none of them are things you get a vote on.

What does "owning your store" actually mean?

Self-hosted open source is the other side of that trade. With Adobe Commerce, Magento Open Source, or Mage-OS (the community-run distribution), you're running code you possess on infrastructure you chose:

| Question | Hosted SaaS | Self-hosted open source |
| --- | --- | --- |
| Who decides what you may sell? | The platform's AUP | You, within the law |
| Who can shut off your store? | The platform | Your host, and you can change hosts |
| Where does your data live? | Their database | Your database, your backups |
| Can you fork the checkout? | Only where they allow it | Anywhere in the code |
| What happens if pricing doubles? | You pay or you migrate | You move servers |
| Who sets the upgrade timeline? | The platform | You |

Let's be honest about the limits, because the vape story proves the point in both directions. Open source does not put you outside the law. If a product is illegal to sell in a state, self-hosting doesn't change that. Your payment processor still has an acceptable use policy, and for high-risk categories that's often the real gate. Your host has terms too, though hosts are commodities and swapping one is a weekend, not a rebuild.

What open source gives you isn't immunity. It's standing. Nobody sends you a two-week notice about your own catalog. When something does force a change, you decide what to change and when, and you still have your store, your data, your customers, and your integrations on the other side of it. That's the whole difference, and it turns out to be a big one on the week it matters.

Is Magento overkill for a small store?

Sometimes, honestly, yes. If you sell thirty SKUs with no B2B pricing, no ERP, and no complex catalog logic, a hosted platform is a reasonable trade and we'll tell you so.

The calculation changes when any of this is true: you're in a category that platforms get nervous about, you have customer-specific pricing or quote workflows, you integrate deeply with an ERP or PIM, your catalog has real structural complexity, or your margins have grown to where platform fees and per-transaction cuts are a line item you notice. At that point you're paying rent on a building you're not allowed to renovate.

What migrating off Shopify actually involves

No hand-waving. A real migration is products, variants and media; customers with their addresses and order history; the order archive itself; a URL map with 301 redirects for every product, collection and page you're keeping (skip this and you donate your rankings to competitors); your payment and shipping setup rebuilt; whatever your apps were doing rebuilt as extensions or integrations; and a plan for the theme, because Liquid doesn't port.

The app inventory is usually where the surprises live. Merchants tend to know their product count and forget the eleven apps quietly running subscriptions, bundles, loyalty and tax. Each one is a decision: native feature, extension, or custom build.

It's a project, not an afternoon. But it's a finite project with a finish line, and at the end you own the thing.

If you're the one holding a takedown notice

We've moved stores between platforms in both directions for years, including migrations where the honest answer was to move to a hosted platform. So this isn't a pitch that open source wins every time. It doesn't.

But if you just found out your storefront was never really yours, that's a bad week and a clarifying one. We can help you scope what a move to Magento or Mage-OS actually looks like for your catalog: what ports cleanly, what has to be rebuilt, what it costs, and how long you'd be in transition. If the answer is "stay where you are," we'll say that too.

Get in touch, or take a look at how we build and migrate ecommerce stores.