The Shift That Changes Everything

Consumer shopping has moved off the storefront. Not partially. Fundamentally.

By early 2026, a growing share of product discovery happens inside Gemini, Google Search's AI Mode, ChatGPT, and Microsoft Copilot. A shopper types "best ergonomic chair under $400 that ships by Thursday" — and an AI agent resolves the query directly, recommending products, comparing prices, and in some cases completing the purchase without the user ever visiting a website.

This is agentic commerce. And it breaks the assumption that your Shopify store, Magento catalog, or WooCommerce instance is the front door to your business. The front door is now a data feed. The decision-maker is an AI.

The question for every e-commerce developer is: who controls the infrastructure that feeds that AI? Goofre's answer: you do.

What's Actually Changing at the Platform Level

Before we explain Goofre, you need to understand exactly what Shopify, Magento, and Google are doing right now — because this changes the developer's market position.

Shopify — January 2026

Shopify launched Agentic Storefronts,¹ a centralized Admin setting that pushes your catalog to AI platforms (Google AI Mode, ChatGPT, Copilot, Gemini). By early 2026, it activates by default. Shopify also co-developed the Universal Commerce Protocol (UCP) with Google — announced January 11, 2026 — enabling AI agents to query and transact with merchant catalogs through a standardized interface. Shopify also launched an Agentic Plan: brands that aren't Shopify stores can list products in the Shopify Catalog to reach AI shopping channels.

Adobe Magento — March 2025

Adobe Commerce as a Cloud Service² went generally available in June 2025 — versionless, fully SaaS, with automatic updates and 250M SKU scale. Their GraphQL API + API Mesh remains the headless data layer for composable builds. But the platform's AI agents are Adobe's, not yours.

Google Merchant Center — Critical API Deadline

GMC now carries dozens of new conversational data attributes — product Q&A, compatible accessories, substitute recommendations — because AI agents use these to answer nuanced queries. New fields like ucpEligibility, loyaltyProgram, and channel now determine whether an AI agent routes intent to your product at all. Missing these doesn't just affect paid ads — it affects organic AI discovery.

What Goofre Is

Goofre is an open-source Agentic Commerce Orchestrator (ACO). It is not a platform. It does not host your store. It does not replace Shopify or Magento. What it does is bypass those platforms as the middleman between your catalog data and Google's commerce stack — and adds an intelligence layer on top.

Goofre makes GMC your PIM, wires every other Google service to that canonical source, and adds an AI reasoning layer across the whole pipeline. GMC is a catalog. Goofre is what keeps that catalog alive.

The Architecture: Layer by Layer

Layer 1: Data Ingestion (Platform Plugins)

Every data source connects to Goofre as a plugin. The contract is the IGoofRePlugin interface. Goofre ships production-ready plugins for Shopify (ShopifyCatalogPlugin — handles variants, metafields, GTIN, loyalty) and Magento 2 (MagentoAdapterPlugin — products, MSI inventory, B2B shared catalogs, company hierarchies, negotiated pricing, requisition lists).

// This is all you write. The rest is orchestrated.
async normalizeProduct(raw: ShopifyProduct): Promise<UCPProduct> {
  return {
    ucpId: `shopify::${raw.id}`,
    title: raw.title,
    price: { amount: parseFloat(raw.price), currency: 'USD' },
    inventory: { available: raw.inventory_quantity, locationId: 'warehouse-1' },
    ucpVersion: '1.1',
    ucpEligibility: true,   // Flagged for AI agent routing
    loyaltyProgram: raw.metafields?.loyalty ?? null,
  };
}

The Magento plugin is the developer's secret weapon for B2B. Magento's account-specific pricing and shared catalogs are notoriously hard to expose to external systems. Goofre normalizes that complexity into UCP events — meaning an AI agent can correctly quote different prices to different buyer accounts from the same catalog.

Layer 2: The Core Engine — UCP Normalization

The SwitchboardOrchestrator is the event bus at the center of everything. Every raw event from every source flows through here and is validated against the UCP v1.1 schema, GTIN-enriched, and emitted as strongly-typed events.

Layer 3: Google Stack Orchestration

This is the core proposition — and what separates Goofre from every other integration tool. Most developers interact with one or two Google services in isolation. Shopify talks to GMC. GA4 sits in a separate tab. Google Ads has its own interface. None of them share data with each other.

• GMC becomes your PIM. Every normalized UCPProduct syncs to GMC via Merchant API v1. GMC is the canonical record — not Shopify, not your ERP. Everything else derives from it.
• GBP updates automatically. When a UCPInventorySnapshot event fires, Goofre updates Google Business Profile with real stock levels — so a Gemini query like "does this store have it in stock?" gets an accurate answer.
• GA4 feeds back into the loop. Behavioral data is ingested as UCPInsight events. The intelligence layer uses these for dynamic pricing recommendations and feed gap identification.
• Google Ads auto-retargets. When a new UCPProduct is added or a UCPCartEvent fires an abandonment, Google Ads campaigns are automatically updated. No manual audience refreshes.
• Performance Max fires from UCP events. A new SKU event can trigger an entire creative pipeline — assets generated and submitted without human intervention.

Layer 4: The Intelligence Layer

Sitting above the normalized UCP data is a set of autonomous management personas, each powered by Gemini 1.5 Pro via the Intelligence API Gateway:

How This Enables Platform-Independent Agentic Commerce

The conventional wisdom is that you need Shopify or Magento to sell online. Goofre challenges that. Here's what a platform actually provides:

• A product catalog (data)
• Inventory management (data)
• Order processing (transaction)
• A storefront (UI)

Goofre handles items 1 and 2 directly — platform-agnostically. It normalizes catalog and inventory data from any source and maintains the canonical version in GMC. For item 3, Goofre integrates with payment systems and handles UCPOrderEvent webhooks regardless of the originating platform. Item 4 — the storefront — is what agentic commerce is actively disrupting. Shopify itself acknowledged this when it launched the Agentic Plan for non-Shopify brands.¹

The developer running Goofre becomes the ACO — the operator who owns the infrastructure, controls the data pipeline, and charges a managed service retainer for maintaining what Google's AI agents trust.

Goofre vs. GMC Alone: The Precise Difference

GMC is the destination. Goofre is the infrastructure that keeps the destination accurate, enriched, and reactive. The specific risk GMC alone cannot address: Inventory Truth Breaks. When an AI agent recommends an out-of-stock product because GMC inventory is 12 hours stale, the agent's trust model penalizes that merchant. Inventory accuracy requires real-time sync — which requires an orchestration layer.

Critical: Migrate to Merchant API v1 Now

This is not a minor version bump. The Merchant API v1 is a fundamental architectural redesign:

• Resource-name strings replace numeric IDs: accounts/123/products/name
• Pricing uses amountMicros (int64) instead of strings
• Mandatory developer registration linking your Google Cloud project to your Merchant Center account
• Write operations require explicit data source parameters
• Native async patterns replace the old custom batching methods

Goofre's GoogleMerchantPlugin v2.0 already runs on Merchant API v1. If you're building on Goofre, you're on the right side of this migration.

The Technical Summary

Goofre is the layer that:

1. 1Ingests raw catalog and commerce events from any platform via validated plugins
2. 2Normalizes all data to UCP v1.1 schema with strict TypeScript types and GTIN validation
3. 3Orchestrates the full Google commerce stack — GMC, GBP, GA4, Google Ads, Performance Max, GSC — wired as a single reactive system
4. 4Reasons over UCP events with Gemini-powered personas to produce actionable UCPInsight signals
5. 5Exposes the full orchestrator as AI-callable tools via the MCP Server — Gemini, Claude, Copilot, any MCP runtime

npx create-goofre-ucp my-commerce-layer
cd my-commerce-layer
cp .env.example .env
npm start

Goofre is open source under BSL 1.1. Converts to Apache 2.0 on March 14, 2030. © 2026 Goofre OS™