Hi all,
We build Shopify apps for pickup, local delivery, and shipping rates. We are trying to expose merchant fulfillment data through UCP and have hit a blocker we would like guidance on.
What we are trying to do
Our app already shows shoppers, on the product page, which fulfillment methods are available for a given product and location (pickup, local delivery, shipping), the earliest available date and time slot for each, and the location or delivery zone that applies. We want that same data to be readable by agentic surfaces, so that when a shopper asks an assistant something like “can I collect this today,” the answer reflects the merchant’s actual pickup and delivery configuration rather than generic shipping copy.
Where we are blocked
The UCP profile is served by Shopify at the fixed path /.well-known/ucp on the merchant’s domain. As far as we can tell there is no supported way for an installed app to contribute to that response. We have not found an Admin API surface, app extension point, or metafield-backed mechanism that lets an app add fields to the profile or register an additional capability endpoint.
What would unblock us, in rough order of preference:
- An extension point that lets an installed app append namespaced fields or capability entries to the merchant’s UCP profile.
- A way for the native profile to advertise an additional app-hosted endpoint that agents can follow for fulfillment availability.
- Confirmation that this data is meant to be exposed some other way entirely, in which case we would rather build toward that from the start.
The workaround we would rather not ship
The only working path we found is a per-merchant, domain-level redirect from /.well-known/ucp to a profile we host and generate. It functions, but it only applies where the merchant’s domain is proxied through something like Cloudflare, it needs manual DNS work for every merchant, and it means a third party takes over a path Shopify owns. Anything Shopify adds to the native profile later would be dropped for those merchants. That is a lot of fragility and support overhead to put on merchants for a protocol this early.
Questions
- Is app-level extension of the UCP profile on the roadmap? If so, is there a preview or early access program we can join?
- If not, is there a sanctioned pattern today for a third-party app to expose fulfillment availability to agents?
- Is there a better place to file this as a formal feature request?
Happy to share more detail on the data model or to test anything in preview. Thanks.
