> 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/2024/2024-09-17-ce-delivery-shipping.md).

# 2024-09-17: CE - Delivery Methods and Delivery Zones Rename

### Overview

We have renamed **Delivery Methods** to **Shipping Methods** to and **Delivery Zones** to **Shipping Zones** across the platform. This change ensures consistency in terminology and aligns with industry standards, providing a more intuitive experience for our users. All references to delivery methods and zones have been updated to shipping in relevant sections, including settings, notifications, and documentation. Please note that this is a terminological change only.

| Former name     | Current name    |
| --------------- | --------------- |
| Delivery Method | Shipping Method |
| Delivery Zone   | Shipping Zone   |

### Fixes and improvements

Delivery management - entries modification.

### Known problems

No known problems at time of release.

### Documentation and links

* [Shipping Zones and Methods](/user-guides/management-dashboard/settings/shipping-methods.md)


---

# 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/2024/2024-09-17-ce-delivery-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.