Organization setup

Organizations identify the legal entity running the cycle-count program. Stock items, storage locations, team members and stock requests each connect to an organization. A request should use an item and location that belong to the intended entity. Admin maintains these records so a counter does not need to resolve identity or location ambiguity while standing in the warehouse.

A stock item carries its SKU, name, base unit and lot tracking policy. A storage location carries a code, name, address, active flag and eligibility note. Team members connect to platform users and have an organization, active flag, role name and time zone. Those connections make an assigned owner and a review decision attributable to named people.

• Entity scope. Keep item, location, team member and request aligned to the same organization.
• Item rules. Record the base unit and whether a lot is required for that item.
• Location identity. Use the location code and eligibility note when selecting where stock is counted or moved.

The lot record adds a code, expiry date, release state and owner reference to a stock item. Warehouse Operator needs that evidence when choosing stock for a reservation or issue. A released lot can be considered for ordinary work; Pending, Quarantined and Blocked states call for a different decision before selection.

Choose organization codes and the time zone used to interpret operational dates. Agree how locations are named across warehouses and zones, and who keeps an eligibility note current. Decide who can mark an item or location inactive. Define the base unit for each item before requests and movements are recorded; changing it after operations begin needs careful treatment of prior quantities.

Map each team member to the correct platform user and organization. Agree who can prepare counts, who can review them independently and who can post physical stock effects. Give Cycle Count Operations access to assigned work. Assign the preparer, reviewer and physical operator to different people where the count requires independent review, then rehearse their access with example records.

Set up an organization, an active item with a base unit and a location with a distinct code. Create a team member tied to a platform user, then assign that person as the request owner. For a lot-tracked item, add a released lot with an expiry date. Prepare a stock request and confirm that its organization, item, location and owner line up. Have a second person review a submitted count. If any identity points to another entity or an inactive record, correct setup before recording a stock effect.

• Released Lots — Lots with release state and expiry available for selection.
• My Stock Requests — Assigned requests after a team member is linked to an owner.
• Active Reservations — Claims tied to configured items and locations.

See count and review and stock execution.