> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-shopify/shopify-reference/orders/order-promise-dates.md).

# Order promise dates

Learn how Shopify fulfillment-order promises populate HotWax Commerce ship-group dates and how missing estimates are calculated.

During realtime and historical order imports, the Shopify integration reads promise dates from Shopify fulfillment orders and records them on HotWax Commerce ship groups. When Shopify does not provide a promise date, HotWax Commerce calculates the missing estimate from configured service-level agreements (SLAs).

{% hint style="info" %}
This page covers dates recorded after an order is placed. For the pre-purchase estimate shown on the storefront, see [Configure estimated delivery dates](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/learn-hotwax-oms/how-to-guides/configure-estimated-delivery-dates.md).
{% endhint %}

## Map Shopify promise dates

The integration maps Shopify fulfillment-order data to the corresponding HotWax Commerce ship group:

| Shopify value                               | HotWax Commerce value                                                          |
| ------------------------------------------- | ------------------------------------------------------------------------------ |
| `fulfillBy`                                 | `Ship By` and, when no estimated ship date was supplied, `Estimated Ship Date` |
| `fulfillAt`                                 | `Ship After`                                                                   |
| Latest `deliveryMethod.maxDeliveryDateTime` | `Estimated Delivery Date`                                                      |

The same mapping applies to realtime imports and historical orders imported through bulk synchronization.

When a ship group contains items from multiple Shopify fulfillment orders, HotWax Commerce uses the earliest `fulfillBy`, the latest `fulfillAt`, and the latest `deliveryMethod.maxDeliveryDateTime`. Canceled fulfillment orders are ignored. Closed fulfillment orders are included when historical orders are imported so their original promise data is preserved.

## Understand fallback estimates

HotWax Commerce calculates a date only when the order payload does not already contain one. Values supplied by Shopify or another integration are not overwritten.

The fallback applies to ship groups that require fulfillment. Point-of-sale (POS) cash sales and ship groups whose items are already completed are skipped.

HotWax Commerce calculates the dates as follows:

* `Estimated Ship Date` uses `Ship By` directly when it is available. Otherwise, the facility's ship SLA is added to the later of the order date or `Ship After` date.
* `Estimated Delivery Date` adds the carrier shipment method's delivery days to the estimated ship date. The delivery date remains empty when delivery days are not configured.

The ship SLA comes from the facility that currently holds the ship group. An unbrokered ship group uses the brokering queue facility, whose default is one day. An allocated ship group uses the assigned store or warehouse. A missing facility value falls back to one day, while zero represents same-day shipping.

## Configure supporting values

Use the following administration pages to maintain the values used by the fallback calculation:

* Set the facility's `Days to Ship` value in [Manage facility details](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/facilities/manage-facility-details.md#configure-fulfillment-settings).
* Set the carrier shipment method's `Delivery Days` value in [Carrier and shipment methods](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/fulfillment/shipping-methods/carrier-and-shipment-methods.md#shipment-methods).


---

# 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.hotwax.co/documents/learn-shopify/shopify-reference/orders/order-promise-dates.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.
