Product configurator catalogue change pack — Niall Arnfield
23 September 2026
https://niallarnfield.com/maintaining-product-configurator-catalogues/

The three JSON files are reduced fixtures from the original Soft Edge portfolio product. Models, prices, real stock and customer data are not included. Sage is withdrawn ONLY in an isolated test fixture: the public portfolio catalogue is unchanged. The resolver is the same selection-resolution code used in the demonstration. Run `node test-catalogue-change.mjs` with Node.js to reproduce the checks. It reads local files and does not contact a website or change a catalogue.

This demonstrates identifier resolution and a review flag, not an inventory integration, version archive, order migration or an end-to-end checkout. Passing these checks does not establish that a commercial application is ready to release. Use the ten-row CSV checklist for the wider release and record actual results, including untested dependencies. An empty status is untested, never passed.

Do not overwrite an old order's specification when changing the current catalogue. Choose a retention and repricing policy with the business. Retiring a finish is not permission to substitute another finish in an order. Rollback must account for orders created since deployment; restoring an old file alone is not necessarily safe.

The included code and fixtures may be adapted for project evaluation. They are illustrative, with no warranty of fitness for a production system.
