Correct your stock, push it to the POS, and keep the receipts.

Add or remove, never “set”

Every adjustment is a signed delta - plus three, minus one - applied to a specific variant at a specific location. Vendee Pro never pushes an absolute “set on-hand to N” value, because the moment you read a number and the moment you write it are not the same: a sale could land in between. By sending the change rather than the destination, a concurrent in-store sale nets correctly and a stale on-hand reading can never overwrite real activity.

You adjust the exact row you clicked. The push targets the external SKU and location ids captured from the live POS mirror, so the change hits the precise item and store the screen showed - and it works even for POS-origin catalogs that were never created inside Vendee Pro.

A reason for every change

Each adjustment carries a reason, and reasons are yours to manage per store. Out of the box you get a sensible set, each locked to the direction it makes sense for:

• Damaged, Theft / Shrinkage, and Lost - removals only.
• Found and Received (outside a PO) - additions only.
• Recount / Correction - usable either way.

Add your own, rename them, retire the ones you don’t use. The adjust screen only ever offers reasons valid for the direction you picked, and the server rejects a mismatch, so a “Damaged” reason can never be attached to an add. Reasons are a Vendee Pro concept for your reporting - they are never mapped onto Shopify’s or Heartland’s own reason systems, so the rich “why” lives where you can actually slice it.

Pushed once, and only once

Inventory writes are exactly where double-sends do real damage. Vendee Pro writes a pending record before it ever calls the POS, so a crash mid-push can never lose the fact that an attempt was made. Every attempt also carries an idempotency key backed by a hard database uniqueness guarantee: a given intent pushes at most once. Double-click the button, lose Wi-Fi and retry, refresh the tab - you get the existing record back, not a second deduction.

Fix mistakes by reversing, never by deleting

The adjustments journal is append-only. A landed adjustment is never edited or deleted, because that would quietly rewrite history. Got the quantity wrong, or picked the wrong reason direction? You reverse it: Vendee Pro pushes the exact inverse delta to the POS and records a compensating row linked back to the original. The original flips to “Reversed”, the reversal names what it undid, and your on-hand is back where it should be - with both halves of the story preserved.

The only thing you can change after the fact is the merchant-facing annotation - the reason label and the free-text note - so you can re-classify a row without touching the quantity, direction, target, or the push itself. A quantity mistake is always corrected by a reversal, never a silent overwrite.

When a push doesn’t go cleanly

POS APIs fail in two very different ways, and Vendee Pro treats them differently on purpose:

• Definitely didn’t apply - a validation rejection, a missing id mapping, an auth lapse. The row is marked failed, nothing changed, and you can safely re-submit it as a fresh adjustment.
• Ambiguous - a timeout or an unexpected error where the change might have landed. The row is marked needs review and is never retried automatically, because neither Shopify nor Heartland de-duplicates by your reference. You decide, with the full context in front of you.

And when a push succeeds, Vendee Pro refreshes the affected item in the mirror right away (Shopify also self-heals through its inventory webhook), so the corrected number shows up on the inventory screen immediately rather than after the next sync.

The adjustments report

Every add, remove, and reversal lands in the Inventory Adjustments report - a filterable, paginated history of exactly what changed, when, by whom, and why. Filter by direction, status, reason, location, the staff member who made it, a date range, or a free-text search across SKU, reason, note, and location. Summary tiles total the units added, units removed, the net change, and how many rows still need review across whatever slice you’re looking at.

Each row carries the SKU, product, location, reason, note, the user who made it, the push status, and the reversal lineage, and it deep-links straight back to that variant on the inventory screen. Export the filtered history to CSV for your accountant, your insurer’s shrinkage claim, or your own month-end reconciliation.

Stock takes find the gap; adjustments close it

These two features are deliberate opposites, and they pair perfectly. A stock take is report-only - it scans the floor, surfaces the variance against your POS mirror, and stops. A stock adjustment is the deliberate write that acts on what the count found: you review the variance, then push the corrections you actually believe, each with a reason attached. Counting and correcting stay separate steps, so nothing is ever changed by accident.

The AI assistant never adjusts on its own

Ava can answer questions about your adjustment history - which reasons drive the most shrinkage, which locations drift fastest, how a category trended over the quarter - from the same audit-trailed records. But the assistant never moves inventory by itself. Adjusting stock is a human action with a reason and an audit row behind it, and that boundary stays intact.

Frequently asked questions