Coveo Multi-Site & Multi-Brand Architecture: Shared Catalogs, Regional Scoping, and Consolidated Governance

1. The Multi-Site Architectural Spectrum

When architecting multi-brand search, engineering leaders must balance two opposing forces: centralized infrastructure efficiency (avoiding duplicate crawlers, pipelines, and licensing overhead) vs. strict brand isolation (preventing Brand A's products, merchandising rules, or ML trends from spilling into Brand B).

2. End-to-End Multi-Brand Request Routing

In the recommended Single Organization, Partitioned Pipelines pattern, the request flows as follows:

1. Storefront Ingress & Middleware: The client application (e.g. Next.js multi-tenant storefront) attaches the active site context (siteId: "NordicGear-EU") to the request headers.
2. Search Token Binding: The backend authentication service mints an ephemeral JWT search token binding the user to searchHub: "NordicGear-Storefront" and injecting context variables (market: "EU", currency: "EUR").
3. Query Pipeline Dispatcher: Coveo's condition routing engine matches the searchHub condition and routes the request into the brand's dedicated pipeline.
4. Constant Query (cq) Partition Guard: The pipeline injects an immutable constant query:

   cq: @brand == "NordicGear" AND @available_markets CONTAINS "EU" AND @is_active == "true"

   Because cq is evaluated as an in-memory bitset filter before free-text search occurs, it is mathematically impossible for another brand's SKUs to appear in the results.
5. Isolated ML Models: Because Usage Analytics events are stamped with the brand's searchHub, Coveo Machine Learning (ART, DNE, Query Suggestions) trains on brand-isolated behavioral data without cross-brand contamination.

3. Federated Cross-Brand Discovery

While individual brand storefronts require strict isolation, parent company portals or marketplace holding pages frequently require Federated Cross-Brand Discovery:

• Cross-Brand Faceting: The global portal pipeline relaxes the cq: @brand == "..." constraint, exposing an interactive Brand facet widget allowing shoppers to filter or compare products across sister brands.
• Unified Cartridge Slotting: Editorial campaigns can feature curated hero cartridges containing selected items from multiple brands side-by-side.
• Permission Partitioning: If certain brands sell restricted items (e.g. medical devices or hazardous materials), Early Binding security providers ensure that only authorized buyers view restricted catalog entries.

4. Multi-Tenant Middleware Implementation Example

Below is a production Next.js middleware and token generation handler illustrating how to dynamically configure Coveo requests for multi-site deployments:

// lib/coveoMultiSiteToken.ts
import axios from "axios";

interface MultiSiteContext {
  host: string;
  userRole?: string;
}

const BRAND_CONFIG: Record<string, { brandId: string; searchHub: string; market: string }> = {
  "nordicgear.com": { brandId: "NordicGear", searchHub: "NordicGear-Storefront", market: "US" },
  "nordicgear.de":  { brandId: "NordicGear", searchHub: "NordicGear-Storefront", market: "EU" },
  "alpinetrek.com": { brandId: "AlpineTrek", searchHub: "AlpineTrek-Storefront", market: "US" },
  "holdingcorp.com": { brandId: "ALL", searchHub: "Global-Federated-Search", market: "GLOBAL" }
};

export async function generateSiteScopedSearchToken(ctx: MultiSiteContext) {
  const config = BRAND_CONFIG[ctx.host] || BRAND_CONFIG["holdingcorp.com"];
  const COVEO_API_KEY = process.env.COVEO_SEARCH_TOKEN_CREATOR_KEY;
  const COVEO_ORG_ID = process.env.COVEO_ORGANIZATION_ID;

  // Mint ephemeral token valid for 15 minutes
  const tokenPayload = {
    userId: "anonymous_shopper",
    searchHub: config.searchHub,
    // Context attributes drive QPL routing and localized ranking
    context: {
      brand: config.brandId,
      market: config.market,
      userRole: ctx.userRole || "retail"
    }
  };

  const response = await axios.post(
    `https://${COVEO_ORG_ID}.org.coveo.com/rest/search/v2/token`,
    tokenPayload,
    {
      headers: {
        "Authorization": `Bearer ${COVEO_API_KEY}`,
        "Content-Type": "application/json"
      }
    }
  );

  return {
    token: response.data.token,
    searchHub: config.searchHub,
    brandId: config.brandId
  };
}

5. Governance & Telemetry Best Practices