Recall scopes

Recall Scopes hold a lot code, organization, parent stock request, reason, opened date and affected units. Their revision and status let the team distinguish a working draft from a submitted or approved scope. Inventory Coordinator prepares the scope, and Inventory Reviewer makes the independent decision. The team can then follow the affected stock through the lot, movements and reservations associated with the request.

A recall discussion often begins with a short lot code. The app’s records add the organization and request context needed to identify the work precisely. The reviewer should compare the scope with the lot’s item and release state, then check which stock effects and active claims are linked to the relevant request. The scope’s affected units provide a number to reconcile, not a reason to skip examining where stock has moved.

• Scope. The reason, lot code, affected units and organization state what is being examined.
• Review. A specific revision is submitted for an independent decision before the scope is treated as approved.
• Follow-through. Movements, reservations and operation receipts explain the work that followed the request.

Agree who opens a recall scope, how the lot is identified when codes recur, and what supporting files are attached to the parent request. Define how affected units are counted and which location owners should be consulted. Decide the evidence needed before marking a scope Completed. App Administrator maintains the item and location context, but Inventory Reviewer remains responsible for the review decision.

Pilot a lot with one movement to another location and an active reservation. Ask the coordinator to prepare the recall scope and state its reason. The reviewer checks the current revision, lot context and affected units. The team then follows the movement and reservation rather than treating the scope’s total as a complete map of stock locations.

A team finds an issue with a lot after receiving it at a warehouse. Inventory Coordinator opens a scope tied to the stock request, records the lot code, reason and affected units, and submits it. Inventory Reviewer decides the submitted revision. The team checks any signed movements for that lot and any active reservation at a location. Operation receipts and attachments on the parent request help explain the actions taken. Before closure, the reviewer compares those records with the affected scope and records the outcome.

• Recall scope review — Submitted scopes with lot code, affected units, reason and revision.
• Open recall scopes — Draft, Submitted and Approved scopes that still need follow-through.
• Restricted lots — Lots marked Quarantined or Blocked for immediate review context.

Begin with lot recall handling and use exception review for any outcome needing reconciliation.