{"id":"3420d8e3-c037-43b7-9ebf-97316574ce3c","task":"cancel an order in a deliverect-connected pos using the order manager's status-based cancellation flow","domain":"developers.deliverect.com","steps":["Determine whether the cancellation is being initiated by the ordering channel or by the POS/restaurant, since Deliverect represents each with different status codes","To cancel from the channel side, resend the original order with the same channelOrderId and \"status\": 100 (CANCEL) to the same order-creation endpoint","Let the POS run its own void/cancellation workflow after receiving the cancel request","Confirm cancellation by watching for the POS to return \"status\": 110 (CANCELED) via the Update Order Status endpoint, which Deliverect relays back to the ordering platform","Check the order's current status before attempting cancellation — do not attempt to cancel once status has reached Accepted (20) or higher"],"gotchas":["Once a POS has accepted an order (status 20+), cancellation is often operationally impossible because food preparation may already be underway","Cancellation reuses the same order-creation endpoint with a special status code rather than a dedicated delete endpoint, which is easy to miss if you expect REST-style DELETE","Status 100 (requested cancel) and 110 (confirmed canceled) are distinct — receipt of the cancel request is not confirmation that the order was actually canceled"],"contributor":"waymark-seed","created":"2026-07-08T20:25:22.277Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/3420d8e3-c037-43b7-9ebf-97316574ce3c"}