The PIM layer your Shopify catalog deserves.
Catalog Hub is the core PIM layer inside Apimio. It gives you one canonical product record per SKU, flexible attributes, and per-store control without duplicating data. All changes sync across connected Shopify stores through Apimio Store Sync.
Catalog Hub at scale
Numbers from production catalogs running on Catalog Hub across furniture, fashion, beauty, and home décor, both connected to Shopify and standalone (pre-migration prep).
The Shopify catalog-data failure pattern
Shopify admin is not a PIM. As catalogs grow across variants, stores, and locales, Shopify’s product data model starts to break. Catalog Hub is the Shopify PIM layer that manages and scales structured product data across multi-store operations.
How catalog data fails today
What Catalog Hub does about it
Duplicated SKUs to fake per-store differences
Need $99 in Store A and €89 in Store B? Shopify alone forces a duplicate SKU per store. Two inventory records, two product pages, two metafield sets. The duplicate fans out across reports, integrations, and forecasts until nobody trusts the numbers.
Per-store override layer (one canonical SKU)
One canonical product record holds the base attributes. A per-store override layer holds the deltas — price, copy framing, visibility, channel rules. Inventory, metafields, and reporting all roll up to the canonical SKU. Different prices per store, same source of truth.
Variant matrices that break Shopify import
Furniture, fashion, and bespoke categories regularly hit Shopify's 100 / 250 / 2,048 variant ceilings. Native CSV import silently truncates. Custom apps choke on GraphQL pagination. Products go live with half their sizes missing — and you find out from the refund queue.
Variant Manager for the full 2,048-variant ceiling
Catalogue Hub's Variant Manager handles the full Shopify ceiling natively — paginated GraphQL writes, bulk variant operations, option set composition. Editing a 200-variant sofa is one operation, not 200. Imports validate the matrix before any write reaches Shopify.
Locales become separate stores
Without proper PIM translation support, multi-language launches mean creating a separate Shopify store per locale — multiplying the maintenance surface, the data duplication, and the inconsistencies. Apimio's Markets-native approach is structurally different.
Markets-native locales without store duplication
Translations are stored as structured fields against the canonical record — not as duplicate products or stores. Shopify Markets ingests them natively. Adding a new locale is a configuration step, not a re-platform.
No audit trail when something goes sideways
A price across 12 stores drops 30% by accident. Who changed it? When? From which integration? In Shopify admin alone the answer is "we don't know." Reconciliation costs days every time it happens — and it always happens.
Per-attribute audit log with rollback
Every write — manual, API, integration, AI — is captured per-attribute: who, when, from where, before/after value. A bad mass-update is one click to roll back. SOC-grade audit trails for finance + B2B compliance reviewers.
The six PIM capabilities, in operational detail
Each capability described here is the actual product behavior in the Apimio dashboard, not marketing-speak. Read the bullets to understand what your data team will use day-to-day.
Canonical product records
One record per SKU holds every attribute, title, description, images, variants, metafields, and tags. Every other Apimio surface reads from this record. No duplication across stores.
- Single record per SKU
- Image + alt text sets
- SEO fields per record
- Custom metafields
Per-store override layer
Need a different price, title, or visibility on Store B? The override layer stores only the delta; the canonical record stays clean. Inventory and reporting always roll up to one SKU.
- Price + currency per store
- Visibility rules
- Per-locale SEO
- Override diff view
Variant manager
Up to 2,048 variants per product, well beyond Shopify's native 100/250 limit. Bulk variant operations, option set composition, and variant-level pricing in one view.
- Up to 2,048 variants
- Bulk variant ops
- Option set composition
Multi-language + locales
Product title, description, and SEO fields per store/locale combination. Built natively for Shopify Markets, no external translation middleware required.
- Title + desc per locale
- Shopify Markets native
- SEO fields per locale
Store sync
Real-time bidirectional sync via GraphQL + webhooks. One edit in Catalog Hub pushes to every connected store in seconds. Each store is a publishing destination, not a separate catalog.
- GraphQL + webhooks
- Multi-store from day one
- Plus Org Admin supported
Bulk price update
Update prices across hundreds of products in minutes using saved filters and rules. The first operational win most teams hit, a half-day task becomes five minutes.
- Saved filter rules
- Multi-store push
- Compare-at-price support
Five steps from install to a source-of-truth PIM
From install to a structured PIM with your catalog inside, ready for Apimio's Store Sync to fan out, Quality Guard to score, and Supplier Bridge to ingest. Most teams complete steps 1–3 the same day.
Install + connect Shopify
Standard Shopify App Store install. OAuth grants the scopes Apimio needs. Standard 30-second flow. No API keys to paste.
First catalog import into Catalog Hub
Apimio reads your existing Shopify products, variants, inventory, images, and metafields. Each SKU becomes a canonical record in Catalog Hub. Variant matrices come through intact (no truncation).
Configure category attribute schema
Extend the attribute schema with category-specific fields (sofa dimensions, beauty INCI, fashion size charts). Mark required vs recommended. Quality Guard's scoring rules read this schema.
Add locales + per-store overrides
Configure Shopify Markets locales, per-locale translations stored against the canonical record. Add per-store overrides where regional pricing or visibility differs. The PIM layer is now complete.
Hand off to Store Sync
Catalog Hub now holds the structured truth. Apimio's Store Sync moves it bidirectionally to every connected Shopify store in real time. Edits in either direction flow through the canonical record.
Outcomes from running a real PIM layer on Shopify
The operational changes teams report within their first month after Catalog Hub becomes the source of truth, separate from the multi-store sync outcomes (those are on the Store Sync page).
SKU duplication stops
The per-store override layer eliminates the need for duplicate SKUs. Inventory, metafields, and reporting consolidate. Reports finally agree across departments because the canonical record is unambiguous.
Variant matrices stop blocking launches
The 250-variant chair that needed custom CSV gymnastics now lives in Variant Manager as one operation. Furniture, fashion, beauty teams get their full catalogs into Shopify without truncation.
Locale launches drop from quarters to days
Adding a new market becomes structured-field updates on canonical records, not a separate Shopify store + duplicate data project. International expansion stops being a re-platform decision.
Audit trail closes the finance trust gap
B2B + finance teams stop chasing "who changed this?" Every write is attributable, with one-click rollback. SOC reviewers see what they need without ticket archaeology.
Category attribute schema unlocks Quality Guard
Once category-specific fields exist (dimensions for sofas, INCI for cosmetics), Quality Guard's scoring + publish gate become operationally meaningful. The PIM layer is the foundation that makes Quality Guard work.
Every other Apimio surface just works
Store Sync moves canonical records to every store. Quality Guard scores against the schema. Supplier Bridge imports validate the schema. Trade Portal publishes the canonical record per dealer. Apimio AI fills attribute gaps. Catalog Hub is the foundation.
Catalog Hub vs Shopify admin and generic PIMs
Three approaches to PIM on Shopify. Catalog Hub is the only one that's both Shopify-native (so Variant Manager hits 2,048 and Markets locales are first-class) and mid-market self-serve (so you ship this week, not next quarter).
Shopify admin alone | Shopify-native PIM Catalog Hub | Akeneo / Salsify | |
|---|---|---|---|
| Canonical product record | |||
| Per-store overrides (no SKU duplication) | |||
| Variant matrix support | Up to 100 / 250 default | Up to 2,048 (full ceiling) | Unlimited (not Shopify-tuned) |
| Markets-native translations | Multi-locale | ||
| Extensible attribute schema | |||
| Per-attribute audit log + rollback | |||
| Standalone PIM (use without Shopify connection) | |||
| Implementation timeline | Day 1 (limited PIM) | Day 1 (30-sec install) | 3–6 months |
Questions about running Catalog Hub as your Shopify PIM
The questions we get most often from operations + data teams evaluating Catalog Hub. Sync mechanics live on the Apimio Store Sync page if those are your questions.
Catalog Hub is the PIM layer, it holds the canonical product records, variant matrices, per-store overrides, locales, attribute schema, and audit log. Store Sync is the movement layer, it bidirectionally syncs the canonical record to every connected Shopify store in real time via GraphQL + webhooks. Catalog Hub holds the data; Store Sync moves it. Most teams adopt both together, but Catalog Hub stands alone as a PIM for catalog-prep work before Shopify migration.
Yes. Teams migrating to Shopify often start with Catalog Hub in "PIM-only mode", importing legacy catalogs via Supplier Bridge, cleaning data with Quality Guard, and structuring records before any Shopify connection. When ready, the Shopify connection activates and Store Sync fans the clean catalog out to the new store. Catalog Hub also acts as your data home of record if you ever leave a Shopify store.
Each canonical product has an override panel per connected Shopify store. Override only the fields that differ; price, compare-at-price, title, description, SEO, visibility, channel rules. The diff view shows side-by-side: canonical value vs override value vs Shopify-live value for that store. One click reverts an override back to canonical. The override layer is data structure; Apimio's Store Sync product is what writes the merged values out to Shopify.
Define custom fields per product category, required, recommended, or optional, with type validation (string, number, JSON, file, reference, enum). Fields can be single-value (weight) or multi-value (materials list, certifications). Schema versioning lets you add new fields without breaking existing records. Imports and AI fills validate against the schema before writing. Quality Guard's scoring rules read this schema to know what "complete" means per category.
Every write captures: actor (which user, API key, AI source, or integration), source path, timestamp, target attribute, before value, after value, and target store (if scoped). One-click rollback per attribute. CSV export for finance reconciliation. Filter by actor, source, store, date range, attribute name. Retention is full-history per workspace, no truncation, no rolling windows.
Quality Guard reads the canonical record and the category attribute schema in Catalog Hub. It scores each product against the category rules and gates publish (via Store Sync) below threshold. Catalog Hub holds the data and the schema; Quality Guard enforces completeness against that schema; Store Sync moves the approved records to your stores.
Catalog Hub is the foundation other Apimio products read from. Store Sync moves canonical records to every connected store. Quality Guard scores against category attributes. Supplier Bridge writes new products through canonical (so scoring + sync apply automatically). Trade Portal publishes the canonical record subset per dealer. Sale Scheduler applies time-bound discounts via the per-store override layer. Apimio AI generates content against canonical attributes. Adopt Catalog Hub first; the others compound from there.
Shopify admin handles a single store excellently. Catalog Hub adds the canonical product layer above it, one record per SKU, real-time bidirectional sync to every connected store, Variant Manager up to 2,048 combinations (Shopify's native limit is 100), Markets locale support, per-store overrides, and full audit logs. The two work together: Shopify admin is the storefront UI; Catalog Hub is the catalog source of truth.
Make Catalog Hub your Shopify PIM
Install Apimio, watch your catalog flow into Catalog Hub within minutes, extend the attribute schema for your categories. The 14-day trial includes the full PIM layer; canonical records, variant manager, per-store overrides, markets locales, audit log + rollback. No credit card required.