Your range, ready to load into the shop's POS

The shop picks models and downloads a ready file instead of keying in articles by hand. Prices and stock are kept current.

What do we deliver to the shop?

We deliver your product data straight to the retailer, in the format the shop's POS or webshop actually reads. The shop picks models and format and downloads a ready file. Nobody copies fields by hand.

Every article carries what it needs to be sold and found:

Article number and EAN, so the article matches the shop's register and the till's scanner.
A name that works on the receipt and in the webshop.
Purchase price and recommended retail price.
Your stock status.
Images linked to the right article and variant.
Specifications in structured fields: frame size, motor, battery, colour.

Variants get rows of their own. A model in three colours and four sizes is twelve sellable articles in the till, not one product with a note.

How often is the data updated?

Prices and stock are updated continuously from your source, so the figures in the shop do not go stale. An API can be read several times a day, a price list whenever it is replaced.

New model years are added when you release them, and discontinued articles are marked rather than left as sellable. The shop decides what is published.

What do we need from you?

We start from what you have. The more structured it is, the faster it goes, but a price list and an image bank are enough to begin.

InputWhat it is used for
Price list with article numbersThe foundation: article, name, purchase price and recommended retail price
EAN listMatching against the shop's register and the till's scanner
Image bankImages per article and variant, at the resolution you publish
SpecificationsFilter values and product copy: frame, motor, battery, gears, weight
API or portal accessContinuous prices and stock without anyone sending files

If your data is in DST or Veloconnect we start there, so you do not have to deliver the same thing twice.

What goes wrong most often in supplier data?

Most of what we fix is the same thing supplier after supplier. It is not carelessness. The data was built for a different purpose than the shop's till.

ProblemWhat it means in the shopWhat we do
EAN missingThe till cannot scan the article, the webshop cannot match itWe ask for your EAN list and link it to the article numbers
Images without article linkThe shop hunts for the image by handWe match image files to article and variant
Variants without their own rowsSizes and colours cannot be sold or stocked separatelyWe split the model into sellable articles with their own numbers
Categories that do not match the shop'sArticles land in the wrong department, or in noneWe translate your category structure to the shop's
Specifications as free textNo filters on the web, and the text cannot be reusedWe break the values out into fields

Unique product copy per shop instead of the same paragraph on 200 sites

Run your models through our copy engine and every retailer gets its own search-optimised product copy, written from your specifications. Otherwise everyone pastes in the same manufacturer text, and identical text on many sites is exactly what Google filters out; then only one of your retailers is visible.

The shop decides whether the copy goes live at once or is reviewed first. No extra work is required in the shop, and you do not have to write anything new.

Next step

Start at the small end

We suggest a pilot with one shop and one range, so that the whole chain proves itself in live use before anything is rolled out across your network.

A 20-minute call is enough to see whether there is something worth trying.

Frequently asked questions

Does the shop have to take the whole range?
No. The shop picks models, often a handful at a time, and gets only those. What is not taken affects nothing.
Which POS systems and webshops does it work with?
The systems the shops actually use; the format is adapted per system. We have no POS of our own, the data goes into the one the shop already has.
What happens with data that is wrong on our side?
We correct what we can and show you what is missing, usually EAN and image links.
Do we need an API?
No. An API gives continuous prices and stock, but a price list and an image bank are enough to begin. If the data is in DST or Veloconnect we read it there.