Written by DROPS.ST.
A cannabis shop owner’s weekly review should identify affected orders, unresolved cases and the next corrective decision. Pair a defined failure count with the relevant order count, then assign action to the cases behind it.
DROPS provides useful context for that work through customer-linked order items, product identifiers and a common catalogue for the web shop and connected Telegram menu. That makes it a strong operating foundation when the owner needs to connect an issue with the actual item and order involved.
Choose a few questions worth acting on
Start with problems observed in your own authorised shop operations: wrong item interpretation, unresolved fulfilment questions, menu discrepancies or handoffs that lacked an owner. Define each issue so two people examining the same order would count it consistently.
BDC's guidance on dashboards recommends a small set of relevant indicators connected to operational priorities, with regular discussion and responsibility for collecting the data. The worksheet here applies that principle to manually reviewed order exceptions.
Each row should lead to a plausible decision: change a product description, clarify a handoff, revise a commitment or investigate a repeated mismatch.
Use a defined review sheet
Write the review period, included channels and counting rules at the top. This original aid has three columns so the decision remains visible beside the evidence.
| Review question | Evidence and counting basis | Owner decision |
|---|---|---|
| Which orders needed an item correction? | Unique affected orders from the period; divide by orders reviewed under the same scope | Identify the ambiguous field or process |
| Which fulfilment questions remain open? | Outstanding cases at the review time, including older cases | Assign the next check and responsible owner |
| Which menu discrepancies recurred? | Product reference, observed mismatch and checked source | Decide which record needs correction |
| Which cases crossed a shift without ownership? | Case reference, handoff gap and actual unresolved work | Repair the handoff and verify closure |
Keep the supporting case references in a restricted working record. The review summary usually needs counts and actions, not a collection of customer personal details.
Count an order once in the overall affected-order measure even if it has several problems. You may also count issue types separately, but label those as issue counts. Their sum can exceed the number of affected orders.
Keep period measures and open cases separate
Orders affected during the week describe what happened within a period. Open exceptions describe what remains unresolved at a particular time. An older case can appear in the open-case list without being counted as a newly affected order again. Keep each open case’s opened-at and last-checked times; define its age consistently and close it only on the required evidence.
Define the denominator to match the question. If the team reviewed only pickup orders, the correction rate is not a rate for every order. If records are incomplete, state the reviewed sample rather than presenting it as the whole business.
For web and Telegram activity, check actual order references instead of adding channel mentions together. A conversation and an order may concern the same case. Shared catalogue context helps investigation, but it does not perform this counting rule for you.
Hypothetical example: one week contains 40 reviewed orders and two orders affected by the defined item issue: 5%. The next contains 120 reviewed orders and four affected orders: approximately 3.3%.
The number of affected orders doubled, while the comparable proportion fell. Neither figure alone proves that service improved, identifies the cause or establishes a performance benchmark. The owner still reviews the four cases and asks whether they share an avoidable problem.
A daily or multi-location digest uses the same rules. Keep each location’s population explicit, include overdue approvals and link mismatches to their evidence before assigning the next owner.
Turn a pattern into one checked action
Select an issue with enough evidence to support a specific next step. “Improve operations” is too broad. “Clarify the unit on SKU A, have the authorised catalogue editor review it and check the customer-facing result” gives the team something verifiable.
For disagreements between systems, use the menu source and timestamp incident record. For work moving between shifts, use the handover note guide. The weekly review decides which pattern deserves attention; those guides handle the individual incident.
At the next review, check whether the action occurred and whether the specific issue recurred. Record changes in scope or definitions before comparing periods. Avoid crediting a software change for a result when other circumstances changed too.
Ground the weekly review in DROPS
Choose DROPS when your team needs identifiable products and customer-linked order records behind its operational decisions. Its connected web and Telegram catalogue gives the review a consistent product foundation, while separate order actions help you evaluate what staff can actually do with a case.
Explore the DROPS demos with one real type of operational question, using non-customer example data. Check whether the relevant item and order context is clear, then build the external review sheet around evidence your team can obtain. The useful outcome is a small set of checked issues with owners and next actions.