UCP is here. Is your delivery promise ready for AI agents?
Anastasiia Starchenko
Two weeks ago, the retail tech world lit up with news of the Universal Commerce Protocol (UCP) — a partnership between Shopify and Google that promises to reshape how AI agents interact with online stores, which followed OpenAI's earlier Agentic Commerce Protocol (ACP).
The initial reactions are over, we're past the hot takes. Now comes the harder part — making sense of what UCP actually means and what consumer brands need to do in 2026 to stay competitive.
The gap between knowing and doing
There's always been a disconnect in retail AI adoption — between industry buzzwords and ground-level strategy, between conceptual potential and operational reality. Awareness of AI in retail has never been higher, but organizational readiness lags far behind the pace of change.
Retail leaders know consumers are already using AI agents to discover, browse, and buy. They know agentic commerce is coming. What they don't always know is how to get there, what infrastructure they need, or which tools will actually work when AI agents ask questions.
What UCP actually changes
With the introduction of UCP, Google and Shopify are accelerating agentic commerce in 2026, and AI agents are truly becoming a structured interface for discovery and shopping. UCP lets AI agents connect with retailers to browse products, manage carts, apply discounts, access loyalty programs, and complete checkout across millions of retailers and billions of transactions. Add to that delivery options, payment methods and rules that differ based on properties of the cart, customer, and region.
Why most brands struggle with delivery
Let’s consider delivery. Just as in traditional browser-based shopping, customers want delivery times they can trust and options they can choose with ease. Brands offering multiple delivery options see an average 27% increase in checkout conversions, yet if a package arrives late, one in three consumers blame the brand, not the shipping carrier.
Now add AI agents into the mix. When they compared 2-3 retailers for the same product, and one can promise delivery by Tuesday while the other says '3-5 business days,' which do you think will get the sale?
When they ask "When will this product arrive?", the question every shopping interaction will include, retailers need to provide an answer the agent can trust. That means dynamic, accurate delivery promises that account for real-time inventory, carrier capacity, customer location, and dozens of other variables.
Introducing Ingrid Delivery Intelligence →
How to get ready for AI and agentic commerce
Ingrid's Delivery API already supports OpenAI's Agentic Commerce Protocol (ACP), which means delivery options from Ingrid can be used directly in AI-powered checkout experiences. It's a step toward universal checkout interoperability where Ingrid powers both traditional and agentic commerce.
Better yet, the checkout dynamically predicts delivery times for every order using AI models trained on both historical and real-time fulfillment data. Because predictions are more precise than static rules, retailers no longer need to add extra days ‘just to be safe’, especially during peak season.
For retailers, this leads to higher checkout conversion, fewer delivery related support cases, and less time spent managing delivery promises. For shoppers, it means knowing when an order will arrive and being able to plan around it.
Building for tomorrow
Agentic commerce is moving fast. UCP just accelerated adoption, and consumer brands need infrastructure that can keep up. The agentic checkout capabilities by Ingrid are ready, and we'll continue adapting our solutions to match the pace of change. As AI agents become the primary shopping interface for millions of consumers, delivery will be a critical factor in every AI-assisted purchasing decision.
Learn more about Ingrid AI →
FAQs
When does the 14-day withdrawal clock start?
For goods, the 14-day period begins the day after the shopper takes physical possession of the order, which in practice means the day after delivery. If multiple items in one order are delivered separately, the clock starts the day after delivery of the last item.
Is the withdrawal the same as returns?
No. The right of withdrawal is a statutory right under EU law; a return is a commercial process. Labels like ‘Return’ or ‘Get a refund’ do not qualify on their own — the withdrawal option has to be clearly and unambiguously labeled as such. Some teams are leaning toward separate flows, others toward one combined flow. Both can work, but only if withdrawal remains a clearly labeled, unobstructed step within it.
Do shoppers have to give a reason to withdraw?
No. Providing a reason is not required by law. Reason fields in the withdrawal flow must be optional and must not delay or block completion of the withdrawal. Designing the interface in a way that pressures shoppers to provide a reason is treated as a manipulative pattern under the directive.
Does this apply to retailers based outside the EU?
Yes — if they sell to EU shoppers. The directive applies to distance contracts with EU shoppers, regardless of where the retailer is established.
Related blog posts
How to choose a multi-carrier delivery platform: a buyer's guide for enterprise e-commerce
Carrier orchestration, checkout impact, delivery accuracy, analytics, and cost control.
EU Right of Withdrawal: Your implementation guide for 2026
How to choose the implementation path that fits your stack and the pitfalls to watch out for
EU Right of Withdrawal: What retailers need to know in 2026
Here's what the rule says, what counts as compliant, and where most teams are stuck.
