top of page
Search

Retail POS Cutover Checklist for Opening Day

Sep 9
5 min read

A retail POS cutover is the controlled move from setup and testing into real transactions. The goal is simple: before the doors open, prove that staff can sign in, ring a sale, take payment, print or send a receipt, update inventory and recover from a basic failure.

Do not treat the first customer as the final test. Run the checklist below with the actual devices, network, catalog and staff roles that will be used on opening day. Record who owns each issue and set a deadline for resolving it.

Set a Clear Go-Live Decision

Choose one person to make the final go/no-go decision. That person should have a short list of conditions that must be true before the store opens:

  • At least one complete test sale and refund has passed on every active register.

  • Taxes, prices, discounts and receipt details have been reviewed.

  • Staff can sign in with the correct permissions.

  • The primary internet connection is stable and the fallback process is understood.

  • Support contacts, escalation steps and credentials are available to authorized managers.

Vendor timelines vary. Shopify's current POS launch checklist, for example, recommends ordering hardware weeks in advance, configuring the store before installation and setting up devices before opening week. The useful lesson is vendor-neutral: cutover is the end of a sequence, not a same-day setup task.

Seven Days Before Opening

Freeze the Core Configuration

Set a deadline for changes to products, prices, taxes, employee roles, discounts and receipt settings. Last-minute edits create mismatches between registers and make test results unreliable.

Export or otherwise preserve the approved item list. Confirm that every sellable item has the correct name, SKU, barcode, price, tax treatment and inventory location. Test several edge cases, including a discount, a returnable item, a non-taxable item if applicable and an item with variants.

Label and Record Every Device

Create an inventory of registers, tablets, payment terminals, barcode scanners, receipt printers, cash drawers, customer displays, switches, routers and backup hotspots. Give each device a simple location-based name such as Register 1 or Stockroom Scanner.

The PCI Security Standards Council advises merchants to keep a list of payment terminals, know what the devices and cables should look like and inspect them for unexpected changes. Photographing the approved terminal setup can give managers a practical reference for future checks.

Two to Three Days Before Opening

Test the Complete Transaction Path

Do not stop after confirming that the POS app opens. At each register, run a controlled test that covers:

  1. Staff sign-in.

  2. Barcode scan and manual item search.

  3. Price, tax and discount calculation.

  4. Chip or contactless payment using an approved test procedure.

  5. Printed and emailed receipt.

  6. Cash-drawer opening where applicable.

  7. Inventory reduction in the correct location.

  8. Refund or void with the correct manager permission.

  9. End-of-day report visibility for an authorized manager.

Document the test transaction so it can be identified and reversed correctly. Never use or record real customer payment data for testing.

Verify Staff Roles

Create individual accounts instead of sharing one manager login. Test what cashiers, supervisors and managers can actually do. A cashier should not gain administrative access simply because a manager signed into the register during setup.

Confirm the process for a forgotten password, locked account, new employee and terminated employee. Keep emergency access information in an approved password manager or other controlled location, not on a note beside the register.

Check Printers, Scanners and Drawers

Accessories often fail for simple reasons: the wrong printer is selected, paper is loaded incorrectly, a scanner is paired to a different tablet or a cash drawer cable is connected to the wrong port. Test every accessory from the register that will use it.

Keep spare receipt paper, approved charging cables and batteries where staff can find them. If the store uses labels, confirm the label size and print alignment before inventory is placed on the sales floor.

The Day Before Opening

Test Connectivity and Segmentation

Confirm that every register has reliable access to the required POS and payment services. Walk the store with any mobile POS device and test the checkout path in the places where staff will use it.

Keep payment and business devices off an open guest network. Verify that guest Wi-Fi cannot reach registers, printers or back-office systems. Confirm that switches, wireless access points and firewalls have power and that critical network equipment is not connected to an outlet that staff may unplug during cleaning.

If you need help validating checkout connectivity, see Sosa Solutions NYC's network cabling and Wi-Fi installation services.

Rehearse the Internet-Outage Procedure

Decide what staff will do if connectivity fails: pause card transactions, use a supported offline mode, move to a backup connection or accept only approved payment types. The answer depends on the POS platform, hardware and merchant policy.

Do not assume offline payments work on every device or payment type. Square's current guidance, for example, lists hardware and payment limitations, requires sellers to manage the feature in advance and places responsibility for declined or expired offline payments on the seller. Review your own provider's documentation and risk terms before enabling any fallback.

Print a short outage card for managers with the approved steps, support numbers and the instruction not to improvise with personal devices or unapproved payment apps.

Opening-Morning Checklist

Complete this check before the first customer arrives:

  • Power on and visually inspect every payment terminal.

  • Confirm the date, time and store location on each register.

  • Sign in with a cashier account and verify the correct permissions.

  • Scan one item from each important product category.

  • Confirm receipt printers, cash drawers and scanners respond.

  • Check that inventory and online orders are syncing where applicable.

  • Verify the primary and backup connectivity status.

  • Confirm managers have the support and escalation sheet.

  • Remove test orders, notes and temporary setup labels from customer view.

  • Record the time, result and initials of the person completing the check.

First-Hour Monitoring

Assign one person to watch the system instead of assuming silence means success. Track slow checkouts, payment declines, printer errors, barcode failures, inventory mismatches and login problems. Separate genuine system issues from training questions so the right owner responds.

Avoid making broad configuration changes during a busy period unless they are necessary to keep the store operating safely. Capture the symptom, device name, time, error message and transaction context before escalating. That information helps support teams diagnose the issue without asking the store to repeat the failure.

POS Cutover Sign-Off

Use a simple sign-off record for each register:

  • Register and location name

  • Device serial or asset identifier

  • Test sale and refund result

  • Scanner, printer and drawer result

  • Staff-role test result

  • Network and fallback result

  • Open issues and responsible owner

  • Final go/no-go decision, name and timestamp

Keep the completed record with the store's launch documentation. It becomes a baseline for later troubleshooting, new-location rollouts and equipment replacement.

Get Opening-Day Support in Place

A good cutover reduces uncertainty before opening day and makes remaining problems easier to isolate. Sosa Solutions NYC provides POS installation and support, store-opening IT solutions and retail IT support for businesses preparing new or upgraded locations.

If your opening date is approaching, schedule a readiness review before the final cutover so there is time to correct device, network, account and workflow issues without disrupting customers.

Comments


bottom of page