> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/ordering-channels/uber-eats/manage-order-prep-time.md).

# Manage order prep time

You can set and manage your **Normal** and **Busy** prep times directly in Atlas, helping you better align with kitchen operations and improve customer experience.

***

#### **Getting Started**

Follow these steps to set up your prep times:

1. **Log in** to your Atlas account.
2. Navigate to:\
   **Settings → Platforms → Automations Tab → Food Preparation Time**
3. Enter your desired:
   * **Normal Prep Time**
   * **Busy Prep Time**\
     \&#xNAN;*(Note: Busy time must be **greater** than the normal prep time.)*
4. Select the appropriate level to apply these settings:
   * **Location level** or
   * **Business level**
5. Click **Save and Sync** to push the prep times to **Uber Eats**.

***

{% hint style="info" %}

#### **Important Notes**

* The **active prep time mode (Normal or Busy)** is controlled from **Prime** — not Atlas.
* Atlas is used **only for configuring and syncing** prep time values.
* **Changing prep time does not require a menu publish**. However, after updating, you **must click “Save and Sync”** for changes to reflect.
  {% endhint %}

***

This gives you more flexibility and control over your order flow during peak and non-peak hours.

 Reach out to our support team for further clarification.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.urbanpiper.com/ordering-channels/uber-eats/manage-order-prep-time.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.