These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Lot Tracking
- Features
- Locations and teams
Locations and teams
Give every stock request an organization, location and accountable owner.
OverviewMy team membership×
SCM with Lot Tracking · Locations and teams
New
My team membership
Team members
| Name | Organization | Role name | User | |
|---|---|---|---|---|
| Member 722 | ORG-2761 | Role 486 | ||
| Member 437 | ORG-5505 | Role 621 | ||
| Member 913 | ORG-1471 | Role 913 | ||
| Member 528 | ORG-9481 | Role 746 | ||
| Member 610 | ORG-1029 | Role 270 |
6 of 6 records
Member 722Team members · TM-73183
OrganizationORG-2761
Role nameRole 486
What you can do
Place stock in the right operating scope
Organizations own items, locations and requests. Storage Locations name the places where work happens, such as a warehouse, cold room or staging area, and carry an active flag, address, contact and eligibility note. Team Members identify the people who prepare, review and execute work for an organization. This setup gives each request a clear owner and place before a stock action is considered.
A request can identify both a location and a counterparty location. That distinction matters in a move: the team should know where the stock is worked and which other location is involved. Inventory Coordinator can prepare the request with the relevant item and location. Inventory Reviewer can inspect the submitted revision against those references. The location code and contact help the team confirm it has the intended site when names are similar.
How the work is organized
- Organization. The operating entity owns the item, location, team membership and request scope.
- Location. The named storage place carries contact, address and eligibility information for stock decisions.
- Person. Team membership links a named worker to an organization and user account.
What to agree during setup
App Administrator should agree a naming and code convention for organizations and locations before importing stock. Decide how the eligibility note will be used in daily review, who maintains it, and how an inactive location is taken out of use. Confirm each team member’s organization and user link. An administrator’s ability to maintain membership does not replace an Inventory Reviewer’s independent decision on a request.
For a pilot, use two distinct locations with different eligibility notes. Give the coordinator a request for one item and ask them to name the operating location and counterparty. The reviewer should be able to explain which location would hold the resulting stock and why the selected place is appropriate. The records should remain understandable after a location contact or address changes.
Check the handoff on an actual case
A cold room and a staging area may share an organization but serve different stock. App Administrator confirms the active locations and their codes. Inventory Coordinator prepares a movement request with the correct item, owner and both relevant locations. Inventory Reviewer checks the requested quantity and revision before deciding. Later, a movement record can identify its location, and the request remains available to explain why the movement was made. An Auditor can follow the authorized trail from organization through request to movement.
What your team sees
- My team membership — The signed-in person’s organization and team role.
- Stock request board — Requests grouped by their current status, with owner and location in view.
Follow the work through
Use stock request review to rehearse a location decision, then movement reconciliation to follow its effect.
What it keeps track of
Data model- Organizations
- Operating organizations that own stock, locations and requests.
- Storage locations
- Warehouses, cold rooms and staging areas holding stock.
- Team members
- People who prepare, review and execute stock operations.
- Users
- Users
- Stock items
- Stock item master with base unit and lot tracking flag.
- Stock requests
- Stock receive, move, reserve and recall requests with lifecycle and revision.
- Stock movements
- Posted signed stock movements produced by guarded workflows.
Who uses it
Permissions- App Administrator
- Maintains organizations, locations and team membership.
- Inventory Coordinator
- Owns assigned requests.
- Inventory Reviewer
- Checks revisions independently.
- Auditor
- Reads authorized records.
Set up SCM with Lot Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.