Repair a changing breadcrumb before replacing the catalogue

An item's category path can change between page loads even though its memberships are correct. Before replacing the publishing platform, inspect whether the problem lies in the content model, the template's selection rule or a genuine unsupported requirement.

This fictional catalogue item P-42 belongs to both Mounting components and Workshop equipment. The owner wants it discoverable in both, with Mounting components as its primary public breadcrumb.

Reproduce the inconsistent path

The item has one stable URL and two valid category relationships. The template takes the first relationship returned by the database and uses it as the breadcrumb. Because no primary relationship is specified by that query, the displayed path can switch when the retrieval order changes.

The buyer reaches the same item through a saved link but sees Workshop equipment on one visit and Mounting components on another. The page's item facts remain correct. The unstable path makes the catalogue harder to understand without demonstrating that the entire CMS is incapable of supporting it.

Inspect the available model

The platform review finds a supported primary-category field. It can identify one of the item's existing memberships for display while retaining all memberships for discovery. The current template simply does not use it.

The owner compares two options. Replacing the CMS would require migrating the catalogue, documents, URLs and editorial workflow. Repairing the template and completing primary-category values would address the observed failure within the current system.

The selected scope is the repair. That conclusion depends on the demonstrated capability; it is not a general claim that every catalogue platform supports the same feature.

Apply the explicit rule

P-42's primary category is set to Mounting components through the supported editor. The template reads that field and verifies that it remains one of the item's valid memberships. Workshop equipment remains a secondary discovery route.

For records with no selected primary category, the owner approves a neutral Products breadcrumb until the classification is reviewed. The template does not return to choosing an arbitrary first relationship. The unresolved state is visible to editors so it can be completed deliberately.

The item's canonical URL and reference do not change. A display-category decision should not automatically move the item to another address or duplicate the page under every category.

Check both entry routes and the fallback

The reviewer opens P-42 from Mounting components, from Workshop equipment and from its saved direct URL. All three reach the same item and display the approved primary breadcrumb. Both category lists still include P-42 under the owner's discovery rule.

A control item with only one category remains unchanged. Another test item without a primary selection uses the neutral Products path and appears in the editorial review list. The repair has a defined fallback without inventing a classification.

The reviewer then changes the order in which category relationships are returned in the test environment. P-42's breadcrumb remains Mounting components. That check addresses the actual cause rather than relying on one favourable query result.

Record the cost that remains

The template correction does not select the primary category for every existing item. The owner must review items with multiple memberships and decide their intended display path. That editorial work belongs in the estimate.

It also does not resolve unrelated concerns about the CMS, such as unsupported software or missing source access. Those need separate assessment. A successful narrow repair should not become a claim that the whole system is suitable indefinitely.

Make the replacement decision evidence-based

Keep the observed failure, inspected platform capability, selected rule and checked outcomes in the decision record. If a future requirement cannot be represented by the supported model, the replacement question can be reopened with that evidence.

The catalogue service can assess page roles and relationships. The handover checklist shows how an ordinary successor task can expose another repairable boundary without assuming that every difficulty requires migration.