Something changed this year, and it's easy to miss.
People have started asking AI assistants to do their shopping for them. Not just "what should I buy Mum?" but "send Mum some roses for Monday, around $90, to her place in Potts Point."
Google, OpenAI and others are publishing ways for an assistant to find products and place orders on someone's behalf. The open one, the one anyone can use, is called the Universal Commerce Protocol (UCP for short). Think of it as a shared language that lets an AI assistant talk to a shop's website.
I've spent 25 years building online shops for independent florists, and my first question with anything like this is always the same: does it help the florist, or does it help someone stand between the florist and their customer?
So we built it the florist's way.
Flowers are not a parcel
Here's the problem with these shopping protocols.
They were designed for parcels. A parcel order needs an address, a courier, and a rough "arrives between Tuesday and Friday".
A flower order needs things a parcel never does:
- The day it arrives. Not "sometime this week". Monday. Her birthday.
- The delivery time. Morning, afternoon, before the funeral starts.
- The card message. Often the most important part of the order.
- A recipient who isn't the buyer. Their name, their phone number, whether we can leave it at the door.
The standard has no field for any of these. An assistant speaking plain UCP simply has nowhere to put "Monday, 9 to 11am, card says Happy Birthday Mum, love Sam".
What we built
In Flower Store In a Box, delivery isn't a bolt-on. Your suburbs, fees, cut-offs, blocked dates and delivery times are part of the platform itself. That meant we could do something better than refuse the order.
An assistant can ask your shop real questions. "Do you deliver to Potts Point on Monday? What's the fee? What times are available? What's the same-day cut-off?" The answers come straight from your own settings: your closures, your blocked dates, your suburb rules, your same-day cut-offs, your weekend ordering rules, and any ranges that need a few days' notice.
It can build the order, priced by your shop. Every price, delivery fee and rule comes from your website, using the same checks your checkout uses. The assistant never makes up a price.
Then your customer finishes on your website. There are two ways this goes:
- The assistant knows the date, the time and the card message. Some assistants can pass these on (we publish a florist add-on to the standard so they can). Your customer goes straight to your payment page with the order filled in, checks it and pays.
- The assistant can't say them. That will be most of them, for now. Your customer lands on your own checkout form, already filled in with everything the assistant gave: their name, email and phone, the recipient's name and phone, the address, any delivery notes. They pick the date and time, write the card, and pay.
The UCP standard actually describes this hand-off. When a shop needs something only the customer can give, it can send them back to the shop's own checkout to finish. We built the florist version of it.
What it looks like
Here's a made-up conversation to show how it feels for your customer. The shop, Bloom Street Florist, is invented for this example.
Every answer in that conversation came from the shop itself: the delivery day, the fee, the times on offer and the price. The assistant never asked for a card number, and the order was only placed when Sam paid on the florist's website.
The assistant never pays
This part matters to me, so I'll say it plainly.
The assistant never pays and never sees card details. Your customer always pays on your website, with your own payment options, after reading the order back.
Nothing is ordered until they do. When they pay, the order arrives in your dashboard like any other order, with a small "AI agent" label so you know where it came from.
Your shop, your customer, your rules
Each Flower Store In a Box website speaks only for itself. There's no directory, no "find a florist" list, and nothing that routes a customer from one florist to another.
If an assistant asks your shop for roses to Potts Point on Monday, it gets your real answer: your fee, your delivery times, your cut-off. If it can't say which time, your checkout asks the customer.
That's the opposite of the order gatherer model. The customer stays yours, the order stays yours, and your delivery rules stay in charge.
Is anyone using this yet?
Honest answer: it's early.
The big platforms' own shopping programs are led from the US, and shops usually have to register with them first. So the near-term win is assistants that read your website's instructions directly. That's assistants like Claude, and custom agents people are already building.
The standard route is ready for the bigger platforms when they arrive in Australia. I'd rather your shop be ready the day they turn up than be scrambling after.
What you need to do
Nothing right now.
We proved it all end to end on our demo site on 9 October, and we're rolling it out shop by shop as sites are updated. We'll let you know when yours is live.
If you're curious, you can already see part of it: add /agents.md to the end of your website address. That's a plain page written for AI assistants, describing what you sell, where and when you deliver, and how to order.
For the curious (the technical bit)
You don't need any of this to run your shop, but if you like to know how it works:
- Every Flower Store In a Box website publishes a UCP profile at
/.well-known/ucp(version 2026-08-25), plus/agents.md,/llms.txt,/llms-full.txtand a machine-readable catalogue. - Assistants talk to
agentic.flowerstoreinabox.com.au, which answers for one florist at a time and passes every order request to that florist's own website to price and check. - Our florist add-on to the standard carries the delivery date, delivery time, pickup time, recipient, card message and how the card is signed.
- The profile and checkout answers are checked against the published UCP schemas, and the whole flow was tested end to end before release.
Quick Summary
- AI assistants are starting to shop for people, using open standards like UCP.
- Those standards were built for parcels, not flowers. There's no place for a delivery date, a delivery time or a card message.
- Flower Store In a Box lets an assistant ask your shop real delivery questions and build an order priced by your shop.
- If the assistant can't give the date, time or card, your customer finishes on your own checkout form, already filled in.
- The assistant never pays. Your customer pays on your website, and the order lands in your dashboard like any other.
- Your shop speaks only for itself. No directories, no middlemen.
People will always want to buy and send flowers. How they ask for them is changing. We want to make sure that, however they ask, the order still comes to you.
