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

# Shipping Locations

Our Shipper Database contains extensively researched location data for shipper facilities.

### Overview

The shipper database contains researched and vetted information about thousands of shipping locations. Locations are a specific instance of a facility operated by that shipper. All locations belong to a [parent company](https://docs.shippercrm.com/shipper-database/parent-companies.md), which makes it easy to associate it with a larger organization.

Shipping locations are how points on the Magic Map are rendered. The location of the point on the map corresponds with the physical location of the facility that the shipper operates. You can use this location data to find shippers are in geographies that your company serves.&#x20;

### Shipping location information

The shipping location information is the first set of data in a [Shipper Details Card](https://docs.shippercrm.com/magic-map/shipper-profiles.md), and will appear at the very top of the card. You can view this information by clicking a point on the Magic Map, which will open up the shipper details for that point.&#x20;

You can expect to find the following information under this section:

1. **Location name**
2. **Address**
3. **Main phone number**

All locations will have an address. 90% of locations will also have a direct facility phone number.

### Conclusion

Shipper locations in Shipper CRM are the locations of specific shipper facilities. These are easily viewable from the Magic Map, where you can select locations that correspond with the lanes that your organization runs.


---

# 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.shippercrm.com/shipper-database/shipping-locations.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.
