> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/settings-1/email-notifications/fulfillment-notifications.md).

# Fulfillment notifications

When working with orders in equipme, you will receive email notifications about different fulfillment stages.

These notifications reflect what is happening on the supplier side, for example when an order is being processed, prepared for delivery or shipped.

At first glance, you might expect to receive an email for every single update immediately.\
However, fulfillment notifications follow a slightly different logic.

***

### How fulfillment notifications are sent

Fulfillment emails are not sent instantly for every status change.

Instead, they are bundled and sent in regular intervals.

Between 12:00 and 20:00, notifications are grouped and sent every two hours.

This means that if a supplier updates the status of an order, there can be a delay before the corresponding email is sent.

In practice, this helps avoid a constant stream of emails when multiple updates happen within a short period of time.

***

### Only the latest status is considered

Another important aspect is that notifications always reflect the most recent state of a service.

If several status updates happen before the next email is sent, only the latest one is included.

For example, an order might move through the following steps:

* processing
* ready for delivery
* shipped

If all of these happen within a short timeframe, you will only receive a notification for the final state.

Earlier updates are skipped and not sent separately.

***

This behavior can sometimes feel unexpected if you are waiting for a specific update.

For example, you might not receive a notification that an order is being processed, but instead directly see that it has already been shipped.

This does not mean that intermediate steps were skipped in the system.\
It simply means that only the most relevant update was sent via email.

The goal of this approach is to reduce unnecessary noise.

Instead of sending multiple emails for every small update, Equipme consolidates changes and sends a single notification that reflects the current state.

This keeps inboxes cleaner and makes notifications more meaningful, especially in environments where many orders are processed at the same time.

{% hint style="info" %}
Fulfillment notifications are bundled and sent in intervals.\
Only the latest status is included in the email.
{% 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:

```
GET https://hub.equipme.io/equipme/settings-1/email-notifications/fulfillment-notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.