> For the complete documentation index, see [llms.txt](https://docs.tuplo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/preferences/shipping.md).

# Shipping

Determine any shipping services.

<figure><img src="https://3633098189-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV0nc9z5ERStcxnY8SDZS%2Fuploads%2FduGoRWqdmkoFBAgNhzs4%2Fdashboard-pref-shipping.webp?alt=media&amp;token=257431f1-5425-408a-83f4-61acb8a5550d" alt=""><figcaption><p>Shipping preferences.</p></figcaption></figure>

You can connect your Shippo account to integrate their services with Tuplo Studio. The [Shippo section](https://docs.tuplo.com/tuplo-account-management-guide/integrations/shippo.md) of this guide provides step-by-step details and more information.

If you do not plan on using Shippo, you can select Custom as your Shipping Type and then define your settings accordingly.

{% hint style="info" %}
**Quick Tips!**

With options for live shipment tracking, in-house label printing, and calculated shipping rates, we highly recommend using the Shippo integration, especially for businesses focused strictly on online sales.
{% endhint %}


---

# 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.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/preferences/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.
