Follow the product all the way to the cart

It is possible to spend a lot of time discussing traffic without looking at what awaits the visitor. An imprecise search, two almost identical references or a confusing price can create a question where the journey should have been simple.

My first step would be to choose a few representative products and retrace a customer’s journey. A simple item, a variant, a bundle and a harder-to-find product already give several useful perspectives.

A reference should tell the same story

For each product, I compare the product page, search results, cart and operational data. The aim is to spot contradictions. The name, quantity and information needed to choose should remain understandable at each stage.

In a technical catalogue, I would pay particular attention to the attributes that support a decision. Compatibility mentioned in a description but missing from a filter does not help a customer who starts with that filter.

• A consistent naming rule for references in the same family.
• Variants clearly distinguished from different products.
• Bundles with an explicit quantity and content.
• Decision-making information available where the customer needs it.

Write the rules before making corrections

Fixing a list of products can be quick. Preventing the same problem from returning takes a shared rule. Which information is authoritative? Who can change it? How should an unknown field be handled?

I prefer a short, usable rule to an exhaustive document nobody opens. For example: preserve the source value, flag ambiguities and do not fill technical gaps with guesses. “To be checked” is an operationally useful status.

Import with a way back

For a bulk change, I would organise a small representative batch, a backup and a post-import check. I would compare the changed products against the written rule, then inspect how they actually appear.

Import formats are not interchangeable. Shopify documents the fields and dependencies in its CSV, including how blank values behave in different contexts. The Shopify CSV documentation should support file preparation.

Check what should have stayed the same

A useful check covers both the expected correction and neighbouring information. A variant still being visible, an image remaining attached to the right product or a bundle being correctly identified all deserve a place on the checklist.

A reliable catalogue is more than a cleaned-up catalogue. Its rules can be repeated without relying on one person’s memory.

With that foundation, acquisition work can build on a more consistent experience. That does not promise a specific commercial outcome. It avoids leaving known contradictions in the middle of the customer journey.