Written by DROPS.ST.
Set the physical closing time, online order cutoff and latest pickup time separately. The final accepted order needs enough preparation and handover time while responsible staff are still available.
DROPS gives the closing team customer-linked orders with the items they need to prepare. The website and connected Telegram shop use the same catalogue and order system, providing a common shop record for reviewing the workload.
Automatic cutoff enforcement and pickup-window scheduling require their own demonstration; shared orders and administrator-controlled settings do not establish them.
Separate the three times
Store closing time says when the physical shop closes. Order cutoff says when acceptance ends for the stated service, such as same-day pickup. Latest pickup time says when the final supported collection can occur.
A browseable menu after the cutoff does not explain whether customers can request another date or submit an order. Test the agreed behaviour separately.
Flowhub’s own guidance distinguishes store and ordering hours and discusses an earlier ordering cutoff. That illustrates the operating distinction, not a DROPS scheduling feature. Flowhub: store and ordering hours.
Canadian cannabis operators must check the local arrangement. Health Canada identifies provinces and territories as responsible for rules governing sales and store operation. Health Canada: provincial and territorial responsibilities.
Work backward from the service deadline
Identify when required work must finish. That deadline may precede physical closing if the responsible staff leave earlier.
Candidate order cutoff = completion deadline − preparation allowance − handover allowance − contingency.
| Input | Include | Evidence |
|---|---|---|
| Completion deadline | Staff availability and approved service end | Roster and procedure |
| Preparation | Remaining picking, checking and queue work | Observed closing workload |
| Handover | Work for the final accepted pickup | Ordinary handover observations |
| Contingency | Time for a foreseeable exception | Recent problems and staff judgment |
Use elapsed minutes. The fastest order is not a reliable preparation allowance for a closing queue with several items or unresolved instructions.
The result is a planning estimate, not a promise that every order will fit. Review it when workload or staffing changes.
Hypothetical example: earlier cutoff, unchanged closing
A fictional shop plans to finish service at 18:00. It allows fifteen minutes for preparation, ten for handover and ten for contingencies.
18:00 − 15 − 10 − 10 minutes = 17:25.
Physical closing remains 18:00. The 17:25 time concerns accepting new same-day pickup work.
The team must still agree the collection instruction and treatment of existing orders. This calculation does not promise every submission an identical readiness time.
If the remaining preparation queue needs thirty minutes, the same assumptions produce a 17:10 cutoff. That is a workload decision, not evidence of automatic queue-based scheduling.
Account for orders already accepted
Stopping new orders does not finish existing work. Assign someone to review the current orders and unresolved instructions.
Distinguish received from accepted, and prepared from handed over. Identify whether collection remains possible within the agreed arrangement and which exceptions need a decision.
Use the current customer-linked order record. A printed package or open message may reflect an earlier state.
Test the customer-facing boundary
In a demo or approved test environment, assess the view before, at and after the proposed cutoff. Use fictional details, with no funds, outbound messages or real fulfilment.
Record the expected result: same-day pickup versus a later request, the stated time zone and the behaviour of an already-open checkout. A static hours message does not prove ordering is restricted.
Include connected Telegram if it is in scope. Shared shop data is a reason to check both channels, not a refresh-time guarantee.
Assign an owner to review the cutoff and use the menu permissions guide to distinguish escalation from authorised settings changes. For exceptional dates, use the temporary-hours process.
Organise the closing workload with DROPS
Choose DROPS when you want customer-linked item records and a common web and connected Telegram order system for the closing team. Staff can assess the actual selection instead of reconstructing it from messages.
Explore DROPS and open the demo shops. Bring the deadline and buffer worksheet, demonstrate the intended boundary behaviour, and make the displayed times match the service your team can complete.