Introducing Forced Closures

Deliveroo introduced an additional tool, called Forced Closure, to support Partners in reducing the risk of appearing open for orders during periods when they are actually closed. This new tool can only be enacted by Deliveroo.

With Forced Closures, we eliminate the risk of a Partner's site being accidentally opened by automations, when they should be closed, and minimise the risk of disappointing customers with cancellations and rejections. Forced Closures ensure Partners remain closed on the Deliveroo platform during periods they are not open, such as Christmas Day, holidays or during refurbishment.

Please note that if Partners wish to open their restaurant when a Forced Closure is active, they will need to contact Deliveroo by calling our Partner Support team. As only Deliveroo can open a site during an active Forced Closure, the Partner will not be able to open the site from their side.

Suggested Action - What changes can you make?

While this tool is ready for use by Deliveroo starting from the upcoming holiday period, your partners will benefit from being notified about the state, via the integration. To support this launch, Integrators can make the below change, so a message can be surfaced to your Partners directly, to let them know if they are in a Forced Closure and need to contact Deliveroo to re-open.

You will find full details about the proposed changes in our updated documentation: API-Docs: Cancel a site days off period.

Once the action is completed and Forced Closure messaging becomes visible for your Partners, please also update your Support articles to advise Partners to contact Deliveroo directly, if they wish to remove Forced Closure and open for orders.

When do you need to complete the development work?
The changes are live and available now for you to configure on your integration. The sooner you can make these changes, the quicker your partners will benefit from the messaging regarding Forced Closures.

If you have any questions or require assistance, please raise a query on the Technical Integrations Support Portal.

Steps to surface forced closure messaging using Site API:

If a partner has a forced closure active, the partner will not be able to open directly and the API will return the following error:

Status-code: 400 (bad request)  
{  
    "error": {  
        "code": "bad_request",  
        "message": "Unable to open restaurant, reason: CLOSED_PERIOD"  
    }  
}

When listing days off, you may encounter a new days_off type where the reason is “FORCED_CLOSURE”:

{  
    "days_off": [  
        {  
            "id": 100226,  
            "days_off_id": "gb:91029a10-8045-4fd6-8e83-326b6a39935a",  
            "local_start_time": "2024-12-04 00:00",  
            "local_end_time": "2024-12-04 23:59",  
            "reason": "FORCED_CLOSURE",  
            "cancelled_at": null  
        }  
    ]  
...  
}

If you try to a cancel a forced closure, then the API will return the following error:

Status-code: 400 (bad request)  
{  
    "error": {  
        "code": "bad_request",  
        "message": "This closed period can only be updated by Deliveroo."  
    }  
}