Written by DROPS.ST.
For cannabis and vape shop operators changing software, a working new shop does not complete the review of old service charges. Identify each billed service, confirm its remaining purpose and follow its actual cancellation terms. Close the task with documented confirmation and a review of the relevant subsequent invoice.
DROPS brings products, stock and customer-linked orders together, with the website and connected Telegram using the same catalogue and order system. That common shop can replace separately handled work where the demonstrated scope fits. Confirm which old functions have actually ended before deciding which services to cancel.
Separate cutover from the billing decision
Write down when ordinary work moved, which accounts remain needed and who can authorize their closure. A service might still hold required history, supply another function or remain subject to agreed charges.
For a concrete vendor example, Bold's July 2026 guidance tells merchants moving between its subscription apps to remove the old app to stop future app charges and export wanted history first. That is Bold's process, not a cancellation rule for DROPS or every provider. Bold: charges after migration.
The useful question is: what action and effective date do the terms for this exact service require?
Use a cancellation-and-invoice register
Make one entry per billed service or separately agreed add-on. This is an owner-managed register, not an automatic DROPS cancellation workflow.
| Stage | Evidence to keep | Decision |
|---|---|---|
| Identify | Provider, account, service and invoice reference | Which charge are we reviewing? |
| Check dependency | Remaining work and retrieval needs | Retain, replace or ready to close? |
| Authorize | Named decision owner and exact scope | Who approves the action? |
| Follow terms | Applicable notice/process and proposed effective date | What must happen next? |
| Confirm | Provider response or supported cancellation result | What ended, and when? |
| Review billing | Relevant invoice period and line item | Closed or explanation still needed? |
Keep the register's evidence references in approved storage. Do not include payment credentials. Several products from the same provider may still need separate entries if their accounts or terms differ.
Confirm that retiring the service will not break another job
Review the software dependency map. An old menu tool may also supply an image file, operational report or another still-used function.
Assign each remaining dependency an outcome. Preserve the needed record through an approved process, demonstrate its replacement or retain the service for its specific remaining purpose. Do not delete an account merely to make the software list shorter.
The migration rehearsal checklist establishes catalogue acceptance. Cancellation needs its own account, terms and billing evidence even after those checks pass.
Compare the charge with its period and scope
Record the invoice issue date separately from the service period it covers. Ask whether the line concerns the service being closed, another add-on or a separately agreed charge. Keep an unexplained amount marked unresolved.
Use the dated agreement and provider explanation to determine the next authorized step. Do not treat an unfamiliar charge as automatically invalid or assume a pause, refund, credit or fee waiver is available.
If the provider response concerns another account, return to the service identity in the register. A confirmation for one product does not close every entry carrying the same provider name.
Hypothetical example: one migration, two old charges
A fictional operator moves ordinary catalogue work to the new shop. Its next invoice contains an old catalogue-app line and a separate reporting add-on.
The catalogue-app entry has cancellation confirmation, but the operator has not checked the period billed. The reporting add-on still supplies a required record and has no authorized exit decision.
They request an explanation of the first line and keep the second service under its named owner until retrieval is resolved. They do not mark both charges as duplicates or describe the migration as a demonstrated saving.
Close each entry with a named outcome
Use retained for a defined purpose, cancellation confirmed and billing checked, or unresolved with an owner and next review. Distinguish the provider's confirmation from evidence that you have checked the agreed billing outcome.
Keep disputes within the appropriate provider and business-adviser process. This register organizes facts; it does not determine contractual entitlement or instruct anyone to stop a payment.
Consolidate the shop around DROPS, then review the leftovers
Choose DROPS for a coherent catalogue and customer-linked order context shared with connected Telegram. Evaluate the supported work together, then give every remaining service a clear purpose or documented exit decision.
See DROPS and explore the demos. Bring your function map and service register. Confirm what the proposed shop replaces, what remains necessary and which owner will review the actual cancellation and billing evidence.