Written by DROPS.ST.
Before correcting an order, identify the record, capture the customer’s request and check what has happened. Use an authorised process, reconcile the resulting items and totals, and verify what fulfilment staff will receive.
DROPS keeps orders and items linked to the customer record. Separate order-action controls provide a practical basis for deciding who handles each step instead of giving every worker the same powers.
Native item amendments, built-in approval history and post-payment changes require separate demonstration; order records and permissions do not establish those workflows.
Distinguish a request from approval
Record the order, affected line, intended quantity or instruction and any condition. A question about an item is not necessarily an amendment request.
Confirm the request through the approved contact and verification process. An order number in a message does not automatically authorise changes to another customer’s order.
“Would one unit work instead?” is a proposal until the customer decides. Retain the agreed result and confirmation time in the approved recordkeeping system.
Check the current state
Before acting, establish:
- Correct customer and order reference.
- Received versus accepted order.
- Recorded or unresolved payment state.
- Preparation started, finished or not begun.
- Already handed over, cancelled or replaced.
Use current evidence. A request before preparation may need a different process from one after handover. An order already replaced should not remain actionable.
Do not give “complete” a second unofficial meaning in a staff note while the operational record says something else.
Use a correction record
| Element | Capture | Check |
|---|---|---|
| Original order | Reference and customer link | Correct record? |
| Requested change | Line, quantity or instruction | Specific outcome understood? |
| Current state | Payment, preparation and handover | Appropriate process? |
| Approval | Agreed result, channel and time | Proposal confirmed? |
| Authority | Person and permitted action | Within their role? |
| Result | Final items, quantities and total | Matches approval? |
| Fulfilment recheck | Current preparation instruction | Old version removed from use? |
“Fixed” does not explain what was approved or what staff should prepare. Keep the original request and final result distinguishable.
For personal details, OPC’s PIPEDA guidance calls for accuracy appropriate to their use and recommends recording verification steps. OPC: accuracy.
Separate customer approval from staff powers
The customer agrees to the outcome; the business authorises how it happens. Define permitted requests, actions and escalation.
DROPS has separate order controls and administrator-only settings. Test the configured role rather than assuming a broad label grants narrow correction access.
Use the permissions guide. Catalogue-edit access also covers account edits and wallet adjustments; staff should not receive unrelated powers to resolve one order.
If the supported process requires replacement rather than editing, identify the actionable record and preserve its relationship to the original. Do not leave two active records representing one intended order.
Reconcile totals and prepared items
Compare final items, units and quantities with the agreed request. Review applicable package or quantity pricing and all included charges.
A quantity reduction may change the relevant pricing range. Do not copy the earlier unit price without checking the resulting calculation.
Use the approved process for final amount and service confirmation. Refunds, additional payments and paid-record adjustments are separate authorised financial actions; this guide does not instruct staff to move funds.
Check the physical preparation too. A corrected screen is insufficient if the old package is still awaiting pickup.
For a destination correction, distinguish the original address from the approved new one. Reassess delivery eligibility and charges before the supported change. Product-edit access does not establish an address-amendment capability.
Hypothetical example: two units become one
A fictional customer requests one unit instead of two after preparation but before handover.
The responsible person verifies the order, confirms the request and determines whether the supported process allows an amendment or needs a replacement.
After the authorised action, staff reconcile the item, quantity and total, then match the package to the current actionable record. The request, record and prepared order now agree.
Rehearse pre-preparation and already-prepared cases separately using fictional records in an approved environment, without funds, messages or fulfilment. The checkout acceptance guide establishes the original customer-to-order comparison.
Keep customer intent connected with DROPS
Choose DROPS when you want customer-linked items and clear order responsibilities as the factual starting point for corrections. Staff can assess the actual selection instead of relying on an isolated message.
Explore DROPS and open the demo shops. Bring one correction scenario and assess the permitted action, resulting record and fulfilment instruction together.