What the POS thinks vs. what’s actually there.

Stocktakes that finish before lunch

The reason stocktakes get put off is that most tools force you to count the entire store every time. Vendee Pro doesn’t. Pick a location, then narrow to a vendor, a category, or a product type, and the count is scoped to just those variants. A single-brand cycle count at one store is usually a few dozen rows, not a few thousand. You finish counting before the next break.

Inside the scope, every variant the POS thinks you have is on the count list, plus anything in your catalog at that location. Outside the scope, nothing is touched. The next stocktake can take a different slice. Most retailers run them on a rolling cadence rather than a once-a-year fire drill, and Vendee Pro is built around that habit.

Scan-to-count, +1 per beep

The count screen has a single focused input that accepts barcode or SKU. Each scan finds the matching variant in scope and adds one to its counted quantity. The input stays focused, so a hardware barcode scanner plugs in and just works. No hunting for fields, no popping modals, no double-keystrokes. If the count is already known, you can type it directly into the row and skip the scan. Per-row plus and minus buttons handle quick corrections, and clearing a row back to "not counted" is one click.

The variance dashboard, in five buckets

While the count is in progress, the dashboard shows four summary tiles that update live: SKUs in scope, matches, variances, and the priority bucket called Not scanned. Below the tiles, five filter tabs let you switch the row list between:

• All. Every variant in scope, in one list.
• Not counted. Variants nobody has scanned or typed yet.
• System has stock you didn’t scan. The high-value bucket. POS says you have one or more on hand but the floor count is zero. Usually the thing on the shelf that the team walked past.
• Variances. Counted, but counted differs from system. Surfaces shrink and overage in the same view.
• Matches. Counted equals system. The healthy rows.

Switching tabs is one click. The summary tiles stay synchronized with whatever filter you have open, so the numbers you see at the top match the rows you see below.

Multi-counter, fully audited

More than one staff member can work on the same stocktake at the same time. Each counted row records the user who scanned it and the timestamp, so you can audit who counted what after the fact. When you have two people walking the floor and a third entering known-quantity rows from the back office, the dashboard reflects all three streams at once.

Export the variance, hand it off

Any of the five filter tabs can be exported to CSV. Export the full variance list, or just the "didn’t scan" bucket, or just the matches if you need a clean reconciled list for your accountant. The export includes vendor, category, system quantity, counted quantity, variance, status, the user who counted each row, and the timestamp. Hand the file to your team, open it in Excel, or keep it as the paper trail behind the reconcile step below.

Count first, write only what you approve

This is the design decision that separates Vendee Pro from most stocktake tools. Counting never writes anything back automatically. We snapshot your POS stock levels at the start of the count, surface the variances at the end, and stop. The variance report is an artifact - a forensic record of what was on the floor on a specific day, who counted it, and what the gap was.

Then, when the count is complete, the optional reconcile step closes the loop: it stages every variance as a proposed correction, you review the list and approve only the rows you believe, and Vendee Pro pushes those counted-minus-system deltas to your POS through the same audited, append-only adjustments journal used for manual adjustments - each row with the stocktake as its reason and a full lineage back to who counted it. No blind writeback, no mystery on-hand changes: every unit that moves has a human approval and an audit row behind it.

Stocktakes and the AI assistant

Once a stocktake is complete, the variance becomes data the AI assistant can reason about. Ask which vendors had the most short rows over the last quarter, or which categories drift fastest between counts, and the assistant answers from the same audit-trailed records. The assistant never adjusts inventory on its own - that boundary stays intact - but it makes the variance history queryable.

Frequently asked questions