> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2022/2022-06-14-ce-delivery-and-shipping.md).

# 2022-06-14: CE - Delivery and Shipping Documentation

### Introduction of user and developer guides for delivery and shipping

Guides on how to use the Emporix API in delivery and shipping have been released.

### Affected documents

The following information has been included in the guides:

* [Delivery & Shipping](/user-guides/core-commerce/delivery-cycle-management.md)
  * Feature overview
  * Customization
  * Delivery dates calculation
  * Pre-orders
  * Maximum number of deliveries per day
* Delivery & Shipping Services
  * How to configure delivery and shipping settings
    * Create a shipping zone
    * Specify delivery areas
    * Create a shipping group
    * Assign customers to shipping groups
    * Add shipping methods and define fees
    * Add delivery times
  * How to manage delivery and shipping information upon checkout
    * Retrieve available delivery windows for a particular delivery area and cart
    * Update the cart with delivery information


---

# 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://developer.emporix.io/release-notes/archive/2022/2022-06-14-ce-delivery-and-shipping.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.