Catalog reconciliation
Compare incoming supplier truth with the catalog you already govern.
Measure what a delivery would add, change or remove before commit, while respecting source precedence, manual overrides and existing product state.
Current catalog8,104 productsv14
+ 43 new~ 701 changed− 742 missing
Proposed statereview requiredmass deletion guard
Before commit
Look at the blast radius, not just the rows that parsed.
A technically valid file can still be operationally dangerous. Reconciliation compares normalized delivery effects against current catalog state.
New records
Identify products and relationships that would be created.
Changed fields
Classify canonical field, attribute and compatibility changes.
Missing source rows
Separate ordinary disappearance from suspicious mass deletion.
Protected state
Respect customer overrides and other state that should not be overwritten by a later source delivery.
Controlled reversal
Rollback is safe only when later changes have not invalidated the snapshot.
Import snapshots and integrity checks support rollback where it remains valid rather than presenting an unconditional undo button.
- Restore prior product graph state from the import snapshot.
- Block automatic rollback when later manual changes make reversal unsafe.
- Resume interrupted rollback safely when partial restoration already occurred.
- Keep source and product locks from fighting active workers.
v14Current catalogpost-import
v13Import snapshotrollback target
v12Manual reviewhistorical
Rollback allowed only if current integrity checks pass
Reconciliation starts with change