Your First Week on a New POS: A Setup Checklist
A day-by-day checklist for your first week on a new POS: verify imported data, lock down staff logins, run an early end-of-day close, test the hardware, and keep the old system read-only until the numbers reconcile.
The first week on a new POS decides whether the switch pays off or turns into three months of cleanup. The software is rarely what fails. What fails is verification: a price that imported wrong, a tax rate nobody checked, five staff sharing one PIN, an old account cancelled before the last deposit cleared. This checklist walks the week day by day. None of it takes more than an hour or two, and all of it is cheaper now than after your first busy Saturday.
What should you verify before your first real sale? (Days 1 and 2)
Treat every imported record as unverified until you have checked it against the old system. A typical POS import carries products, prices, categories, stock counts, and customers. Historical orders, discounts, and gift card balances usually stay behind in the old system, which means the import hands you a starting point, not a proven catalog.
Spot-check your top 50 sellers: name, price, tax category, and stock count against the old system.
Confirm tax rates for every jurisdiction you sell in, and for every product class taxed differently (prepared food, alcohol, exemptions).
Run one complete transaction: a sale, the receipt, then a refund. Confirm all three appear correctly in reports.
Check the receipt itself: business name, address, and tax registration number where required.
The tempting shortcut is to start selling and fix issues as they surface. A wrong price costs you a few dollars and a correction. A wrong tax rate compounds silently on every sale and surfaces at filing time, as your accountant's problem and your liability.
How do you set up staff without creating security holes? (Days 2 and 3)
Give every person their own login and start with restrictive permissions. A shared PIN feels faster during a hectic first week, and it also erases accountability for every refund, void, discount, and drawer variance from day one.
Create an individual login or PIN for each employee before their first shift.
Set roles so refunds, voids, and price overrides need a manager.
Train exactly two flows on day one: a normal sale, and what to do when a payment fails or a customer disputes a charge. Everything else can wait.
If your team is new to the vocabulary, this rundown of 30 POS terms every new merchant should know shortens the training conversation.
When should you run your first end-of-day close? (Days 3 and 4)
Run it on your quietest day, and run it slowly. The close is where data problems become money problems, so you want your first one to happen when the drawer holds twelve transactions, not two hundred.
Set a consistent float (the starting cash in the drawer), count blind at close, and compare the count to the report. The full routine is covered in cash drawer management in a cloud POS. Then take it one step further: when the deposit lands in your bank account, match it against the POS report for that day. Settlement (when your payment processor actually pays you out) runs on its own cycle, and learning that cycle in week one beats discovering it during month-end.
What should you test on hardware before the weekend? (Days 4 and 5)
Test everything a customer touches, with real cards and real paper. Demo mode proves nothing about a Saturday rush.
Tap, insert, and swipe with actual cards, then refund one of those payments back to the card.
Print receipts and fire the cash drawer from a live sale, not a test screen.
Drop the Wi-Fi mid-sale and watch what the POS does.
Stock spare charging cables and know how long the card reader runs on battery.
A reader that fails at Saturday noon is a crisis. The same failure on Wednesday afternoon is an email to support.
When can you switch off the old system? (Days 5 to 7)
Later than you would like. The old system holds your history, and week one is exactly when you will need it.
Keep read-only access for returns of items sold before the switch, warranty lookups, and year-over-year comparisons.
Export the reports you will want later: monthly sales, tax summaries, inventory valuation.
Do not close the old payment account until its final settlement deposit has landed.
Put the cancellation date in your calendar. Paying two subscriptions for an extra quarter is a common, avoidable tax on switching, and it stacks on top of the rest of a retail SaaS bill.
One structural note: this checklist assumes a careful first week costs you nothing extra. On Final there is no monthly software subscription; you pay per transaction through Final Pay, so a slow week of verification is free. The help center covers the week-one how-tos, from setting up your first station to creating staff roles.
What actually matters in week one?
Verification beats speed. Check the imported data before the first sale, give every employee their own login, run the first close early and slowly, break the hardware on purpose before customers can, and keep the old system readable until the numbers prove out. The rule of thumb: do not retire the old system until the new one has survived one full end-of-day close and one bank deposit you personally matched to a report.
If you are still choosing the system rather than setting it up, start with why merchants are switching POS in 2026, which pairs a buying rationale with a no-downtime migration checklist.
Frequently asked questions
How long does it take to set up a new POS?
The data import itself usually takes a day or less. Verifying that data, training staff, and reconciling your first close is what fills the rest of the week, so budget a full week of running carefully before you trust the system.
Should I run my old and new POS in parallel?
Keep the old system accessible at least until your first end-of-day close and your first settlement deposit both reconcile against the new system's reports. After that, read-only access is enough.
What data actually transfers to a new POS?
Most imports carry products, prices, categories, stock counts, and customers. Historical orders, discounts, and gift card balances usually stay in the old system, so export any reports you need before that account closes.
When should I cancel my old POS subscription?
After you have exported historical reports (monthly sales, tax summaries, inventory valuation) and confirmed the final settlement deposit from the old payment account has landed in your bank.
Do staff need full retraining on a new POS?
Not on day one. Train two flows first: a normal sale, and what to do when a payment fails. Add refunds, exchanges, and edge cases across the rest of the week once the basics are muscle memory.