Retail shop software: rent it or own it
Retail shop software: what a till and a stock ledger have to get right, and what changes when the copy on the counter is yours.
retail shop software is a broad search typed by someone with a narrow problem: a till, a stock count, and the gap between them that opens up over a quiet Tuesday and never closes. This page is about what the software actually has to get right, and about what changes when the copy running on the counter belongs to the shop rather than to a subscription.
The three things a shop floor breaks
Stock that drifts. The count on screen and the count on the shelf part company, slowly, and by the time anyone notices nobody can say when it started.
The oversold last unit. Two cashiers ring up the same final item within the same second. In most systems both sales succeed and the argument happens later.
Cost of goods that is not really the cost. A profit report built on the latest purchase price rather than what the units on the shelf actually cost tells you a story you would like to hear.
A hosted point-of-sale service solves the first two to varying degrees and charges monthly for the privilege, usually per terminal or per location. The third it often leaves to whoever reads the report.
What owning the copy changes
Vendra is engineered so overselling is impossible -- the checkout refuses the second claim on the last unit at the database level rather than accepting both and reconciling afterwards. Stock movements are an immutable ledger with a one-click verification, which is a different promise from a stock number that gets edited: every change is an entry, and the total is derived from the entries rather than stored and hoped for. Costing is weighted average, so the margin report is computed from what the units actually cost.
Try the Vendra demo ↗Live, on sample data, no sign-up.
The commercial change is that the till stops renting. The licence covers the installation, so a second workstation behind the counter is not a second subscription, and the sales history is in your own database where a quiet Tuesday three years ago is still queryable.
What to look for
A refusal, not a reconciliation. Ask what happens when two terminals sell the last unit at once. If the answer involves fixing it afterwards, that is the answer.
A ledger rather than a number. Stock as an append-only movement history, with a verification you can run.
Weighted-average costing, stated as such. Then the gross margin is arithmetic rather than opinion.
A screen built for a scanner. Keyboard-wedge USB scanners behave as typed input, which is what the point-of-sale screen expects; no driver integration is involved either way.
A day-close that produces a document. The end-of-day report is the thing that gets compared against the drawer, and having it arrive in an inbox is worth more than having it available on request.
Receipts the customer can keep. Emailed through your own SMTP server, and printable regardless.
The limits, stated plainly
One shop per installation: a single stock ledger and a single drawer, so a second branch is a second installation rather than a location switcher. Vendra records card tender; it does not process cards, so the terminal beside the till stays the terminal beside the till. There is no e-commerce or website stock synchronisation, so an online shop selling the same stock is not kept in step. Emailed receipts and the day-close email both need your own SMTP details and both ship switched off; without SMTP the receipt is still on screen and still printable.
If the shop is part of a wider back office -- suppliers, reordering, expenses -- the Retail Suite is the related products bought together, and the suite page carries the current figures with their date.
Questions people ask
What stops the last unit being sold twice? A database-level guard in the checkout: the second attempt is refused at the moment it happens rather than accepted and corrected later.
Can it run two shops? Not in one installation. It holds one stock ledger and one drawer by design; a second shop is a second installation, which the licence tier governs.
Does it take card payments? No. It records that a card was tendered. Card processing stays with your terminal and your acquirer, which is also why there is no card data on your server.
Where to look next
The product page is Vendra, with the whole feature record and the limits in the product's own words, and the Retail Suite holds it with the rest of the shop stack. The alternatives page covers one of the hosted tills people arrive from, another covers a second, and the side-by-side sets them against each other. For what the hosted tills charge per terminal or per location, read the observatory: each figure is quoted verbatim beside the date it was read and a link to the page it came from. Prices are on the observatory; read them on the date shown there.