Organizations and locations

Give every stock request and holding site the correct organization context. Keep the related request, decision and stock evidence together as the case moves between people.

• Record the operating identity. An organization identifies the legal entity with code, active state, time zone and currency. Each storage location belongs to an organization and records the name, code, address, contact and eligibility note for each warehouse, distribution center or third-party site. The location reference on a request makes the intended stock effect concrete.
• Keep the control visible. A team membership binds a person and user account to an organization, with role name, active flag and time zone. The request owner points to one of these memberships. That link lets coordinators and reviewers discuss responsibility in the same organizational context as the item and location.
• Make the decision traceable. A counterparty on a stock request is also a location. Teams should agree what each location means before using it in a movement: the current holding site and the counterparty should not be swapped because their codes sound alike. Inactive organizations, locations and memberships should be reviewed before new work is assigned.

Agree legal entity codes, site codes and location eligibility notes with each operating team. Decide who maintains membership and who checks that a coordinator’s assigned organization is the one on the request.

Use a real size-color SKU and storage location to rehearse the first case. App Administrator should confirm the entity and site codes; Inventory Coordinator and Inventory Reviewer should agree which revision is ready for a decision. Keep that convention available to Auditor when the movement is reconciled.

A fashion brand uses a distribution center and an outside storage site. The administrator records both locations under the correct organization and adds the coordinator membership. A request names the item, holding location and counterparty. The reviewer checks the site identities before approval. When the effect posts, its movement references the actual item and location so the organization can reconcile where stock changed.

At the handoff, compare the current request revision with the reviewer decision and any related lot, claim, receipt or posted movement. If a reference differs, give the case back to Inventory Coordinator with the mismatch named. Keep the earlier decision and effect visible to Auditor.

• Active locations — Current sites with organization and eligibility note visible.
• Request board — Owned cases that show the location selected for work.

Open the underlying record before making a decision that depends on revision, expiry, ownership or location. Inventory Reviewer should read the linked request and evidence before recording a reason; Auditor can follow the same references later.

See the operating handoff and the implementation sequence. Use the data model when mapping existing identifiers and references.