Locations and items

An App Administrator maintains the organization, active stores and distribution centers, stock items and the team members who own or review work. Each item belongs to an organization and records its SKU, base unit and lot tracking rule. Each location has a code, contact, address and eligibility note.

An item and a location must belong to the right organization before a request uses them. The item provides its SKU, base unit and lot rule; the location provides its code, contact and eligibility note. Team members links each named operator to an app user. These records give coordinators a consistent identity for a store, distribution center and replenished item.

• Maintain organizations. App Administrator checks the organization code, active state, time zone and currency.
• Maintain stock context. Keep item SKU and base unit stable; set the lot rule and location eligibility before operational work.
• Connect people. Link a named team member to the correct user and organization so ownership and review are traceable.

Agree location codes before migration, decide which locations can act as request destinations or counterparties, and keep item codes stable across the operating cycle. A store and distribution center can both be storage locations; the request identifies the item, its location and the counterparty. The team member record links an app user with an organization and role name.

App Administrator owns organization, item, location and membership data. Inventory Coordinator checks those records when preparing a request. Inventory Reviewer uses the same identities for decisions. Auditor reads the resulting case.

For a newly opened store, the administrator confirms its organization, active setting and eligibility note before coordinators create requests against it. For a lot-tracked SKU, confirm the base unit and lot rule before recording lots or movements. Keep changes to item and location identity deliberate so historical request evidence stays understandable.

For a newly opened store, check the organization and active state before using the location on a request. Confirm its code and contact against the distribution center that will supply it. For a lot-tracked SKU, check the base unit before adding lots or movements. If a team member moves to another organization, verify the user and organization links before assigning new requests.

• Active locations — Store and distribution center codes, organizations, contacts and eligibility notes.
• Active stock items — SK us, base units and lot rules available for requests.
• My team membership — The signed-in person’s organization, role name and active state.

See request review for the decision path and stock execution for the resulting stock effect. The data model shows the record links behind the screens.