> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-12-delivery/file/external-zones.md).

# External Zones

**Use External Zones**

Enable this option to import delivery sections from an External Orders Service (EOS).

**Zones**

This column displays the name of each external section.

NOTE: This description is modified by the EOS only.

**Delivery Fees**

This column displays any amount added for each external zone.

NOTE: This value is modified by the EOS only.

**Base Delay**

This column displays the minimum number of minutes required to get to each external zone.

{% hint style="info" %}
NOTE: This time is modified by the EOS only.
{% endhint %}

**Additional Delay**

Enter the extra time required to get to each zone, according to road conditions and rush hours.

{% hint style="info" %}
NOTE: This second delay is modified at the restaurant, and then transmitted to the EOS in real-time.
{% endhint %}

**Status**

Set this field to Close if the drivers currently can not get to that zone, because off road conditions. For example, if the main road leading to this zone is closed, you can shut down this zone for this restaurant, so that the EOS refuses orders, or tries to assign orders to another restaurant with their permission.

{% hint style="info" %}
NOTE: This status is modified at the restaurant, and then transmitted to the EOS in real-time.
{% endhint %}

**Reset at End Of Day**

Enable this option to automatically bring back the Additional Delays to zero and the Statuses to Open at the end of the fiscal day. The Zones, Delivery Fees and Base Delays fields will then also be imported from the EOS.

**Manual Update**

Touch this button to import immediately the Zones, Delivery Fees and Base Delays from the EOS.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-12-delivery/file/external-zones.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.