A sequence of visible updates.
Products arrive before categories. Prices update while assortments still reflect yesterday. Every consumer needs reconciliation logic for transitional state.
The Prologus difference
Catalogue releases.Not catalogue mutations.
Most catalogue systems expose a stream of individual changes. Prologus treats the complete state of one source as a release that can be validated, inspected, and published as a single unit.
Discuss your catalogue boundaryOne architectural decision
Consumers should never witness a catalogue changing.
One validated state change.
The complete graph is staged away from readers. A single transaction moves consumers from the preceding revision to the complete new revision.
A catalogue release
Complete in. Coherent out.
The caller provides the complete truth for one source boundary. Prologus owns everything required to turn that snapshot into dependable consumer state.
- 01
Stage
Upload typed records outside the live catalogue. Consumers continue reading the active revision.
- 02
Validate
Resolve references and verify the complete product, taxonomy, organization, price, and offer graph.
- 03
Reconcile
Match source keys, GTINs, and identity keys to durable Prologus masters.
- 04
Activate
Apply the complete revision and switch the active source pointer in one database transaction.
- 05
Serve
Read APIs expose only committed, consumer-ready state—never the transition.
Stable across every release
The catalogue changes. Product identity does not.
A source revision is temporary; the product master is not. Prologus reconciles each source record into a permanent identity that can be shared across feeds, retained through retirement, and reused during restoration.
Supplier
SKU-8472
Retailer NL8712345678901
Retailer BEproduct-1128
Permanent Prologus master
Product UUID
gtin:8712345678901
What this changes
Less recovery logic in every system around the catalogue.
A simple publishing contract.
Send the complete source truth. Omission has explicit retirement semantics, retries are bounded to one source, and failed activation changes nothing live.
A catalogue that is already coherent.
Storefronts and internal products read activated identity, structure, facts, prices, and offers without rebuilding source reconciliation.
A release you can inspect and restore.
Every revision has validation state and history. Restoring a preceding release follows the normal reviewed activation path without duplicating masters.
Deliberately focused
Not another scraper, storefront, ERP, or editorial PIM.
Source systems keep harvesting and normalization. Consumer systems keep presentation and transactions. Prologus owns the release boundary where normalized records become dependable catalogue truth.