Text version of this lessonExpand
Shopify setup is not clicking through every settings page. It is making account, markets, checkout, tax, notifications, and permissions ready for launch.
The previous lesson leaves a DNS and business email authentication checklist: primary-domain and HTTPS evidence, role-inbox receipt, official sending plus SPF / DKIM / DMARC state, and account/recovery records. It explains how to accept the address and contact path; it does not complete Shopify Admin, Markets, payment, or checkout for you.
That checklist does not prove store details align, a primary market can go public, payment eligibility passed, a test order completes, notices arrive, or orders, fulfillment, and launch are released. It leaves infrastructure evidence and an explicit unresolved item only; it is not proof that Admin or the store is complete.
Enter this lesson only when address, receiving, official sending, and recovery already have reviewable records and Shopify Admin configuration is the earliest blocker. The output is a Shopify admin setup acceptance sheet, not a conclusion that the store is open or ready for traffic.
Read one order through before opening the task board
On a first read, treat Shopify Admin as the back office for one order. A shopper sees a product and price in a defined market, checks out, pays, and receives confirmation. You should be able to find that same order in Orders, notifications, and data tools. Markets, Payments, notifications, permissions, and events live on separate screens, but they need to agree on the same record.
Use this lesson's 20oz tumbler case. Start with one hero SKU for the US market, where the mobile product page shows US dollars and the market's shipping rate. After a test payment, the admin creates an order, a confirmation email arrives, and GA4 or the pixel records purchase. A payment button without a complete test order, or an admin order without a customer email, means the order path is still incomplete.
Set store identity, the primary market, and basic access first. Then verify payment and checkout, followed by notices, shipping policies, and data evidence. Later checks depend on the information left by earlier ones. Do not expand payments or markets while the entity, default currency, or recovery email is unsettled. Do not use theme polish to decide whether the store can sell before the test order has finished.
- 1. Read the order first: Connect the market, price, and shipping promise to checkout, payment, the admin order, and notices.
- 2. Then find the evidence: Ask what screenshot, order ID, email, or event record each step should leave behind.
- 3. Use the task board last: The cards below are for practice and recordkeeping, not a prerequisite for understanding the lesson. Checkout and payments open first to separate a visible button from a completed order.
Accept the Shopify admin as an operating base
Beginners often treat theme installation as store setup. The real launch risk sits in markets, currency, tax, checkout, notifications, permissions, and security.
This lesson uses an admin acceptance sheet. Any setting that affects payment, shipping, notifications, permissions, or data deserves a business check.
Decision lens for this lesson
- Admin setup: Making the store foundation match the target market and operating model.
- Permission: What each team member can view or change inside Shopify.
- Checkout setting: A setting that affects payment, contact details, tax, address, or order notices.
Even when one item has pass evidence, do not record the whole store as complete. It only shows that this part can be reviewed. Reliable collection, refunds, and deeper payment questions still need their own checks.
Put that judgment back into one test order next: what must Shopify Admin catch today, and which gaps cannot be hidden by a theme, homepage, or another market. Set that boundary before moving into the detailed admin tasks.
Lesson output: Shopify admin setup acceptance sheet. Use this output to decide whether the lesson is truly complete.
How this connects: after Shopify setup, build store structure and payment
Shopify setup is not finishing settings. It means account control, Markets, checkout, tax logic, notifications, permissions, and test orders are ready to verify.
- Store route: Shopify store structure to connect navigation, Markets, cart, and policy access into a user path.
- Payment route: payment gateway setup to prove checkout and payout with test orders, not settings alone.
Lesson boundary: make Shopify admin catch the order before polishing the store
This lesson does not cover every Shopify setting or turn into page design, payment risk, or global market strategy. It does one job: use one test order to prove admin setup is reviewable.
| Boundary | This lesson owns | Next or later lesson owns | Acceptance line |
|---|---|---|---|
| Admin setup before page polishing | Store details, Markets, checkout, notifications, permissions, recovery, data events, and the test order. | shopify-store-setup handles navigation, homepage, collection pages, cart entry, policy access, and the shopper path. | If one test order cannot move from storefront to admin, a polished homepage still does not prove the store is operational. |
| Payment path first | Whether payment, order creation, notices, cancellation, or refund can work, with test mode and admin order evidence. | payment-gateway-setup goes deeper into gateway choice, payout, disputes, KYC, PayPal, and bounded real small-order checks. | Here we only decide whether Shopify admin catches the order, not turn this lesson into a full payment-risk lesson. |
| Release one real primary market first | The first real selling market must explain currency, language, shipping, tax, and checkout state. | Cross-market pricing, localization, tax, and complex compliance move later to Cross Border, Profit Finance, and operating lessons. | Do not set global markets Active before one primary market is accepted. |
Official admin path map: know where to check each setting
Beginners often get stuck not because they are lazy, but because they do not know which Shopify admin page owns which decision. Use this map to connect admin path, field, and review record before you change defaults.
| Admin path | Check first | Acceptance record | Official reference |
|---|---|---|---|
| Settings -> Store details | Store name, legal name, address, timezone, default currency, support email. | Field values, responsible lead, review date, and entity source. | Shopify new store checklist |
| Settings -> Markets | First selling market, currency, language, product availability, and markets not released yet. | Active / Draft state, primary-market URL, and mobile checkout test time. | Shopify Markets and domains |
| Settings -> Payments | Shopify Payments eligibility, third-party gateway, PayPal, Shop Pay, and test mode. | Test order ID, payment state, and test-mode-off record. | Testing Shopify Payments |
| Settings -> Checkout | Contact method, address fields, marketing opt-in, privacy, and checkout experience. | Mobile checkout path, customer notification email, and field-level issue notes. | Checkout contact method |
| Settings -> Shipping and delivery | Shipping zones, rate names, amounts, packages, and countries you do not ship to. | Primary-market shipping table, checkout display value, and paused regions. | Shipping zones and rates |
Use the table this way: every field change needs a reason, a responsible person, and a review date. Admin setup is not one-time decoration. It is the ledger payment, ads, support, and data review will all rely on later.
60-minute admin setup walkthrough: do not skip evidence
When you enter Shopify admin for the first time, do not spend the whole session on theme colors and homepage banners. A steadier path is to use the first hour to accept six launch-critical areas: store identity, access and recovery, Markets, payment and checkout, notifications and policies, and data events. Keep records or notes at every step because payment review, ad launch, support work, and order review will all come back to this evidence.
| Time | Admin path | Action | Evidence | Stop rule |
|---|---|---|---|---|
| 0-8 min | Settings -> Store details | Check store name, legal name, address, timezone, default currency, support email, and invoice inbox. | Settings path record, entity source record, responsible lead, and review date. | If legal name, address, or email is not settled, do not continue to payments or policies. |
| 8-18 min | Settings -> Users and permissions | Split store lead, operator, agency, finance, and support access; enable 2FA for key accounts. | Staff permission record, 2FA state, backup admin, recovery email, and backup-code location. | While the main account is still shared, do not expand theme, payment, app, or data access. |
| 18-30 min | Settings -> Markets | Release only the first real selling country and confirm currency, language, product availability, shipping, tax display, and Active / Draft state. | Markets record, target-market product page, mobile checkout, and list of markets not ready to sell. | If shipping, tax, or policy promises do not align, keep that market in Draft. |
| 30-42 min | Settings -> Payments / Checkout | Confirm whether Shopify Payments is available; if not, document third-party gateway, PayPal, accelerated checkout, and test mode. | Test order ID, payment state, admin order, customer email, team notice, and cancel or refund path. | If test mode is still on or no complete test order exists, do not send live ad traffic. |
| 42-52 min | Settings -> Notifications / Policies | Sample order confirmation, shipping notice, refund policy, shipping policy, privacy policy, and Contact details. | Notification email record, policy links, support inbox receipt, and correction notes for mismatched promises. | If notices are not received or policies are blank templates, do not open public orders yet. |
| 52-60 min | Shopify order / GA4 / Pixel | Use the test order to check view_item, add_to_cart, begin_checkout, purchase, or matching base events. | Event record, Shopify order ID, reconciliation rule, repair list, responsible lead, and next review time. | If purchase is invisible or order events cannot reconcile, do not judge ad quality yet. |
The point of this walkthrough is not speed. It turns "I think I set it up" into "I know which setting affects which part of the order experience." If you hit a stop rule, fix admin first before moving into store structure, policy pages, payment gateway setup, or data integration lessons.
Shopify Solves Infrastructure, Not Product-Market Fit
Shopify is strong for 0-to-1 store launches because it bundles storefronts, checkout, payment integrations, themes, and international selling tools. But it is still only the infrastructure layer. It will not choose your market, fix your offer, or make your traffic convert automatically.
Who Shopify Fits Best
- Teams that want to launch fast: you do not want to build store, cart, and payment systems from scratch.
- Brands needing international infrastructure: you expect to manage markets, currencies, languages, and global shipping logic.
- Operators willing to pay a platform subscription: you prefer faster execution and stability over lower software cost with more technical burden.
- Sellers building long-term brand assets: not only depending on marketplace traffic.
Two Mistakes to Avoid First
- Let’s just open the store first: if entity, payments, and market direction are unclear, you will end up rebuilding key parts.
- Shopify will solve growth for me: it gives you tools, not automatic demand or conversion.
How to Choose a Shopify Plan: Check Operating Boundaries Before Price
Plan choice is not only a monthly-price decision. It affects transaction fees, team access, theme capacity, and the real operating cost of the store. Most beginners do not need a higher plan immediately, but they should not look only at the subscription fee either. The better question is not which plan sounds more advanced; it is whether this store needs team permissions, reports, international markets, or a lower transaction-fee boundary now.
Shopify’s current pricing page shows about $29 USD/month when billed yearly.
This is a practical starting point for validating product, pages, payments, and first traffic.
Shopify’s current pricing page shows about $79 USD/month when billed yearly.
Upgrade only when permissions, rates, and team workflow really need it.
Shopify’s current pricing page shows about $299 USD/month when billed yearly.
Shopify’s current pricing page lists it from about $2,300 USD/month on a longer-term agreement.
Most beginners do not need to start here unless organization, B2B, checkout, or compliance complexity is already blocking the business.
Official Boundary Check Before Launch
- Basic is enough for most new stores while you validate product, page structure, payments, and demand.
- If you cannot use Shopify Payments, remember to factor in third-party transaction fees too.
- Pricing varies by region, billing cycle, and promotion, so confirm the official pricing page before you commit, and record the plan, billing cycle, current promotion, transaction-fee boundary, and renewal reminder in your acceptance sheet.
- The payment path needs its own acceptance check: Shopify Payments depends on business location, business type, product category, compliance details, and 2FA. If it is unavailable, configure a third-party provider and a test-order path early.
What to Watch During Account Registration
Shopify’s onboarding flow is simple, but mistakes made here tend to carry forward into domain setup, payment configuration, billing, and permissions.
Recommended Registration Flow
Registration-Stage Reminders
- Keep the admin email aligned with the address you want to use for billing, payment, and theme purchase notices.
- Avoid creating too many duplicate test stores early. It creates unnecessary billing and asset confusion.
- If multiple people will work in the store, design access and permissions early instead of sharing one main account.
The 6 Admin Settings to Do First
Many beginners start with homepage edits and theme styling immediately. That is the wrong order. Your first job is to define how the store will operate.
Store information
Set store name, legal details, contact information, timezone, base currency, and shipping origin.
Markets
Create markets by country or region and decide which should be Active now versus Draft for later.
Shipping
Define where you ship, expected transit times, and how shipping charges will work.
Payments
Confirm Shopify Payments availability, 2FA, third-party provider needs, and whether you can run a test order through test mode or Bogus Gateway.
Policy pages
At minimum, prepare refund, privacy, terms, and shipping policies instead of leaving default blanks.
Notifications
Review order emails, shipping emails, and support contact paths before traffic starts.
Why Markets Should Be Set Early
- Customer experience changes by market: pricing, currency, language, URL structure, and product visibility can all differ.
- Shopify supports Draft vs Active market states: you can stage markets before showing them publicly.
- Page copy and shipping promises depend on market setup: if markets are undefined, many page assumptions become unreliable.
Payments Are the Most Critical Setup Layer
New operators often treat payments as a small settings step. In reality, checkout and payout readiness determine whether the store can sell at all.
Payment Decision Logic
- First check Shopify Payments eligibility: this only works when business location, business type, product category, compliance records, and 2FA meet current Shopify requirements.
- If Shopify Payments is available: you can also enable Shop Pay for faster checkout, but still test the regular credit-card path and the accelerated checkout path.
- If Shopify Payments is not available: you need to design around a third-party payment provider from the start.
- If you sell subscriptions: Shopify’s help docs state that Shopify Payments must be your primary gateway.
The constraint is eligibility: location, business type, product category, compliance records, and 2FA all matter.
Remember to account for both provider fees and Shopify transaction fees.
Whether they fit depends on region, risk, fee profile, and test-order results.
They are rarely the main path for a cross-border DTC launch.
Do Not Release Payments Just Because a Button Appears
Shopify’s test-order documentation says you should place at least one test order during setup. If you use Shopify Payments, test mode is the primary path. If you do not use Shopify Payments, Bogus Gateway can simulate a checkout. Save order ID, notification emails, order status, tax and shipping display, and the record that test mode was turned off. Without that evidence, a visible payment button is not enough to release live ad traffic.
How to Choose a Theme in 2026
A theme is not just decoration. It controls how efficiently your store communicates products, trust, navigation, and purchase flow. Shopify now lets merchants add free themes, trial paid themes, and in some cases generate free personalized themes with AI, but beginners still benefit most from staying simple.
For most new stores, free themes are enough to launch with better compatibility and simpler support.
This is the safer way to compare structure before spending.
This matters if you collect too many test drafts.
Theme Selection Rules
- Choose based on category structure and content flow, not only visual style.
- Prioritize mobile readability, product hierarchy, and speed over animation.
- Do not start with heavy code edits if native sections and blocks can handle the first launch.
- Trial a paid theme before buying it and confirm that it really fits your selling format.
What to Prepare Before Uploading Products
Products should not be treated as something to fill in later. The information you upload now directly influences conversion, landing-page quality, SEO, and support load.
Product Upload Sequence
Early-Stage Product Strategy
- Build strong pages for 1-3 hero products before expanding SKU count.
- Product pages should support purchase decisions, not just mirror supplier specs.
- Product copy, shipping promises, and policy pages should all stay consistent.
Pre-Launch Checklist
If the store only looks almost ready, that is not a real launch state. This checklist is closer to what actually ready to sell means.
Must-Confirm Items
- Your Shopify plan is chosen and you understand billing and related costs.
- Target markets are configured, with intended markets set to Active and unfinished ones kept in Draft.
- Payments are configured and the checkout flow has been tested end to end.
- Domain, email, notifications, and policy pages are complete.
- The theme works clearly on mobile and does not block purchase flow.
- The first homepage, collection, and product structure can support incoming test traffic.
- GA4, pixels, or other data tools have basic implementation in place.
Common Launch Failures
- Payments were never truly tested: checkout fails only when the first buyer tries it.
- Markets and shipping were never aligned: the site says you sell there, but rates, currency, or shipping availability are wrong.
- Too much theme customization too early: the store becomes slower and less stable before launch.
Operating Recommendation
- Use Shopify’s native capabilities for version one instead of overloading the store with apps and custom code immediately.
- Get one market, one payment path, and one theme structure working before broadening scope.
- Any setting that affects billing, market publishing, payments, or theme licensing should be decided early and deliberately.
Admin continue-or-pause practice: decide whether Shopify admin can keep moving
Admin setup is not finishing the setup guide. It is knowing whether to continue, pause, or return to a specific settings area when launch pressure appears. Use this table to turn a store that looks ready into five continue-or-pause calls: account control, Markets, test order, theme/apps, and data evidence.
| Pressure scenario | Unsafe move | Continue condition | First evidence | Stop line |
|---|---|---|---|---|
| Team still shares the main account | Let agency and operators keep sharing admin, then clean permissions after launch. | Hold. Split staff or collaborator permissions, enable 2FA, and record backup admin, recovery email, backup-code storage, and billing lead. | Staff permission record, 2FA state, backup admin email, and recovery record. | Before account sharing is removed, do not expand theme, payment, app, or data access. |
| Markets status is not clean | Run a little global traffic and fix Markets after orders appear. | Continue with one accepted primary market only; unfinished markets stay Draft. The primary market needs currency, language, shipping, tax/duty wording, policies, and mobile checkout sampling. | Markets status record, target-market checkout record, and shipping plus tax display notes. | For countries or regions that fail Markets acceptance, do not launch ads or promise delivery. |
| No test order yet | Publish the store and start traffic because the payment button appears. | Hold public traffic. Run a test order with Shopify Payments test mode or Bogus Gateway, then save order ID, notice emails, order status, and test-mode-off record. | Test order ID, admin order record, customer order confirmation email, and team notice. | Before test order and test-mode-off evidence exist, do not continue real ad traffic. |
| Theme and apps are drifting | Install more apps or keep redesigning visuals. | Return to one first theme and required apps only. Each app needs purpose, removal condition, and responsible lead; mobile PDP, cart, and checkout must be rechecked. | App list, reason to keep each app, mobile purchase-path records, and hero SKU list. | Before the first order path passes, do not add nonessential apps or keep rebuilding the theme. |
| Data is invisible before traffic | Run a small ad budget first and diagnose later when data arrives. | Accept events with a test order and key page actions first. Record which events are visible, which are not, and what to inspect on launch day one. | DebugView / Pixel / Shopify order records, event names, test time, and order ID. | If purchase or order-level data is fully invisible, do not continue paid traffic. If launch is unavoidable, write the measurement exception and manual reconciliation method. |
Why this practice matters
Beginners can be fooled by a good-looking storefront. The admin continue-or-pause record forces the pressure scenario, unsafe move, continue condition, first evidence, repair target, and pause line into writing, so the next store-structure, payment, and launch-QA lessons do not build on a half-ready base.
Set Shopify around markets, payments, and admin responsibility
Do not treat Shopify setup as simply clicking through the setup guide. Shopify international sales tools bring target countries, currencies, languages, duties, payments, and international shipping into one market system, while Shopify Payments payout documentation shows that payout account and region rules affect receiving funds.
Order-path acceptance checklist: after the 60-minute walkthrough, decide whether the real-order path can continue
The common admin setup illusion is “I clicked through it.” The real question is whether the primary market can be public, payment has a test order, shipping, tax, and policies explain each other, Customer events can see purchase, and notices/access are transferable. This is the evidence list to bring into Store Launch Readiness Scanner.
| Acceptance line | Admin path | Acceptance job | Proof to keep | Release rule |
|---|---|---|---|---|
| Lock primary market and currency first | Settings -> Markets | Prove the first real selling country has aligned currency, language, product availability, shipping, and tax display. | Primary market Active screenshot, other markets Draft screenshot, mobile PDP, and checkout currency/shipping/tax screenshots. | Before the primary market is accepted, do not add a second market, change ad countries, or promise cross-border shipping. |
| Accept payment and test order together | Settings -> Payments / Checkout / Orders | Use one test order to prove add-to-cart, checkout, payment, admin order, customer email, team notice, and cancel/refund path. | Test order ID, payment state, order confirmation email, team notice, refund/cancel path, and test-mode-off record. | Without a complete test order, with test mode still on, or with unclear PayPal/third-party gateway boundaries, do not release real ad traffic. |
| Align shipping, tax, and policy promises | Settings -> Shipping and delivery / Taxes and duties / Policies | Accept shipping rate, delivery timing, tax display, refund/return promise, and Contact email together. | Shipping profile, tax display screenshot, policy URLs, order-confirmation promises, and mismatch correction record. | When policies are templates, shipping conflicts with page promises, or support inbox misses notices, do not open real orders. |
| Accept Customer events with the test order | Settings -> Customer events / GA4 / Pixel | Use the test order to see view_item, add_to_cart, begin_checkout, purchase, or equivalent base events. | Customer events status, GA4 DebugView, Pixel diagnostics, purchase screenshot, Shopify order ID, and review time. | If purchase is invisible, events duplicate, or GA4 cannot reconcile with Shopify orders, do not rush to judge ads or page quality. |
| Make notices and access transferable | Settings -> Notifications / Users and permissions | Confirm what customers receive, what the team receives, who can handle orders, and who can edit payments and theme. | Order confirmation email, shipping notice sample, team notification inbox, staff permission screenshot, 2FA, and backup admin record. | When the main account is shared, notices go nowhere, or key permissions have no responsible person, do not hand the store to ads or support. |
Do not write only “admin is configured” in copyable lesson notes. Write the weakest acceptance line, admin path, first evidence, Scanner input, paused action, and next review time.
Shopify admin setup order map: fix money and order flow before polishing pages
Shopify admin is not a set of isolated buttons. Store details, Users and permissions, Markets, Payments, Shipping, Notifications, and Customer events are connected. The beginner risk is not finding the menu; it is not knowing whether a setting affects payment review, shipping promises, notification email, access, or performance review.
| Admin area | Path | Setup job | Do not change blindly | Pass evidence |
|---|---|---|---|---|
| Fix store identity first | Settings -> Store details | Controls the base merchant information seen by admin, invoices, notifications, policies, and payment review. | Before legal name, address, and support email align with entity records, do not submit payment review or publish Contact. | Store details screenshot, entity source record, policy contact, support inbox receiving test, and review date. |
| Split account access early | Settings -> Users and permissions | Decides who can edit theme, read orders, touch payments, install apps, and export customer data. | While the main account is shared and 2FA plus backup admin are undocumented, do not expand payment, theme, customer, or settings access. | Staff permission screenshot, collaborator permission screenshot, 2FA state, backup admin, recovery email, and backup-code storage location. |
| Release one primary market first | Settings -> Markets | Affects country, currency, language, product availability, taxes, domains, and shipping. | Before shipping, taxes, policy promises, and checkout pass, do not make multiple countries Active at the same time. | Primary-market Active screenshot, Draft market list, mobile product page, and checkout currency/shipping/tax screenshots. |
| Prove payment and checkout with a test order | Settings -> Payments / Checkout | Reads gateway, PayPal, accelerated checkout, checkout fields, tax/shipping, and test order together. | When test mode is still on, no complete test order exists, or refund/cancel path is unclear, do not send live ad traffic. | Test order ID, payment state, admin order screenshot, customer confirmation email, team notice, cancel/refund path, and test-mode-off note. |
| Read shipping, policies, and notices together | Settings -> Shipping and delivery / Notifications / Policies | Makes shipping rates, delivery timing, refund policy, order confirmation, and shipping notice tell the same story. | When policies are templates, notices do not arrive, or shipping rates conflict with page promises, do not open the first real orders. | Shipping profile, policy links, order confirmation email, shipping notice sample, support inbox receipt, and mismatch correction record. |
| Keep minimum data-event evidence | Shopify Customer events / GA4 / Pixel | Proves view_item, add_to_cart, begin_checkout, and purchase can be seen. | When purchase is invisible, events duplicate, or GA4 cannot reconcile with Shopify orders, do not rush to judge ads or pages. | Customer events state, GA4 DebugView, Pixel diagnostics, test-order purchase screenshot, order ID, and review time. |
Write this back to copyable lesson notes
Do not write only "admin is configured." Record the admin area fixed first, which chain the setting affects, what should not be changed blindly, where the first evidence lives, and who will read the evidence in the next lesson.
Define Pixel first: launch behavior must be visible
A Pixel is a tracking code from an ad or analytics platform that helps detect actions such as product views, add-to-cart, checkout start, and purchase. You see it in Shopify customer events, Meta Pixel, TikTok Pixel, Google tag, GA4 DebugView, or ad-platform event diagnostics.
| What to understand | Where it appears | Who reads it | What breaks when wrong |
|---|---|---|---|
| Pixel is not the sale itself. It helps platforms see buyer behavior. | Shopify customer events, GA4, Meta Pixel, TikTok Pixel, and Google tag. | Ad platforms, GA4, Shopify order data, the ad operator, and the performance reviewer. | If the Pixel is missing, duplicated, or cannot see purchase, ad systems lose conversion signals and GA4 becomes harder to reconcile with Shopify. |
| Pixel should be accepted with a test order, not only checked as installed. | view_item, add_to_cart, begin_checkout, purchase, or equivalent base events. | Ad optimization, performance review, support, and finance reconciliation are all affected indirectly. | You can mix up ad issues, page issues, and tracking issues, making the first traffic cycle hard to judge. |
20oz tumbler store example: prove one explainable order first
Imagine a US launch for the first 500 units of a 20oz commuter tumbler before the first ad budget opens. At this stage, do not obsess over homepage polish first. Prove the smallest order path: mobile product page is clear, checkout can finish, a test order can be created, notifications arrive, and purchase is visible.
| Area | Decision to make | Wrong consequence | This-week action |
|---|---|---|---|
| Primary market | The United States is the current primary market; other countries stay Draft instead of going global at once. | Currency, shipping, tax wording, and policy promises drift, making ad landing pages unstable. | Save Markets status record and mobile checkout record. |
| Order path | Use a test order to verify add-to-cart, checkout, payment, admin order, customer notice, and team notice. | The first real order reveals payment, notification, or inventory deduction problems. | Save test order ID, notification emails, and test-mode-off record. |
| Data events | Pixel / GA4 should at least show view_item, add_to_cart, begin_checkout, and purchase. | After ads start, conversion is invisible and the team cannot tell whether ads, pages, or tracking broke. | Save DebugView / Pixel event record and test time. |
Copyable lesson notes: turn admin setup into a reviewable record
If the theme looks ready but checkout currency, shipping notifications, staff permissions, Pixel, and market status are unchecked, launch errors can stay hidden. After this lesson, do not keep only "the store is open." Keep admin evidence that can be reviewed.
Write at least these 6 lines
- Current pressure: What is blocking you now: account control, Markets, payment testing, notifications, theme/products, or Pixel / data events.
- First evidence: Which admin record, test order, notification email, permission record, or Pixel / DebugView record you will keep first.
- This-week action: Choose one action this week, such as split permissions, accept the primary market, run a test order, fix notifications, prepare hero SKUs, or verify Pixel events.
- Pause action: Until evidence is ready, pause live traffic, ad scaling, more apps, or more market releases.
- Review window: Define when to review: after the test order, after the first real order, the day before launch, or before the first ad cycle.
- Next route: Go to store structure if admin passes; go to payment setup if payment is not proven; go to launch QA if the chain is almost ready.
| Admin setup field | What to copy | Release / pause rule |
|---|---|---|
| Account and security | Primary account email, 2FA state, recovery path, staff permissions, and who can change billing, payments, or domains. | If recovery and key permissions are unclear, do not release live orders or ad-account connections. |
| Markets and currency | Primary market, Active / Draft state, currency, language, domain path, paused markets, and the reason each stays paused. | Keep unaccepted markets in Draft. Do not promise delivery or launch ads there. |
| Payments and test order | Shopify Payments / third-party gateway / PayPal state, test order ID, payment state, and test-mode-off record. | Without a complete test order and test-mode-off record, do not send live traffic. |
| Checkout, tax, and shipping | Contact method, address fields, tax display, shipping-rate name, delivery zone, and mobile checkout record. | If checkout price, tax, or shipping display disagrees, pause launch first. |
| Notifications, policies, and support entry | Order confirmation email, shipping notice, refund policy, shipping policy, support email or form test result. | If notices do not arrive or policies are still blank templates, do not open real orders. |
| Theme, products, and app boundary | Current theme, first SKUs, required apps, apps not installed yet, and changes that may affect speed or checkout. | Before first SKUs and theme path are stable, do not keep adding apps or custom work. |
| Data events and review window | Shopify order ID, GA4 / Pixel event name, test time, responsible lead, next review date, and fallback settings page. | If purchase or order-level events are invisible, do not judge store quality from ad performance. |
This table turns "the store is open" into "which admin fields are accepted and which ones are not released yet." If these seven lines are unclear, complete admin evidence before buying traffic, adding more apps, or opening more markets.
Before moving into store structure and payment setup, bring store account control, market settings, checkout settings, notification templates, tax logic, staff permissions, security state, Pixel / purchase event, and test-order evidence.