Connecting Superpilot to Salesforce B2C Commerce

Superpilot publishes high-quality landing pages on your storefront so your brand shows up in AI answer engines and search — with no migration or complex integration project.

This guide walks through the setup.

What you'll set up

Two things connect Superpilot to your Salesforce B2C Commerce storefront:

  1. Catalog — read access to your product catalog, so pages are factually accurate.
  2. Reverse-proxy setup — so Superpilot pages live on your storefront's domain, indistinguishable from native pages to shoppers, bots, and AI crawlers.

Step 1 is admin work in B2C Commerce. Step 2 is for your development team.

Step 1 — Connect your catalog

Without a catalog connection, Superpilot can't ground pages in your real product data.

Choose an instance

When you sign into Superpilot using a Salesforce B2C Commerce account with an administrative role, Superpilot automatically discovers your B2C Commerce instances.

In Superpilot, open your environment settings and choose Connect B2C Commerce.

The instance you choose controls what catalogs Superpilot can use:

  • Production is safe to connect, even during testing. Superpilot only reads your catalog — it never writes.
  • Alternatively, connect a non-production instance like staging, development, or sandbox. Ensure it has an up-to-date, representative catalog. A stale or partial catalog means stale or partial pages.

Create the Account Manager API client

Superpilot will ask permission to create an Account Manager API client. The client is a prerequisite to allowing Superpilot to query your catalog.

You can revoke Superpilot's permissions at any time by disabling it in Account Manager.

Optionally, you can grant Superpilot access to Commerce Intelligence Platform data. This allows Superpilot to make grounded recommendations in your site's traffic patterns.

Update OCAPI Shop config

The last piece is an OCAPI Shop config that Superpilot creates for you. Add it to your instance's OCAPI Shop settings.

Superpilot follows the principle of least privilege — the config requests only the high-scale, read-only endpoints Superpilot needs.

What else you can connect

Catalog is the only context that's strictly required. With the catalog connected, Superpilot can create pages informed by your real product data.

From there you can layer in more context as you want: customer reviews, digital asset management, and analytics.

None of those are blockers — you can go to production with catalog alone.

Step 2 — Serve Superpilot pages on your storefront

A Superpilot reverse-proxy client routes a subset of requests on your storefront's domain to Superpilot and returns those responses transparently. The result: Superpilot pages live on your domain — not a separate subdomain — and are indistinguishable from native pages to shoppers, bots, and AI crawlers.

Start with crawlability

Verify your site is reachable by AI crawlers. The whole point of publishing through Superpilot is showing up in answer engines and search — that only works if your path is crawlable.

Pick a URL pattern

Decide where on your site Superpilot pages will live. The conventional pattern is a path prefix like /landing/*, but the choice is yours and depends on how you want the URLs to read.

Choose an integration approach

There are three ways to set up the proxy:

  • CDN integration. Best fit for teams with an existing enterprise CDN. The proxy lives at the edge, so requests never have to round-trip through your origin.
  • Node.js npm package. Best fit for headless storefronts or MRT-based storefronts. Drops into your existing Node app and routes the right subset of requests to Superpilot.
  • B2C cartridge. Best fit for traditional B2C Commerce storefronts that aren't headless. Lives in your B2C codebase with other cartridges.

Superpilot can assist with the setup or hand you code to commit directly — whichever your team prefers.

Security and trust

Superpilot is designed with security in mind. The integration's surface area is intentionally narrow:

  • No PII or payment card data is transferred to Superpilot.
  • Superpilot can be configured so only your CDN or proxy client can reach it.
  • Requests to Salesforce B2C Commerce from Superpilot are verified.

For our full security posture visit our Trust Center.