> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/readme-1/work-with-work-orders/orders-adding-due-date.md).

# Add a due date to a work order

1. Create a new order or recall an existing order.
2. Tap **Orders** | **Order Details** | **Order Due**.
3. On the **Order Due** screen, enter the date on which the order should be ready for pick up.

You can enter the date manually or click the calendar icon and select a date.

<div align="left"><img src="/files/b0UohJtdnYWo7n4kUr1Q" alt=""></div>

4. Tap **OK**.
5. Finish creating the order.

The due date displays in the transaction summary on the Transaction screen.

<div align="left"><img src="/files/b0UohJtdnYWo7n4kUr1Q" alt=""></div>

{% hint style="success" %}
It may be your store's policy to print a report of orders that are due on a specific date. The **Order (Detailed) Report**, located under **Reports** | **Active Reports** | **Custom** | **Orders** in Store Manager, can be used to print out a list of orders that need to be fulfilled on the current or next business day.
{% endhint %}


---

# 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://docs.rmhpos.com/readme-1/work-with-work-orders/orders-adding-due-date.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.
