Evidence-led buying guide
POS system for small business: a practical buyer's guide
Choose a POS by proving the work your counter must complete: sell, return, receive stock, close a shift, recover data and explain every payment difference. Feature lists and a free trial are useful only after those tasks pass on the exact hardware and operating model you plan to use.
Evidence and review scope
Evidence reviewed 2026-08-17. Primary standards review, pinned Posnic source, a reproduced Windows sale and restore, and focused hardware tests.
Stable release: v1.3.0. This is a buyer acceptance method, not a claim that one POS fits every business or market.
What a small-business POS decision includes
Counter operation
Map sale, return, discount, tax, receipt, cash handover and day-close work. A system that demos well can still fail on corrections and exceptions.
Business control
Prove product import, stock receiving, low-stock review, permissions, reports, export and restore. The owner needs records that can be checked after a busy shift.
External dependencies
List the payment provider, internet, cloud service, computer, database, printer, scanner and power assumptions separately. Test how each failure is detected and recovered.
Compare operating models before brands
| Operating model | Useful when | Acceptance question |
|---|---|---|
| Local POS | One counter needs local control and lower internet dependence. | Who owns backup, restore, updates, device replacement and off-machine copies? |
| Cloud POS | Owners need browser access, managed service and connected locations. | What stops during an outage, how is data exported, and what is the full recurring cost? |
| Hybrid or local-first | Checkout should remain local while selected data or services connect remotely. | Which tasks are truly local, which sync later, and how are conflicts or failed syncs shown? |
| Self-hosted open source | A technical team values source access and deployment control. | Who will patch, monitor, back up and support the production installation? |
| Managed implementation | The business needs migration, hardware setup and accountable support. | Are scope, response path, data ownership, rollback and acceptance results written down? |
What Posnic v1.3.0 evidence currently proves
| Area | Observed evidence | Boundary |
|---|---|---|
| Local sale | A synthetic INR 125 cash sale was completed and reopened on Windows x64 while external hosts were blocked inside Electron. | This was not an operating-system-wide network disconnection and no payment terminal or printer was used. |
| Backup and restore | A synthetic backup restored 20 collections and 53 documents; a post-backup item disappeared while the original item and sale remained. | The test used a disposable profile, not a production shop database. |
| Hardware code paths | Thirty-five receipt, report and scale protocol tests passed. | No physical printer, scanner, drawer, scale or customer display was connected. |
| Developer checks | The pinned API Jest run recorded 7,953 passed tests and zero failures. | It was the repository's curated suite, not an independent security or production acceptance audit. |
| License and price | The desktop source is AGPL-3.0-only and the local edition is documented as free without a trial timer. | Cloud, implementation, hardware, payment processing and business support can still add cost. |
Build a shortlist without sales-demo bias
- Write one page of mandatory workflows, volumes, tax and receipt rules, payment methods, hardware and failure constraints.
- Remove any candidate that cannot explain total cost, data export, backup ownership, security updates and the support path in writing.
- Load representative products, including awkward barcodes, weighed or variant items, tax groups, discounts and opening stock.
- Use the same test script for every finalist so a polished demonstration does not replace evidence.
- Record failures, workarounds, training time and unresolved dependencies before choosing a rollout date.
- Keep a rollback path until a real shift, close report and restore drill have passed.
Ten tasks to run before go-live
- Create one cashier and one manager with different permissions.
- Import representative items and verify barcode, price, tax, unit and opening stock.
- Complete cash and non-cash sales, then reconcile the payment summary.
- Return an item, cancel a line, apply an approved discount and reprint a receipt.
- Receive a purchase and verify stock movement and low-stock reporting.
- Disconnect each required network service and document what stops, what remains local and how staff are warned.
- Test the exact printer, scanner, drawer, scale or display model used at the counter.
- Close a mock shift and explain every difference between sales, cash, digital settlement, refunds and open orders.
- Create an off-machine backup, restore it to a disposable environment and verify representative records.
- Export business data and document support, update, device-replacement and rollback contacts.
Questions buyers ask
What should a small business test first in a POS system?
Start with one complete shift: representative products, each payment method, a return, a discount, a stock receipt, day close, backup and restore. Test the exact hardware and failure paths too.
Is free POS software enough for a small shop?
It can be enough for a simple local counter if the required workflows, backup, hardware, security updates and support path pass acceptance. Free software does not make hardware, payment processing, setup or recovery work free.
Does offline POS mean every feature works without internet?
No. Verify each task separately. Local sales may continue while card authorization, hosted ordering, remote dashboards, support, updates or cloud sync still require a network.
Does a small merchant need to consider PCI DSS?
Yes. PCI SSC says PCI DSS is intended for merchants involved in payment processing regardless of size or transaction volume. The merchant should confirm validation requirements with its acquirer or payment brand.
Will any standard POS printer or scanner work?
Do not assume that. Match the operating system, driver, protocol, interface, paper width and workflow, then test the exact model before rollout.
Primary sources used
PCI merchant resources
Primary guidance on payment-data risk, merchant responsibilities, secure technology and vendor questions.
PCI small-merchant safe-payments guide
A practical payment-security guide for small merchants; it supplements rather than replaces PCI standards.
GS1 retail barcode guidance
Primary barcode standards and implementation guidance for retail point-of-sale scanning.
CISA small-business resources
Cybersecurity guidance covering software updates, backups, encryption, authentication and logging.
Posnic v1.3.0 release
The exact stable installer and source release referenced by the evidence table.
Posnic product evidence
Versioned runtime, hardware, privacy, backup, security and source limitations in one public specification page.