Dutchie Plus support ends with 2026: a storefront migration checklist that keeps your rankings, your orders and your POS

The deadline is about your website, not your register. Decide the storefront path, keep your URLs, and finish well before the cutoff so you are not migrating in the busiest weeks of the year.

What is changing

Dutchie Plus is the developer layer that lets a dispensary build its own branded, "headless" storefront on top of Dutchie's e-commerce back end. In August 2025 Dutchie launched E-Commerce Pro, and in the same announcement its CTO wrote that Dutchie was committed to supporting legacy Plus customers through the end of 2026, recommending that Plus customers start the upgrade conversation. Dutchie describes E-Commerce Pro pricing as tailored to the number of locations and the complexity of the implementation.

If your site is a Dutchie-hosted menu or an embedded menu, this may not affect you. If an agency built you a custom storefront on the Plus API, it does.

Your three paths

None of these requires a POS switch. If you are also unhappy with the register, that is a separate decision; see Dutchie alternatives. Change one thing at a time.

The migration checklist

Before you choose

1. Confirm your date. Ask your Dutchie contact for the end-of-support date on your account, in writing.
2. List what the Plus storefront does today: menu, product pages, cart, checkout, pickup scheduling, delivery, loyalty sign-in, deals, age gate, analytics, review widgets.
3. Pull your search data. In Search Console, export pages and queries for the last 12 months. The pages that bring traffic are the ones you must not lose.
4. Crawl your own site. Save every URL, title and description. This is your redirect map's left-hand column.

Choosing

5. Score each path against the list from step 2. Ask each vendor how inventory reaches the menu (real-time, scheduled, or on page load), how orders reach the register, what happens when the POS is offline, and what you can export if you leave.
6. Ask about URLs. Can product, category and brand URLs keep their current paths? If not, can the platform serve permanent redirects at the edge?
7. Ask about order handoff. The sale must still be completed in the POS so the state receipt is created there. Confirm exactly how an online order becomes a ticket.

Building

8. Keep the domain. Never move domain and platform at the same time.
9. Keep URLs where you can. Every URL you keep is one you don't have to redirect.
10. Map every other URL to its closest new equivalent and set permanent (301 or 308) redirects, straight to the final page with no chains. Google treats 301 and 308 as permanent.
11. Carry over what search engines read: titles, descriptions, headings, product structured data, canonical tags and image alt text.
12. Block the staging site from indexing, and remember to remove that block at launch.

Launch week

13. Launch on a quiet weekday, not a Friday and not near a holiday or 4/20.
14. Switch redirects on, remove staging blocks, submit the new sitemap in Search Console.
15. Place real test orders at each store, pickup and delivery, and check they ring in the POS with the right items and taxes.
16. Spot-check URLs from your old crawl: each should land on the right new page in one hop.

The month after

17. Watch Search Console daily for two weeks: coverage errors, 404s, and pages whose impressions fall. Expect some movement; Google says ranking fluctuation is normal while it recrawls.
18. Fix internal links so they point at new URLs directly rather than through redirects.
19. Keep the redirects for at least a year.
20. Compare online orders week over week with the same weeks last year, by store.

When to start

Work backwards. A rebuild with a redirect map is weeks of agency time, and every Plus customer has the same deadline, so build slots will be scarce late in the year. Give yourself room to launch, watch and fix before support ends.

Where BudAlly fits

If you are taking path 3, BudAlly's white-label menu and branded app runs on your own domain with SEO you control, and every sale still rings in your POS so the state receipt is created there. If you are taking path 1 or 2, BudAlly sits beside whichever storefront you choose: it reads Dutchie for reconciliation, pricing and loyalty without touching the site. Either way, the Dutchie integration page lists what Dutchie's API reads and writes.