POS startup, product lookup, barcodes, pricing, promotions, payments, printers, cash drawer, returns, loyalty, omnichannel, offline mode, security, retesting, and corrective-action template
POS Functionality Checklist
Test whether each retail POS lane can complete the full customer transaction reliably, from login and item scan to pricing, promotions, payment, receipt, returns, loyalty, offline recovery, and final transaction posting.
Can the terminal complete a card payment with the correct amount and return a clear final status to the POS?
Store Manager and IT Support | Activate fallback | Capture error | Assign owner | Retest before closure
Select an answer to preview the workflow.
About this checklist
What a POS functionality checklist should help you test
Verify that terminals, item data, pricing, promotions, payment methods, peripherals, returns, loyalty, omnichannel services, offline recovery, security permissions, and end-to-end transaction posting work together before customers find the failure.
When
Before opening, after POS changes, during store readiness, after incidents, and during recurring technology checks
Use the full checklist after new deployments, software updates, payment changes, pricing launches, store openings, or outages, and use a shorter core test routinely.
Who
Store managers, supervisors, IT support, POS administrators, payments, pricing, and retail operations
Store teams can run functional tests while technical owners resolve configuration, integration, device, payment, pricing, or network issues.
Outcome
A transaction-ready store with clear fallback and support ownership
Create one evidence trail across terminal status, product entry, price, promotions, payments, peripherals, exceptions, integrations, offline recovery, and retesting.
Complete POS functionality checklist
60 checks across terminal startup, item entry, pricing, promotions, payments, peripherals, returns, customer functions, offline recovery, and security
Ten sections, sixty checks. Expand each section, then adapt tender types, promotion logic, taxes or fees, peripheral devices, customer functions, offline limits, role permissions, test transactions, and escalation rules to your POS environment.
Section 1POS setup, terminal scope, store configuration, user access, ownership, and previous issues
- Confirm the store, test date, reviewer, POS terminal IDs, checkout lanes, self-service devices, mobile POS devices, payment terminals, and other transaction points included in the check.
- Verify the correct store, register, business date, currency, tax configuration, language, location profile, and trading setup are loaded on each sampled POS terminal.
- Confirm required cashier, supervisor, manager, and support user accounts can sign in with the correct role permissions and no shared or unauthorized credentials are being used.
- Review recent POS outages, payment failures, pricing errors, printer issues, network incidents, failed promotions, hardware faults, and open support tickets before testing.
- Identify critical POS failures for the location, such as inability to complete sales, widespread payment failure, incorrect customer pricing, missing transaction records, or an unavailable fallback process.
- Assign ownership for POS application, payments, pricing, promotions, products, peripherals, network, devices, store support, and corrective-action closure.
Section 3Product lookup, barcode scanning, PLU, quantity, variants, item data, and transaction entry
- Scan representative barcodes and verify the correct product, description, SKU, size, variant, unit price, and tax or category treatment appear on the transaction.
- Test manual item search, PLU entry, SKU lookup, menu navigation, or category selection used when a barcode is unavailable.
- Verify quantity changes, multiple-unit entry, weighted items, open-price items, modifiers, add-ons, variants, or other store-specific transaction inputs work as intended.
- Check invalid, duplicate, unreadable, discontinued, or unknown barcodes trigger the expected message and do not add an incorrect product silently.
- Confirm product master changes, new launches, discontinued items, price files, and assortment updates are visible on the POS within the expected rollout process.
- Record barcode mismatch, wrong item data, failed search, missing product, incorrect variant, duplicate scan behaviour, or other item-entry issues.
Section 5Card, contactless, QR, wallet, gift card, voucher, split tender, and payment processing
- Complete a test transaction using the primary card-payment method and verify authorization, amount, terminal response, POS status, and transaction completion are synchronized.
- Test contactless, QR, mobile wallet, local digital payment, or other commonly used electronic tender methods supported by the store.
- Verify gift cards, store credit, vouchers, coupons used as tender, or other stored-value instruments can be validated, redeemed, and reflected correctly where applicable.
- Test split tender, partial payment, mixed cash and card, or other multi-tender scenarios used by the business and confirm the remaining balance updates correctly.
- Check declined, cancelled, timed-out, duplicate, reversed, or failed payment attempts return a clear status and do not create an unintended completed sale.
- Record payment-terminal disconnects, authorization mismatch, duplicate charge risk, tender mapping error, failed stored-value redemption, or other payment-processing issues.
Section 7Returns, refunds, exchanges, voids, cancellations, suspended sales, reprints, and exception workflows
- Process a representative return or refund and confirm product, quantity, original payment method, refund amount, stock treatment, and authorization follow the approved workflow.
- Test an exchange or return-and-resell scenario where supported and verify the POS calculates the correct net amount and tender difference.
- Verify item void, transaction void, cancellation, no-sale, post-void, or other exception functions require the intended reason, role, and approval.
- Check suspended, parked, held, recalled, or saved transactions can be retrieved accurately without losing items, customer information, pricing, or tender status.
- Verify receipt reprint, invoice copy, transaction lookup, order lookup, or other recovery functions retrieve the correct historical transaction.
- Record refund failure, incorrect stock movement, unauthorized void, lost suspended sale, duplicate reversal, failed receipt lookup, or other exception-workflow issue.
Section 9Offline mode, network loss, synchronization, recovery, failover, updates, and business continuity
- Confirm the store knows the approved fallback procedure for POS, payment, or network outages and that required offline or manual controls are available where supported.
- Test or review offline transaction behaviour, cached product data, tender restrictions, transaction limits, or other offline-mode controls without creating uncontrolled sales risk.
- Verify transactions created during temporary connectivity loss synchronize correctly after connection is restored and do not duplicate or disappear.
- Check the POS recovers normally after application restart, terminal reboot, payment-terminal reconnect, printer replacement, or temporary network interruption.
- Confirm software updates, configuration changes, price files, product data, device firmware, or other scheduled changes complete without leaving terminals on inconsistent versions.
- Record failed synchronization, lost transaction, duplicate transaction, unusable offline mode, inconsistent terminal version, or weak outage fallback requiring action.
Section 2Terminal startup, application login, register status, connectivity, speed, and basic navigation
- Confirm each sampled POS terminal powers on normally and completes the expected startup sequence without repeated error messages or hardware warnings.
- Verify the POS application launches, authenticates, loads the correct register, and reaches the transaction screen without abnormal delay.
- Check terminal date and time, network connection, store server or cloud connection, device status, and required background services are operating normally.
- Navigate through core cashier functions and confirm menus, buttons, item search, transaction controls, and role-based options respond correctly.
- Observe application speed during login, item entry, tender selection, receipt generation, and transaction completion for excessive delay or freezing.
- Record startup failure, login error, slow performance, frozen screens, connectivity warnings, incorrect register mapping, or other terminal-level issues.
Section 4Pricing, promotions, discounts, taxes, fees, bundles, coupons, and offer calculation
- Compare sampled shelf or displayed prices with the POS selling price and confirm the correct base price is applied.
- Test active promotions such as percentage discounts, fixed discounts, multi-buy offers, bundles, buy-one-get-one offers, member pricing, or campaign prices as applicable.
- Verify coupon codes, voucher codes, promo codes, loyalty offers, or other redemption mechanisms apply only when eligibility rules are satisfied.
- Check manual discounts, price overrides, manager approvals, employee discounts, and exception pricing require the intended role or authorization.
- Confirm taxes, service charges, fees, deposits, rounding, or other required transaction calculations are applied correctly for sampled items and tender scenarios.
- Record displayed-price mismatch, incorrect promotion logic, failed bundle, unsupported override, wrong tax or fee calculation, or other pricing defect.
Section 6Cash drawer, receipt printer, scanner, customer display, scale, label printer, and POS peripherals
- Verify the cash drawer opens only during approved transaction or manager functions and closes securely after use.
- Print a receipt and confirm store details, transaction number, date, time, items, quantities, prices, discounts, taxes, tenders, total, and other expected information appear clearly.
- Check receipt printer paper feed, cutter, print quality, status alerts, and replacement process work without repeated jams or missing output.
- Verify barcode scanner, handheld scanner, customer-facing display, weighing scale, label printer, keyboard, touchscreen, or other connected peripherals respond correctly where used.
- Confirm customer-facing displays show appropriate item, price, promotion, subtotal, payment, and completion information without stale or incorrect transaction data.
- Record drawer failure, printer error, scanner issue, peripheral disconnect, inaccurate scale data, blank customer display, or other hardware-related POS fault.
Section 8Customer profile, loyalty, membership, order lookup, omnichannel, pickup, and service functions
- Verify customer search or profile lookup returns the correct customer using the approved identifier and displays only the information required for the store workflow.
- Test loyalty or membership identification, points earning, points redemption, tier benefits, member pricing, or other customer-program functions used by the business.
- Confirm online order, click-and-collect, pickup, delivery, reservation, service order, or other omnichannel transaction lookup works where integrated with the POS.
- Check order status, customer name, item details, payment status, balance due, pickup code, or other required service information remains consistent between systems.
- Verify customer-facing functions such as digital receipts, email or SMS receipt options, warranty registration, order confirmation, or pickup acknowledgement operate where enabled.
- Record customer lookup failure, loyalty mismatch, missing order, incorrect status, duplicate redemption, failed digital receipt, or other customer-service integration issue.
Section 10Security, test transaction, evidence, corrective actions, validation, support escalation, and final sign-off
- Verify cashier and manager permissions restrict sensitive functions such as refunds, voids, price overrides, cash-drawer opening, reports, configuration, and administrative access to authorized roles.
- Check terminals are not left signed in unattended, unauthorized applications are not used on POS devices, and physical devices, cables, payment terminals, and access points show no obvious tampering or uncontrolled access.
- Complete an end-to-end representative sale covering product scan, price, promotion, customer or loyalty function, payment, receipt, and final transaction posting to confirm the complete workflow.
- Record every failed check with terminal ID, exact error, transaction or test scenario, screenshots or photos where appropriate, customer impact, immediate workaround, and support reference.
- Assign each POS issue to a named store, IT, payments, pricing, product, network, vendor, or operations owner with severity, due date, escalation route, and verification requirement.
- Record the final POS-functionality status, unresolved critical issues, open tickets, affected terminals, fallback readiness, next retest date, reviewer, store manager, date, time, and sign-off.
Printable POS test sheet
Run one structured POS test before checkout problems reach customers
Download the printable version, or continue below to see how the same workflow can capture terminal evidence, critical failures, fallback status, support ownership, retesting, and multi-store reporting in Taqtics.How to use it
Test the complete transaction, not just the POS home screen
Start with terminal and network readiness, add products, verify price and promotions, complete different tenders, test peripherals and exception workflows, then finish with offline recovery and one end-to-end sale.
Start with terminal readiness
Check startup, login, register mapping, application speed, connectivity, and user permissions.
Build a representative basket
Scan normal items, promotions, variants, difficult barcodes, new products, and store-specific transaction types.
Test payment and exceptions
Complete common tenders, failed payments, returns, refunds, voids, suspended sales, loyalty, and customer functions.
Retest the full flow
After fixing an issue, repeat the end-to-end sale through final payment, receipt, transaction posting, and any required synchronization.
Live interactive demo
See how a POS functionality check works in Taqtics
Test a representative payment step, record a critical failure, attach terminal evidence, assign the technical owner, and preview the retest workflow.
Capture store, register, test scenario, error, screenshot or photo, fallback status, owner, ticket, and retest evidence together.
Route POS, payment, pricing, promotion, product, network, printer, or device issues to the responsible support team.
Track affected terminals, recurring defects, critical outages, open tickets, fallback readiness, and resolution trends.
Illustrative website demo. Responses are not stored or submitted.
Why digitize it
A clearer way to verify POS readiness across every store
Taqtics connects POS test schedules, terminal-level evidence, failed checks, technical ownership, support tickets, corrective actions, retesting, approvals, reports, and dashboards in one multi-location workflow.
Standardize POS test scenarios
Use consistent checks for terminals, items, prices, promotions, payments, peripherals, returns, loyalty, offline mode, and security.
Capture the exact failure
Record terminal ID, screenshot or photo, error message, receipt, payment status, network condition, test basket, and customer impact.
Route issues to technical owners
Assign IT, payments, pricing, product, network, vendor, or store actions with severity, deadlines, escalation, and support references.
Verify the fix with a retest
Keep the issue open until the same scenario passes and the complete sale posts, prints, synchronizes, and closes correctly.
Frequently asked questions
POS functionality checklist FAQs
What should a POS functionality checklist include?
It should cover terminal startup, login, connectivity, item scan and lookup, pricing, promotions, taxes or fees, payment methods, printers and peripherals, cash drawer, returns, refunds, voids, customer or loyalty functions, offline mode, synchronization, permissions, evidence, retesting, and final sign-off.
When should POS functionality be tested?
Test after new-store setup, POS deployment, software or configuration changes, payment changes, major pricing or promotion launches, device replacement, network incidents, or recurring support issues. A shorter critical-path test can also be part of opening readiness.
Which POS failures should be treated as critical?
Examples include inability to complete sales, widespread card or payment failure, materially incorrect customer pricing, transaction loss or duplication, inability to produce required transaction evidence, or another failure that makes normal checkout unreliable without an approved fallback.
What test transactions should be included?
Use a representative normal sale plus scenarios for promotions, common tenders, failed payment, return or refund, void, loyalty or customer lookup, and any store-specific flow such as pickup, delivery, weighted items, gift cards, or split tender.
What evidence should teams capture for POS issues?
Record store and terminal ID, exact test scenario, error message, receipt, screenshot or photo, payment-terminal status, network condition, support ticket, fallback used, owner, and successful retest evidence.
How should a POS issue be closed?
Fix or configure the affected component, repeat the same failed scenario, then complete an end-to-end sale to confirm item data, pricing, promotion, payment, receipt, transaction posting, and synchronization work correctly before closure.
Schedule POS checks, capture terminal evidence, flag critical failures, assign support owners, track fallback status, verify fixes, and compare checkout readiness across every location.
Know whether every POS lane can complete the customer transaction before trading starts
Standardize functional testing, capture exact failures, route issues to the right technical team, verify the fix through retesting, and see recurring POS problems across your store network.
Printable PDF | Free Taqtics trial | No credit card required