> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/donor-support/faq/shipment-information.md).

# Shipment Information

Anedot does not manage event logistics, shipping, or merchandise fulfillment for organizations. This guide is written for donors.

Anedot does not manage event logistics, shipping, or merchandise fulfillment for organizations. For questions about merchandise, order shipments, or other fulfillment issues, contact the organization you supported.

### Finding The Organization's Contact Info

* Check the email receipt for your purchase—organization contact details are usually in the footer.
* Log in at <https://donor.anedot.com/support>:
  1. From the main menu, select **Donations**.
  2. Select the donation for that organization.
  3. Scroll to the bottom of the donation details for email and phone.
* Visit the organization's website or social pages.
* Check the Privacy Policy link in the site footer—it often includes contact details.

### Still Need Help?

Email <help@anedot.com>, and we will do our best to point you in the right direction.


---

# 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.anedot.com/donor-support/faq/shipment-information.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.
