Items and lots

Stock Items give each product a SKU, name and base unit within an organization. The lot-tracking flag tells the team when a lot must remain visible through stock work. Stock Lots records a lot code, expiry date, release state and owner reference for an item. The Inventory Coordinator should select the item on the request and check the lot when reading a related reservation or movement.

• Ownership. App Administrator and Inventory Coordinator handles the decisions and records in this area; keep the named owner visible on each request.
• References. Follow the organization, item, location and parent request links when checking related work.
• Evidence. Read the current status and revision together with the related decision or effect before a handoff.

Stock Items and Stock Lots are reference records for operations, while Stock Reservations and Stock Movements record consequences of work. Keep the item record active only while it is intended for new requests. The team should rehearse a lot-tracked item and an item without lot tracking, because their checks differ. Use a real SKU and lot code in that rehearsal.

Agree the authoritative SKU and base unit before importing items. Decide who may mark a lot Released and how Quarantined or Blocked lots are identified during work. Use the expiry date as a handling input rather than a substitute for the release decision. The App Administrator maintains active item records; the Inventory Coordinator checks that request quantities are expressed in the selected item’s base unit.

Choose a lot-tracked item for a stock request due this week. Inspect its lot code, release state and expiry date. A Released lot can be considered for the matching request and location; a Quarantined lot needs a separate decision before use. Follow the item reference from the lot to the request, then to a reservation or movement. If the item code typed on the request differs from the selected item, resolve it before recording an effect.

• Released stock lots — Check lot release state and expiry before reviewing stock work.
• My stock requests — Follow the selected item into assigned requests.
• Posted movements — Read an item’s recorded movement history.

Follow the operating process and implementation steps with a real request. Confirm that the item, location and organization references still point to the intended records after each handoff. Use the data model when preparing migration mappings, and bring the team’s actual codes and review authority to the rehearsal.