The Merida range with images and specifications

We fetch the bikes from Merida product data and create them with model year, specification and image material.

Bikes sell on image and specification

A bike is rarely bought on its name. The customer wants to see the frame, read which drivetrain is fitted and compare two sizes against each other. That is exactly the information that tends to be missing when a bike is created in a hurry.

We fetch Merida product data and bring both the specifications and the image material into your systems.

The model year comes through as a value of its own. That lets you keep two bikes with the same model name apart, which is hard when the information only lives inside the product name.

What each model includes

The source is the supplier's own product data, which means it matches what is actually delivered.

Article numbers and EAN codes per size and colour.
Model year as its own field, not a digit inside the name.
A specification list covering frame, drivetrain and equipment.
Product images at the supplier's resolution.

From model data to product page

Images and specifications are only useful if they end up where the customer sees them.

Sizes and colours are created as variants under the same model.
Specification fields are mapped to your filters on the web.
Images follow the article instead of being uploaded separately.

The result is a product page that stands up to comparison with another bike, and an article register in the POS pointing at the same model.

Model years that can be kept apart.
Specifications that fill the filters on the web.
Images that come with the article from the start.

A customer should be able to compare two bikes without calling you.