Store replenishments

A store replenishment is a proposal linked to a stock request. It holds the store name, forecast units, target units, required date and revision. Coordinators can compare the target with the forecast entry and the parent request before sending the proposal for review. Draft and Submitted identify the preparation handoff; Approved, Rejected and Completed record later outcomes.

The proposal has its own revision and status, while the parent request carries the item, location and owner. A forecast entry gives context for the target; it is not an automatically calculated recommendation. The reviewer checks both records before setting the proposal decision time. A Completed proposal alone does not establish a stock movement.

• Link the proposal. Inventory Coordinator connects the store entry to its parent request and records the forecast and target units.
• Submit the current revision. The coordinator moves the proposal from Draft to Submitted after checking store and required date.
• Decide and verify. Inventory Reviewer checks the request and submitted proposal, then records the outcome and decision time; the team traces any later stock effect through the parent.

Agree who enters forecast units, what the target represents, and how the store name maps to an authorized storage location. Forecast units are a value on the proposal; any upstream demand model is a connection to plan separately. For a store asking for more units before a promotion, preserve both the forecast entry and the requested target so the reviewer sees the actual choice.

Inventory Coordinator enters store targets and keeps the parent link correct. Inventory Reviewer checks the submitted revision and records the decision. App Administrator maintains the organization and location context. Auditor reads the outcome.

The reviewer checks the parent request revision and records the decision time on the proposal. Keep the decision time with the proposal and inspect any operation receipt on the parent request. A changed proposal needs another review of its current revision before execution.

Use a store asking for extra units before a promotion. Compare the forecast entry, target units and parent request quantity. If the store target changes after review, inspect the new revision before another decision. A rejected proposal remains distinct from a rejected request. Where an operation receipt is recorded, read its outcome with the parent request and posted movement.

• Store replenishments for review — Submitted store entries with forecast, target, required date and revision.
• Store replenishment board — Draft through Completed outcomes grouped by proposal status.
• Requests due — Parent requests approaching their required date.

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.