The Shopify Plus launch checklist (2026): a phased playbook

Roughly 70% of Shopify Plus projects hit significant post-launch issues inside the first 90 days. The damage is rarely the site itself. It is the silent email flows, the broken Meta pixels, the orphaned product reviews, the missing 301 redirects, and the phone calls that nobody planned to answer.

Most launch checklists are flat lists. They give you 50 boxes to tick with no sense of timing, no sense of risk, and almost nothing on customer support readiness. That is the gap this guide fills.

What follows is a phased playbook you can run from T-90 days through day 30 post-launch. It is built for a real Shopify Plus brand, not a hypothetical enterprise. We have written it the way we wish someone had written it for us: opinionated, with specific dollar risk per task, and with the support side treated as a first-class problem instead of a footnote.

Hear what AI support calls sound like for your store. Just paste your Shopify URL and get sample calls in under 20 seconds, no email required. Listen to demo calls for my store.

Why most Shopify Plus launches go sideways

The launch itself is the easy part. The first 30 days is where the real damage happens, and almost nobody plans for it.

Here is what actually breaks:

Apps collide under real load. The average Plus merchant runs 12 to 18 apps. In a staging environment, with one tester, they all behave. On launch day, with real traffic, the conflicts surface (AcquireX migration breakdown).
Pixels stop firing. Meta pixel events, GTM containers, GA4 event IDs all need to be re-installed on the new platform. Miss this and ROAS can drop 60% or more until somebody notices (ITGeeks).
Email flows go silent. Event IDs change on migration. Welcome series, abandoned cart, post-purchase flows stop triggering. US Shopify merchants typically lose 5 to 12% of email revenue in the first 30 days if this is not caught in advance.
Reviews orphan themselves. New product IDs after migration mean a perfectly migrated catalog with zero stars on every product, even though the reviews still exist in the database.
Phone support gets buried. WISMO ("where is my order") tickets account for 20 to 40% of all ecommerce support volume. On launch day that figure climbs to 50% or more. Launch-related call volume spikes are typically 2 to 9x normal (Edesk, BoldDesk).
Agencies hand off and disappear. Projects are scoped, budgeted, and staffed for delivery. The internal team takes ownership without context. Monitoring is absent.

This is why the playbook below is structured around time, not topic. Topic-based lists let you do the easy stuff first and ignore the risky stuff. A phased countdown forces you to confront integrations, redirects, and support readiness on a schedule, not when you feel like it.

How this checklist works

The full sequence is broken into seven phases:

T-90 days: foundation work (date, owner, data audit, contract)
T-60 days: build the new store (theme, products, Checkout Extensibility)
T-30 days: integrations, apps, B2B
T-14 days: testing, redirects, DNS prep
T-7 days: final QA and customer support readiness
Launch day: the hour-by-hour playbook
Day 1 to day 30: the post-launch protocol

Before you start T-90, three things should already be locked: the decision to move to Plus is made, a launch owner is named, and your agency (if you use one) is briefed. If any of those is fuzzy, fix that first. Otherwise the rest of this slips.

A few honest baselines on timing. A typical Plus implementation runs 6 to 12 weeks. Complex migrations with custom design and ERP integration push to 16 weeks or 3 to 6 months. A native B2B rollout using out-of-the-box features can run in 90 days. Catalog size barely affects the timeline. Approval cycles do.

T-90 days: foundation work

Most of T-90 is decisions, not building. Decisions made here save you weeks later.

Lock the launch date with a 2-week buffer. Pick a calm window. Avoid the 30 days before BFCM. Build a 2-week buffer for slippage. Then assume it will slip.
Name a launch owner. One person, decisions stop here. Not a committee. Not the agency. Someone inside your company who owns the calendar and the call list.
Audit your data. Pull a complete export of products, customers, orders, gift cards, subscriptions, custom fields, and media. Confirm subscriptions and gift card balances are actually exportable. They usually aren't via CSV.
Pick the migration tool. Native CSV works for catalogs under ~5K SKUs and clean data. Above that, or for historical orders, use Matrixify or LitExtension. Order matters: products first, then customers, then historical orders. Get this wrong and customer purchase history detaches.
Document every integration. ERP, 3PL, helpdesk, email, SMS, reviews, returns, subscriptions, loyalty, search. Note the data flow direction and the credentials owner. Half your launch friction comes from forgotten integrations.
Sign the Plus contract. Pick the term. The 3-year contract is roughly $2,300/mo, the 1-year contract is around $2,500/mo. Once your monthly GMV passes $1M, Shopify replaces the flat fee with a 0.25% revenue share. Budget the real number: most $1M/yr brands end up at $5,000 to $8,000/mo all-in once apps and dev are counted.
Plan your URL map. Pull a full crawl of the current site with Screaming Frog. Every product URL, every collection URL, every blog URL, every static page. This becomes your 301 map at T-14.

Risk framing: skip the data audit and you find out about orphaned subscriptions and gift cards weeks after go-live, usually from a customer email. There is no clean fix at that point. We have seen brands eat thousands of dollars in goodwill credits to make it right.

This is also the right moment to read up on the broader Shopify migration timeline and pick a Shopify migration agency if you don't already have one. Our Shopify replatforming guide walks through the platform-selection part in more depth.

T-60 days: build the new store

This is where the bulk of the actual building happens. The goal is to have a working store on a dev URL by the end of week T-60.

Pick the theme. Use a Dawn-based or vetted paid theme. Custom theme dev only if your brand demands it. Custom themes can add 4 to 8 weeks and a lot of QA risk.
Build the development store. Lock branding (colors, type, logo, favicon, social meta). Build the homepage, collection templates, product templates, cart, and any custom landing pages.
Run the product migration. Strict order: products, then customers, then historical orders. If you are coming off a platform that nested categories, plan the collection structure now (smart collections vs manual).
Set up Checkout Extensibility from day one. This is non-negotiable for 2026. The Plus Checkout Extensibility deadline already passed in August 2025. Since April 2026 the legacy checkout.liquid customizations have been broken. Build with Checkout UI Extensions and Shopify Functions, not Scripts.
Plan the Shopify Scripts migration. If you are coming from a Plus store running Scripts for discount, shipping, or payment logic, those break on June 30, 2026. You can no longer edit them after April 15, 2026. Migrate the logic to Functions during this phase, not after launch.
Install your core apps. Helpdesk, email, reviews, returns, shipping, loyalty. Get them working in the dev store before you start configuring flows.
Set up Shopify Flow. Automate the routine stuff: tag high-value customers, route fraud-flagged orders, notify your warehouse, escalate negative reviews. Flow is one of the genuinely useful Plus features and most brands underuse it.
Configure Markets if international. One Markets instance per region (or one per currency) depending on tax setup.
Plan B2B if it applies. Companies, catalogs, quantity rules, custom pricing.

Risk framing: skip the Checkout Extensibility build now and your launch breaks the day Scripts deprecates. Skip the Flow setup and your team spends the next year tagging customers by hand.

The full feature stack is documented in our Shopify Plus features guide. If you are deciding between Plus and an enterprise platform, Shopify Plus vs Commerce Cloud covers that decision.

T-30 days: integrations, apps, B2B

T-30 is the integration crunch. Every system that touches your store needs to be wired to the new instance and tested with real (or realistic) data.

Connect every integration to live. ERP, 3PL, WMS, helpdesk, search. Document the test cases per integration. Run them. Document the failures.
Wire analytics the new way. Google Analytics 4, Google Tag Manager, and the Customer Events tab in Shopify (the Plus-only Web Pixels framework that replaces the old Additional Scripts box). Verify every conversion event fires correctly.
Re-set every email flow. Welcome, abandoned cart, post-purchase, browse abandonment, win-back. Event IDs change on migration. Flows go silent for 30 days if you do not re-wire them. The cost: 5 to 12% of email revenue in the first month, per ITGeeks migration data.
Migrate reviews carefully. Product IDs change on import. Reviews orphan unless you use a review platform that re-maps to new IDs (or you manually re-map them post-migration). A perfect catalog with zero stars on every product is a real launch disaster, and it is shockingly common.
Set up B2B if relevant. Companies, catalogs, quantity rules, payment terms. The native Plus B2B stack works well enough that you do not need a third-party app for most use cases.
Schedule Launchpad events if you have a launch promo, drop, or sale. Launchpad handles the timed switch from "draft" to "live" without you sitting at a keyboard at midnight.

Risk framing: broken Meta pixel equals ROAS dropping 60% or more until somebody catches it. Silent email flows equal 5 to 12% email revenue gone in 30 days. These two failures alone account for more lost revenue than any other launch issue we see.

If your email platform is part of this work, our Shopify marketing apps breakdown is worth a read, and Klaviyo alternatives covers the options if you are reconsidering the email side.

T-14 days: testing, redirects, DNS

Two weeks out is when the abstract becomes concrete. Everything you have built gets tested by people who didn't build it.

Build the 301 redirect map. Every old URL maps to a new URL. Use Screaming Frog to crawl the old site, then map manually for products and collections. Use a pattern for predictable URLs (e.g., /products/old-handle → /products/new-handle). Avoid JavaScript redirects. Use Shopify's native URL Redirects tool.
Test the order flow end-to-end. Multiple payment methods (Shop Pay, PayPal, Klarna, credit card). Multiple shipping zones. Mobile, tablet, desktop. Refund, exchange, gift card redemption, store credit. Failed payments. Promo code stacking. Tax variations by state. Do not skip a single combination.
Submit the new XML sitemap structure to Google Search Console (you will resubmit on go-live day).
Reduce DNS TTL to 300 with your domain registrar. Do this a week early so the lower TTL is already propagated when you cut over. Most brands forget this and end up with a 4-hour DNS lag on launch day.
Set up monitoring. Uptime (Pingdom, UptimeRobot), error rate, Core Web Vitals (LCP, INP, CLS). You want a baseline before you go live so you can spot regressions.
Run a real $50 ad test. Spend actual money. Confirm the Meta pixel, Google Ads tag, and GA4 conversion events fire end-to-end. Catch broken events here, not on day 1 of the launch.
Verify the GTM container is published, not just saved.

Risk framing: miss redirects and you lose 30% or more of organic traffic in two weeks, usually permanently. Skip the ad test and you find out about broken pixels at the worst possible time, when you have launched and turned ads on.

Our Shopify SEO guide and ecommerce SEO covers the long tail of post-launch organic protection. And Shopify conversion rate optimization is worth reading before launch, not after.

T-7 days: final QA and customer support readiness

The last week is part QA, part operations prep. The QA part is obvious. The operations part is what almost everyone gets wrong.

QA pass:

Walk every page on the new site, on mobile and desktop. One person, two hours, no shortcuts.
Submit five test orders covering different scenarios.
Trigger every email automation manually.
Verify the cart and checkout from two devices.
Test the password reset flow.
Confirm the contact form goes somewhere a human reads.

Operations prep:

Brief customer service on the new admin. New ticket views. New escalation paths. New refund workflow. They will be the first to see launch-day problems.
Plan for the call volume spike. WISMO calls jump 2 to 9x in the first week post-launch (Edesk launch spike data). Fully-loaded cost per support ticket runs $40 to $80. A 5x spike on a normal day of 100 tickets means 400 extra tickets at $50 each, or $20K in support cost in one week. That number gets your attention.
Wire phone support to your helpdesk (Gorgias, Richpanel, or whatever you run). If calls aren't logged as tickets, you will not know how bad it is.
Document the top 20 questions customers will ask. Tracking, returns, exchanges, account issues, payment problems, shipping delays. These power your self-serve content and your AI phone agent script.
Back up the old site. Keep it for 1 to 2 months. You will need to look at something you forgot to migrate. It always happens.
Notify your integration partners of the go-live date.
Pause paid advertising for the cutover window if your URL structure is changing. Dead-link ads cost real money.

Risk framing: WISMO accounts for 20 to 40% of ecommerce support tickets in normal times and 50%+ during peaks. If you have not planned phone coverage by T-7, you are planning to lose revenue on launch day.

This is also a good moment to read Shopify Plus customer service and WISMO calls so you understand the shape of the spike you are about to hit. Our 24/7 ecommerce phone support guide covers the coverage models.

Customer support readiness: the section nobody runs

Every other Plus launch checklist either skips this or treats it as one bullet. That is a mistake. Here is what to lock before you flip DNS.

Three things to nail down:

Phone coverage. Who answers calls? What hours? Logged into which helpdesk? Most Plus brands set up email and chat for launch and forget phone. Then launch day hits and the phone rings constantly.
Helpdesk escalation rules. When does chat go to email? When does email go to phone? When does phone go to a human supervisor? Write the rules down. Pin them in your helpdesk.
Self-serve content. A tracking page that resolves WISMO without a human. A returns page that handles 80% of return requests without a human. An FAQ that answers the top 20 questions.

The phone problem. If you have a support team, brief them on what's launching, what's changing, and what to expect. If you don't have a phone team, you have two choices: hire one, or use an AI phone agent.

Hiring a phone team for a launch window is expensive and rarely lasts. AI phone agents are the modern alternative. They keep the channel open without payroll.

Ringly.io is AI phone support for Shopify brands. Instead of hiring and training a phone team, the AI handles inbound calls 24/7: order status, returns, product questions, abandoned cart rescue. Across 50+ brands, the AI resolves 73% of calls autonomously at roughly $0.42 per resolved call. Plans start at $349/mo with a 65% resolution guarantee. Live in under an hour.

What to test in the final week, regardless of how you handle phone:

Place a real test call. Ask about an order. Time the resolution.
Place a real return request via your tools. Time the resolution.
Run a real WISMO scenario end-to-end (lookup, status, follow-up).

If any of those takes longer than five minutes, you have a problem to fix before launch.

If you're on Shopify, Ringly.io gets a fully working AI phone agent answering your calls in about three minutes. Try it free for 14 days.

More detail on the phone side in our Shopify voice agents breakdown, AI phone agents for Shopify, AI receptionist for ecommerce, and the broader ecommerce phone support guide.

Launch day playbook

Launch day is mostly DNS, monitoring, and not panicking. The work is already done at this point. The job is to flip the switches in order and watch the dashboards.

Morning of launch (in order):

Deactivate test mode on payment providers. Confirm live payment processing.
Switch your primary domain in Shopify admin.
Update DNS records: A record to Shopify's IP, CNAME to your Shopify URL.
Remove the storefront password.
Verify the site loads on the live domain (use multiple devices, multiple ISPs, mobile networks).
Import the 301 redirect map.
Resubmit the sitemap to Google Search Console.
Send the customer reactivation email (legacy customers need to set new passwords).
Activate any Launchpad events.

Hour 1 to 4:

Watch the order flow. First five orders should complete without intervention.
Watch the error rate. Anything above baseline is a problem.
Watch page speed (Core Web Vitals dashboard).
Watch the support queue. WISMO surge usually starts in hour 2 to 4.

Hour 4 to 24:

Spot-check redirects. Pull 20 random old URLs, confirm they hit the right new URL.
Verify ad pixels are firing on the live site.
Confirm one email flow fires end-to-end (place a real order, watch the post-purchase email arrive).
Pause unrelated marketing campaigns for the first 24 hours so you can isolate launch traffic in analytics.

Risk framing: the biggest launch-day mistake is going dark on monitoring once the site is up. Day 1 problems cost 10x what week 1 problems cost because they compound. Stay on the dashboards.

Day 1 to day 30: the post-launch protocol

Most launches fail here, not at the launch itself. Block calendar time now for these three checkpoints.

Day 1:

Redirect spot-check (20 random old URLs)
Payment confirmation (refunds, exchanges, gift cards all working)
One full email flow check (trigger and confirm delivery)
Ad pixel firing check (Meta, Google, GA4)
Call volume baseline (you can't manage what you can't measure)

Day 7:

Full redirect crawl with Screaming Frog. Every old URL should return 301 to the right destination.
GA4 conversion sanity check. Are conversions tracking? At baseline rate?
Helpdesk ticket categorization. Top 10 question types this week. Trend up or down vs baseline?
Review re-mapping confirmation. Spot-check 20 products. Reviews showing? Star counts right?
Integration health. ERP sync timing, 3PL order push, helpdesk thread creation, email provider event flow.
Phone call volume vs baseline. Resolution rate if you are using an AI agent.

Day 30:

Organic traffic check vs pre-launch baseline. Any drop should be diagnosed and fixed.
Email revenue check. Should be at or above pre-launch monthly run rate.
Ad ROAS check vs baseline. If down significantly, your pixels are probably still broken.
Support ticket per order rate. Higher means launch fallout still hitting your team.
CSAT or NPS check.

Risk framing: issues found at day 30 cost roughly 10x what day 1 issues cost. They have compounded in the analytics, in customer perception, and in cumulative lost revenue. Block the time now.

Our ecommerce customer service guide covers the post-launch support shape in more depth, and customer service response time benchmarks gives you targets for the day 30 check.

Ready to see what AI phone support looks like during your launch? Start your free trial. Setup takes about three minutes.

Frequently asked questions

How long does a Shopify Plus launch take?

A typical Plus implementation runs 6 to 12 weeks. Custom design and ERP integration push that to 16 weeks. Native B2B rollouts can hit 90 days. Catalog size barely affects the timeline; approval cycles do.

What is the single biggest risk in a Shopify Plus launch?

Broken analytics on launch day. A broken Meta pixel can drop ROAS by 60% until someone catches it, and silent email flows can cost 5 to 12% of email revenue in the first 30 days. These two together cause more lost revenue than any other launch issue we see.

Do I need an agency to launch on Shopify Plus?

Not always. Lean brands with one technical person and a clear roadmap can launch native. Brands with custom design needs, complex integrations, or international rollouts should use an agency. Either way, name an internal launch owner who survives past the agency hand-off.

What is the Checkout Extensibility deadline?

For Plus stores, the original deadline was August 28, 2025. Since April 2026, the legacy checkout.liquid customizations are broken. Shopify Scripts shut down on June 30, 2026, so any discount, shipping, or payment Scripts need to migrate to Functions before then.

How do I handle phone support volume on launch day?

Wire phone support to your helpdesk before launch so calls log as tickets. WISMO accounts for 20 to 40% of normal support volume and 50%+ during peaks. If you don't have a phone team, an AI phone agent like Ringly.io handles inbound calls 24/7 and resolves 73% of them autonomously at roughly $0.42 per call.

How much should I budget beyond the $2,300/mo Plus fee?

A realistic all-in monthly cost at $1M/yr revenue is $5,000 to $8,000 once apps, transaction fees, and occasional dev are counted. At $10M/yr, plan for $15,000 to $25,000/mo. Apps alone for a mid-size Plus store run $1,000 to $3,000/mo.

What is a 301 redirect map and how detailed does it need to be?

A 301 redirect map is the list of every old URL mapped to its new URL. It needs to cover products, collections, blog posts, and static pages. Use Screaming Frog to crawl the old site. Avoid JavaScript redirects, use Shopify's native URL Redirects tool, and keep the redirects live for at least one year.

A final, opinionated note

Most Plus launches fail at the post-launch handoff, not the migration. The site goes live, the agency leaves, the team breathes out, and a week later somebody notices that ROAS dropped, the email flows are silent, the reviews are zero, and the phone is ringing nonstop.

If you only do three things from this checklist, do these:

Build the 301 redirect map and verify it the day after launch.
Re-wire every analytics and email event before launch, and test them with real money.
Decide who answers the phone before launch day, not after.

The phone one is the cheapest fix and the one almost nobody plans for. If you don't have a phone team, the AI phone agent route is the lowest-effort version of solving this problem.

If you're running a Shopify brand and want phone support live by tomorrow morning without hiring anyone, try Ringly.io free for 14 days. The AI is live in under an hour, resolves 73% of calls autonomously, and starts at $349/mo with a 65% resolution guarantee.

Article by Ruben Boonzaaijer. Co-founder of Ringly.io. We build AI phone support for Shopify brands so they can scale support without hiring a phone team.