Choose a food inventory workflow that keeps product identity, batch dates and waste movements connected. Establish where date information comes from, who checks it and how an unsuitable batch leaves available stock. Demonstrate those relationships with a representative sample before accepting a system on the strength of its expiry-date screen alone.
Start with the goods the business actually handles and the records supplied with them. A packaged item, an ingredient and a prepared product may have different information sources and operating decisions. Ask the responsible team to identify those differences before proposing a common data-entry form for everything.
What should the batch record explain?
A useful batch record lets the team recognise the intended goods and trace the information associated with them. Agree the product identifier, batch reference, supplier or production record and relevant dates. Keep the unit of measure explicit so a quantity recorded as individual packs is not read as an ingredient weight.
Odoo’s expiration-date documentation offers a concrete software example. Odoo assigns expiration information to products tracked by lots or serial numbers. Enabling lot and serial tracking exposes the Expiration Dates option. Confirm the proposed tracking configuration alongside the product record before demonstrating the date fields.
Odoo’s date configuration distinguishes expiration, best-before, removal and alert timing. Ask the process owner to explain which source and decision each relevant field represents. Similar-looking date labels should not be used interchangeably merely because they occupy the same form.
Configured date values compute expiration dates for goods entering stock. Expiration dates can be entered manually when product date fields are not configured. Record which route the proposed workflow uses and where its input values are verified. The software’s ability to compute or accept a date does not decide which date is appropriate for the goods.
Give date corrections an owner. If the source document and stored value disagree, the person receiving goods needs an agreed route to resolve the difference. Retain the reason and supporting reference for a correction in the operating record required by the business. Do not silently replace the source value to make a demonstration pass.
How should receipt and batch visibility be tested?
A validated receipt exposes a Traceability smart button. Use the documented relationship to ask the demonstrator how the sample receipt, product and batch can be followed. Retain the relevant references so another reviewer can inspect the same proposed journey rather than relying on a general dashboard screenshot.
Odoo can group lot records by expiration date. Include a view containing the intended sample batches and ask the operator to locate the one being discussed. Compare the displayed batch reference and date with the agreed input record. A recognisable product name alone may not identify the particular stock the team needs to assess.
Ask how responsibilities change between receipt, storage and the next operating step. The person who receives goods may not be the person who reviews a date exception or records waste. Write those handovers into the requirements, including what information each person must see to act correctly.
| Workflow question | Proposed record | Acceptance observation |
|---|---|---|
| Which batch arrived? | Product, lot and receipt reference | Operator finds the intended received batch |
| Where did its date come from? | Source information and entry route | Stored date agrees with the approved source |
| Which date decision matters? | Relevant field and process owner | Team explains its intended meaning |
| What was removed from stock? | Batch-specific waste movement | Quantity and batch match the authorised record |
| Can the movement be traced? | Linked source operation | Reviewer follows the relationship without guessing |
The table is an original requirements worksheet. Add the business’s real handling and review requirements with the appropriate operational owner. Keep those decisions distinguishable from the documented software fields so configuration choices remain reviewable.
How should waste be recorded separately from available stock?
Odoo’s scrap documentation describes the stock-record mechanism. Odoo scrap operations designate unusable goods or materials for disposal or recycling. Scrapped inventory is placed in a virtual scrap location. Ask the implementer to show how the proposed record affects the sample stock view.
A scrap operation can reference a specific source document. Use that relationship where it fits the process so the reason for a movement can be reviewed with its context. Agree which person authorises the movement and what evidence they require before applying the record to real stock.
Keep the database movement and physical handling responsibilities clear. A recorded scrap entry needs to correspond to the business’s actual authorised action, and the team needs to know who confirms that action. Ask the operator to explain both sides during the demonstration rather than assuming the screen completes the operating task.
Review how the team will investigate a mismatch. The relevant issue may be the wrong batch, an incorrect quantity, a date-entry error or an unrecorded movement. Retain the initial observation and reference before changing data so the investigation can distinguish those causes.
Original two-batch and waste-movement exercise
Consider a fictional store receiving two labelled batches of the same packaged ingredient. Use approved sample records in a separate test copy. Assign different illustrative dates from the prepared sample documents, then identify one sample quantity for an authorised waste movement. The exercise examines record relationships and operator understanding.
First, write the expected product, batch and date details before entering the receipt. Have the receiver follow the proposed workflow and locate the resulting records. Compare each stored date with its source and record the entry route used. Retain any correction as a separate observation with its reason.
Next, ask another participant to locate the intended batch through the date and lot views. Give them the operating question without describing every click. Record which fields identify the batch and any ambiguity they encounter. Use that feedback to refine the handover and field meanings.
Then follow the authorised sample waste route. Record the batch, quantity and source operation, and inspect the stock view afterwards. Have the stock owner explain the result and compare it with the expectation written before the exercise. Leave any mismatch open until the relevant record or configuration has been understood.
Finally, review the worksheet with the receiving and stock owners. Separate demonstrated software behaviour from unresolved handling requirements and assign each open item. Use that record to decide whether the configuration fits the intended workflow before planning a later stock migration or rollout.
For wider requirements, see business systems and software development. Get started with your batch records, date-entry route and waste authorisation questions.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.