Skip to content

A relaunch does not fix product data by itself

A new shop can inherit incorrect variant values. Follow an item from its verified reference through import to the resulting order.

Lena Fischer2 min read
Product card with a headphone image, a highlighted detail with a question mark and a blue shopping-cart bar.

A shop relaunch can improve navigation and product selection. Which physical item a variant represents, however, must be established through reliable data. If an incorrect value is copied unchanged, the new interface can display it incorrectly too.

Concrete product cases therefore belong in early planning and acceptance checks. An attractive design alone does not show whether the selected variant remains linked to the correct item through to the order.

An incorrect value travels too

A hypothetical retailer sells two bottle variants. Verified product information is compared with an export. The last column shows the value that an unchanged transfer without additional checks would display.

Item identifier

Verified contents

Contents in export

Value displayed unchanged

F-500

500 ml

500 ml

500 ml

F-750

750 ml

500 ml

500 ml

The larger bottle would consequently have an incorrect contents declaration. Depending on its data model and validation rules, the target shop might reject the import instead. This example makes no claim about a particular platform's import behaviour.

A new photograph or different font cannot resolve this contradiction. In the example, the responsible person must check the exported value against the verified product reference and correct the faulty source. Changing only the display in the new shop can allow the next import to introduce the error again.

The error can also arise during transfer

If the source value is correct but the import program reads the wrong column, the mapping needs correcting. Rewriting the maintained product data wholesale would then address the wrong part of the process.

Follow the same item through source, export, transfer rule and destination. Record the step at which the value first differs. The item identifier, variant attributes and unit must describe the same goods. A successful file transfer does not prove this business-level agreement.

What acceptance checks should show

Before the full migration, check a small, deliberately chosen set: a simple item, a variant and a previously troublesome case. Open the selection in the target shop, add the intended variant to the cart and inspect the resulting test order. Do the identifier and the goods ordered still match?

A relaunch can introduce these rules and checks. Its benefit then becomes visible through verifiable product cases. A general promise of higher sales or fewer returns cannot be derived from the new interface alone.

Sources

Written by

  • Lena FischerEditor for E-CommerceLena Fischer looks after the e-commerce articles at ASES. She writes about shop systems and how they connect to other applications, and explains the technical processes behind online retail.

Follow ASES

Read more

All articles

E-Commerce with ASES

Online shops, marketplaces and B2B portals