> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/fulfillment.md). # Fulfillment - [Shipping Methods](https://docs.hotwax.co/documents/system-admins/fulfillment/shipping-methods.md) - [Carrier & Shipment Methods](https://docs.hotwax.co/documents/system-admins/fulfillment/shipping-methods/carrier-and-shipment-methods.md): This guide outlines how to efficiently manage carriers and shipment methods in HotWax Commerce, covering tasks such as creating carriers, linking shipment methods, and enabling methods for brands. - [Shipping Gateways](https://docs.hotwax.co/documents/system-admins/fulfillment/shipping-methods/shipping-gateway.md): Learn how to set up shipping gateways in HotWax Commerce to integrate with Third-Party Logistics companies (Carriers) for efficient fulfillment of online orders. - [Shipping Boxes](https://docs.hotwax.co/documents/system-admins/fulfillment/shipping-methods/shipping-box.md): Learn how to create customized packing boxes in HotWax Commerce, ensuring precise shipping cost calculations and accurate label generation. - [Configure Rate Shopping](https://docs.hotwax.co/documents/system-admins/fulfillment/configure-rate-shopping.md): This guide walks you through setting up rate shopping in HotWax Commerce. --- # 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.hotwax.co/documents/system-admins/fulfillment.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.