A Shopify POS launch is ready when products, inventory, payments, devices, staff access, and customer workflows pass a live rehearsal before opening day.
Installing the POS app is not the same as being ready to sell. A fashion or beauty team can have a working card reader and still send the wrong size, shade, price, receipt, or inventory count into the customer journey. Treat the launch as a connected operating workflow: product data enters the device, staff use it to build a cart, payment completes the order, and the resulting stock and report records remain trustworthy.
This guide turns that workflow into an owner-based readiness review. It is useful for a first store, a pop-up, or a multi-location rollout. The operating times and checks are a framework for planning, not a promise that every store or plan has the same settings.
Write down the launch decision before testing. A useful readiness record has four columns: outcome, proof, limit, and next step.
| Area | Outcome | Proof to capture | Limit or condition | Next step |
|---|---|---|---|---|
| Catalog | Staff can find the exact sellable item | Product search and barcode scan return the intended variant | A parent product appearing does not prove every size, color, or shade is correct | Fix the product record or barcode mapping |
| Inventory | A sale changes the right location’s stock | Compare the POS quantity with the admin quantity after a test | Multi-location inventory must be allocated deliberately | Correct the location or pause the launch |
| Checkout | A shopper can pay and receive the intended confirmation | Run the approved test transaction and inspect the receipt | Live payment settings, taxes, discounts, and return rules still apply | Assign a payment or operations owner |
| Staff | Each role can complete its permitted job | Test the real device with the real staff access | The first device setup may require an owner or administrator account | Finish setup or revise permissions |
| Reporting | The team can reconcile the first day | Match POS totals, orders, payouts, and exceptions | A clean dashboard does not replace a physical or operational check | Schedule a daily review |
Shopify’s launch checklist separates the preparation into products, payments, staff, hardware, and a test transaction rather than treating app installation as the finish line.[2] Use the same separation in your launch brief. Give each area one owner and one piece of evidence; otherwise a team can report that “POS is ready” without knowing which part was actually tested.
For a small or mid-size rollout of five or fewer locations, Shopify currently recommends starting at least four weeks before opening, configuring the admin two to three weeks ahead, and setting up devices about one week before launch.[2] Larger rollouts or migrations need more runway because catalog cleanup, integrations, hardware, and staff training add dependencies.[5]
Decide what the location will and will not support on day one:
This is also the point to order hardware, confirm the POS plan and location settings, identify integration owners, and inspect the product data before it reaches a device. Shopify’s current guidance highlights product organization, barcode/SKU preparation, payment setup, network configuration, staff permissions, and hardware selection as separate preparation areas.[2]
Do not promise a launch date based only on hardware delivery. A reader arriving on time cannot compensate for missing variants, unallocated inventory, an untested discount, or staff who cannot complete a return.
Complete the admin work before device setup week:
Shopify’s POS guidance distinguishes barcodes, which a scanner uses to retrieve a product, from SKUs, which teams use for internal reference.[2] That distinction matters when a fashion associate is holding a physical garment or when a beauty associate is looking for a particular shade. Decide which identifier staff will use when a label is damaged or the scanner fails, and rehearse the fallback.
For fashion, inspect every sellable size and color combination. For beauty, inspect shade, finish, size, and any kit or refill relationship that changes the item a customer receives. For a broader product catalog, choose a small set of high-risk items—products with many variants, high value, active promotions, or frequent returns—and test those first.
Set up the devices at the selling location early enough to leave time for a replacement, network fix, or data correction. Before relying on a new device, confirm the catalog synchronization is complete in the POS app; Shopify notes that initial catalog sync time varies with network speed, catalog size, and product complexity.[2]
Run this device sequence:
Shopify advises setting up the network before connecting POS hardware because network misconfiguration can affect payment processing, hardware connectivity, and data synchronization.[2] A practical test is not “Wi-Fi works in the office.” It is “this device can find the intended product, communicate with the payment hardware, print or send the intended receipt, and complete the workflow at the register.”
A launch rehearsal should follow the same path a customer and associate will follow. Do not test only a successful product search.
Use a representative product and test, in order:
Shopify’s launch checklist describes processing a low-value custom sale as a payment test before launch; treat any test order as an operational record that must be reconciled and reversed or refunded using the store’s approved procedure.[2][5] If a payment, receipt, or inventory step fails, the workflow has failed even if the card reader itself lights up.
A useful rehearsal includes the situations that create queues and support messages:
For each failure, record the fallback in one sentence: who acts, where they look, what they record, and when they escalate. “Ask the manager” is not enough if the manager does not know which order, stock location, payment state, or customer promise to inspect.
This bounded audit is designed for the final review before a rehearsal or opening. It does not replace Shopify’s setup documentation or a full training session.
Choose three products: one simple item, one variant-heavy item, and one item with a promotion or return risk. Search for each, scan the physical label where applicable, and compare the displayed product, variant, price, and availability with the admin record.
Pass: the associate can identify the exact sellable item without guessing.
Fix: correct the product, variant, SKU, barcode, price, or availability before continuing.
Escalate: stop if the team cannot establish which system is the source of truth.
Check that the products are available to the intended POS location. Perform one controlled stock check and compare the POS, admin, and physical count for a high-risk variant.
Pass: the location, quantity, and variant agree.
Fix: correct allocation or tracking and repeat the check.
Escalate: pause if an online promise could be made from stock the store cannot actually sell.
Confirm the gateway is in the intended live or test state, then run the approved payment rehearsal. Inspect the receipt, order, tax, discount, and refund or void procedure.
Pass: the complete payment record is understandable to the customer and the finance or operations owner.
Fix: correct settings or hardware and repeat.
Escalate: stop if the team cannot explain how the transaction will be reconciled.
Ask the person who will open the register to complete a sale, a return, a discount, and a product lookup without coaching. Repeat one step with the manager or elevated role.
Pass: routine tasks and escalation boundaries are clear.
Fix: update permissions, smart-grid layout, or training.
Escalate: hold the launch if the only trained operator will not be present.
Write down where the team will check orders, inventory exceptions, payouts, hardware issues, and staff feedback. Name the opening lead, backup lead, and end-of-day reconciler.
Pass: every likely issue has an owner and a next check.
Fix: add the missing owner or evidence location.
Escalate: do not call the launch ready if the first-day review has no accountable person.
The same POS checklist needs different evidence by category.
Test size and color variants from a physical label, not just from the admin. Rehearse a return or exchange that changes the variant, and verify that the resulting inventory record is understandable to both the store associate and the online team. If a promotion is seasonal, check the selling price and the return treatment before staff training.
Test shade or finish selection, product bundles, and any customer notes the team genuinely needs to serve the shopper. Keep the staff workflow short enough that collecting customer context does not create an avoidable queue. Shopify’s POS requirements guidance identifies variant management and customer profiles as relevant considerations for apparel and health-and-beauty retailers.[4]
Test the workflows that create operational risk for the assortment: serial or lot references where your business requires them, gift cards, ship-to-home orders, pickup, high-value refunds, or products sold in multiple channels. Do not add a workflow to the launch plan merely because the POS can technically support it; prove that staff can use it correctly and that someone owns the resulting record.
If the same launch includes social catalog work, keep that as a separate approval and customer-path check. Shopify and Meta control their own eligibility and catalog rules; use the current Instagram Shopping guide rather than treating a POS pass as proof that a social channel is ready.
Use a simple decision record after the rehearsal:
The aim is not to produce a perfect score. It is to prevent a known uncertainty from becoming a customer-facing surprise. Record the evidence that supports the decision, not just a green checkbox.
On opening day, Shopify’s going-live guidance says to verify device connectivity, the selected location, catalog loading, live payment mode, cash tracking, and staff permissions before customers arrive.[3] During the day, monitor hardware disconnections and confirm orders appear under the correct location. At closing, reconcile each register and record training gaps.[3]
Choose one primary operational metric for the first week: unresolved transaction or inventory exceptions at end of day. Pair it with risks to monitor such as:
These are observational controls, not proof that a POS rollout caused or improved revenue. Compare the records with the launch baseline, note the store conditions and staffing, and make one change at a time when possible.
For multiple locations, Shopify recommends a phased rollout rather than opening every location simultaneously; its current guidance describes waves of two to five stores at least a week apart, with standardized device and card-reader choices to simplify support and training.[3] Use that as a starting option, not a universal rule. A smaller brand may pilot one representative store; a mature retail team may have the capacity to launch more locations while maintaining the same evidence and escalation discipline.
Before calling the Shopify POS launch ready, confirm:
A reliable POS launch is not the moment the app opens. It is the moment the brand can show that the product a customer chooses, the payment they make, the inventory the team promises, and the record the business reconciles all belong to the same workflow.
[2] https://help.shopify.com/en/manual/intro-to-shopify/shopify-pos-launch-checklist — Shopify POS launch checklist [3] https://help.shopify.com/en/manual/sell-in-person/getting-started/going-live-with-shopify-pos — Going live with Shopify POS [4] https://www.shopify.com/blog/pos-requirements — POS Requirements: Hardware and Software Checklist [5] https://www.shopify.com/blog/opening-a-new-retail-location — Opening a New Retail Location with Shopify POS: The Complete Launch Countdown (2026)