One canonical schema
All sources land in one open product model. Each attribute knows its data type, unit, language behaviour and the markets it applies to.
FEATURE · DATA MODEL & QUALITY GATELIVE
Nothing incomplete passes the gate.
Every record is mapped onto one canonical schema and checked against your rules before any portal, shop or feed sees it. Complete records pass. Questionable ones wait for review. Wrong ones stop — with the exact field that failed.
CANONICAL OPEN SCHEMARULES PER CHANNEL & MARKETFIELD-LEVEL ERRORS
01 · What it does
One model. Clear rules. A view for every audience.
Rules at the gate
Validation and completeness are checked centrally, per channel and market — not rebuilt in every shop, feed and portal.
Views per audience
Catalog views select exactly the products, markets and languages a portal or consumer should get — by hand, by rule, or both.
02 · Canonical open schema
One product model that every consumer can rely on.
PIM Gate keeps one canonical record per product, independent of the systems that fed it. The schema is open: documented, readable in full through the API and exportable at any time — your data model does not get locked into PIM Gate. Every attribute carries metadata that tells downstream systems how to treat it: what type it is, which unit it uses, whether it is translated, and in which markets it is valid.
- Canonical open product schemaLIVE
- Attribute metadata: data type, unit, locale behaviour, market flagsLIVE
- Product, hierarchy and media viewers for every recordLIVE
- Source recorded per attribute, including machine-translated values
Canonical open schema
One product model that every consumer can rely on.
03 · Validation rules
Rules you define once, enforced for every channel.
Validation rules describe what a record must satisfy before it may leave the gate: which fields are required for which channel, market and language, which data types and units are allowed, which values come from a controlled list, and which formats must hold. Each record ends in one of three states — passed, held for review, or rejected — and rejections name the exact field and reason, so the fix happens once, at the source.
- Required fields per channel, market and languageLIVE
- Type, unit, format and value-list checksLIVE
- Three outcomes: PASSED · HELD FOR REVIEW · REJECTED with field-level errors
- The same rules power the Supplier Portal's live validation → Supplier Portal2026
Validation rules
Rules you define once, enforced for every channel.
04 · Completeness
See what's missing — per product, language and channel.
Completeness is the share of required attributes that are filled for a given channel and locale. Because requirements differ — a wholesale feed needs other fields than a customer portal — PIM Gate calculates it per combination and names the missing attributes. Teams fix what blocks a channel instead of chasing a single average.
- Completeness per product × locale × channel — LIVE
- Missing attributes listed by name
- Catalog-wide data-quality scoring dashboardROADMAP
Completeness
See what's missing — per product, language and channel.
05 · Markets & languages
Fallbacks you define, instead of empty fields.
A Swiss portal should show Swiss German where it exists and German where it doesn't — never a blank field. PIM Gate resolves every attribute through a fallback chain you configure per market, such as de-CH → de-DE → en-GB. Market flags decide which products, prices and attributes exist in which country at all, so a CH customer never sees an EUR price.
- Multi-language and multi-market data with configurable fallback chainsLIVE
- Resolution per attribute, not per product
- Market flags on attributes and products (e.g. DE · AT · CH)
- Languages and markets selectable per portalLIVE
Markets & languages
Fallbacks you define, instead of empty fields.
06 · Catalog views
One catalog, as many curated views as you need.
A catalog view is a defined subset of your catalog: the product groups, markets and languages a portal, customer group or API consumer should get. Build it by rule so it stays current as the catalog changes, pin or exclude individual products by hand, and save the combination as a template your team can reuse.
- Catalog selections by hand and by ruleLIVE
- Saved filter templatesLIVE
- Markets and languages per portalLIVE
- Views feed portals, API tokens and exports alike → Roles & entitlements
Catalog views
One catalog, as many curated views as you need.
07 · On the roadmap
What we're building next into the model.
- Inheritance Attributes, texts and assets inherited from product families and parent products, with overrides where a variant differs.ROADMAP
- Per-tenant schema extension Add your own attributes to the canonical schema for your tenant, without affecting other tenants.
- Data-quality scoring dashboard Scores and trends across the whole catalog, by product group, market and channel.ROADMAP
On the roadmap
What we're building next into the model.
See the roadmap →
08 · Specifications
Data model & quality gate at a glance.
| Spec | Value | Status |
|---|---|---|
| Product model | CANONICAL OPEN SCHEMA | LIVE |
| Attribute metadata | TYPE · UNIT · LOCALE · MARKET FLAGS | LIVE |
| Viewers | PRODUCT · HIERARCHY · MEDIA | LIVE |
| Languages & markets | MULTI-LOCALE · MULTI-MARKET · FALLBACK CHAINS | LIVE |
| Catalog views | MANUAL + RULES · SAVED TEMPLATES | LIVE |
| Validation rules | REQUIRED · TYPE · UNIT · FORMAT · VALUE LIST | LIVE |
| Validation outcomes | PASSED · HELD · REJECTED (FIELD-LEVEL) | LIVE |
| Completeness | PER PRODUCT × LOCALE × CHANNEL | LIVE |
| Data-quality scoring dashboard | — | ROADMAP |
| Per-tenant schema extension | — | ROADMAP |
| Attribute / text / asset inheritance | — | ROADMAP |
| ETIM classification & BMEcat output | ETIM · BMECAT 2005 | 2026 |
09 · Works with
Standards the model speaks.
GTIN / EAN-13ISO language & country codesETIM · MODULE · 2026BMEcat 2005 · MODULE · 2026schema.org/Product · OPEN DATA · 2026Digital Product Passport · MODULE · 2026