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