added
Separate _id for Channel Cancellations
6 months ago by Ewan Farry
This update is relevant to any POS or any integration which receives orders via Deliverect.
When a channel initiates a cancellation, the secondary order which we generate will no longer bear it's own unique _id
but will match the _id
of the original order.
The identifier of the original order will remain as the channelOrderId
and the "status":100
confirms it's status as a cancellation request.
This allows for the streamlining of cancellations, both in API implementation and for customer's reporting and order management.
New format
The new format will send an _id
for the order cancellation which matches the original like below;
{
"_id": "6655bf36f231f2d853bca910",
"channelOrderId": "TEST123",
"status": 1,
...
}
{
"_id": "6655bf36f231f2d853bca910",
"channelOrderId": "TEST123",
"status": 100,
...
}
📆 Deprecation Date
Deliverect will remove the previous behaviour of creating two separate
_id
's as part of the cancellation flow on
September 9th 2024