The states a count moves through, the fields on every count and adjustment screen, and who can run each step.
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
Two of the crew walk the dry racking on Monday with a clipboard, counting cases bay by bay. By Wednesday a manager has to decide which of those numbers to trust and post to stock. An carries that work from the floor to that decision. This page names every state and field along the way. Open Inventory Counts under Inventory to read along.
The list holds every count in the company you're working in, one per row, newest first. Each count carries a number Bettr assigns when you create it — an IC- prefix and six digits, like IC-000001. A row reads as its number alone, or as its number and the name you gave it when there is one. Beneath that, a line of meta: the date it was created, who created it, and how many of its locations are counted — 1/1 location, 0/2 locations. A status badge sits at the right.
Four controls sit above the list:
New sits at the top right for anyone who can create a count. When nothing matches, the list reads No inventory counts found.
Every count carries exactly one status, and you never set it by hand: Bettr derives it from what has happened to the count, so the badge always reflects the real record. While the count is open:
Once the count is resolved:
States are derived, never overwritten
A count's status is read from its events — a start, a completion, an application — not stored as a value that gets edited. That's why Bettr can show who did what and when at every step. How inventory works in Bettr explains why nothing here is ever overwritten.
Selecting a count opens its detail. The number heads the panel, the name beside it when there is one, with the created date and creator underneath and the status badge alongside. The actions offered depend on the state: Start Count and Delete on a draft, Continue Count while in progress, Adjust Inventory once it's under review, and Discard on a count that's been counted. A rejected or discarded count shows a red banner with the reason it was closed.
A progress section reads how far the count has gotten — x/y locations counted and a percentage, with a bar. Below it, every location in the count sits on its own row with a status dot and label:
Each row also carries the location code, the Odoo location it maps to, and how many items were counted there.
When a count has been adjusted, a Manager adjustments section lists each corrected lot: its product and code, the location and lot number, who adjusted it and when, and the Expected, Counted, and Adjusted quantities with the signed variance. A Notes section shows any free text entered when the count was created.
New opens the create form, which is where a count picks up its locations:
One active count per location
A location that's already in an in-progress or under-review count shows In another count and can't be picked — a single location is never counted by two open counts at once. Once that count is applied, rejected, or discarded, the location is free to count again.
The per-location screen is reachable only while the count is In Progress; open a resolved count and it returns you to the detail. You reach a stock item three ways — search by product, code, or lot; type an exact lot number and Find it; or Scan QR Code. With an item selected, two fields record the count:
Count item saves it, and each item you count lands in a list below with who counted it and when, its counted figure, and the final quantity. Complete Location closes the location; a location with nothing counted asks you to confirm it's empty first. The full walk-through lives in Run an inventory count.
Adjust Inventory opens the review, reachable only while the count is Under Review — Bettr bounces you back to the detail if the count has moved on. A table carries one row per counted lot:
A summary strip totals Expected, Counted, Adjusted, the Difference, and the item count. Three actions close the review: Apply Selected posts the checked lots, Apply All posts every lot with a typed adjustment, and Reject Count closes the count with a reason and posts nothing. Adjustments must be whole numbers of zero or more, and each lot can be adjusted once. Review and apply count adjustments walks the decision through. Applied corrections are kept on the count as Manager adjustments; they don't post to the stock movements feed, which tracks stock entering and leaving the building, not on-hand corrected in place.
Applying corrects stock and can't be undone
Applying posts the adjustments to stock as an event you can't reverse. If you apply while a lot still shows a variance you haven't reviewed, the count locks as Partially Applied and that lot can never be reviewed — so resolve every varying lot before you apply, or reject the count and recount.
Access is set per role, under Warehouse & Inventory in the permission catalog: