Written by DROPS.ST.
A temporary ordering-hours change needs a date, authorised owner, customer-facing check and restoration step. Updating today’s hours is incomplete if ordinary ordering stays closed after staffing returns.
DROPS keeps accepted orders and their items linked to customers, giving the team a clear record of existing work. Connected Telegram shares the website’s catalogue and order system. Separate order-action controls and administrator-only settings also help distinguish order handling from configuration responsibility.
A dated exception calendar, automatic reopening and location-specific scheduling require separate demonstration; this process does not assume they are native features.
Record the ordinary schedule
Capture the shop address, time zone, physical hours and supported ordering or pickup window before approving an exception.
“Close early” could mean stopping new requests, ending collections or closing the physical shop. Specify the affected service and consequences for already accepted work.
Use the pickup-cutoff worksheet to calculate the time allowance. This guide manages applying and ending the exceptional arrangement.
In Canada, provinces and territories govern cannabis sales and store operation. A national holiday calendar does not establish an identical closure requirement everywhere. Health Canada: provincial and territorial responsibilities.
Keep an exception-date record
Use the planning system your staff already rely on, with one approved schedule.
| Field | Record | Purpose |
|---|---|---|
| Date and time zone | Exception start and end | Defines when it applies |
| Affected service | New orders, pickup or stated service | Defines what changes |
| Baseline and exception | Ordinary and temporary window | Gives the exact change |
| Owner and deputy | Approver, editor and backup | Covers absence |
| Existing orders | Review owner and treatment | Accounts for accepted work |
| Restoration | Time, owner and baseline | Ends the exception |
Keep internal staffing details out of the public instruction unless needed. Customers need the service arrangement, not employees’ reasons for absence.
Separate approval, editing and checking
The approver decides the arrangement. The authorised editor applies it. The checker confirms the customer view and treatment of existing work.
A small team may combine roles, but should record all three responsibilities. Saving a setting is not customer-facing verification.
DROPS settings require an administrator and order responsibilities have separate controls. Evaluate the actual role; a label alone does not prove narrow location or field access. Use the menu permissions guide.
Name a deputy for restoration. A reminder sent only to someone on leave is not a reopening plan.
Check before, during and after
Before: approve the temporary window, preserve baseline values, identify accepted orders and agree customer wording. Define the channels and addresses to check.
At the change: record application time and inspect the customer view. Test ordering behaviour in an approved environment without real orders, funds or messages.
During: review existing work and record any further authorised change. Keep staff instructions consistent with the published arrangement.
After: restore the baseline, repeat the customer check and close the record. If hours changed permanently, record that decision instead of restoring an obsolete schedule.
Flowhub’s help describes manually managed holiday hours. It illustrates why restoration ownership matters, not how DROPS implements exceptions. Flowhub: managing ordering hours.
Hypothetical example: one day, not a new baseline
A fictional shop normally stops same-day ordering at 17:25. Reduced staffing on 18 November produces an approved 15:25 cutoff for that day.
The record names the shop, time zone, editor and deputy, and assigns someone to review accepted collections. The checker assesses the customer message and intended boundary in an approved test environment.
The next morning, the deputy restores 17:25 and records the customer observation. A planning note saying “18 November only” would not restore a manual setting by itself.
Handle sudden shortages with the same ownership
For an unexpected change, capture who approves, which service changes, when it starts and who restores it. Reconcile accepted orders rather than assuming the workload disappeared with new ordering.
Escalate a mismatch between the approved service and customer view. Give staff one agreed instruction while it is resolved.
Keep exceptional days organised with DROPS
Choose DROPS when you want customer-linked orders and a shared web and connected Telegram order system while the team manages changing capacity. Clear order and settings responsibilities give the change owner a practical starting point.
Explore DROPS and open the demo shops. Bring an ordinary day and an exception record. Assess the proposed change method, customer view and restoration proof together.