Quick answer: Before a new retail store opens, validate a real sales workflow from POS sign-in and order creation through receipt/label printing, an approved payment test and reconciliation. Also check Internet, LAN/Wi-Fi, access rights, scanners, printers and incident ownership. Mark an item ready only when it has an owner, a recorded test result and a fallback confirmed by the store and relevant provider.
Opening a store involves more than installing computers. The network may be up while POS accounts are not provisioned; a scanner may read a code while the product catalog is unsynced; a test sale may work at one counter while another printer is misconfigured. This checklist gives IT, store management and vendors a shared acceptance process before trading begins.
Pre-opening IT checklist for a retail store
| Area | Checks | Acceptance evidence |
|---|---|---|
| Connectivity | Primary ISP, modem/ONT, router, IP/DNS; confirm backup path if the store depends on cloud services | Documented network map, ISP contact, failover method and authorized owner |
| LAN and Wi-Fi | Separate business, staff and guest devices according to the approved design; test checkout, stockroom and office | Correct SSID/VLAN and a walk-through/roaming test in working areas |
| POS and payments | Role-based login, catalog sync, shift open, test order, authorized void/refund and reconciliation | POS/payment vendor confirms accounts, environment and fallback process |
| Printers and scanners | Receipt/label/kitchen printers where used, scanner, paper, IP, drivers and supplies | Test the real counter workflow; suitable spare device or consumables are known |
| Accounts and access | Store, manager, finance and vendor accounts; MFA, handover and emergency access | Named owner, least privilege, access-change process and no shared passwords |
| Devices and power | Approved UPS scope, outlets, cables, asset labels and equipment placement | Model/serial, connection map and receiving owner; no unapproved electrical work |
Plan the work by deployment milestone
1. Before installation: map the site and assign owners
Confirm checkout, stockroom and office locations, plus router/switch/access-point, printer and POS placement. Inventory each device with asset ID, serial, location, recipient and provider. Name the owners for ISP, local network, POS, payment gateway, printers and accounting/inventory software. If vendors own only their components, appoint one coordinator for dates, dependencies and acceptance criteria.
Do not assume Wi-Fi coverage is adequate because a nearby office has signal. Shelving, stock, walls, checkout layout and concurrent devices change the result. Mark required connection points and test in operating positions rather than standing next to an access point.
2. Before opening: validate connectivity against the approved design
Confirm the Internet circuit has been handed over and network equipment is labeled, documented and backed up under the agreed process. Test POS, store administration and related services using accounts with the right roles. Verify business and guest Wi-Fi separately according to the company design. Do not move POS onto guest Wi-Fi as an improvised fix unless an authorized owner has approved and tested it.
If the store needs backup connectivity, agree on activation conditions, the person authorized to switch paths, notifications and the procedure for returning to the primary connection. A phone receiving 4G/5G is not an accepted failover test by itself: verify the device, data plan, coverage, application path and operational steps.
3. Accept the full sales workflow
Use approved sample products or test data. Verify staff and manager accounts; find or scan an item; create an order; send it to the required printer; perform an authorized payment test; then verify status in POS and reporting. Test void/refund only where the account and environment permit it. Record which steps belong to IT, the POS vendor and payment provider.
Do not swipe a real card, create an unapproved sale or delete production data just to test. If a sandbox is available, follow the vendor’s procedure and confirm when the environment changes to live credentials.
4. Check printers, scanners and peripherals
Print a receipt, label or kitchen ticket where required at every relevant counter. Confirm paper size, printer mapping, connection port/IP, driver and paper location. Scan approved sample products and verify the returned code matches the catalog. Place spare supplies where staff can find them and clarify who may clear a jam, replace a roll or restart equipment.
If a device works only under one account or on one computer, record that constraint rather than calling the store fully ready. Do not install unverified drivers or software just to meet the opening date.
Assign responsibilities across store, IT and vendors
| Owner | Responsible for | Do not assume |
|---|---|---|
| Store manager | Shift readiness, user accounts, opening/closing procedure and device receipt | Do not recover uncertain payments by repeatedly entering or charging them |
| Internal/managed IT | Network, endpoints, Wi-Fi, access process, inventory, tickets and coordination | Do not change POS business rules or payment data without authorization |
| POS/software vendor | Application setup, catalog, integration, admin access and product support | Do not assume responsibility for ISP, all store Wi-Fi or unrelated endpoints |
| ISP/infrastructure provider | Connectivity and equipment within contract; escalation contacts | Do not assume responsibility for LAN/Wi-Fi installed by another party |
Minimum handover record
- Placement and connection map for modem/router, switches, access points, POS, printers and scanners.
- Device list with serial/asset ID, location, condition and receiving owner.
- System names, account roles and provisioning/revocation process; never put plaintext passwords in the handover.
- Test results, time, tester, redacted error evidence and open issues.
- Contacts, support hours, ticket channel, priorities, vendor dependencies and after-hours escalation.
- Approved fallback, activation criteria and reconciliation process after recovery.
Every unresolved issue needs an owner, due date and an explicit decision: block opening, accept a defined risk, or schedule post-opening improvement. Avoid a vague “monitor” status without an accountable person.
Run a short pre-opening drill
- Staff sign in with individual accounts and the correct roles.
- The manager validates POS connectivity and completes an approved test print/transaction.
- IT safely simulates a connectivity scenario without disrupting production; staff practice incident reporting.
- The owner checks that the ticket includes store, counter, device, time, symptoms and business impact.
- Restore, repeat the workflow, verify reporting and record acceptance.
Do not intentionally interrupt live connectivity or payment services without an approved test window. A tabletop scenario or sandbox can be used instead.
For a multi-branch retailer
Use one standard checklist but record each store’s floor plan, ISP, equipment and vendors. The opening report should show passed/failed items, blockers, response times and current owners. This helps headquarters identify branches that need attention without creating an unmanageable process for every location. Also see how to organize IT support channels for multi-branch companies and the IT model for 10–50-person offices.
Frequently asked questions
What should we check first before opening?
Test connectivity at actual work locations, use role-correct accounts, and run an approved end-to-end POS workflow including item lookup, order, printer and reconciliation. Confirm incident ownership at the same time.
Does every store need backup Internet?
It depends on cloud/POS dependency and the impact of an outage. If needed, test service reachability, switching and restoration. A spare SIM or router alone does not prove the fallback works.
Who owns a POS problem during opening?
The store manager protects the sales workflow and confirms impact; IT isolates network/device issues and coordinates the ticket; the POS vendor handles its application, configuration and data scope. Contracts and handover records should identify each boundary.
Should we create a real sale to test?
Only when the business and provider approve the test method, account, amount and void/reconciliation procedure. Prefer an authorized sandbox or test scenario; do not create live transactions or production data without approval.
Opening a new store or adding a branch?
IT Systems can review devices, network, Wi-Fi, access and incident intake, and coordinate relevant providers within the agreed scope.
