Organizations and locations

Organizations and locations define which operating entity owns a request and where its stock can be held. The App Administrator records the organization code, time zone and currency, then identifies active storage locations. A location carries a name, code, contact, address and eligibility note. Team membership links a person and platform user to the organization. This foundation lets the Inventory Coordinator select a real location and accountable owner when preparing stock work.

• Ownership. App Administrator 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.

Organizations, storage locations and team members are the setup record. Stock requests connects the scope to day-to-day work. Keeping the reference stable matters because movement history and reservations also point to locations. A code change must not erase a prior request or movement. During setup, bring a real address list and one example request so the team can agree how location names appear to operators.

Use one code per physical storage address and decide whether a location represents a warehouse, zone or bin. Agree how the eligibility note is maintained and who deactivates a location that should no longer receive work. Check that each active Team Member has the right organization and time zone before assigning requests. A change to an address or contact should be reviewed against open requests that already point there.

Take a request for an item moving into a named storage location. Verify its organization matches the location and the owner belongs to the team. Read the location eligibility note before assigning the plan zone. If the location is inactive, correct the setup before using it in new work. The App Administrator can inspect the organization and member record while the Inventory Coordinator checks the request itself.

• Due stock requests — Find upcoming work and confirm its owner before checking organization membership.
• My stock requests — Open an assigned request to verify its selected location and item against the setup records.

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.