A loop becomes usable through separate reference, release and physical setup decisions. Follow Setup checklist and check the actual site; completing a form must not stand in for looking at a container or testing the intended scanner.
Prepare the reference and people
The author prepares the material, receiving location, stores queue, loop and containers. Check exact codes, whole refill quantity, destination and allowed queues. Draft references or an unreleased loop revision must not be described as live floor configuration.
Before the release candidate is proved, the owner opens Stores queues and chooses Enable [queue code] for each queue intended to receive requests. Enabling counts against the plan's stores-queue allowance. The release's default queue must already be enabled when the reviewer releases it. If a queue is enabled after proof, rebuild and review the candidate because the configuration changed.
The owner assigns people, queue membership and stations in Team & stations. Pair the intended browser and set its scanner terminator, Enter or Tab. Test at the actual floor station. Record what the test showed using the setup checklist, rather than simply marking the scanner done.
Configure a working calendar and review its timezone. Arrange how tickets will reach stores. The checklist can record a deliberate attended download/print arrangement while no routed printer is set up.
Release, then enable loops and containers
A reviewer proves and releases the intended configuration and rules through Rules and releases. After that release includes the loop, the owner opens Physical activation, inspects missing readiness steps and plan capacity, and chooses Enable [loop code]. This page controls loops and container opening conditions; queue enablement is on Stores queues. Enabling loops and activating containers count against their plan allowances; setup does not start an evaluation.
Look at each actual container before selecting its opening condition. Full or Partly filled means ready for a future request when empty. Empty means it needs refill now. Unresolved keeps it held. RefillFlow does not guess how much is inside from those conditions.
Record the observed condition and check the result. An unresolved opening needs later reconciliation by an owner or supervisor: choose Condition now confirmed, state What was reconciled and Record the condition. Merely releasing an unrelated hold does not establish an unknown opening condition.
Confirm operational readiness
Issue the correct container and location cards through their controls. Check that physical cards correspond to the current container generation and receiving location. The owner can issue cards; a lost or damaged card replacement is a supervisor decision.
Run the intended real operating checks separately. Rehearsal data does not migrate into production, and a source-confirmed setup screen is not physical device qualification. Hand over the active release, paired stations, queue assignments, opening conditions and remaining setup limitations to the operator and stores team.
Resolve an unresolved opening truthfully
An owner can activate with an unresolved observed opening, leaving that container held. Once its actual condition is reconciled, Owner or Supervisor uses Condition now confirmed and What was reconciled in Physical activation, then Record the condition. Select the condition now supported by physical evidence. Do not use a normal refill receipt to invent an opening condition.
The checklist reads current records and retains its confirmations. Scanner and attended-printing confirmations need notes describing the checks actually performed. A missing rehearsal or scanner confirmation remains a setup dependency; neither a printed card nor this written guide marks it complete.
Follow the sample rehearsal to its recorded end
Use Rehearse one refill in the sample site. Follow its offered next step in order: Request refill, Accept, Pick, Dispatch, then Receive. Request and receipt use the sample floor station. Check the displayed synthetic cycle and completion, then choose Back to the real site.
The rehearsal uses the normal command path in isolation. Nothing is printed or sent, and only the checklist note that rehearsal was completed carries to the real site. It does not copy reference data, pair the real floor browser or witness the real container opening. Keep those actual checks separate.