Tracing product movements with logs and adjustments

When the bar reports 8 bottles of vodka and the system says 14, the question is 'where did the 6 go'. The Inventory Report shows planned movements (POs, transfers, deductions). When that doesn't explain it, two more diagnostic reports are next: Inventory Adjust Report and Order Product Logs Report. Together they cover the unplanned and the per-order detail.

Inventory Adjust Report

Reports → Inventory Adjust Report. Every time someone runs a stock count and forces the system to match the count (via Adjust), this report records it. Picks per warehouse, per date+time range.

Filters

• Date range with start and end times — useful when an adjustment was done specifically during a quiet period.
• Warehouse — required, single-select. Run once per warehouse if you need a property-wide view.

Columns

• Name — the product.
• Date/time — when the adjustment was applied.
• Old value — what the system thought before the count.
• New value — what the count said it actually was.
• Difference — new minus old. Negative = stock was removed (loss). Positive = stock was found (or a previous PO had been missed).

What it tells you

Repeated negative differences on the same product = persistent shrinkage. Could be theft, breakage not being recorded, or an unrecorded sale path. Repeated positive differences = POs being missed when received, or sales not ringing up. Both are process problems, surfaced by the report. The Adjust button at the top right of the report navigates straight to the corrections page when you've spotted a current discrepancy.

Order Product Logs Report

Reports → Order Product Logs. Every product event on every order: added, removed, voided, plus the user, the POS Point, the date/time. This is the per-order detail layer that explains why stock moved.

Filters

• Date range with times.
• User — filter to one waiter or kitchen staffer.
• POS Point — the till.
• Product — the SKU you're tracing.

Columns

• Order # — links to the original order.
• POS Point — which till the order was on.
• Date/time — to the second.
• User — who did the action.
• Product — the SKU.
• Quantity — how many.
• Action — added / removed / voided / etc.

A practical investigation flow

You count the bar at end of shift. Vodka is 8 bottles physical, system says 14. The 6-bottle gap walkthrough:

1. Inventory Report (date range = since the last count). Filter to vodka. Confirm the POs received and any deductions. Total received minus total sold should give the expected on-hand. If it does, the gap is at the POS — go to step 2. If it doesn't, you're missing a deduction — go to step 3.
2. Order Product Logs (same date range, filter to vodka). Look for: voided orders that put stock back but maybe shouldn't have (waiter error); orders by one user with a high removed/voided ratio; quantities that look high for the order context. The action column tells you what to flag.
3. Inventory Adjust Report (same warehouse, same date range). Was a previous adjustment done that you don't remember? Sometimes a prior count corrected stock and nobody documented it.
4. If all three reports agree the system stock is correct as-recorded, the gap is physical: breakage not recorded, samples not deducted, or theft. Record an inventory deduction with a reason; the Adjust Report will reflect the correction with the right paper trail.

Permissions

The Adjust button on the Inventory Adjust Report is permission-gated (inventories: adjust). Standard waiters can see the report (so they can confirm what was changed) but only managers/admins can apply a new adjustment. Order Product Logs is reporting-only — no actions to perform from the report itself.