Choose the lowest Shopify plan that meets the store's launch needs, then check the billing entity, who pays and the billing periods. Budget the plan, domain, email, theme, app subscriptions and usage charges separately. Every trial needs a responsible person, an end date and an exit condition. An authorized person can then decide whether to accept the charge.
10 parts · 3 checkpoints
Show all 10 parts
- 01Step 1: record the plan, trial and next charge
- 02Step 2: give the plan decision a business reason
- 03Step 3: check the Billing profile and payer
- 04Step 4: separate charge categories and dates
- 05Step 5: approve the app's job, access and exit
- 06After uninstalling, identify which cycle produced the charge
- 07Step 6: archive invoices and schedule a monthly review
- 08Decide about the trial, then check your own cost sheet, has a checkpoint
- 09Save the decision and continue to domains and email, has a checkpoint
- 10Work it out: which store pays for a plan it cannot use
Key point Separate a cost decision from a completed payment
A plan decision, a subscription action, app billing and launch readiness establish different things. A plan page, install button or paid invoice cannot cap future costs or establish that a store is ready to take orders. Payments, tax, shipping and customer experience still need their own checks.
You can begin here without an earlier course record. Confirm the selected store, who can view bills, and who can approve plan and app spending. Gather entity and billing-contact details, a payment method the business controls or has approved, expected orders and team size, inventory locations, markets and reporting needs. List installed and proposed apps. Inspect any existing trial or subscription rather than treating a previous draft as a saved setting.
Questions to settle before accepting costs
- How do you choose a sufficient plan without paying for hypothetical needs?
- Who decides whether to continue when a Shopify or app trial ends?
- How should the Billing profile entity, address, tax details and contact be checked?
- Why separate invoice periods, app cycles and bank settlement dates?
- How do an app recommendation, installation access and spending approval differ?
- After uninstalling, how can you distinguish an accrued charge from a new renewal?
- What evidence belongs with developer-billed cancellations and refunds?
- What should a monthly review retain so finance can trace each charge?
Credits are the balance shown at the top of the billing page and applied to the next invoice; they are not a discount and cannot be withdrawn.
Step 1: record the plan, trial and next charge
The teaching example remains a new desk-organization store with one physical product, Variant A and Variant B, planning a US launch with USD and an English storefront. That sales plan does not determine the entity's country, Shopify billing currency, promotional eligibility or ability to accept payments. Use the selected store's actual conditions and quote.
Plan controls the Shopify subscription and its capabilities. Billing contains amounts Shopify bills to the merchant. Apps may be billed through Shopify or directly by their developers. Customers paying for merchandise use a separate payment flow. Distinguishing these makes it possible to identify why a charge arose, who authorized it and where to cancel it.
Read the current state first
Review the current plan and trial state
Open Settings > Plan. Record the plan, free-trial or promotional status, end date, billing cycle, total payable, next charge date, capabilities and limits. In Settings > Billing, inspect current bills, pending charges and payment status as well. An advertised monthly equivalent is not a complete cost record.
How to confirm
Explain why the plan supports launch, what rate or plan follows the trial, and who will decide whether to retain, upgrade or cancel it on which date. Keep the price summary, check time, responsible person and redacted evidence location.If it goes wrong
If the state is unclear, confirm the store, page title and billing-view or plan-management permissions, then return to the complete Plan or Billing area. Check account conditions, required fields and returned messages instead of guessing the plan from an app page.
A Shopify free trial begins at signup, not when you start building the store. Trial length and promotions can depend on the account, date and location. An old screenshot or another merchant's offer is not your ongoing price. Expiry also differs depending on whether a paid plan has been selected. A store without a selected plan can pause; an account with a selected plan needs the applicable cancellation or deactivation process if it will not continue. Simply staying away from the admin is not cancellation. Apps can incur charges during a Shopify trial too.
The historical Plan screenshot below contains Basic, Development store and a subscriptions entry. It does not show an ordinary merchant's trial deadline, renewal quote or successful payment.
Admin path: Settings › Plan

Historical screenshot: locate plan and subscription areas. Development-store status does not establish a merchant's current price, trial duration or paid-plan eligibility.
Keep the current plan state and the next decision date. Mark an unconfirmed cycle or quote as unresolved. Do not subscribe or create a real payment just to complete a lesson record.
Step 2: give the plan decision a business reason
A higher plan is not automatically the better starting point. Write down current requirements for orders, staff accounts, Locations, Markets, reports, shipping, checkout and app dependencies. Then compare those needs with currently available plans. Historical plan names do not establish today's seat limits, features or regional eligibility.
Define an upgrade trigger
Set the business conditions for plan choice
Put the actual capability gap, monthly technology-cost ceiling, upgrade trigger, approver and review date in the cost sheet. Include revenue, margin, operating complexity, migration or exit costs, and capabilities lost on downgrade. For a possible future need, define a trigger and test an alternative on the current plan first.
How to confirm
The decision traces to a business condition and a responsible person. For example, compare verifiable transaction-fee savings at the applicable rates and actual savings from needed functionality with the plan difference and added tools. Total sales and hypothetical savings are not upgrade benefits.If it goes wrong
If an upgrade does not reduce costs, return to its written condition and recalculate with actual orders, rates and work. If the target is not met, assess a downgrade, its effective date and lost capabilities rather than adding more apps to cover the problem.
Record both an equivalent monthly budget and the cash payment when comparing annual and monthly billing. An annual plan's displayed monthly equivalent is not a monthly installment; the full year is generally charged upfront. Under current standard rules, an upgrade can take effect immediately with a prorated bill, while a downgrade or annual-to-monthly switch generally takes effect at the end of the current cycle. Free trials and promotions have separate rules, and a discontinued plan might not be available to return to. Read the actual confirmation amount, effective date, outstanding charges and service effects before the owner or an authorized plan manager acts.
Shopify Plan Cost Comparison
Bring applicable plan quotes, order assumptions and rates. Compare the cost difference and upgrade trigger, then record the result in the cost sheet. Confirm actual capabilities, billing cycle and payable amount in the selected store; an estimate does not approve a subscription.
Choosing a plan in a working document does not approve Subscribe. Before accepting a charge, inspect the billing period, currency, total payable, post-promotion rate, scheduled changes and refund conditions. Access to a new feature is not verification of its cost or service behavior. For changes affecting shipping services, also check whether carrier settings need reconfiguration.
Step 3: check the Billing profile and payer
Billing profile manages billing details and payment methods. Brand, legal entity and invoice company names can differ, but their relationship must be traceable to real entity and finance records. The customer-contact address in General, the Shopify account's billing address and the card address used by the bank have different jobs. Changing one does not update all the others.
Assign billing responsibility
Check the Billing profile
In Settings > Billing > Billing profile, inspect entity, invoice company and address, applicable tax information, currency, billing contact and payment method. Payment should be company controlled or have explicit approval and reimbursement responsibility. Do not depend indefinitely on a temporary employee's card. Handle card details only in the controlled payment process, outside this lesson's notes.
How to confirm
Invoices, the plan, app charges and payer responsibility map to the correct entity. If information needs changing, complete the authorized save and reopen it. Keep redacted fields, invoice identity, tax status, contact, time and version.If it goes wrong
For incorrect details, check permissions, entity and applicable tax fields first. For payment failure, an authorized person should inspect the payment method, outstanding bills and service restrictions, follow the actual payment flow, and confirm its result. Replacing a card does not establish that an old bill has been paid.
Current billing-address rules require a country supported by an active business entity and a billing currency supported for that country. Some contract accounts cannot edit this themselves. Do not invent an address to obtain a price or tax result. An address change applies to later bills; previously issued bills keep their original information. Finance still needs to confirm invoice identity, tax numbers and local accounting requirements before treating it as an appropriate company expense record.
The historical Billing overview below shows the Billing profile button, Current billing cycle, Add payment method and Past bills. The profile form is not open, so the image cannot establish that entity, tax or payer details were verified.
Admin path: Settings › Billing › Billing profile entry

Historical screenshot: the button is an entry point, not a completed billing profile. Zero-value CAD development bills cannot estimate an ordinary merchant's costs.
Step 4: separate charge categories and dates
A bank debit alone does not identify which app or period produced it. Budget the Shopify plan, domain, email, theme, required apps, optional apps, subscriptions, usage, shipping labels, transaction or payment-related fees, tax and credits separately. For each item, retain payee, charging basis, currency, service period, approver, payment result and review date. An external subscription might never appear on a Shopify bill.
Trace each charge
Read billing detail and timing
In Billing, use View current charges for pending amounts and open issued invoices from Past bills. Distinguish the Shopify period, each app's cycle, charge creation, invoice date and bank settlement date. Current standard monthly Shopify subscriptions and app billing use thirty-day periods, with a separate annual subscription cycle. They are not necessarily calendar months or synchronized renewals.
How to confirm
Reconcile individual items with invoices, apps, relevant orders and finance reports. Assign anomalies to someone. If a usage app offers a spending limit, record its scope and reset period; one app's limit is not a store-wide cost cap.If it goes wrong
For an unexpected total, separate source and period, then inspect trial conversion, usage, transaction fees and credits. Locate an unknown app charge and time in Billing, then check its installer, plan and uninstall status in Apps. Do not remove an app or change plans merely to guess at the cause.
An applicable billing threshold can produce an invoice before the regular subscription date. It is not a free allowance or spending cap. Annual plans can still receive bills for apps and other charges. Since bank settlement and invoice timing differ, a calendar month's card total cannot establish duplicate billing. Check where credits apply and whether they were used; a credit is not automatically a cash refund.
Step 5: approve the app's job, access and exit
A recommendation, permission to install and approval to spend are separate decisions. For every app, record its job, what it replaces, data access, recurring and usage fees, trial end, success metric, responsible person and exit condition. When two tools solve the same problem, test one first to avoid duplicate functionality and cost.
Approve app costs before installation
Create an app cost and permission record
Before installation, record name, purpose, billing provider, charge type, trial end, permission summary, success metric, approver and review date. Keep secrets out. Also identify data exports needed before exit, any leftover-code checks, and the person who will cancel or uninstall before the deadline.
How to confirm
Every retained app has a defined job and approval record. Leave an unexplained app uninstalled, or pause expansion until its owner resolves the cost or access question. A vanished widget does not establish cancellation or settlement.If it goes wrong
If a trial nears its end without meeting the intended metric, its owner should follow the actual billing provider's cancellation or uninstall process before the deadline and retain confirmation. Treat Shopify-billed and developer-billed subscriptions separately. List accrued charges rather than promising an automatic waiver or refund.
Check the decisions below against actual store values and evidence. An example, recommendation or plan is not a completed action.
Evidence behind plan and app spending
| Item | Decision to make | Reason and completion evidence |
|---|---|---|
| Current plan | Meet present launch needs and verify a capability gap first. | Capabilities, limits, actual quote and owner are traceable; hypothetical needs do not justify early spending. |
| Upgrade trigger | Reassess when order, team, market or functionality conditions are met. | Compare real savings, margin, plan difference, complexity and downgrade consequences. |
| Payment method | Company control or approved reimbursement responsibility. | Offboarding or a reimbursement dispute does not leave payment and invoices without an owner. |
| App approval | Approve job, permissions, cost, owner and exit condition individually. | Control recurring costs, usage and data risk; check replacement tools and trial dates. |
| Review cadence | Monthly, plus checks before trial deadlines and charges. | Reconcile invoices, apps, fees, tax and credits to catch duplicate subscriptions and usage anomalies in time. |
Return to the relevant step when a row lacks permission, an actual result or a responsible person. A completed table or apparently sufficient budget does not authorize a subscription.
After uninstalling, identify which cycle produced the charge
This separate hypothetical example is neither an app quote nor the store's actual bill. An app costs $20 per cycle. It is removed 2 days into a new cycle, but the same amount appears on the next invoice. Investigate when the charge arose, not just when the invoice arrived.
Hypothetical case: uninstalling after a new cycle starts
- Example fee per app cycle (USD)
- $20
- Days into the cycle at uninstall
- 2
Separate accrued current-cycle charges, future renewal and a developer's external subscription. The uninstall date is neither the cutoff for the whole Shopify invoice nor an automatic refund date.
Removing functionality can leave different billing states
| Item | Evidence to inspect | Supported conclusion |
|---|---|---|
| Uninstalled after the cycle started | Compare the app cycle start, approved charge, creation time and uninstall confirmation, not only the Shopify invoice date. | The $20 can have accrued before removal; it does not establish another renewal. Confirm that future cycles stop. |
| Only the theme app embed was disabled | Check whether the app remains installed, its subscription state and the actual billing route. | Hiding a storefront widget does not cancel a subscription. Complete the applicable cancellation or uninstall process and retain confirmation. |
| Removed in Shopify, still renewing with the developer | Inspect subscription, cancellation receipt and actual charges in the developer's billing account. | Cancel the external subscription with its provider. A refund request, approval and settlement are separate states. |
If I uninstall this app today, what do I still pay?

As text: the whole walk-through
- Uninstalled in Shopify Uninstall the app in Shopify: future billing cycles stop, but the pending charge already generated does not disappear.
- Next invoice The line can have accrued before removal and does not prove another renewal; still confirm future cycles stop.
- Embed hidden only Another case: only the theme app embed is hidden; the block is gone but the subscription is not cancelled.
- Developer may still bill A third case: the developer bills in its own account, and it may still renew after the Shopify uninstall.
- Cancelled with developer Cancel in the developer's billing account, then check the receipt and the actual charges that follow.
- Refund requested For a fee already paid, ask the developer for a refund; agreement and settlement are confirmed separately.
- Records kept Keep the install and uninstall dates, fee amount and time, invoice, cycle start and the developer's reply.
Illustrative: only the cases the lesson names, with no amounts or day counts; your app follows its real bill and the developer's terms.
For an app billed through Shopify, uninstalling stops future billing cycles but does not automatically remove a pending charge already generated. Before payment, ask the developer to investigate or issue an applicable credit. After payment, request a refund from the developer; agreement and actual processing must still be confirmed. Retain installation and uninstall dates, charge amount and time, invoice, cycle start and developer response. A submitted request is not a completed refund.
Step 6: archive invoices and schedule a monthly review
Make the costs traceable to finance
Download invoices and schedule review
Open the relevant invoice in Settings > Billing > Past bills and use Export bill for an appropriate PDF or CSV. Inspect entity, invoice identity, applicable tax details, category, currency, period, payment result and credits. Archive developer-billed invoices separately. Keep originals in controlled storage and expose only necessary redacted fields in shared evidence.
How to confirm
Invoice location, reviewer, anomalies, actions and next date are clear. Put the monthly review in the calendar and handle earlier trial deadlines or charges sooner. Finance can trace the source and the business can decide to retain, downgrade or cancel.If it goes wrong
If invoices, apps and payment records disagree, pause non-essential expansion and reconcile each charge and period. Give the developer or Shopify Support relevant evidence and retain the actual reply. A card total is not a breakdown, and reimbursement or tax treatment still needs its own confirmation.Keep as evidence
Retain cost-sheet version, redacted admin results, invoice location, approval and review responsibility, dates and unresolved items. A screenshot shows page state; the accompanying review explains how the team understands and manages the ongoing commitment.
Decide about the trial, then check your own cost sheet
Suppose a different app offers a 14-day trial without an assigned owner or recorded end date. This is a teaching input, not the current Shopify trial or a universal app offer. The desk-organization store should settle the missing responsibilities before deciding to install it.
An app trial without an owner or deadline
Self-check not answered
The choice records a decision. It does not install an app, cancel a subscription or change Shopify. Check these items against the actual store and leave any item without a result unticked.
Confirm invoice storage, its owner and the monthly calendar appointment in the work record too. Those two extra checks cannot be inferred from the three ticks above. Keep unresolved charges and access questions visible.
Conditions for continuing setup
| Done when | Stop if |
|---|---|
The plan has a business reason, Billing profile and payer are clear, charges can be separated, every app has an owner, deadline and exit condition, and invoice storage and monthly review are arranged. | Plan or trial costs cannot be explained, entity and payer responsibility conflict, an unknown app is charging, or a proposed app has no job and budget. |
| Evidence Redacted current plan/billing results, cost sheet and approval records. Unresolved charges, future usage and external subscriptions remain separate follow-ups. | |
Save the decision and continue to domains and email
Keep the complete budget, invoices and payment details in your own controlled work documents. Use a non-sensitive summary here for decisions, blockers, owners, deadlines and evidence locations. This browser saves choices, checks and notes automatically; export or copy before changing devices. Do not enter full invoices, card numbers, credentials or other secrets.
What this record establishes
Hold
Make the trial decision first
Assign responsibility and cost limits first
Actual items still need checking
Decision and checks recorded
Once cost and payment authority are clear, connect the domain and sender email, verifying website access and email identity separately. Locate billing anomalies and retain evidence before adding more tools.
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- Which Shopify plan should a new store choose?
- Choose the lowest plan that meets current launch needs. Define an upgrade trigger from orders, team, markets, margin and app dependencies, then compare actual savings with the price difference once business and cost data exist.
- Does a trial ending guarantee there will be no later charge?
- No. Distinguish Shopify free trials, promotions and app trials, then check whether a paid plan or charge has been selected or approved, its deadline and cancellation flow. Inactivity or not logging in does not cancel a subscribed service.
- Can a recommended app be installed immediately?
- A recommendation and installation access do not approve cost or permissions. Record job, access, fees, metric, owner, deadline and exit condition first. Test one tool for a shared job.
- Why might a deleted app still appear on a bill?
- App and Shopify invoice cycles can differ, and an accrued pending charge can reach a later invoice. Compare approval, cycle and uninstall timing. Cancel developer-billed subscriptions separately. A refund request is neither approval nor settlement.
- Can Billing invoices support company accounting?
- They can form part of expense evidence. Finance must confirm entity identity, tax details, expense allocation and local accounting requirements. This lesson cannot replace that check, and changing a billing address does not rewrite issued bills.
- Why keep reviewing billing monthly?
- Trials end, usage varies, and app plans or fees can change. Regular reconciliation can find duplicate tools, anomalies and pending cancellations. Set additional checks for deadlines and charges that occur before the monthly review.
Continue checking identity and app management
Work it out: which store pays for a plan it cannot use
Four stores as they stand (example data). Rule: read the feature gate first and the order volume second — a plan earns its price by what it unlocks (reporting, languages, staff accounts), while volume only says the store is busy, not that it must move up.
Plan against real need for four stores
| Item | Orders / month | Actually needs | Current plan |
|---|---|---|---|
| Store A | 20 | Basic products and checkout | Basic |
| Store B | 200 | Professional reporting and languages | Basic |
| Store C | 5 | Basic products and checkout | Plus |
| Store D | 60 | Three staff logging in separately | Basic |
Decide before you read on. Say which store pays for a plan it cannot use, and why B, with by far the most orders, is not that case.
Answer key: store C — five orders a month needing only basic products and checkout, while paying for Plus, which means every advanced capability it buys has no scenario attached to it. B and D are the opposite situation: B needs professional reporting and languages, D needs three separate staff logins, and both are feature gates rather than volume problems. C is the trap: its plan is the most capable, which reads as "safer anyway", while a plan's value can only be cashed out by features actually used.