Wevion's unified product catalog at /product-catalog merges Shopify, WooCommerce, and manual products into one canonical model with cross-source matching.

Unified product catalog (cross-source CDM)

Wevion's unified product catalog at /product-catalog consolidates products from every connected commerce source — Shopify, WooCommerce, and manually added products — into a single canonical variant model. It matches the same product across sources, lets you merge or split variants, and links products to campaigns for attribution and AI creative workflows.

Who is this for

Anyone whose products come from more than one source (e.g. a Shopify store plus manually added items) and who wants one clean product list instead of duplicates. This is Wevion's cross-source catalog. For the Meta Business Manager catalog surface used by Meta catalog ads, see meta-109 — a distinct surface.

The canonical model

Each product is a variant master with a canonical title and SKU. Wevion links one or more source variants (from Shopify, WooCommerce, or manual entry) to that master, so the same product appearing in two stores becomes one canonical entry rather than two rows.

Browse and filter unified variants via GET /api/v1/catalog:

Results are cursor-paginated.

Adding manual products (spot products)

Beyond synced commerce sources, you can add products directly. Wevion calls these spot products, and each also creates a matching Creative Hub product context so it's immediately usable in AI creative flows:

You can update a manual spot product's attributes (PATCH /api/v1/catalog/spot-products/:variant_master_id). Products linked to Shopify, WooCommerce, or another external provider are read-only here — edit those at the source.

Creating or importing spot products requires an active subscription.

Cross-source matching

When the same product exists in multiple sources, Wevion generates match suggestions so you can consolidate them:

• List suggestions (GET /api/v1/catalog-v2/match-suggestions) — filter by pending, approved, or rejected, each with candidate/source snapshots and field diffs
• Accept a suggestion — links the source into the canonical variant and clears review state when nothing pending remains
• Reject a suggestion
• Create separate — turns a source variant into its own new canonical product instead of merging
• Auto-resolve safe (bulk) — approves suggestions with confidence ≥ 0.95, with an optional dry-run preview
• Bulk reject — dismiss many at once

Products with unresolved suggestions surface under the needs_review status.

Merging and splitting variants

• Merge (POST /api/v1/variants/merge) — fold one or more loser variants into a winner variant. This runs asynchronously and supports idempotent retry via an idempotency key.
• Split (POST /api/v1/variants/:id/split) — restore a merged variant to active review state and remove aliases so source links can be reassigned manually.
• Field override — pin a specific field value on a variant when sources disagree.

Performance and events

Once products are unified, Wevion ties them to advertising:

• Product performance per campaign — see how each product performs in a given campaign
• Catalog events per variant — the event history for a variant
• Attribution reconciliation snapshots — reconcile attributed orders against catalog data

Integration health (admin)

For operators, the catalog exposes sync progress, integration telemetry and events (with replay), dead-letter handling, and per-catalog feature-flag toggles. These are observability tools around the sync pipeline rather than day-to-day catalog editing.

Common issues

• Duplicate products across stores: resolve the match suggestions — accept to merge, or create-separate to keep them distinct.
• Can't edit a product: it's linked to Shopify/WooCommerce and is read-only here; edit it in the source store. Only manual spot products are editable.
• Product stuck in needs_review: it has pending match suggestions; accept, reject, or create-separate to clear it.
• Wrong merge: use split to restore the variant and reassign source links.
• CSV import ignored rows: check the CSV headers (name, description, image_url, price, external_ref).

FAQ

How is the unified catalog different from the Meta catalog?

Wevion's unified catalog (/product-catalog) merges products from all your commerce sources — Shopify, WooCommerce, and manual entries — into one canonical variant model with cross-source matching. The Meta catalog (/catalogs, see meta-109) manages Meta Business Manager catalogs and product sets used specifically for Meta catalog ads. They're separate surfaces serving different purposes.

What is a spot product?

A spot product is a product you add directly to Wevion's unified catalog rather than syncing from a store. You can create one manually, import it from a product URL (Wevion scrapes it), or bulk-import from a CSV. Each spot product also creates a matching Creative Hub product context so it's ready for AI creative workflows. Spot products are editable; products linked to Shopify or WooCommerce are read-only here.

How does Wevion avoid duplicate products across stores?

When the same product appears in multiple sources, Wevion generates match suggestions with candidate/source snapshots and field diffs. You accept a suggestion to link the sources into one canonical variant, reject it, or create-separate to keep them distinct. A bulk auto-resolve approves high-confidence matches (≥ 0.95), optionally as a dry-run, so most duplicates clear automatically.

Can I undo a variant merge?

Yes. Use split on a merged variant to restore it to active review state and remove its aliases, so its source links can be reassigned manually. Merges themselves run asynchronously and are idempotent on retry, so a repeated merge request for the same winner and losers won't double-apply.

Related articles

• Connect Shopify
• Connect WooCommerce