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.
- Product Lifecycle Mgmt (PLM)
- Features
- Batch acceptance
Batch acceptance
Release inspected pending output and reconcile the finished-goods inventory effect.
OverviewPending batch decisions×
Product Lifecycle Mgmt (PLM) · Batch acceptance
New
Pending batch decisions
Action waits for the quality inspector
| Id | Work order | Lot number | Produced at | Expiry date | Disposition | |
|---|---|---|---|---|---|---|
| IDD-187 | WO-8760 | L26-9629 | 15 Oct | 20 Oct | Pending | |
| IDD-966 | WO-8552 | L26-8045 | 06 Oct | 11 Oct | Pending | |
| IDD-950 | WO-3516 | L26-0259 | 08 Oct | 14 Oct | Pending | |
| IDD-188 | WO-7823 | L26-5831 | 20 Oct | 27 Oct | Pending | |
| IDD-148 | WO-7382 | L26-4837 | 13 Oct | 16 Oct | Pending |
6 of 6 records
IDD-187Batches · BTC-75404
PendingWork orderWO-8760
Lot numberL26-9629
Produced at15 Oct
Expiry date20 Oct
What you can do
Decide which pending output can enter finished goods
Quality Inspector reviews the Pending batch against its work order and lot identity. Production date and expiry date provide dated context for the output. The inspector needs the actual inspection and accepted-quantity evidence before authorizing release. Production Planner watches the related work-order outcome while Inventory Controller reconciles the resulting stock.
The accepted-output action requires Pending disposition. Held and Rejected batches are ineligible. Success marks the batch Released and increases finished-goods inventory by the accepted quantity once. The action completes the work order only when every sibling batch is terminal, so the planner needs the whole sibling population when explaining whether production is complete.
How the work is organized
- Inspect pending scope. Review the work order and lot alongside production evidence. Confirm which output is being examined and resolve any disagreement about its identity before deciding acceptance.
- Retain acceptance evidence. Keep the accepted quantity and the inspection basis available for the release action. Quality Inspector should be able to explain the decision from that evidence after the result is recorded.
- Reconcile siblings. Inspect the other batches associated with the work order. Resolve outstanding disposition through the authorized action before explaining completion to the operating team.
What to agree during setup
Agree the inspection evidence, deciding person and finished-goods destination used by the release action. Test the decision with the ordinary Quality Inspector account. Decide how Inventory Controller retrieves the accepted basis when comparing the receipt with the changed balance. The inspector and inventory team should recognize the same product and lot without resolving identity from a name alone.
Rehearse the hold and rejection procedures your team will use and decide who follows up on excluded output. Review expiry dates as part of the operating attention routine. Agree where detailed inspection results originate; any connection to another quality system is a setup choice. Preserve the evidence needed to explain both accepted inventory and output still awaiting disposition.
Check the handoff on an actual case
Take a Pending housing batch from a recorded production interval. Quality Inspector examines the inspection and accepted-quantity evidence, then invokes release. Inspect the Released result and selected finished-goods balance. Repeat the same action and confirm that the receipt remains unchanged after its original successful effect.
Try a Held batch and a Rejected batch. Neither may pass the accepted-output action. Resolve the cause through the authorized quality procedure and keep the excluded output visible for follow-up. Inventory Controller should be able to explain why those batches have not supplied accepted stock.
Next, use a work order with another sibling still Pending and release only its eligible inspected batch. Production Planner checks that the work remains incomplete while that sibling needs a decision. Once the terminal-state requirement is satisfied, explain the work-order result and reconcile received inventory to output actually accepted. Retain the separate disposition of any held or rejected output when reporting the operating outcome.
What your team sees
- Pending batch decisions — Inspect pending lots and their work-order context before deciding acceptance.
- Held and rejected batches — Keep excluded output visible for authorized follow-up.
- Lot balances on hand — Inspect positive on-hand inventory after the controlled receipt, with reservations visible.
Follow the work through
Record and accept output rehearses the final handoff. Review and implement changes supplies the earlier design context. Use implementation to prepare the pilot.
What it keeps track of
Data model- Batches
- Produced batches and disposition.
- Work orders
- Production work orders.
- Production logs
- Production interval logs.
- Inventory balances
- Item inventory balances by location and lot.
- Items
- Materials, components and finished goods.
- Design documents
- Controlled design documents and approvals.
Who uses it
Permissions- Quality Inspector
- , Production Planner, Inventory Controller, Admin.
- Quality Inspector
- Decides acceptance.
- Production Planner
- Checks work completion and Inventory Controller reconciles the stock result.
Set up Product Lifecycle Mgmt (PLM) your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.