POS operations guide
Retail self-checkout POS software guide
A self-checkout lane must complete one retail basket from scan or weight through payment, sale, stock and receipt exactly once. Prove the customer path, attendant exceptions and day-close reconciliation together before rollout.
Evidence and review scope
Evidence reviewed 2026-08-18. Pinned source and documentation review plus 92 focused source and DOM tests.
Stable release: v1.3.0. No bundled customer self-checkout screen, physical lane, integrated payment terminal, loss-prevention system, accessibility conformance audit or complete unattended shift was accepted.
What the current evidence establishes
92 focused tests passed
At exact source commit b531ef4308c4dc3a25f250551a54fc5616e3b8d9, ten focused desktop test files passed 92 tests with zero failures.
Retail record path documented
The pinned user guide covers item barcode, tax, sale, payment, receipt, stock movement, inventory logs and low-stock workflows.
Scan and weight boundaries tested
Focused tests cover item-grid barcode handling, scale frames, weighed quantity and precision, and mixed counted and weighed receipt lines.
Receipt, report and sale controls tested
Focused tests cover receipt and report layout, payment labels, report lifecycle, till shortcuts, one sale-submit path and write-permission checks.
Hardware limits are published
The pinned hardware matrix distinguishes code-tested, standards-based and unsupported devices. Integrated card terminals and label printers are not implemented in that matrix.
Self-checkout itself remains unproven
The review did not run a customer-facing checkout UI, attendant station, physical scanner or scale, provider payment, anti-loss control, installed accessibility test or complete closing shift.
Choose the self-checkout operating model before hardware
The same scanner does not create the same operating risk. Assign customer help, exceptions and closing ownership before choosing a lane design.
| Model | Customer task | Staff responsibility | Acceptance threshold |
|---|---|---|---|
| Cashier checkout | Presents goods and pays | Scans, resolves every exception and closes payment | Stable baseline for item, tax, payment, stock and receipt |
| Supervised self-checkout | Scans or weighs goods and follows payment prompts | Monitors nearby lanes and approves exceptions | Every help request is visible and one attendant can recover a failed basket |
| Unattended checkout | Completes the basket without nearby staff | Responds remotely or after an alert | Identity, restricted goods, payment, loss, accessibility, outage and recovery controls are independently accepted |
| Restaurant self-order kiosk | Chooses menu items and modifiers | Manages menu, order and kitchen exceptions | Use the separate restaurant kiosk guide; it is not retail self-checkout |
Practical workflow
Use one item and price truth
Customer and cashier lanes must resolve the same identifier to the same item, unit, price, tax, offer and availability. Version catalogue changes and test one sample from every important rule.
Design exceptions before the happy path
Unknown or duplicate barcodes, loose goods, restricted items, quantity changes, removals, abandoned baskets and help requests need visible states and an authorized recovery owner.
Treat payment as a separate contract
Approved, declined, cancelled, timed-out and uncertain provider states must map to one POS sale or no sale. A retry must not create a second charge or stock movement.
Reconcile the whole lane
Compare opened baskets, completed POS sales, payment settlement, receipts, voids, refunds, stock movement and unresolved exceptions before close.
Self-checkout acceptance flow
Treat each handoff as a test record. A lane is not accepted because one barcode scanned or one card payment succeeded.
Identify the lane and session
Record the branch, lane, software version, device versions and basket reference so staff can trace every later event.
Identify or weigh each item
Read the approved barcode or price-lookup choice, or capture a stable weighed quantity using the exact installed device and local legal-metrology process.
Apply the POS rules
Show the intended item, quantity, unit, price, tax, discount and total from the approved catalogue before payment.
Route exceptions to staff
Unknown codes, duplicate scans, removals, restricted goods, unstable weight and customer help create a visible request with an authorized response.
Confirm the basket
The customer can review items and totals, correct permitted mistakes and cancel before payment without leaving an unexplained sale.
Resolve payment state
The system distinguishes approved, declined, cancelled, timed-out and uncertain outcomes. Staff can see and recover the same state.
Commit sale, stock and receipt once
One accepted basket creates one durable sale, the expected stock movement and a searchable receipt. Retry logic cannot duplicate them.
Reconcile and recover
Closing reports connect lane sessions, POS sales, settlement, exceptions, refunds and stock. Outage tests prove fallback and restart behavior.
Hardware and software required
Hardware
- Touchscreen and enclosure tested at the installed height, reach, viewing angle and lighting.
- Barcode scanner tested with every symbol and package condition the store accepts.
- Commercial scale and price-lookup method reviewed for the installed market when loose goods are sold.
- Receipt printer with a visible paper-out state and a staff reprint path.
- Payment terminal supplied and supported by the merchant's acquirer for the exact integration.
- Attendant alert, network and power equipment with a rehearsed fallback.
Software and ownership
- Versioned item, barcode, unit, price, tax, offer and restriction data with named owners.
- Customer flow with clear progress, correction, cancellation and help controls.
- Role-based attendant actions for approval, removal, void, refund, reprint and recovery.
- Documented payment states and duplicate sale or charge prevention.
- Sale, stock, receipt, exception and settlement reports that share traceable references.
- Market-specific accessibility, payment, privacy, consumer and legal-metrology review.
Setup sequence
- Start with one supervised lane beside a stable cashier checkout. Record exact software, scanner, scale, printer, payment, network and enclosure versions.
- Freeze a representative catalogue and test ordinary, discounted, taxed, unknown, damaged-code, loose and restricted examples that the store actually sells.
- Review the installed customer interaction using applicable accessibility requirements. W3C WCAG2ICT is informative guidance for non-web and closed-functionality systems, not an installation certificate.
- Confirm local legal-metrology rules and inspect the exact commercial scale workflow before charging by measured quantity.
- Complete approved, declined, cancelled, timed-out and uncertain payment paths with the acquirer-approved terminal and integration.
- Test remove, void, abandon, help, reprint, refund and attendant authentication without creating duplicate sales or hidden stock movement.
- Disconnect scanner, scale, printer, payment, network and POS dependencies one at a time. Record customer message, staff fallback and recovery evidence.
- Close a mock shift by reconciling lane baskets, sales, settlement, exceptions, refunds, receipts and stock, then run a supervised pilot before expansion.
What each person sees
Customer
Can identify each item and total, correct permitted mistakes, request help, understand payment outcome and receive a searchable receipt.
Attendant
Sees the lane and exception, authenticates once, performs only permitted actions and returns control without losing the basket.
Store manager
Reconciles baskets, sales, payment, voids, refunds, interventions and stock, then reviews failure rates by lane and cause.
Implementation owner
Maintains the version record and coordinates hardware, accessibility, payment, privacy, legal-metrology and recovery acceptance.
Mistakes to avoid
Avoid these during rollout
- Buying several lanes before one supervised basket and close can be reconciled.
- Assuming a barcode scanner, scale or terminal works because its connector fits.
- Hiding uncertain payment, printer or network states from customers and attendants.
- Letting a retry create a second sale, charge, receipt or stock movement.
- Treating staff intervention as a failure instead of measuring why it was needed.
- Using a web checklist as proof of legal, accessibility, payment or weighing compliance.
- Calling a restaurant order kiosk retail self-checkout or promising a bundled Posnic lane that has not been accepted.
Run the 24-record retail self-checkout worksheet
Record the exact lane, item samples, exception paths, payment outcomes, accessibility and legal reviews, dependency failures and close evidence. Observation and pass fields stay blank until the installed system is exercised.
Primary sources used
Posnic v1.3.0 release
Stable public release used for the pinned product review.
Posnic v1.3.0 user guide
Pinned documentation for item, barcode, sale, payment, stock and retail hardware workflows.
Posnic hardware matrix
Pinned support levels and exclusions for scanners, scales, printers, drawers, displays and payment terminals.
Focused Posnic tests
Exact source directory containing the ten focused test files used for the 92-test result.
GS1 2D barcodes at retail POS
Current primary implementation guidance covering POS lanes, self-checkout and exception workflows for 2D barcode transition.
W3C WCAG2ICT
Current informative guidance for applying WCAG concepts to non-web software and closed-functionality systems such as retail self-checkout.
PCI PTS Point of Interaction
Primary device-standard overview that includes Unattended Payment Terminals as a category; it does not validate a Posnic integration.
OIML R 76
International model recommendation for non-automatic weighing instruments. Confirm the binding local requirements for the installed market.
NIST Handbook 44
Current US-specific weights-and-measures reference supplied as an implementation example, not a global rule.
NIST contingency planning
Primary recovery-planning model used to structure dependency, fallback and restart tests; it is not presented as a retail legal requirement.
Questions
Does Posnic v1.3.0 include a complete self-checkout lane?
No bundled customer self-checkout screen or accepted physical lane is established by this review. The pinned release provides documented retail item, barcode, weighing, sale, stock, receipt, report and permission foundations that an implementation can evaluate.
Is retail self-checkout the same as a restaurant self-order kiosk?
No. Retail self-checkout identifies or weighs merchandise and closes a retail basket. A restaurant kiosk builds a menu order and routes it to preparation. Posnic keeps those intents on separate guides.
Can any barcode scanner or scale be used?
Do not assume that. The pinned hardware matrix documents keyboard-wedge scanners and specific continuous-output scale behavior, with support levels and exclusions. Test the exact make, model, mode, symbols and commercial weighing process before purchase.
Does WCAG2ICT certify a self-checkout installation?
No. W3C's WCAG2ICT note gives informative guidance for non-web software and closed-functionality systems. The complete installed hardware and software still needs review against the applicable requirements.
Does Posnic drive an integrated unattended payment terminal?
Not in the pinned hardware matrix. It says integrated card terminals are not implemented. Select an acquirer-approved device and integration, define card-data scope and test every payment state with the responsible parties.
Should a small store start with unattended checkout?
A supervised single-lane pilot gives the business a safer way to measure scans, help requests, payment uncertainty, voids, reconciliation and customer access before considering less supervision.
Where Posnic fits
Posnic v1.3.0 provides documented retail item, barcode, weighing, sale, stock, receipt, report and permission foundations. Ninety-two focused tests establish source and DOM boundaries only. The review does not establish a bundled customer self-checkout screen, physical lane, integrated unattended payment terminal, loss-prevention system, installed accessibility conformance, complete shift, regional compliance package or worldwide onsite service. Run the worksheet on the exact implementation before production.