Skip to content
Ecomwith

Before You Start: Account, Store Identity, and the Admin Map

  • Beginner
  • 45 minutes

Before setting up Shopify, confirm that you are in the right store and that its long-term owner controls both the owner account and its recovery methods. Then draft the business identity, launch market, and store currency. Keep these decisions in a store-start card so product, payment, and shipping work begins with consistent information. You will enter the agreed details in General in the next lesson.

Key point Confirm control and launch scope first

Settle who controls the store, where it will sell first, and which entity and currency it will use before theme work or app installation. A start card records decisions and checks; it does not establish that the store can take orders.

This lesson is for a first visit to Shopify admin or for taking over a store built by staff or a contractor. You do not need to learn every menu at once. Start by connecting the selected store, the business behind it, and the work that comes next.

Note Do these three things today

  1. Write who controls the store owner account and where the recovery email or phone lives. 2. Write the legal entity, first market, and store currency. 3. Put the three items on the start card and mark each "confirmed" or "to confirm".

Draft the store-start card

A store-start card separates things that are easy to confuse: verify account control now; keep business details as drafts until they are confirmed. Being able to sign in establishes that a user has some access. It does not tell you who owns the store, who can recover the account, or whether this is the store you intended to change.

The teaching example throughout this series is a new store selling desk-organization products. It starts with one physical product and uses Variant A and Variant B through the product, inventory, shipping, and test-order lessons. Its launch plan is the United States, USD, and an English storefront. These are example choices, as are the shipping amounts in the course map. Your entity, payment eligibility, warehouse, and customer promises need their own checks.

Here, A and B are labels for two sellable options of one product; no particular color or size is assumed. Later lessons will set the actual options and check each through product, inventory, shipping, and test orders.

Suppose theme work has begun, but a contractor still controls the owner email and the team has not chosen its launch country. Another theme change will not establish who can recover a lost account, which entity belongs on payment records, or which currency product prices should use. Recover control and agree on a narrower launch scope before configuring work that depends on those decisions.

Prepare a durable email address controlled by the long-term owner. Gather the intended entity and address details, plus the documents that identify who will receive payments. Avoid temporary addresses and an employee's personal inbox that the business could lose when that person leaves. Mark unresolved fields as pending and name a person and review date. Do not invent a temporary value to get through a settings form.

The decisions below carry into later lessons. For example, writing “United States” in the market row records an intention. That sales flow becomes verified only after payment, shipping, tax, and test orders support the intended US address.

Decisions to settle before setup

ItemWhat to recordWhy it comes first
Owner accountA durable owner-controlled email and the custodian of each recovery methodOwnership and recovery must not depend on temporary staff. Give people individual users and roles for daily work.
Launch marketThe first country you can actually advertise to, charge customers in, and fulfill orders toProve one payment and fulfillment flow before deciding to add countries.
Store currencyA currency consistent with launch pricing, payment arrangements, and reportingCurrency affects later business records. Treat it as an operating decision rather than a display preference.
First physical productThe product and SKU you will inspect throughout the setup lessonsUsing the same product through inventory, shipping, and test orders makes mismatched settings easier to find.

The card also needs a working store name, business entity, default timezone, support email, public-phone decision, and the separate purposes of the registered and warehouse addresses. Drafting these fields is enough for this stage. A plan does not establish that later settings were saved, the storefront displays them correctly, or orders can be processed.

Step 1: confirm the selected store

A Shopify account can have access to several stores. Checking the name and address first helps prevent changes to a test store or client store by mistake. Shopify's current desktop instructions use the store name in the top bar: select a recent store, or open View all to search the full list.

Enter the store you intend to set up

  1. Create or enter the correct Shopify store

    Create a store through Shopify's official entry point or sign in to an existing one. Check the name in the store switcher against the current admin address. Record the working name and myshopify.com address in your own start card.

    How to confirm

    The store name and admin address must match the store you are authorized to work on. A familiar-looking screen is not enough.

    If it goes wrong

    If a new store is missing, check the signed-in email, then search the complete store-switcher list. Ask the owner to resolve missing access before making changes in another store.

    Keep as evidence

    Record the check time, responsible person, and screenshot location. Keep the store context, page title, and complete area being inspected in the image; mask personal details before sharing it.

The retained screenshot below is from a development store in the earlier course. Use it to locate the store name in the top bar, the work areas on the left, and the Settings entry. Quickstart is the example store shown in the image; its status and configuration do not belong in your store record.

Admin path: Shopify admin › Home › Store name › Recent stores / View all

Historical English Shopify Home screen with the example store name in the top bar, business menus on the left, and Settings at the bottom.

Historical screenshot: identify the store context before choosing a work area. It does not establish ownership, recovery control, or launch readiness in your store.

Read the store name first, then the page title. Home progress cards cover only part of the work and do not replace launch acceptance checks. A saved status still needs the relevant storefront, order flow, or settings-page check before you can rely on the result.

Step 2: confirm ownership and recovery

The store owner is an ownership role. Permission to edit products or process orders does not replace it. Account security also requires more than knowing a password: the responsible person must receive recovery messages, use their own verification methods, and have a recovery option if a device is lost.

Identify the owner and recovery custodians

  1. Confirm the owner account and recovery route

    Open Users in Settings, or the applicable account-security area, and identify the user marked Store owner. Establish who controls the recovery email, phone, password manager, and backup codes. Record the custodians and secure storage locations.

    How to confirm

    The long-term owner controls sign-in and recovery. Other people use individual accounts with suitable roles. Keep only custodians and storage locations in the notes, never passwords, verification codes, or recovery codes.

    If it goes wrong

    If a contractor controls the owner email, an authorized person needs to complete the ownership and recovery transfer first. Then confirm that the owner can sign in independently. Changing a displayed email alone does not establish that the transfer is complete.

    Caution

    Do not share the owner login. User invitations and roles must also fit the current plan and permission rules; sharing owner credentials is not a substitute for staff access.

In the historical Users screen below, read the Role column. One row says Organization owner, Store owner; the other says Organization administrator. An active user is not necessarily the store owner. Find the row that carries the ownership role.

Admin path: Settings › Users › Store owner role

Historical English Users screen with names masked and a Role column distinguishing Store owner from Organization administrator.

Historical screenshot: inspect the Store owner role. A user list cannot establish who currently controls recovery email, a phone, or backup codes.

After finding the role, confirm who actually controls recovery. If staff use the owner account for daily orders, arrange individual users and roles. If you suspect unauthorized access, deal with account security before continuing setup.

Steps 3 and 4: draft identity and launch scope

The working store name identifies the shop to customers and the team. The business entity is the person or organization responsible for the business; it can have a different name. Registered, warehouse, and customer-return addresses may serve different purposes too. Define the purpose before deciding which value belongs in a settings field.

Turn the business plan into a usable draft

  1. Draft the store identity

    Write down the working store name, business entity, support email, whether to publish a phone number, registered address, and warehouse address. Note how the payment entity relates to the operating entity. Keep these as drafts here; enter them against the actual General fields in the next lesson.

    How to confirm

    Each address has a purpose, someone receives support messages, and the entity details have supporting documents. A working name can be provisional, but review domains, branding, payment details, and customer touchpoints together before launch.

    If it goes wrong

    Mark an unresolved entity or address as pending, with an owner and review date. Do not save an invented address to finish this lesson or assume the warehouse address belongs in every address field.
  2. Choose the launch market and store currency

    Choose one country you can realistically promote to, accept payment in, and ship to. Record the store currency and a storefront language you can support. The desk-organization example plans to start with the United States, USD, and English. Those choices still require later payment-eligibility and fulfillment checks.

    How to confirm

    Explain how country, currency, and language fit pricing, payment, and shipping arrangements. Resolve conflicts among currency, entity, and market before accepting live payments.

    If it goes wrong

    If the initial plan includes many countries, narrow it to one launch market. Check payment, shipping, tax, and test orders in the relevant lessons before adding markets or languages.

General brings store details and defaults together, but you do not need to edit them all now. The historical screenshot below helps you distinguish Business details, Store contact details, and Store defaults. Its Canadian business details, CAD display, and other defaults belong to the development store at capture time; they are not recommended values for the US launch example.

Admin path: Settings › General

Historical English General screen showing Business details, Store contact details, currency, units, and timezone, with private information masked.

Historical screenshot: distinguish business details, store defaults, and the selected store. Prepare the inputs here; enter, save, and reopen them in the next lesson.

A field being available does not make its current value right for your business. Match planned values to entity documents, launch pricing, and operating arrangements first. If the store already has real orders, investigate the effect of a change before treating currency as an ordinary preference.

Step 5: find the right work area

Admin areas are organized around different objects and jobs. Finding the right place for product information, order handling, and store details prevents changes in a similarly named area. Menu placement can change with permissions, store state, and Shopify updates. The page title and the object you are working on are more reliable guides than a memorized button position.

Learn the admin through concrete tasks

  1. Learn the six common English admin work areas

    Locate Home, Products, Orders, Customers, Marketing, and Settings. Practise finding three tasks: Products for product information, Orders for order handling, and Settings for basic store details. You are finding the right areas, not configuring every menu in this pass.

    How to confirm

    Explain the object each area handles, and check the current store name alongside the page title.

    If it goes wrong

    If an entry is missing, first check the selected store, user access, and page title. Then check plan, market, or feature conditions where relevant. Do not guess by editing a similarly named page.
Work areaWhat you handle hereWhat to distinguish
HomeOverview, reminders, and setup tasksHome progress does not replace a complete launch check.
ProductsProduct, variant, and inventory informationAn existing product is not necessarily available in the intended channel and market.
OrdersOrders and their subsequent handlingOpening the page does not establish that payment, fulfillment, and refunds have been tested.
CustomersCustomer recordsCustomer information and staff sign-in permissions concern different people and objects.
MarketingMarketing work and related entry pointsA captured Home menu may use labels such as Growth. Check the current function.
SettingsStore foundations and underlying settingsGeneral, Users, Payments, and other settings have separate jobs.
Online StoreStorefront pages, themes, and navigationPresentation work cannot resolve ownership, identity, or payment preparation.
Sales channelsThe channels through which products sellProducts need availability in the relevant channel.
MarketsThe markets served and their selling experienceA market is different from a sales channel. Both can affect where a product is available.

For example, creating a product in Products does not establish that a US shopper can buy it. Later checks also cover the channel, market, stock, shipping, and checkout result. For now, understand which object each area controls rather than reading one menu status as proof of an entire sales flow.

The same inspection order applies in a Chinese-language admin: confirm the store, identify users and ownership, then prepare entity, market, currency, and timezone details. Chinese paths beside the retained images are historical references. Use current page titles, fields, and results as well as translated labels when finding the right area.

Step 6: schedule the remaining setup

Use a task sheet to organize the series' 20 lessons. Give each row an owner, status, evidence location, and review date. A solo merchant can own every row without inventing team roles. Keep the statuses consistent: Not started, In progress, and Verified, in your own spreadsheet or project list.

Create the execution checklist and keep its order

  1. Assign the work and its verification record

    Begin with an owner, status, record location, and review date for this lesson and the next. Before moving ahead with an app, theme, or additional market, check the ownership, entity, and launch-scope decisions that work depends on.

    How to confirm

    Mark a row Verified only when its actual result, evidence link, and pass condition agree. Screenshots should identify the current store and page and include the relevant fields, message, or saved result.

    If it goes wrong

    When a prerequisite is unresolved, retain the record and name the item and person needed to resolve it. Return to that lesson. Leave later work pending rather than skipping the problem.

Take the shipping row as an example: a later lesson uses US addresses to test a standard rate and the free-shipping boundary. Those amounts are teaching inputs. Your own product economics, policies, and fulfillment coverage determine the appropriate settings. You do not need to finish the entire course today; open the full map when assigning later work.

Open the full course map to plan the work

When copying this map into your task sheet, add an owner, Not started / In progress / Verified status, evidence link, and review date to every row. Use both the required output and pass condition to decide whether to continue or return to the relevant lesson.

Two-factor authentication (2FA) adds a second identity check at sign-in; reviewing its status alongside each user's permissions helps the owner check both account protection and access. A stock-keeping unit (SKU) is an internal code used to identify and track an item or variant; recording the right code for each sellable option helps match the customer's selection to inventory and fulfillment records.

LessonRequired outputPass condition
1. Before You Start: Account, Store Identity, and the Admin MapA store-start card covering owner, entity, working name, target country, base currency, timezone, contacts, recovery, and setup order.The correct store, owner control, recovery, launch market, and base currency are explicit.
2. General Settings: Store Details, Address, Timezone, and CurrencySaved General screenshots and field notes covering address responsibility, currency and market alignment, and order-time conventions.Address purposes are clear; the team can explain timezone and units; currency fits the launch market, with change conditions checked if orders already exist.
3. Users, Roles, and Security: Give Each Person Only What They NeedA permission matrix, active-user 2FA status, recovery-code custody, collaborator expiry dates, and revocation steps.The owner account is uniquely controlled; users sign in individually; privileged users have 2FA; external access is limited to the work.
4. Plan and Billing: Know the Cost Boundary Before Installing AppsMonthly technology costs covering plan, domain, email, theme, required and optional apps, usage fees, billing owner, and cancellation dates.The plan has a business rationale; billing details are correct; trials and apps have an owner, end date, and monthly review.
5. Domains and Sender Email: Primary Domain, DNS, TLS, and AuthenticationRecords of registrar, renewal owner, DNS, primary domain, redirects, TLS, mailbox hosting, support receipt, Shopify sender address, and authentication.Domain and redirects are stable; registrar and DNS are controlled; support receives mail; the sending domain has the required authentication.
6. Products, Variants, and Inventory: Publish the First Sellable SKUThe first physical product with 2 sellable variants, A and B, each with SKU, price, cost, weight, stock location, channel, and mobile check.Images, SKU, stock, weight, and channel match each variant; storefront price and add-to-cart results agree.
7. Collections and Catalog Structure: Make Products Findable and ScalableMinimum viable All Products, Desk Organization, and New Arrivals collections, with automatic rules, URLs, sorting, images, and storefront entry points.Field responsibilities are documented and collection conditions are explainable; sorting, navigation, filters, and actual product results are checked.
8. Theme Backup and Customization: Duplicate Before Editing Sections, Blocks, and TemplatesA dated theme copy, template inventory, home and product-page structure, mobile screenshots, and a recovery method for each change.The backup is clearly named; key templates and the mobile first view are previewed; the publisher and recovery point are known.
9. Pages, Menus, and Navigation: Connect Home to CheckoutMain navigation no deeper than 2 levels, a complete footer, customer-account entry, core-page object links, mobile checks, and a redirect register.Core pages have an entry; mobile menus work; links target the right objects; old handles have necessary redirects.
10. Policies, Brand, and Contact: Turn Promises into Operable PagesConsistent, operable policy and trust pages with owner, review date, applicable market, support route, and storefront link location.Policy figures agree; support can honor the promises; footer links work; required market-specific professional review is arranged.
11. Payments and Payouts: Eligibility, Verification, and Settlement AcceptanceEach method's status, entity, settlement currency, payout account, fee source, tests, refund path, dispute owner, and reconciliation record.Entity and account match; success and failure paths pass; refunds are traceable; a second person confirms test mode is off.
12. Checkout and Customer Accounts: Reduce Friction Without Losing Required InformationCheckout-field decisions, guest and signed-in tests, marketing-consent screenshots, branding preview, and order-processing rules.Required fields have a business reason; marketing consent is not preselected; both customer paths reach pre-payment with policies and shipping visible.
13. Locations, Inventory, and Fulfillment: Route Orders to the Right PlaceA fulfillable location, variant stock assignments, online-order handling, out-of-stock rules, routing priority where needed, and a test order's warehouse assignment.Variants use the right location; a test order moves stock to Committed; cancellation with restock restores quantity.
14. Shipping and Delivery: Zones, Rates, Packages, and Free-Shipping ThresholdsA US General shipping profile example: real origin, US zone, $12 standard rate, $75 free-shipping threshold, package data, displayed timing, and 4 checkout tests.Standard rate, free-shipping boundary, and unsupported-address results match policies and product promises, with no duplicate rates.
15. Taxes and Duties: Register First, Then Configure Rates and Product CategoriesProfessionally confirmed registration regions, numbers, collection dates, tax service, product categories, price display, duties treatment, test addresses, and filing owner.Obligations and dates have external support; registrations are real; categories are accurate; test-order and refund results are explainable.
16. Markets, Languages, and Currencies: Prove One Market Before ExpandingThe US launch example: one active US Primary market, other markets inactive, a complete USD and English experience, and catalog, domain, product-availability, and test-address records.Product, price, currency, language, domain, shipping, and policies agree; the target address reaches pre-payment.
17. Notifications and Email: Test Order, Shipping, and Refund Messages One by OneTrigger, recipient, From, Reply-To, language, test result, screenshot, and owner for each customer and staff message.Real events trigger key messages; product, amount, shipping, tracking, and reply address are correct; at least 2 receiving environments are checked.
18. Customer Privacy and Events: Consent, Cookie Banner, and Pixel DeduplicationApplicable markets, cookie banner, opt-out, policy links, request owner, pixel ownership, events, consent behavior, and deduplication records.Target regions show the intended entry; decline/accept differences are explainable; page_view, add_to_cart, and purchase are not duplicated.
19. Apps and Sales Channels: Review Permissions Before Install and Cleanup After RemovalOwner, purpose, permissions, data, cost, trial end, products, pixels, webhooks, privacy impact, uninstall steps, and review date for each app and channel.Retained items have an owner and job; permissions and cost are explainable; products and events are tested; removals include residue checks.
20. Test Orders and Launch QA: Run Payment, Fulfillment, Cancellation, and Refund End to EndA signed report covering success, failure, and boundary cases, evidence, blockers, fixes, retests, test-mode removal, password-removal time, monitoring owner, and recovery conditions.Post-order activity reconciles; every case has a result; a second person checks test mode, password removal, and monitoring.

One screenshot does not pass an entire row. Compare actual values and tests with its condition. Record a mismatch and return to that lesson instead of substituting Home setup progress for verification.

Decide whether to continue

Return to the desk-organization store: a contractor still controls the owner email, and the launch country is unsettled. Choose what should happen now, then check your own store. Your choice is retained in the lesson record.

Decision · 1 question0/1 answered

Choose the next action

You are ready to customize the theme, but a contractor controls the owner email and the launch market is unsettled. What should happen now?

Self-check not answered

The recommended choice addresses the control and scope problem. Choosing it does not transfer ownership or inspect the admin for you. Check the items below against your own store. Leave an item unticked when information is missing and record who will resolve it.

Checklist0 / 3 required
Confirm these in your store
  • Check the store name, admin address, and Store owner role together.
  • Record custodians and secure locations, never passwords or backup codes.
  • Mark unresolved fields pending, with a responsible person and review date.

A tick records a check you made; it does not save Shopify settings or run a test. Draft details may still have pending questions. Resolve any pending question that affects entity, market, or currency alignment before continuing work that depends on it.

Conditions to continue or pause

Done whenStop if
The correct store, long-term owner's control, recovery, launch market, and base currency are explicit, with material conflicts resolved.
A contractor or other third party still controls ownership or recovery, or entity, launch market, and currency conflict.
Evidence
A check of the current store and user role, plus a start card naming responsibility, actual values, pending work, and review dates.

Keep the start card, then open General

Write down your actual observations now. A useful order is working name and store address; owner and recovery custodians; entity and address purposes; support contacts; launch country and language; currency; timezone; and the first product. Finish with blockers, responsible people, evidence locations, and review dates. Assign this lesson and the next in the course task sheet, and list theme, app, or additional-market work that should wait.

Use only non-sensitive practice details, role names, and references to your own records below. Keep actual business information in a work document you control. Do not enter passwords, recovery codes, card numbers, or real account identifiers. The lesson record saves automatically in this browser. Export it before moving to another browser or device.

What this record establishes

Hold

Make the scenario decision first

Choose the action that resolves control and launch scope, then inspect your own store.

Move to General only when ownership, recovery, and launch scope are clear. Enter the confirmed identity, timezone, and currency against the actual fields. Later settings still need saving, reopening, and inspection; customer-facing behavior also needs a storefront or test-order check.

What you finished

No checkpoint finished in this lesson yet. Start with “Go to the exercise”.

Self-check not answered

FAQ

Can the Shopify store name change later?

A working name can be provisional, and the display name can be changed. Domains, branding, payment details, and customer recognition become connected, so review those touchpoints before launch rather than treating a name change as a complete identity update.

Can the owner account use an employee email?

It is not recommended. The long-term owner should control the account and be able to use its recovery methods. Staff should use individual users and appropriate roles for daily work.

Why not choose a theme first?

A theme does not settle the business entity, currency, payments, shipping, or account security. Establish those foundations so theme and product work can use consistent inputs and avoid repeated rebuilding.

Why is a newly created store missing?

Check the signed-in email, then click the store name in the top bar and search the complete list through View all. Verify the store address. Ask the owner to resolve missing access before changing another store.

Should every store use the United States, USD, and English?

Those are teaching choices for this series. Choose a launch scope that fits your actual entity, payment arrangements, shipping, pricing, and support capacity, then verify it in the later lessons.

Does a finished start card mean the store can launch?

No. It records control, plans, and pending work. Payments, shipping, tax, notifications, and post-order handling still need their own tests before the final launch check.

Fill the preparation gap you have now

Work it out: which store can open today

Four stores in preparation (example data). Rule: check the irreversible items first — business entity, payment, domain ownership; if one of those is missing, no amount of polish takes money. Theme, copy and images are changeable after launch.

The real state of four preparations

ItemEntity and paymentsDomainProductsTheme and copy
Store AEntity unverified, payments offBought, not pointed10 products livePolished
Store BEntity cleared, payments onBought, DNS not live10 products livePolished
Store CEntity cleared, payments onLiveNothing purchasable (hero out of stock, rest not published)Polished
Store DEntity cleared, payments onLive10 products liveDefault theme, copy pending

Decide before you read on. Say which store can open today, and where the other three are stuck.

Answer key: only store D can open — the three irreversible items are done (entity, payments, domain), while theme and copy can change any day after launch. A cannot take money, B cannot be reached, and C can open but has no hero product, which sends the first traffic to an empty shelf. C is the trap: every technical box is ticked and it looks one restock away, yet opening means the first customer can buy something, not that a checklist is complete.

Edition notes

  • Author Ranfeng Wei
  • Published
  • Updated
  • Reviewed
  • Next review

This update: Clarified A/B as two sellable options of the example product and defined 2FA and SKU in prose before the course-map table; the map rows and remaining lesson content are unchanged.