> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/data-model/shipping.md). # Shipping - [Shipments and shipping categories](https://docs.commercelayer.io/data-model/shipping/shipments-and-shipping-categories.md): Shipment creation and splitting logic, stock line items, and how shipping categories affect order fulfillment - [Stock transfers](https://docs.commercelayer.io/data-model/shipping/stock-transfers.md): Moving inventory between stock locations — automatically during order fulfillment or manually to reorganize stock - [Shipping zones and methods](https://docs.commercelayer.io/data-model/shipping/shipping-zones-and-methods.md): Defining shipping zones by location and configuring shipping methods with cost structures, availability rules, and weight-based tiers - [Delivery lead times](https://docs.commercelayer.io/data-model/shipping/delivery-lead-times.md): Providing customers with estimated delivery time ranges based on stock location and shipping method - [Shipping carriers](https://docs.commercelayer.io/data-model/shipping/shipping-carriers.md): Connecting carrier accounts to markets for rate options, shipping labels, and tracking numbers - [Parcels, packages, and pickups](https://docs.commercelayer.io/data-model/shipping/parcels-packages-and-pickups.md): Organizing shipment contents into parcels and packages, with parcel line items and carrier pickup scheduling - [Geocoders](https://docs.commercelayer.io/data-model/shipping/geocoders.md): Converting customer addresses into geographic coordinates to power address validation and location-based features --- # 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.commercelayer.io/data-model/shipping.md?ask=&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.