Client scope

The Admin records the client organization, its code, time zone and currency. The team then links staff, stock items and storage locations to that organization. A stock item has a SKU, base unit, active state and lot tracking choice. A storage location has its own code, contact, address and eligibility note. These records make the scope of a request legible before anyone reserves or moves quantity.

• Client membership. Link each team member to a user and client organization before assigning request work.
• Stock ownership. Keep each item and storage location under its organization; check those links when a request names both.
• Operating details. Record the site’s contact and eligibility note and the item’s base unit and lot-tracking choice.

Agree who maintains client codes, who can mark a location active, and how the warehouse checks the eligibility note. Choose the time zone used to interpret local due dates. Review member accounts against the organization they serve. Give the Admin a client with two storage sites and ask the Coordinator to prepare a request at one site. Check the item and location’s organization links before the Inventory Reviewer sees the request. Assign a team member linked to a user in the same client scope. Then try the other client’s similarly named item and confirm it cannot be substituted in the handoff. When a site contact or eligibility note changes, the Admin should make that change on the location record so the next request uses current details.

Suppose a client asks for stock from a particular site. The Coordinator checks that the organization, item and location belong together, confirms the responsible team member and uses the item base unit when entering the requested units. If the item is lot tracked, the lot code and release state become part of the stock decision. Another client may use a similar SKU; the organization link still matters. The Coordinator can hand the mismatched request back to the Admin for correction before review. Once the item and site point to the intended client, the request owner can prepare its quantity in the item’s base unit. The Inventory Reviewer checks the corrected client scope against the attached source evidence. If the team later investigates a stock effect, the parent request leads it back to the same client, item and site. This makes the organization link part of each decision rather than a name inferred from a SKU.

• My stock requests — Requests assigned to the signed-in member, with their client, item and due date.
• Lots needing disposition — Lots whose release state needs a decision before they can support a claim.

Start with the client stock request path, then use review and correction when a decision or quantity needs attention. The data model shows how the records link, while roles helps the team rehearse access.