Back office for independent liquor & convenience
Keep the register you already have. Veloz reads it, closes the day, and pushes a balanced journal straight into QuickBooks, Sage or Xero — with nothing left unreconciled.
Running today in a three-store liquor group in North Texas.
Every format posts the same balanced journal into QuickBooks, Xero or Sage. Veloz doesn't run a ledger — your accountant does.
The whole thing, on one page
Formats don't get their own system — they get their own configuration of the same one. What changes is which modules switch on and which rules follow the product through receiving, pricing and the close.
Case-to-bottle depletion. Sell one 750 ml bottle out of a twelve-bottle case and the case falls by one twelfth. One item record, no manual breakout.
Age-restricted controls, distributor invoice ingestion, blind counts with reason codes.
Pricebook, inventory, receiving, counts, compliance and the close — one set of records every format reads from.
Standard merchandise pricebook, DSD and EDI receiving, age-gate and scan data on the same item record that drives price and stock.
Weight, bulk and date codes. Certified scale capture and GS1 decoding for random-weight barcodes; bins, tare and repack; waste and quality hold.
Recipe explosion. A menu item breaks down into raw ingredients, so food margin is reported against what was actually consumed rather than what was rung.
Keep your counter. A read-only bridge reads the register you already own. No new hardware at the front, no clerk retraining.
Each invoice line matched to what was received, each count blind against book, each cost change checked against retail — with a variance surfaced the same day, not at month end.
A double-entry journal that balances before it posts — not an export for someone to interpret. Veloz stages and syncs; your accountant keeps the ledger.
One engine
Veloz is one platform. What differs between a liquor store and a c-store isn't the engine — it's which modules switch on at setup, and which compliance rules follow the product through receiving, pricing and the close.
variances to reason
deliveries checked in
Illustrative layout · sample figures
Café and QSR counters run as a c-store sub-line, on the same records.
The deepest vertical, and where the platform started.
Weight, bulk and date codes, on the same item record.
The close
Most back offices let you close a day with an unexplained gap and deal with it at month end. Veloz doesn't. Every variance gets a reason code before the day posts, and what lands in your accounting software is a balanced double-entry journal — not a CSV your bookkeeper has to interpret.
Whoever counts the shelf can't see the expected quantity until after they submit. The control is structural: there is no screen that shows the number to match.
Veloz stages the journal and posts it. It does not run a general ledger — your accountant keeps theirs.
Liquor, specifically
| Item | Inv | Recd | Status |
|---|---|---|---|
| Bourbon 750 ml · case of 12 | 4 | 4 | Matched |
| Vodka 1 L · case of 6 | 6 | 4 | Short 2 |
| Cabernet 750 ml · case of 12 | 3 | 3 | Matched |
| Seltzer variety · case of 24 | 10 | 9 | Short 1 |
| Tequila 750 ml · case of 6 | 2 | — | Not scanned |
Illustrative layout · sample figures
Sell one bottle from a twelve-bottle case and the case depletes by one twelfth. No second SKU, no manual breakout, no drift between what the shelf holds and what the system thinks.
Receive against the distributor invoice on a phone at the back door. Line-level shorts and substitutions are recorded where they happen, before the driver leaves.
Blind counts, variance reasons and a movement history that is appended, never overwritten. A correction is a new entry with a reason — the original stays visible.
Age-gate controls and an audit trail that survives an inspection, on the same item record that drives pricing and inventory.
Your register stays exactly as it is. Veloz reads it. Clerks learn nothing new.
Voz
Plenty of back offices now ship an AI assistant. The question worth asking is what it's allowed to do on its own. In Veloz the answer is: nothing that moves money, stock or a price.
A cost that moved, a count that drifted, an invoice line that doesn't match the pricebook.
Every finding arrives with the records it came from. No answer without evidence you can open.
A specific correction, with what it would change and what that does to the day's numbers.
Approved actions are logged with who approved them. Anything applied can be reversed, and the reversal is visible too.
Landed cost rose $1.60 on the 12 Aug invoice and retail hasn't moved. Margin on this item is now 4.1 points under your shelf target.
Evidence · invoice 8792, 3 cost eventsIllustrative layout · sample figures
Voz never posts a journal, adjusts inventory, changes a price or overrides a count on its own. A role check is not an approval, and an approval is a person.
What Voz is watching
Most of what a store loses is never named. Veloz records every invoice line, every count and every cost change, then attributes the loss to a cause — so the part you can act on stops hiding inside the part you can't. Put your own revenue in and the arithmetic runs on your numbers, not ours.
Composition follows the NRF National Retail Security Survey. Roughly two thirds of shrink is theft, and we've greyed it out on purpose: counting it toward a recovery figure would be the trick, not the product.
| Leakage | What Veloz records | How it collates | Report |
|---|---|---|---|
| Vendor short | Every invoice line against every received line | Matched per line, per delivery, per vendor | Receiving Variance |
| Margin drift | Cost-change events against the active retail price | Nightly sweep of the pricebook | Margin Drift |
| Count variance | Blind count against book, with a reason code | Per session, rolled by category | Count Variance |
| Unreconciled day | Tender against sales against goods received | At close — blocking, not advisory | Day Close |
| Unknown loss | The residual after every named cause | Rolled from all of the above | Shrink by Cause |
| Metric | Fragmented back office | Veloz target |
|---|---|---|
| Invoice lines checked | Spot-checked by hand | Every line |
| Time to detect a variance | Month end, ~30 days | At day close, under 24 hours |
| Variances carrying a named cause | Mostly unclassified | Required before the day posts |
| End-of-day routine | ~20 minutes, fragmented | ~8 minutes, four-step wizard |
| Journal handed to accounting | Export to interpret | Balanced double entry |
These are targets the product is built to, not outcomes it has demonstrated. The first measured figures come from the pilot store's own baseline, taken before go-live. When they exist, they replace this table.
