> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/product-theme-blocks/local-pickup.md).
# Local pickup
The **Local Pickup** block displays in-store pickup availability directly on the product page. This enhances the shopping experience by informing customers where and when they can collect their items in person, based on Shopify's built-in pickup settings.
> Only one Local Pickup block is allowed per section (`limit: 1`).
This feature pulls data from your Shopify settings to show available pickup locations and estimated readiness times. It's especially useful for brick-and-mortar retailers offering in-store or curbside pickup.
Settings
Type
Description
Padding
Bottom
range
Controls spacing below the block.
## Notes
* This block integrates with your **Shopify store pickup locations** configured under **Settings > Shipping and delivery**.
* Pickup availability updates dynamically based on the product and selected variant.
* Ensure pickup locations are properly set up in Shopify to take advantage of this feature.
Learn how to set up local pickup for your store here:
{% embed url="" %}
---
# 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://broadcast.presidiocreative.com/product-theme-blocks/local-pickup.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.
.png?alt=media&token=64f5ccf5-3406-475e-adc7-b6b93448fe87)