These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Kitchen Inventory Management
- Features
- Stock requests and review
Stock requests and review
Carry a kitchen stock request from a named owner into a revision-bound supervisor decision.
OverviewStock Requests Review Queue×
Kitchen Inventory Management · Stock requests and review
New
Stock Requests Review Queue
Stock requests
| Record number | Subject | Item | Location | Requested units | Required by | |
|---|---|---|---|---|---|---|
| SR-94207 | Review sr-412 | SI-1959 | SL-120 | 160 | 14 Oct | |
| SR-60786 | Review sr-577 | SI-6675 | SL-110 | 390 | 21 Oct | |
| SR-24973 | Review sr-268 | SI-5420 | SL-120 | 900 | 18 Oct | |
| SR-29386 | Review sr-663 | SI-9131 | SL-140 | 490 | 07 Oct | |
| SR-78465 | Review sr-251 | SI-5678 | SL-110 | 90 | 25 Oct |
6 of 6 records
Review sr-412Stock requests · SR-94207
ReviewItemSI-1959
LocationSL-120
Requested units160
Required by14 Oct
Revision510
What you can do
Review the exact quantity the team intends to use
Stock requests identify the kitchen task through record number, subject, item, location, counterparty location, owner and organization. Required date explains when the work is needed; requested units and revision describe the scope that the supervisor reviews. Draft, Review, Approved, Executed, Rejected and Cancelled separate preparation, decision and operational outcomes.
Operations Overview helps prioritize requests by lateness alongside failed receipts and escalated reviews. Keep that operational context beside the underlying request. An overdue task still needs the proper approval and an eligible stock action; its place on the overview does not grant permission to bypass either.
How the work is organized
- Preparation. Inventory Clerk verifies the item, location and base-unit quantity while the request is Draft. Record attachments can retain a photo, document, signature or delivery note linked through parent request.
- Decision. Inventory Supervisor reviews the current revision and records the outcome through the published action. Review decisions retain reviewer, decision, rationale and decision date with the request reference.
- Result evidence. Each operation receipt links the decision or action to its parent request and retains the owner, quantity and operation key. Status Recorded distinguishes captured evidence from the later completion verification.
What to agree during setup
Agree when a prepared request is ready for Review and which evidence is needed for a waste submission or inspected stock movement. Inventory Supervisor should explain the meaning of an approved quantity to the clerk. A revised request must be reviewed against its current revision rather than an earlier screenshot.
Map stock requests’ owner to the intended team member record and its user reference before configuring My Kitchen Stock Requests. Configure the clerk’s worklist against that identity mapping, then test it with the clerk’s real account. Check the request owner and deadline on the first operating cycle. App Administrator maintains team identity, while Inventory Supervisor keeps decision authority for the stock request.
Check the handoff on an actual case
Rehearse a waste submission for 2 kg of inspected rice. Inventory Clerk prepares the quantity, subject and evidence, then routes the request from Draft to Review. Inventory Supervisor checks the submitted revision, using revision 3 for this rehearsal, and approves it through the waste decision action. Inspect the review decision and matching operation receipt, and confirm that the approved request now has revision 4.
Repeat that decision with the same stable operation key. It should return the established decision without creating duplicate evidence. Then try the old revision as a new decision attempt: the workflow must refuse stale scope. Also test a request already Executed or Cancelled; those records cannot receive the same fresh decision.
Keep stock execution as a separate handoff. Follow the waste submission’s posted stock movement effect and lot balance before reporting the confirmed deduction. Auditor should be able to trace the original rationale after a correction.
What your team sees
- Stock Requests Review Queue — Inspect requests in Review before deciding the current scope.
- My Kitchen Stock Requests — Follow work owned by the signed-in team member after identity mapping is configured.
- Returned and Escalated Decisions — Follow review exceptions, their reasons and the affected request revision.
Follow the work through
Walk through kitchen waste review and correction and reconciliation.
What it keeps track of
Data model- Stock requests
- Requests to receive, move, reserve or issue stock.
- Team members
- Warehouse staff and reviewers linked to an organization and platform user.
- Users
- Users
- Review decisions
- Approved, rejected, returned or escalated decisions on source records.
- Record attachments
- Documents and links attached to operational records.
- Operation receipts
- Recorded, verified, failed or corrected operation evidence.
Who uses it
Permissions- Inventory Clerk
- Prepares requests and evidence.
- Inventory Supervisor
- Decides requests and authorized corrections.
- Auditor
- Reviews the decision history.
- App Administrator
- Maintains team identity.
- Configure Admin's setup permissions before assigning it.
Set up Kitchen Inventory Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.