Agentic Commerce for Magento: 12 Questions Merchants Ask Before Implementing

What is agentic commerce, in practical terms?

It is commerce where an AI agent — not a person clicking through your storefront — performs discovery, cart building, and sometimes the purchase itself, communicating with your store through a defined protocol. The merchant typically remains the merchant of record. The canonical definition is on the agentic commerce protocol definition page.

Do I need to implement this now, or is it too early?

The transactional layer is early and uneven; the discovery layer is not. Product feeds and structured data already affect whether you appear in AI shopping surfaces today, and that same work is the prerequisite for agentic checkout later. The defensible position is to ship the discovery groundwork now and stage the checkout integration as availability expands.

Which should I implement first — ACP or UCP?

The framing assumes you must choose, and you do not. The sequencing argument, with the reasoning behind it, is set out in ACP vs UCP for Magento 2. The key practical point is that most groundwork is shared, so early work is not wasted whichever protocol matters most to your market.

Can AI agents actually place a real order in Magento today?

Yes — this is demonstrable rather than theoretical. An assistant can search a catalogue, build a cart, calculate real shipping, and place an order through the Model Context Protocol, with explicit shopper confirmation before purchase. A live worked example with a real order number is documented in AI agent checkout in Magento 2.

How is MCP different from ACP and UCP?

MCP is a general open standard for connecting assistants to external systems, so one endpoint can serve multiple assistants. ACP and UCP are commerce-specific protocols backed by particular vendors and surfaces. In practice MCP is how you make your store conversational across assistants; ACP and UCP are how you participate in specific vendors’ shopping ecosystems. See the MCP Checkout documentation.

What do I actually have to build?

Four things, in rough dependency order: accurate structured product data, a spec-compliant product feed, protocol-specific manifests or endpoints, and defined policies for returns, shipping, and availability. The first two are the AEO foundations covered in the Magento 2 AEO guide — which is why AEO work is the entry point to agentic commerce rather than a separate track.

Does a product feed get crawled, or do I submit it?

For AI shopping surfaces the model is generally push rather than crawl: the merchant delivers a structured file to the vendor’s endpoint on a schedule, rather than waiting for a crawler to discover pricing and stock. This is why feed accuracy and refresh frequency matter more than page-level SEO for these surfaces.

What happens if the protocol changes after I implement it?

This is the main risk, and it is why sequencing matters. Protocol-specific glue — manifests, endpoints, vendor onboarding — can be invalidated by spec changes. The shared layer underneath, clean schema and accurate feeds, does not. Keeping the ratio weighted toward the shared layer is the practical hedge.

Is my store eligible, or is this only for large retailers?

Eligibility varies by protocol and vendor, and early access has typically been limited by region and merchant type. Readiness is within your control; being live is not entirely. Preparing the feed and data layer costs little and positions you for whenever eligibility opens in your market.

Does agentic commerce mean losing the customer relationship?

Under these protocols the merchant generally remains the merchant of record and retains fulfilment and customer data, but the discovery relationship does shift — the assistant, not your storefront, mediates the first impression. That is the architectural trade-off examined in merchant-controlled AEO.

Does any of this apply to B2B?

Arguably more than to consumer retail, because procurement is repetitive and spec-driven — exactly the work that gets delegated to agents first. Magento’s B2B features are powerful but largely invisible to agents without deliberate configuration. See AI visibility for B2B Magento stores.

Where do I start if I only have limited engineering time?

Start with the audit, not the protocol. Score your current signals with the free AEO self-assessment, fix schema and feed first, and treat protocol integration as a later phase. Every hour spent on the shared layer counts toward whichever protocol turns out to matter for your market.