Dutchie Plus is sunsetting: a dispensary's migration guide

If you built a custom storefront on Dutchie Plus, the news that it's winding down probably landed somewhere between annoying and alarming. You invested in a real website — your branding, your menu, your URL structure — and now the headless platform underneath it is going away. That's a genuine disruption, but it doesn't have to be a crisis. Handled deliberately, a forced migration is a chance to fix the thing that quietly limited you all along: who actually owns your online store. This guide walks through what the sunset means in practice, what's truly at risk, and how to move without losing the search traffic and customers you worked to build.

What the Dutchie Plus sunset actually means for you

First, the important distinction, because it changes everything about how worried you should be. Dutchie Plus is not the same as Dutchie POS. Dutchie Plus is the headless commerce layer — the API and storefront tooling that powered a custom, branded website. Dutchie POS is your point of sale: your inventory, your pricing, your source of truth at the register. The sunset affects the storefront layer, not necessarily the system you ring up sales on.

In plain terms: losing Dutchie Plus does not mean leaving your POS. If you run Dutchie POS, you can keep running it. What you need to replace is the website that sat on top of it. The decision in front of you is a storefront decision — where your menu lives and how it gets to shoppers — not a rip-out of your back office.

This is also worth saying plainly: a sunset is a business decision, not a failure on anyone's part. Companies retire products. The lesson for an operator isn't "pick a different vendor and hope they never sunset anything." It's to set up your storefront so that the parts that are genuinely yours stay yours no matter which platform renders them.

What's really at risk

Four things are exposed during a migration like this. Knowing which ones apply to you tells you where to spend your attention.

• Your domain. The single most important asset. If your store lived on your own domain, you're in a strong position — the address customers know and link to is portable. If it lived on a platform-controlled subdomain, that's the first thing to fix in the move.
• Your SEO equity. The ranking you've earned in Google is tied to your URLs. A migration done carelessly can drop you off the search results page; done correctly, it preserves most of what you've built. How much is at stake depends entirely on where your old pages lived (more on that below).
• Your customer relationship. The people who order from you are your customers — but only if the relationship runs through channels you control. Email lists, your domain, repeat ordering on a site that's yours. Think now about what you can export and where the relationship lives going forward.
• Your storefront experience. The look, speed, and flow your shoppers are used to. A migration is a chance to keep what worked and shed what didn't — but it's also a moment where a clumsy cutover can confuse regulars.

The decisions to make now

Before you evaluate a single replacement, settle three questions. They shape everything else.

Where will the menu live? This is the core choice. Your menu can render on your domain as real, indexable pages — or it can live inside a marketplace or an embedded widget that search engines barely see. If your goal is to rank and keep your own traffic, the menu has to be on your domain as genuine HTML, not buried in an iframe.

Who owns the domain? Log in to your registrar and confirm the domain is registered to your business, under an account you control, with up-to-date contact and billing details. If anyone set it up on your behalf — an agency, a former platform, a well-meaning relative — get it transferred into your name now. You cannot run a clean migration on a domain you don't fully control.

How will you avoid an SEO cliff? Start by inventorying where your current pages actually live. If your Dutchie Plus storefront ran on your own domain, you have real ranking equity to protect, and redirects will matter a great deal. If it ran on a Dutchie-owned subdomain, much of that equity was never transferable to you in the first place — which is precisely the cautionary lesson, and an argument for landing somewhere that keeps it yours from here on.

A calm, step-by-step migration

There's no need to rush this into a weekend. A measured sequence protects you at every stage.

1. Inventory your current setup. List your live URLs, your top-ranking pages, your domain and DNS records, your POS connection, and any customer data you can export (email lists, order history). You can't protect what you haven't written down.
2. Secure your domain. Confirm ownership at the registrar, lock the domain against unauthorized transfer, and make sure you have access to DNS. This is the foundation everything else points at.
3. Plan your redirects. Map each important old URL to its new equivalent so that customers and search engines following an old link land on the right page. Permanent (301) redirects tell Google the page has moved for good and pass along most of its ranking. Skipping this is the most common way operators lose traffic in a migration.
4. Pick a platform that puts the menu on your domain. Choose a replacement that renders your full menu as real, indexable pages on the address that's yours — and that syncs that menu from the POS you already run, Dutchie included. Connecting your POS keeps inventory and pricing accurate without re-keying anything.
5. Cut over without downtime. Build and preview the new store fully before you flip anything. Verify your menu syncs, your key pages exist, and your redirects are in place. Then update DNS to point your domain at the new site. Because you prepared in advance, shoppers experience a refreshed store — not an outage.

What to look for in a replacement

The sunset is forcing a choice you might not have made on your own timeline — so make it count. The criteria below are what separate a store you rent from a store you own. They aren't about any one vendor; they're the shape of a setup that keeps your assets in your hands.

• The menu lives on your domain. Real, indexable HTML with structured data and sitemaps — not an iframe or a marketplace listing where your traffic flows to someone else's brand.
• It's built to sync from your existing POS. Two-way sync with POSaBIT, Dutchie, and Flowhub is planned at launch to keep pricing and availability accurate, so changing your storefront never means changing your register.
• The pricing is a flat fee — never a percentage of your sales. A take-rate quietly taxes your growth; a flat monthly cost doesn't punish you for selling more. See how flat pricing compares.
• Compliance is built in. Age gating and the disclosures your state requires should be part of the platform, not a bolt-on you maintain by hand.
• You keep the customer relationship. Repeat ordering, your branding, and your domain all under your control — so the people who buy from you stay your customers, not a platform's.

A migration you didn't ask for is still a fork in the road. You can move sideways to another setup that rents you your own store, or you can use the moment to plant your storefront on ground that's actually yours — your domain, your search ranking, your customers. The work above is the same either way; the difference is where you end up. If owning that store outright is the direction you want to head, you can take a closer look at the platform features or join the waitlist to follow along.