Shopify now publishes a Poppy file for every store, and Meta's Muse reads it first. Open yours and read it
Yesterday an agent could walk into your Shopify store without saying who it was. Now Shopify hands every store a small file that does the introductions, and Meta's Muse looks for it first. You can read yours in a browser tab.

On November 13, 2026 Sierra released version 1.0 of the Poppy agent protocol and Shopify switched it on for every store, with no merchant setup. Meta's Muse checks for the file first. The file tells an agent who the store is and what it may do, and it hands shopping itself to Shopify's UCP. You don't have to do anything, but you should open yours, read it, and decide who owns agent rules for the store.
What is this file, and why is it on my store?
You may not have heard of Poppy yet. Sierra, the AI customer-service company, released version 1.0 of its Personal Agent Protocol on November 13. It's a standard for how a personal AI agent, the kind that shops or books things for a person, deals with a company: how the agent says who it is and finds out what it's allowed to do. Sierra says more than a hundred companies have signed on as design partners, and Meta's Muse, which Sierra says automatically looks for Poppy first on every site it visits, now has it switched on for everyone who uses it.
The part that touches you: Shopify has enabled Poppy for every merchant on its platform. Sierra's post says every Shopify store now automatically publishes a Poppy file, so merchants don't need to do any extra implementation. Nobody asked you. Nothing in your admin changed. But a file with your store's name on it is now answering questions for software you've never met.
Do I have to do anything?
Not today. Sierra's post presents this as no work for merchants, and nothing in it describes a setting to change. We'd still do one thing this week, which is read it.
The protocol says a company publishes the file at /.well-known/poppy.json on its own domain. That's a public address, so you can type it after your store's domain in a browser. You'll see a block of plain text. It looks technical, but there are only a few parts, and you can read it in two minutes with a coffee.
How the work moves
What happens when a shopper's agent visits
- The agent arrives
Muse looks for the store's Poppy file before it does anything else on the site.
- The file introduces the store
Who the store is, which protocols it speaks and what an agent is allowed to do.
- Shopify's UCP does the shopping
Finding products, filling a cart and checking out.
- The agent asks its person
For certain actions the commerce extension has it check with the shopper first.
- The buyer finishes
The file we read says agents prepare checkouts and the buyer completes the purchase.
You didn't write this file, but you will answer for what it lets an agent do.
What does mine say?
We can only tell you what three live stores' files said on the morning of November 14. We opened the files at allbirds.com, gymshark.com and kith.com. Each came back as a short piece of JSON, and they were the same apart from the store's name and domain. If yours is also a standard Shopify store, we'd expect it to look much the same, but open it and see.
Here's what they said, in plain words. The file names the organization and its domain. It lists one permission an agent can ask for, to manage checkouts, described as letting the agent prepare checkouts as the signed-in customer, with the buyer completing the purchase. It adds that signing in is usually not required, because most stores allow guest checkout, and that if checkout returns a customer_account_required message the agent should sign the buyer in or have them create an account. It also says existing customers may get discounts and other promotions. That permission is tagged as "irreversible" and as involving personal data. Finally, it points to the store's UCP address, the part that handles the shopping.
Two small things stand out. The files say protocol version 0.4, even though Sierra announced version 1.0 the day before. And The Next Web notes that Sierra calls it 1.0 while the specification is still labelled a draft that allows changes which could break existing setups. We don't know whether Shopify will update the files, or what happens to the ones already out there. Look at yours again in a month.
You didn't write this file, but you will answer for what it lets an agent do. If the file tells an agent that signing in may unlock existing-customer discounts, and your discount rules can't tell an agent from the customer, that's your problem on the day it matters, and you'll be the one explaining it to your customer.
What does it change about orders?
According to Sierra's post, the split is simple. UCP, Shopify's Universal Commerce Protocol, handles the shopping: finding products, filling a cart and checking out. Poppy handles what happens before that, when an agent shows up at a store, says who it is and finds out what it's allowed to do. Shopify co-wrote Poppy's commerce extension, which lets an agent shop as a guest or sign in as the customer, and makes the agent ask the customer before certain actions. It also connects to UCP Ask, so a shopper's agent can talk directly to the store's agent.
For you, the practical question isn't whether agents can buy. They could already. It's whether the store behaves sensibly when they do. Place a test order the way an agent would, as a guest, then signed in. We wrote up how to do that for ChatGPT's new wallet in place a test order before your firewall or fraud rules decline one, and the same steps apply here. Discount codes, shipping rules, tax and any fraud check should all be tried on purpose, not discovered by a customer.
Decision guide
Who handles what
| Consideration | Poppy | UCP |
|---|---|---|
| Its job | Introductions and permissions: who is this agent, what may it do | The shopping itself |
| When it acts | Before the shopping starts | During product search, cart and checkout |
| Who set it up on a Shopify store | Published automatically by Shopify | On by default for every Shopify store |
| Where it lives | /.well-known/poppy.json on your domain | /.well-known/ucp on your domain |
Who should own this?
Somebody has to be the person who answers "what may a shopper's agent do in our store?" At a small shop that's the owner. At a bigger one it's split across the person who runs discounts, the one who runs customer accounts and whoever manages the developer or agency. If nobody owns it, the answer will be whatever Shopify's default says.
Give that person three jobs. Open the file on the first of each month and note any change. Keep the guest-checkout and customer-account settings written down, so a change in either is a decision, not an accident. And look at traffic: follow one agent to checkout before you block any explains what you can see.
If you also use apps that edit your checkout, ask which of them can change an order. An agent's introduction means little if three apps can rewrite the page it lands on.
What would we do this week?
Open the file. Write down, in a sentence, what it lets an agent do. Place a guest test order and a signed-in test order. Check that discounts and shipping behave the way you'd want if the shopper were a piece of software. Name an owner. Put a note in the calendar for December.
That's maybe two hours, and it turns a quiet default into something you know about. If you'd like help with the harder questions, such as which rules in your store assume a human and which of your apps would break an agent's checkout, that's our ecommerce work. Talk to us.
Related work: Spin:Market
We build alongside the people doing the work.
Bring us the problem you’re thinking about.