> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/guides/shipping-methods/shipping-glossary.md).

# Shipping glossary

**Shipping app**

A configured application that adds a new shipping method to the store and provides online shipping rates to customers at the checkout.

**Shipping request**

POST request sent from Ecwid API to the shipping app with non-encrypted order data in a JSON body. The shipping app must process the request and respond with shipping rates.

**Shipping rate**

Additional cost applied to the order for its delivery to the customer. The cost is added to the order total before customers proceeds to the payment.

**Shipping option**

Shipping rates returned by the app and displayed to customers at the checkout. One app can return multiple shipping options with different rates to one shipping request. For example, offering premium delivery or several pickup locations.

**Shipping method**

A combined view of the shipping options added by the app in Ecwid admin. Provides additional settings to the store owner: "enabled" toggle, shipping zones, handling fees, etc.


---

# 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.ecwid.com/guides/shipping-methods/shipping-glossary.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.
