Evidence-led product guide
POS software features: verified scope and rollout limits
A useful feature list says more than what a product screen contains. It tells a buyer what was observed, what was source-tested, which outside services remain necessary, and what the business must prove on its own counter.
Evidence and review scope
Evidence reviewed 18 August 2026. The review uses stable release v1.3.0, pinned source commit b531ef4308c4dc3a25f250551a54fc5616e3b8d9, reproduced local runtime evidence, focused source tests, and product documentation.
No complete retail, restaurant or kiosk operating day was executed. No physical POS hardware, card terminal, production database, disk-loss event, macOS run, Linux run, independent security audit or hosted-cloud acceptance test was included.
Evidence at a glance
These results are intentionally labelled by evidence type. A passing source test is not presented as a completed shop rollout.
| Area | Observed evidence | Boundary |
|---|---|---|
| Local sale | One synthetic INR 125 cash sale completed and reopened on Windows x64 while external hosts were blocked inside Electron. | Not an operating-system-wide network disconnection, power-loss test, payment-terminal run or full shift. |
| Backup and restore | A synthetic backup restored 20 collections and 53 documents with matching source and destination totals. | Disposable test data, not a production database, damaged disk or full disaster-recovery exercise. |
| Receipts and reports | 37 focused receipt and report, local-asset and sales call-path source tests passed. | No physical receipt was printed and no complete counter shift was run. |
| Retail and supermarket support | 57 vertical-supporting source tests passed across item, weighed-quantity, receipt, report and related paths. | No complete retail or supermarket day and no physical retail hardware. |
| Kiosk support | 24 focused kiosk source tests passed for settings, availability, guarded routes, order paths and reports. | No physical kiosk order, payment, kitchen print or report was executed. |
| Hardware paths | 35 hardware protocol and source tests passed for receipt, report and weighing-scale paths. | No physical printer, scanner, drawer, scale, display or payment terminal was connected. |
| CSV templates | Six tests checked all seven shipped CSV templates under the application's parser. | An actual bulk import was not executed through the user interface. |
| Local API | A curated API Jest run reported 7,953 passed tests and zero failures. | Curated suite only; conflicting endpoint totals remain in three documents and no stable public plugin or sync contract is claimed. |
See the product records, not a mock-up
These screens come from the reviewed Posnic application. Buyers should reproduce the same records with their own item, tax, user and hardware setup.
POS feature map
Treat each group as a workflow to verify, rather than a checkbox that guarantees a business outcome.
Sales and billing
Product documentation covers sales, returns, customers, taxes and reporting. Validate prices, discounts, tax, payment, permissions, correction records and receipt output with representative transactions.
Stock and purchasing
Documented retail paths include items, barcodes, purchases, returns, stock movements and low-stock views. Accurate stock still depends on units, receiving, returns, wastage, adjustments and physical counts.
Restaurant operations
v1.3.0 documents KOT and Easy Table workflows, and the source contains six KOT report views. Table service, kitchen routing, modifiers and close-out were not run end to end.
Kiosk workflow
The source includes kiosk settings, item availability, guarded routes, order-processing paths and reports. Accessibility, enclosure, payment, kitchen output and staff recovery need an on-device acceptance test.
Local backup
Configurable backups are documented and a synthetic restore passed. The default same-disk location does not protect against disk loss, so copy backups off the till and rehearse recovery.
POS hardware
The hardware matrix covers receipt-printer, scanner, drawer, scale and display paths by support level. Match the exact model, interface, operating system, driver, paper width and fallback before purchase.
Data import
Seven CSV templates passed parser-oriented structural and sample-data checks. Trial a reversible import with representative duplicates, tax groups, units and malformed rows before loading a live catalog.
Local API and source
The desktop process starts a local API and database on derived port ranges. Review the pinned source and API limitations before building an integration or depending on undocumented behavior.
Optional cloud services
Cloud is a separate paid service described for sync, off-site backup and remote dashboards. Confirm current availability, data flow, conflict handling, recovery, support and commercial terms before rollout.
Local privacy model
The local edition documentation says it needs no Posnic account and sends no analytics or telemetry to Posnic. Optional services and business-selected integrations change the data-flow review.
Open-source license
The public repository is AGPL-3.0-only. Inspect the code and license, and review network-use, distribution, trademark and commercial-license questions for the intended deployment.
Published installers
The stable release publishes Windows x64, macOS Intel and Apple Silicon, and Linux x86_64/amd64 builds. This review reproduced runtime behavior on Windows x64 only.
Dependencies to test outside the feature list
| Workflow | Current evidence level | Outside dependency | Buyer test |
|---|---|---|---|
| Local cash sale | Limited Windows runtime result plus source tests | Computer, power, staff permissions, item and tax setup | Run normal and exception sales, then reconcile the saved records. |
| Electronic payment | No physical terminal run in this review | Processor, terminal, network, settlement and refund process | Match approved, declined, reversed and refunded payments to POS records. |
| Receipt and drawer | Focused source and protocol tests | Exact printer, driver, interface, paper width and drawer wiring | Print representative long receipts and test the failure fallback. |
| Barcode and weighed item | Source tests and standards review | Barcode data, scanner mode, scale model, interface and calibration | Test good, duplicate, unknown and damaged labels plus weighed quantities. |
| Restaurant or kiosk | Documentation and focused source tests | Screen, enclosure, accessibility, payment, kitchen routing and recovery | Run a complete customer order through fulfilment, correction and report. |
| Backup and recovery | One synthetic restore | Separate storage, retention, encryption, owner and replacement machine | Restore an off-machine copy into a disposable environment and verify records. |
| Optional cloud | Edition documentation only in this review | Hosted service, connectivity, account, support and commercial terms | Complete a written acceptance test for sync, conflict, outage, export and recovery. |
What this evidence does not prove
- It does not prove compatibility with a buyer's physical printer, scanner, drawer, scale, display or payment terminal.
- It does not prove a complete retail, restaurant, supermarket or kiosk day under production load.
- It does not reproduce runtime behavior on macOS or Linux, even though stable installers are published for those platforms.
- It does not establish country-specific tax certification, payment certification or legal compliance.
- It does not replace an independent security audit, penetration test or business-specific threat review.
- It does not establish hosted-cloud availability, branch-sync acceptance, an integration SLA or a stable public sync/plugin contract.
- It does not prove stock will be accurate without disciplined receiving, units, returns, wastage, adjustments and physical counts.
Ten tasks before a POS go-live
- Write the required sale, return, purchase, stock, tax, payment, permission and day-close workflows before configuring software.
- Create representative items including variants, discounts, tax groups, weighed goods, duplicate barcodes and awkward quantities.
- Use the exact computer, operating system, printer, scanner, drawer, scale, display, payment setup and network planned for the counter.
- Run cash and electronic sales, holds, discounts, returns, cancellations and credit paths with the intended cashier and manager roles.
- Receive a purchase, sell and return stock, record an adjustment, then explain each quantity from the movement history and a physical count.
- Test every required receipt, report, export and tax field against the business's accounting and record-retention process.
- Disconnect each external dependency separately and document what continues, what stops, how staff are warned and how transactions recover.
- Close a mock day and reconcile sales, returns, discounts, cash, processor totals, open credit and selected stock independently.
- Copy a backup off the till, restore it on a disposable setup and verify representative items, sales, stock and reports.
- Record rollout ownership, support contacts, update windows, incident steps, replacement-device setup, export procedure and rollback criteria.
Keep a 20-record POS acceptance log
Record the exact release, configuration, expected result, observed result, retained evidence, owner, specialist review and stop-or-go decision for each critical workflow. The blank log separates an advertised feature from a feature your business has actually accepted.
A blank row is not a pass. Keep screenshots, receipts, exports, provider records and restore evidence outside the till, then link or identify them in the log.
Primary sources and product evidence
Stable source and user guide
Inspect the exact source snapshot and documented workflows used by this review.
Hardware evidence matrix
Review support levels, exclusions and buyer-test requirements for POS devices.
PCI merchant resources
Use primary payment-security guidance to map terminal, processor, vendor and card-data responsibilities.
GS1 retail barcode standards
Use the standards owner for EAN/UPC identity, symbol and scanning guidance rather than assuming every code or scanner behaves alike.
NIST CSF 2.0 for small business
Use current primary guidance to assign governance, protection, detection, response and recovery responsibilities.
Reproducible product evidence
See the release, source commit, runtime boundaries, test files and evidence-maintenance method in one buyer-readable record.
Questions buyers ask
Which Posnic POS features were tested at runtime?
The current review reproduced one synthetic local Windows sale and one synthetic backup-and-restore drill. Other results are labelled separately as focused source tests, documentation review or release-manifest evidence.
Does offline POS mean every Posnic feature works without internet?
No. The local sale continued while external hosts were blocked inside Electron, but this was not an operating-system-wide outage. Downloads, updates, card authorization and optional hosted services may still require a network.
Has Posnic tested every supported POS device?
No. Thirty-five focused protocol and source tests passed, but no physical printer, scanner, drawer, scale, customer display or payment terminal was connected in this review.
What should a business test before using Posnic POS?
Run a representative sales day on the exact operating system, items, taxes, users, printer, scanner, payments and network planned for the business; reconcile cash and stock; then restore an off-machine backup before approval.
Is the free Posnic desktop application a timed trial?
No. The local desktop application is free and open source under AGPL-3.0-only. Optional cloud services are separate and should be evaluated against current availability and terms.