Written by DROPS.ST.
Before a cannabis shop changes systems or operating ownership, list its unfinished commitments and assign each one an accepted next owner. Preserve the original reference, current facts and authorized next action. Move a record only through a demonstrated supported process; a successful catalogue transfer does not establish an open-order importer.
DROPS gives new shop work a coherent destination: customer-linked order items can be reviewed against product references, units and stock, with the website and connected Telegram using the same catalogue and order system. Use that context to assess the shop side of the transition while keeping legacy commitments explicitly owned.
Define the cutover boundary
Record the effective point and which work it affects: new requests, current catalogue editing or specified unfinished orders. Do not use one general “migrated” label for all three.
Identify who may approve the transition and which process remains authoritative for each old commitment. Use the actual business, provider and record-sharing scope. Ownership, commercial terms and financial authority need their appropriate qualified review.
An unresolved paid order should not be recreated as an unpaid new request merely because a different system is opening. Likewise, an old reference should not be silently replaced by a new one that staff cannot relate back to its source.
Use an open-work cutover ledger
Keep this original ledger in the approved business process. It is not a promised native migration tool or immutable history.
| Ledger entry | Record | Handoff check |
|---|---|---|
| Original reference | Existing order/request and source system | Can the original be located? |
| Current facts | Item, unit, quantity and verified state | Which work is actually unfinished? |
| Outstanding obligation | Specific decision or next action | Is it separate from a new request? |
| Active process | Approved system/process controlling the work | Which record should staff act on? |
| Receiving owner | Named person accepting responsibility | Can that person perform the permitted step? |
| Transfer evidence | Actual supported route and reviewed mapping, if used | What changed and what remains unresolved? |
| Completion | Checked outcome and source reference | Is the original commitment closed or still owned? |
The Government Data Quality Framework recommends documentation that makes records understandable and reduces ambiguity. Apply that principle to original references and state meanings; it does not supply an order-transfer format. Government Data Quality Framework.
Establish the actual transfer route
Ask the provider to demonstrate the required fields, reference relationship and supported state treatment with fictional material in an agreed isolated environment. Check the item, unit and customer association as well as the order total.
If a supported transfer has not been established, keep that commitment in its approved existing process with a named owner. Mark the transfer unverified. Opening the new shop does not require pretending every old record has moved.
Do not let the old and new records become two independent instructions for the same unfinished work. Where a supported replacement is necessary, identify which record is actionable and preserve the relationship to the original.
The catalogue migration checklist handles product reconciliation. This ledger addresses work that still needs completing.
Hypothetical example: one open order, two apparent tasks
A fictional legacy order contains two units and remains unfinished. During a rehearsal, a proposed new record looks like another fresh request, while the original still appears actionable to the old team.
The reviewer holds the transfer outcome and records the original reference, verified state and single approved process. A receiving owner accepts the next action before the team treats the new record as an instruction.
The case does not demonstrate an importer, automatic duplicate prevention or a financial correction. It shows which ownership evidence must be resolved before work can continue safely.
Reconcile after the boundary
Compare the ledger's unfinished set with the actual authorized outcomes. Track completed, still open and unresolved cases separately, using their original references.
Check new activity before correcting an earlier transfer. A saved pre-cutover copy may omit later work; do not use it as a blanket replacement for current records.
Keep financial questions with the approved accounting/provider process. A status label, transferred total or customer statement does not prove payment receipt or refund authority.
For preserved historical files, use the readability acceptance sheet. For continuing responsibilities, use the postlaunch ownership matrix.
Put current work around clear DROPS records
Choose DROPS for customer-linked items and a common web/connected Telegram shop context that the receiving team can inspect. Its separate order-action controls help you assess who may perform the next supported step; a business responsibility is not itself that permission.
Explore DROPS and open the demos. Bring one fictional unfinished order and the ledger. Demonstrate the supported shop record, establish any real transfer route separately and keep every legacy commitment attached to an active process and accepted owner until its outcome is verified.