Stop Building Storefronts. Start Orchestrating.

Your Magento store is not disappearing. But the storefront is. AI agents — Gemini, ChatGPT, Claude — are becoming the new product discovery layer. Goofre is the infrastructure that keeps your clients' products visible, trusted, and purchasable inside those agents. And as a Magento developer, you can own that entire layer for your clients.

The Problem: Google AI Mode Just Ate Your Storefront

If you've been watching what's happening to product discovery over the last 18 months, you already feel this. Consumers are asking Gemini "what's the best air fryer under £80" and getting a curated, ranked answer — with a "Buy" button — without ever visiting a website.

The products that appear in that answer aren't there by accident. They're there because their data is UCP-compliant — normalised into the format that Google's AI agents natively understand.

Here's the structural problem for your Magento clients: Getting UCP-compliant is becoming a platform checkbox. Shopify ships it natively. BigCommerce acquired Feedonomics for it. Adobe has a 4-phase roadmap. But staying trusted by AI agents is not a one-time event. It's an operational job:

Goofre is the operations layer that keeps your clients inside the AI's trust radius, every day, automatically. And Magento 2 / Adobe Commerce is one of the first platforms to get a full native adapter.

What Goofre Actually Is (Skip the Marketing)

Goofre is an open-source orchestration engine — BSL 1.1, zero platform lock-in — that wires together the entire Google commerce stack (GMC, GA4, GSC, GBP, Google Ads) into a single, event-driven intelligence layer.

It does not replace Magento. It does not replace Google Merchant Center. It sits between them and does three things:

1. Normalises raw Magento data into UCP types — UCPProduct, UCPInventorySnapshot, UCPOrderEvent, UCPCartEvent — the schema that AI agents consume natively

2. Validates that schema is conformant before it reaches GMC (catching the GTIN mismatches, stock inconsistencies, and pricing errors that cause feed disapprovals)

3. Exposes that normalised data as callable tools to AI agents via UCP, MCP, and the A2A negotiation layer

The result: your clients' Magento catalogues become a first-class citizen inside Gemini, Claude, and Copilot — not as scraped web pages, but as live, structured, queryable commerce data.

The Architecture

The four columns above are the entire mental model:

Core Components You Need to Know

The Magento Integration Path

> Key constraint to understand first: Goofre never writes to Magento. It reads via REST API and translates to UCP. Magento remains the merchant of record for all commerce data.

Step 1 — Bootstrap in 2 Minutes

npx create-goofre-ucp my-client-aco

cd my-client-aco

cp .env.example .env

npm start

Your admin dashboard is live at http://localhost:3000/admin. It ships with a zero-dependency SQLite database, mock data, and MockPaymentGateway so you can build and test the entire Agentic Commerce pipeline locally — no live GMC account needed.

Or deploy directly to production:

Step 2 — Register the Magento Adapter

import { SwitchboardOrchestrator } from '@goofre/core-engine';

import { MagentoAdapterPlugin } from '@goofre/plugins';

const orchestrator = new SwitchboardOrchestrator();

orchestrator.registerPlugin(new MagentoAdapterPlugin({

baseUrl: process.env.MAGENTO_BASE_URL, // e.g. 'https://shop.client.com'

accessToken: process.env.MAGENTO_ACCESS_TOKEN, // Magento Integration Token

storeViewCode: 'default',

webhookSecret: process.env.MAGENTO_WEBHOOK_SECRET, // For HMAC validation

}));

The adapter handles:

Step 3 — Subscribe to Normalised Outputs

// Every Magento product change becomes a UCP event

orchestrator.on('product', (product: UCPProduct) => {

// product.ucpId: 'magento::12345'

// product.gtin: validated GS1 checksum via GTINEnricher

// product.price, inventory, status — all normalised

console.log('Synced to GMC:', product.title);

});

orchestrator.on('inventory', (snapshot: UCPInventorySnapshot) => {

// snapshot.localInventory — per-store BOPIS availability (RFC #375)

// Perfect for clients with physical locations doing click & collect

});

orchestrator.on('order', (order: UCPOrderEvent) => {

// order.idempotencyKey — prevents double-processing on webhook retries

});

Step 4 — Validate GTIN Before GMC Sync

This is the step 90% of Magento integrations skip, and it's why feeds silently fail:

import { GTINEnricher } from '@goofre/core-engine';

const enricher = new GTINEnricher();

// Before pushing any product to GMC:

const result = enricher.validate('0614141000036'); // GS1 checksum

// result.valid: true | false

// result.format: 'GTIN-13'

// result.error: 'Invalid checksum'

Goofre's CI pipeline runs 26 UCP conformance tests (mirrored from the official Universal-Commerce-Protocol/conformance baseline) that catch schema errors before they reach production.

Step 5 — Expose to AI Agents via MCP Server

// Add to Claude Desktop / Copilot config

{

"mcpServers": {

"goofre-client": {

"command": "node",

"args": ["./node_modules/@goofre/mcp-server/dist/index.js"],

"env": { "GOOFRE_PLUGIN_ID": "magento" }

}

}

}

This exposes 6 callable tools to any MCP-compatible AI:

The A2A Layer: When a Gemini Agent Queries Your Client's Stock

This is where the architecture becomes genuinely new. The A2AListener lets any upstream AI agent — a Gemini shopping agent, a procurement bot, a voice assistant — submit a high-level CommerceIntent and receive a structured response:

import { A2AListener, SwitchboardOrchestrator } from '@goofre/core-engine';

const orchestrator = new SwitchboardOrchestrator();

const listener = new A2AListener(orchestrator, {

defaultPluginId: 'magento',

});

// A Gemini Shopping Agent asks: "Is this available for pickup in Brooklyn?"

const response = await listener.receiveIntent({

intentId: 'gemini-query-abc-123', // idempotent — safe to retry

intentType: 'check_inventory',

agentId: 'gemini-shopping-agent-v2',

payload: { productId: 'SKU-001', locationId: 'store-brooklyn' },

constraints: {

requirePickupAvailable: true, // BOPIS required

requiredChannel: 'local',

maxPrice: { amount: 80, currency: 'GBP' },

},

});

// response.status: 'fulfilled'

// response.payload: normalised UCPInventorySnapshot

// response.alternatives: fallback options when constraints can't be met

// response.reason: why partial/rejected (shown to the AI, not the user)

The Merchant PWA: What Your Client Actually Sees

Goofre Enterprise ships with a mobile-first command centre (the Merchant PWA) — a React Progressive Web App that your client installs on their phone and uses as their live commerce intelligence dashboard.

No GMC login. No GA4 report. One screen, one voice interface, one decision queue.

The Dashboard — 2×2 Bento Grid

The Four Tiles Explained

Each tile is a department entry point — tapping it reveals that department's action queue:

The tiles pull live data from reactiveSync.hydrateFromOpenSource() — Goofre's event-driven hydration engine that syncs intelligence from the OS. Alert badges on each tile are real counts, not placeholder numbers.

The Action Card — The Core UX Pattern

Every intelligence output in Goofre surfaces as an Action Card. This is the most important design decision in the entire PWA:

The reasoning model is explicit: every AI recommendation shows why it was generated — the data signal (GSC index parity violation, GA4 churn threshold, A2A constraint failure), the theory (which heuristic fired), and the recommended decision. Your client is never just clicking Approve on a black box.

The Voice Orb — Six States

The Voice Orb floats at the bottom centre of the PWA. It's the merchant's primary interaction method — tap to ask, listen to the briefing:

States:

idle → Purple gradient, ring-4 ring-white

listening → Scale-110, emerald ring, animated waveform bars

processing → Loader2 spinner, processing state

speaking → Scale-110, emerald, "Zara responding..." label above orb

sentinel → Scale-105, amber ring, pulse-amber animation (always-on mode)

error → Scale-105, red-500 background, error message badge

In Sentinel Mode (hold the eye icon), Goofre runs a persistent background listener — the orb pulses amber and the system proactively speaks alerts when new triage items arrive, without the merchant needing to tap.

B2B Mode — One Config Change

The entire PWA is dual-mode. For wholesale/manufacturer clients:

// B2C retail merchant (default)