1. Food Bank Management
  2. Features
  3. Reservations and movements
Feature · Reservations and movements

Reservations and movements

Separate claims against eligible food from signed, posted changes to stock.

OverviewActive Stock Reservations
Food Bank Management · Reservations and movements

Active Stock Reservations

Stock reservations

New
Reservation referenceRequestItemLocationLotQuantity
RR-360SR-22315SI-4863SL-140SL-3110620
RR-493SR-61720SI-6750SL-140SL-9674370
RR-924SR-68170SI-6970SL-140SL-6657590
RR-251SR-32115SI-5056SL-110SL-9214570
RR-857SR-99997SI-6195SL-130SL-8257760
6 of 6 records
RR-360Stock reservations · SR-29365
Active
RequestSR-22315
ItemSI-4863
LocationSL-140
LotSL-3110
Quantity620
Example screen with sample data

What you can do

Keep claims and stock effects distinct

A reservation belongs to a stock request and identifies the item, location, quantity, expiry and optional lot. Its state tells the team whether the claim is active, released or consumed. It does not by itself change on-hand stock. That separation matters when several requests compete for the same food: a claim must be checked against eligible stock before a later issue can be confirmed.

A stock movement records the signed quantity and whether the effect was posted. It retains the request, item, location, optional lot, movement reference and revision. A reversal points back to the movement it compensates. Inventory Coordinator should trace the original and compensating records together rather than erasing an old posted line. The operation receipt records the outcome of the attempted action under an operation key and expected revision.

How the work is organized

  • Claim. Inventory Coordinator selects an eligible item, location and lot and records an active reservation for the request.
  • Post. The coordinator records a signed movement only for an evidenced stock event, keeping its reference and parent request.
  • Reconcile. Independent Reviewer checks posted effects against the receipt result and any linked reversal when the operation is disputed.

What to agree during setup

Set the rule for available stock from posted movements and active reservations. Decide how expiry and release state are checked at both reservation and issue. Agree whether a particular action requires a lot, and ensure the base unit on the item and request matches the movement’s quantity. Give each attempted operation a stable key so a retry can find its earlier result.

Agree how partial issues are represented. A consumed reservation should match the quantity actually issued, while any unused claim is released. For transfers, define the evidence expected at dispatch and receipt before marking the entire operation complete. A correction needs a new, linked movement with bounded quantity and an explanation. It should never silently alter a posted historical line.

Check the handoff on an actual case

A request calls for several cases of canned food. Inventory Coordinator checks Released Stock Lots, selects an eligible lot at an active location, and creates an active reservation. Active Stock Reservations shows the claim. The coordinator then records the signed movement for the physical issue and marks the claim consumed for the evidenced amount. Posted Stock Movements shows the effect and its parent request.

If the operation receipt remains pending, the team checks its operation key, expected revision and referenced movement before another action. A repeated command must resolve to the same effect rather than post the quantity again. If an earlier posted line was wrong, the coordinator links a bounded reversal to it and retains both records for audit. The request status can then reflect only the verified operation result.

What your team sees

  • Active Stock Reservations — Current claims by request, item, location, lot and expiry.
  • Posted Stock Movements — Signed effects with movement references and posting dates.
  • Open Operation Receipts — Pending and failed results requiring reconciliation.

Follow the work through

See reservation and posting for the stock path and receipt reconciliation for pending results.

What it keeps track of

Data model
Stock reservations
Eligibility-scoped claims against available stock.
Stock movements
Immutable signed inventory movements and posting evidence.
Stock requests
Scoped stock requests with revision-controlled lifecycle.
Stock items
Food inventory items with base units and lot tracking.
Stock lots
Lot-level expiry and release state for tracked food.
Storage locations
Eligible food storage and distribution locations.
Operation receipts
Idempotent operation receipts and result evidence.

Who uses it

Permissions
Inventory Coordinator
Makes and reconciles bounded claims and movements.
Independent Reviewer
Checks exception evidence.
Allocation Coordinator
Reads the stock position supporting a proposed allocation.
Admin
Manages access to these records.

Set up Food Bank Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started