Every field on an early kitchen return — its draft and completed states, the two ways an item comes back, what finishing posts to your stock, and who can build and finish one.
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.
A batch tops out early and the crew rolls two cases of rice and a fresh tray of sauce back toward the warehouse. Before the evening pick works off numbers that no longer match the shelf, someone logs what's coming back and puts it on hand. That record is an . Open Early kitchen returns under Inventory to read your own — this page names every field, state, and permission one carries. Plant+
Every return your company has logged sits here, numbered EKR-000001,
EKR-000002, and on. Each row carries:
EKR- followed by six digits.The search box matches a number, a name, or a contact. The status dropdown narrows the list to Draft or Completed, and Clear all returns it to everything. An empty list reads No early kitchen returns found.
A return has two states, and it only ever moves one way between them:
The status isn't a field you set — it's derived. A return stays a Draft until someone finishes it; finishing writes a completion that stamps it Completed for good.
Open any row. The header carries the Number, the Status badge, and the Name — or just Early kitchen return when it has none. Below it sits a details panel:
Each item is one thing coming back, shown as its own card. Every card names the product and its product code, the quantity returning, and a line of identity that depends on how the item was added:
Below that, each item shows where it lands:
RAC_A01_S01 · 5.Not the same as Kitchen returns
Early kitchen returns is its own surface under Inventory, separate from the Kitchen returns list under Production. Both move kitchen stock back to the warehouse; this one captures it as a quick draft you finish as the stock comes off the line.
Finishing a draft is the only thing that moves stock. For each item, Bettr posts an
inbound movement against its lot at the locations you set, tagged with the return's
number — like EKR-000001 — as the reference. A New from product item's lot is
created at that moment, so its Stock item pending badge drops away. The return
is then stamped Completed with who finished it and when. If your company syncs
to Odoo, an incoming transfer is pushed there and the View in Odoo link
appears.
Every one of those movements lands in Stock movements, so a finished return reads as a line in your history, never a quantity typed over the old one. The Finish return button stays off until every item has at least one location, and a draft that's short lists the items still missing one. Finishing then checks that each item's location amounts add up to its quantity before it posts anything.
Finishing can't be undone
Every item goes back on hand the moment you confirm, and there's no reversing a finished return. A finish made in error is corrected the way every mistake in an append-only system is — with a fresh event: an inventory count that fixes the shelf, or a waste record — never by unwinding the return.
Both are draft-only. A draft shows an Edit button in its header for changing the contact, the name, the items, and their locations, and a Delete return button in its Danger zone for dropping the draft entirely. A completed return shows neither — the stock has already moved, so there's nothing left to change.
Access is set per role, under Production in the permission catalog: