Written by DROPS.ST.
For cannabis retail operators, a layout review should connect each ordinary shop task with the information and receiving person it needs. Walk the order through the proposed work positions before approving the operating arrangement. A clear customer area does not, by itself, show that the work behind it is ready.
DROPS gives that walkthrough a concrete record: products have references and units, while orders retain their items and customer links. Website and connected Telegram shopping use the same catalogue and order system. Staff can work from that common context instead of reconstructing the selection at every handoff.
Trace one ordinary order
Start with a representative permitted task. Identify where someone checks the item and quantity, where the next action happens and which person receives the work.
Record the information needed at each position. Keep the ordering unit explicit: an item count and a pack count are not interchangeable.
Use the actual approved site arrangement and responsibilities. Keep building, safety and professional site decisions with the people responsible for them; this walkthrough checks the business information handoff.
GOV.UK describes experience maps as a way to show interactions across stages. Apply that idea to the shop's task and record positions. GOV.UK: understanding user needs.
Use a task-to-record map
| Task | Working record or fact | Position and handoff check |
|---|---|---|
| Understand the selection | Item reference, unit and quantity | Worker can inspect the intended record |
| Confirm the next permitted action | Current order context and approved procedure | Decision belongs to the appropriate person |
| Prepare the agreed work | Item/quantity information | Receiver understands the unit without retyping |
| Review an exception | Specific discrepancy and checked facts | Named owner receives the unresolved question |
| Hand off or update | Verified outcome and relevant reference | Next person understands what actually happened |
These are business tasks, not assumed native DROPS queue stages. Use the supported views and your approved process to supply the information.
If a position cannot access the necessary record, resolve that gap through the supported arrangement. Do not substitute another person's login or a public display of unrelated customer information.
Include an approved arrival prompt: where the pickup or delivery partner goes, whom they contact and who receives the work.
Check the transition between positions
Ask what signals that the next person should act. A verbal instruction, an approved task note and a supported record change have different meanings.
The receiver should know the item, quantity, work already completed and question still open. Repeating the whole conversation is rarely the clearest handoff.
Use the shift-note guide when the work crosses a person or shift. The map shows where the task moves; the note makes that move understandable.
Rehearse a busy-period question
Use fictional case cards or an agreed safe demonstration. Add one interruption, such as an unclear pack quantity or a task waiting for a decision.
Observe which record people use and whether two workers begin competing work. Identify the next owner before changing several parts of the arrangement.
Use the manager permissions guide to review actual access. Business responsibility and the full scope of a software permission remain separate decisions.
Hypothetical example: the record stops at the first position
A fictional worker checks an order's pack reference at the first position. The receiving worker gets only a spoken quantity and cannot tell whether it means packs or individual items.
The reviewer changes the proposed handoff so the receiver can inspect the permitted item reference and unit. They repeat that same case before accepting the arrangement.
The improvement being assessed is the information transfer. This invented example does not show a faster queue, completed architectural design or automatic workflow feature.
Correct the record when the map reveals ambiguity
If the issue starts in a product name or unit, resolve the approved fact before redesigning the handoff. The product-record guide provides that check.
Where your DROPS setup includes the AI shop assistant, use it to inspect products and prepare a catalogue change plan. Review the item matches and proposed fields before applying approved supported changes. Keep the layout and operating decisions with their responsible reviewers.
Put the work around a clear DROPS record
Choose DROPS when your team needs products and customer-linked orders in one shop, with connected Telegram using the same underlying system. That record gives the operating walkthrough something precise to follow.
Explore DROPS and open the demos. Bring one representative task and this map. Identify the record, position and receiving person, then accept the arrangement when every necessary handoff can be explained and demonstrated.