The central decision is source authority and ownership
Before an import, price list, or channel is built, the organization must name stable identifiers, sources, semantics, owners, consumers, exceptions, reconciliation, and acceptance evidence.
Bounded answer
An extensible catalog foundation, not a governed PIM or commerce operation
Open Mercato records and resolves substantial product, variant, taxonomy, attribute, price, channel, media, unit, translation, search, custom-field, and sales-snapshot information. The organization still owns identifiers, semantics, governance, publication, inventory, compliance, reconciliation, and ongoing stewardship.
- Reviewed
- 2026-07-14
- Revision
- 01911d00e28f44cf484d0b1d04860dcfef5370bf (v0.6.5-1202-g01911d00e)
- Latest public tag
- v0.6.5
- Module and provider versions
- catalog 0.1.0 · @open-mercato/sync-akeneo 0.6.5
Independent editorial guide. Not the product owner, PIM vendor, commerce operator, conformity assessor, tax adviser, or implementation supplier.
Tagged milestones and current source
Tagged changelog milestone
v0.3.3
Catalog product UI, price-kind settings, custom-field fieldsets, variant prices and generation, offer validation, and seeded price kinds.
Public release
v0.4.7
Akeneo PIM synchronization provider announced with integration and data-sync infrastructure.
Public release
v0.6.4
Atomic writes, optimistic locking, tenant and organization read-scope hardening, pricing validation, and tier-resolution fixes.
Latest reviewed public tag
v0.6.5
Public release baseline; catalog module metadata remains version 0.1.0.
Current source
current
Post-tag commercial, compliance, SEO, GTIN, and external-id work remains current-develop evidence. The Akeneo source package is present at version 0.6.5, but deployment fit still requires package, mapping, direction, deletion, media, scheduling, security, and support acceptance.
Catalog lifecycle and capability map
Configurable operating design
Source and system of record
Name authority, direction, identifiers, conflict policy, deletion, and reconciliation.
- Current record or mechanism
- Catalog records can be a master or a governed downstream copy.
- Evidence surface
- record and API
- Release status
- released
- Configuration and policy
- Name authority, direction, identifiers, conflict policy, deletion, and reconciliation.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Data owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- No source-of-record policy is shipped.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Product identity
Define immutable and editable keys, uniqueness scope, merge/split, duplicates, archive, history, and downstream references.
- Current record or mechanism
- Products carry title, SKU, handle, GTIN type/barcode, metadata, status, and current external-id seams.
- Evidence surface
- UI, API, validation, event
- Release status
- mixed released/current
- Configuration and policy
- Define immutable and editable keys, uniqueness scope, merge/split, duplicates, archive, history, and downstream references.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Product-data owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- An identifier field does not create identity governance.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Product type and fulfillment boundary
Choose allowed types and prove entitlement, composition, fulfillment, stock, and publication per type.
- Current record or mechanism
- Types include simple, configurable, virtual, downloadable, bundle, and grouped; current edit UI disables bundle and grouped as coming soon.
- Evidence surface
- type, UI, entity
- Release status
- mixed released/current
- Configuration and policy
- Choose allowed types and prove entitlement, composition, fulfillment, stock, and publication per type.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Product owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Enum values and relations do not prove an operating flow.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Categories and tags
Define purpose, depth, multiple assignment, slug stability, translations, channel mapping, reclassification, orphan and deletion policy.
- Current record or mechanism
- Hierarchical categories, tags, and assignments classify products.
- Evidence surface
- UI, API, command, event
- Release status
- released
- Configuration and policy
- Define purpose, depth, multiple assignment, slug stability, translations, channel mapping, reclassification, orphan and deletion policy.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Taxonomy owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Classification records do not prove governed taxonomy.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Custom attributes and fieldsets
Define semantics, allowed values, units, cardinality, requiredness, locale, validation, source, version, reuse, and consumers.
- Current record or mechanism
- Shared custom-field fieldsets extend product, variant, and price information.
- Evidence surface
- UI injection, API, custom-field engine
- Release status
- released/current
- Configuration and policy
- Define semantics, allowed values, units, cardinality, requiredness, locale, validation, source, version, reuse, and consumers.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Information owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Field presence does not prove meaning or quality.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Available mechanism
Option schemas and variants
Define dimensions, allowed combinations, variant identity, generation, invalid combinations, inheritance, and discontinuation.
- Current record or mechanism
- Option-schema templates define repeatable choices; variants carry option values, identity, pricing, media, physical and custom data.
- Evidence surface
- UI, API, validation, commands, tests
- Release status
- released/current
- Configuration and policy
- Define dimensions, allowed combinations, variant identity, generation, invalid combinations, inheritance, and discontinuation.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Catalog owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Variant records do not prove configuration rules or stock.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Custom project work
Relations, bundles, and groups
Define composition, quantities, substitution, pricing, lifecycle, fulfillment, and historical behavior.
- Current record or mechanism
- Variant relations can represent bundle or grouped relation types.
- Evidence surface
- entity and API boundary
- Release status
- current surface bounded
- Configuration and policy
- Define composition, quantities, substitution, pricing, lifecycle, fulfillment, and historical behavior.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Product and fulfillment owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Current UI says bundle and grouped are coming soon; relation storage is not a bundle workflow.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Media assignments
Define source, rights, file policy, rendition, alt text, locale, channel, ordering, validation, deletion, retention, CDN, and failure owner.
- Current record or mechanism
- Product and offer media use shared attachment and assignment infrastructure.
- Evidence surface
- UI, API, attachment assignment
- Release status
- released/current
- Configuration and policy
- Define source, rights, file policy, rendition, alt text, locale, channel, ordering, validation, deletion, retention, CDN, and failure owner.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Content and legal owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- This is not a complete DAM or publication pipeline.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Units and conversions
Define authoritative units, conversion direction, precision, rounding, effective dates, packaging meaning, and golden cases.
- Current record or mechanism
- Products support base and default sales units, conversion records, rounding controls, reference-unit price display, and quantity limits.
- Evidence surface
- UI, API, validation, tests
- Release status
- released/current
- Configuration and policy
- Define authoritative units, conversion direction, precision, rounding, effective dates, packaging meaning, and golden cases.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Product and commercial owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Units do not move inventory or satisfy legal metrology.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Lifecycle and availability
Define draft, approval, active, discontinued, archive, reactivation, channel visibility, and downstream consequences.
- Current record or mechanism
- Status, lifecycle dates, availability dates, order bounds, shipping and quote-only flags are current data primitives.
- Evidence surface
- UI, API, validation
- Release status
- current-develop sensitive
- Configuration and policy
- Define draft, approval, active, discontinued, archive, reactivation, channel visibility, and downstream consequences.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Lifecycle owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Flags do not publish, reserve, procure, or fulfill.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Commercial and compliance data
Assign competent classifier, evidence source, review frequency, jurisdiction, applicability, change and external validation.
- Current record or mechanism
- Current fields include origin, PKWiU, CN, HS, tax classification, GTU, age, excise, prescription, dangerous goods, lithium, GTIN, shipping and SEO data.
- Evidence surface
- UI, validation, current entities
- Release status
- current develop
- Configuration and policy
- Assign competent classifier, evidence source, review frequency, jurisdiction, applicability, change and external validation.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Legal, tax, safety owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Stored codes do not certify legal, tax, customs, safety, marketplace, GPSR, CLP, KSeF, or sector correctness.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Translations and locale policy
Define source locale, required locales, fallback, terminology, reviewer, completeness, channel delivery, index refresh, and stale handling.
- Current record or mechanism
- Declared translations cover product title/subtitle/description/SEO, variant name, offer content, option schemas, categories, and tags; product CRUD is tested.
- Evidence surface
- translation declaration and tests
- Release status
- current/released infrastructure
- Configuration and policy
- Define source locale, required locales, fallback, terminology, reviewer, completeness, channel delivery, index refresh, and stale handling.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Localization owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Translation storage is not an editorial or publication workflow.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Price kinds and contextual prices
Define hierarchy, conflicts, approvals, margins, net/gross, tax, rounding, contract prices, publication, tie-breaks, and golden cases.
- Current record or mechanism
- Price records cover product, variant, offer, channel, currency, price kind, quantity, dates, user/group/customer contexts; resolver scoring, custom resolvers and hooks exist.
- Evidence surface
- settings UI, API, resolver, events
- Release status
- released/current hardening
- Configuration and policy
- Define hierarchy, conflicts, approvals, margins, net/gross, tax, rounding, contract prices, publication, tie-breaks, and golden cases.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Commercial and finance owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Resolver mechanics are not commercial policy or tax correctness.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Integration required
Sales channels and offers
Define adapter, payload contract, acknowledgement, retry, monitoring, cache/index invalidation, reconciliation, outage and owner.
- Current record or mechanism
- CatalogOffer binds a product to a sales-channel id with channel content, media, metadata, activation, and prices; offer APIs require sales.channels.manage.
- Evidence surface
- UI/API cross-module record
- Release status
- released/current
- Configuration and policy
- Define adapter, payload contract, acknowledgement, retry, monitoring, cache/index invalidation, reconciliation, outage and owner.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Channel owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- An offer row does not publish to storefront, marketplace, POS, or feed.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Available mechanism
Backoffice search and indexing
Define index lag, scope, refresh, deletion, failure, operator expectations, and external search handoff.
- Current record or mechanism
- Catalog search covers products, variants, categories, offers, tags, price kinds, conversions, option schemas, and custom fields.
- Evidence surface
- search index
- Release status
- current source
- Configuration and policy
- Define index lag, scope, refresh, deletion, failure, operator expectations, and external search handoff.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Search owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Not storefront navigation, faceting, ranking, merchandising, recommendations, or SEO publication.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Sales snapshots and later changes
Define historical policy for rename, repricing, discontinuation, media change, broken references, correction, and audit.
- Current record or mechanism
- Sales lines preserve product/variant references, names, descriptions, catalog and UOM snapshots, pricing and tax; current media can be enriched from live catalog.
- Evidence surface
- sales document boundary
- Release status
- released/current
- Configuration and policy
- Define historical policy for rename, repricing, discontinuation, media change, broken references, correction, and audit.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Sales and records owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Live enrichment can differ from persisted commercial snapshots.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Integration required
Imports and synchronization
Define version, direction, mapping, idempotency, order, deletion, media, scheduling, credentials, scope, retry, reconciliation, and support.
- Current record or mechanism
- Catalog APIs, events, bulk routes, data-sync infrastructure, and @open-mercato/sync-akeneo 0.6.5 provide technical surfaces.
- Evidence surface
- API, worker, provider package
- Release status
- v0.4.7 announcement plus current package
- Configuration and policy
- Define version, direction, mapping, idempotency, order, deletion, media, scheduling, credentials, scope, retry, reconciliation, and support.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Integration and data owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Provider source presence does not prove configured fit or production readiness.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Custom project work
Approval and publication
Define view/manage split, price/settings separation, approval authority, segregation, service identities, emergency override, audit, periodic review, publication gate.
- Current record or mechanism
- Permissions, statuses, UI, commands, events, and bulk actions provide inputs.
- Evidence surface
- technical surfaces
- Release status
- project-specific
- Configuration and policy
- Define view/manage split, price/settings separation, approval authority, segregation, service identities, emergency override, audit, periodic review, publication gate.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Governance owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Feature vocabulary and default grants do not establish universal approval workflow.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Exceptions and repair
Define duplicate, conflict, partial bulk, invalid translation/media, stale edit, orphan, replay, manual repair, escalation, and evidence.
- Current record or mechanism
- Validation, optimistic locking, undo/history, events, bulk responses, and APIs provide recovery primitives.
- Evidence surface
- commands, API, tests
- Release status
- released/current
- Configuration and policy
- Define duplicate, conflict, partial bulk, invalid translation/media, stale edit, orphan, replay, manual repair, escalation, and evidence.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Operations owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- A rollback primitive is not an operating exception process.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Custom project work
Reconciliation
Define authoritative side, cadence, tolerance, delta, missing/deleted records, price/channel/snapshot mismatches, repair and sign-off.
- Current record or mechanism
- Identifiers, exports, APIs, events, snapshots, and provider acknowledgements can be compared.
- Evidence surface
- project evidence flow
- Release status
- project-specific
- Configuration and policy
- Define authoritative side, cadence, tolerance, delta, missing/deleted records, price/channel/snapshot mismatches, repair and sign-off.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Data-control owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Events do not prove external state or completeness.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Configurable operating design
Retention and stewardship
Define steward, review cadence, archive, deletion, retention, access, evidence, recovery, upgrade, decommission, and broken-reference policy.
- Current record or mechanism
- Soft deletion, history, exports, scopes, and module events provide lifecycle inputs.
- Evidence surface
- record and operations boundary
- Release status
- deployment-specific
- Configuration and policy
- Define steward, review cadence, archive, deletion, retention, access, evidence, recovery, upgrade, decommission, and broken-reference policy.
- Custom or integration dependency
- Custom code or external integration where the desired outcome exceeds the named surface.
- System of record
- Name the authoritative system and stable human-readable key.
- Upstream and downstream
- Record upstream sources and every downstream sales, channel, search, finance, or operational consumer.
- Owner
- Catalog service owner
- Acceptance evidence
- Use synthetic golden cases, denial and scope checks, conflict/failure cases, reconciliation evidence, and owner sign-off.
- Exception and recovery
- Stop or route to a named repair owner when required evidence, authority, acknowledgement, or source is missing.
- Limitation
- Repository records do not guarantee ongoing data quality or support.
- Source, confidence, date
- catalog source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · high · 2026-07-14
Not established in reviewed evidence
These are separate evidence conclusions, not a fifth capability state and not claims of impossibility for custom, optional, provider, or later code.
- stock on hand and reservation
- warehouse execution
- supplier and procurement management
- manufacturing and BOM planning
- hosted storefront
- marketplace or feed syndication
- complete digital asset management
- universal catalog approval workflow
- product-compliance certification
- complete CPQ
Record, surface, action, and outcome are different
- 1
Stored value and validation
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
- 2
Operator UI
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
- 3
API or command
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
- 4
Event or resolver
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
- 5
Integration action
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
- 6
External acknowledgement
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
- 7
Reconciliation evidence
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
- 8
Business acceptance
Advance only when the next layer has its own source, scope, owner, denial and failure behavior, evidence, and acceptance. Do not jump from a field, enum, event, test, or offer record to publication, stock, compliance, or commercial outcome.
Eight catalog decisions
- 1
Scope and system of record
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
- 2
Identity and taxonomy
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
- 3
Attributes and variants
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
- 4
Media and localization
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
- 5
Units and compliance data
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
- 6
Pricing and channels
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
- 7
Integrations and exceptions
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
- 8
Governance, acceptance, and stewardship
Record the scope, source, stable keys, owner, policy, consumers, exception, reconciliation evidence, acceptance gate, and stop condition.
Three synthetic operating examples
Hypothetical only
Hypothetical service catalog
The loaded blueprint exposes available records, configuration, custom or integration work, owners, one exception, reconciliation evidence, and a stop. It uses abstract labels and no real identifiers, prices, providers, results, or timing.
Hypothetical only
Hypothetical configurable physical item
The loaded blueprint exposes available records, configuration, custom or integration work, owners, one exception, reconciliation evidence, and a stop. It uses abstract labels and no real identifiers, prices, providers, results, or timing.
Hypothetical only
Hypothetical multilingual imported assortment
The loaded blueprint exposes available records, configuration, custom or integration work, owners, one exception, reconciliation evidence, and a stop. It uses abstract labels and no real identifiers, prices, providers, results, or timing.
Local planning tool
Catalog blueprint
Describe safe structural decisions only. Required-field completeness is not a readiness, maturity, compliance, or fit score.
Do not enter real data: Do not enter real product names, SKUs, GTINs, barcodes, prices, margins, tax rates, suppliers, contract terms, classifications, regulated-product data, channel identifiers, credentials, tokenized URLs, production ids, or confidential commercial information.
Privacy: this page does not submit worksheet content, place it in the URL, or store it in cookies.
Acceptance pack
1. product create and edit
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
2. variant create and edit
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
3. category create and hierarchy edit
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
4. duplicate SKU, handle, GTIN, or external key
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
5. invalid option value or combination
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
6. invalid GTIN, unit, conversion, price, or date
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
7. category hierarchy loop and orphan
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
8. missing required translation or media
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
9. permission and organization denial
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
10. stale or concurrent edit
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
11. bulk partial failure
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
12. price conflict and deterministic resolution
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
13. channel publication timeout and rejection
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
14. sync replay, out-of-order event, and deletion
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
15. historical sales snapshot after rename or repricing
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
16. search or index lag and purge
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
17. archive and restore
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
18. export and import integrity
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
19. reconciliation mismatch
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
20. undo and history evidence
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
21. operational recovery and upgrade regression
Use synthetic setup, authorized and denied actors, expected result, prohibited side effects, audit or reconciliation evidence, cleanup, and a named owner.
Stop or choose another starting point
- Stop when a turnkey PIM, inventory, WMS, procurement, manufacturing, or storefront suite is required.
- Stop when no catalog owner exists.
- Stop when identifiers are unstable.
- Stop when the system of record is undefined.
- Stop when attribute or taxonomy growth is uncontrolled.
- Stop when price, tax, or compliance authority is missing.
- Stop when no channel or integration contract exists.
- Stop when reconciliation has no owner.
- Stop when acceptance testing has no owner.
- Stop when a legal requirement is unsupported.
- Stop when ongoing stewardship is unassigned.
Method and limitations
Evidence was refreshed at the exact revision above across module metadata, entities, current operator pages, API routes, product-type UI, translation declarations, package inventory, and core-module inventory. Unlike the preparation snapshot, the current checkout does contain @open-mercato/sync-akeneo 0.6.5; the guide records that source presence while refusing to infer configured direction, coverage, deletion, scheduling, security, support, or production fit.
This is not a PIM, CPQ, inventory, warehouse, manufacturing, procurement, storefront, DAM, compliance, tax, outcome, performance, cost, timing, support, or roadmap guarantee. Data quality, product-type maturity, provider availability, localization workflow, search relevance, and channel delivery require project evidence.
Method, assumptions and limitations
Reviewed 14 July 2026. Product facts were checked against both the public code at the cited repository revision and official documentation. Where documentation and code differ, this guide describes behavior supported by code. Interpretations and recommendations concern implementation work, not product guarantees.
This material is not a quote, audit, certification, or legal, tax, or accounting advice. Edition, enabled modules, configuration, custom code, infrastructure, data, third-party providers, and operating practices affect the outcome.
Primary source collections: code repository, documentation, public releases.