SAFETY
Making things up is not a risk we limit.
It is a locked door.
The first thing a cold prospect thinks is: that thing is going to put something in my shop that does not belong there. Fair enough. So here is exactly what we do and do not touch.
pa_materiaal = "rubber" | source: stands in your title | conf: 0.92 | 2026-08-20 09:14
THE HARD LINE
Six fields we never touch.
price
This field lives in your inventory system, not with us. We do not read it and we do not write it.
stock
Same reason. A wrong stock level costs an order, not visibility.
lead time
Depends on your agreements with suppliers. There is no way for us to know that.
mpn
The manufacturer number is there or it is not. We never derive it and never write it.
warranty
A legal promise. Nobody invents those, and neither does a model.
gtin and ean
We do not write those. We have no manufacturer database to look one up in and never invent one, so it stays empty. An invented barcode leads to rejection in Merchant Center and, if repeated, to suspension of the whole account.
THE THRESHOLD
Below 0.85 nothing goes live.
Every derived value gets a number saying how direct the source is. Whatever stays under it does not go to your shop but to the review list, with the source attached so you can decide in ten seconds.
MATERIAL
0.92
rubber
stands literally in your title
Goes live
MATERIAL
0.78
polyester
stands in your description, not in the title
To the review list
GTIN
empty
no match
not in the feed, not in the database
Stays empty
0.85 is fixed and the same for every shop we run. That is the only reason the number means anything: a live value cleared the same bar everywhere. What you can move is the review list; every yes there puts values live that the threshold alone would have held back.
PROVENANCE
Every field carries where it came from.
Four kinds, no more.
01
From your title
A word or a measurement standing in the product name. Three quarters comes from here.
02
From your description
The same, one sentence further in, and held to a higher bar.
03
Yours
What was already there and what we left alone. This is the largest group.
That provenance does not only sit in our log but next to the value in the dashboard as well, so a colleague who knows nothing about it can see why it says what it says.
ROLLING BACK
What is ours is marked as ours. That is why rolling back still works months later.
For every value we record where we read it, when, and with what confidence. Before we put anything back we ask the shop what stands there now: if you changed the field yourself in the meantime, your value stays and we do not touch it.
Roll back per field
One value you do not like? It goes back to what was there, without touching the rest.
Roll back per pass
Undoing a whole run is possible too, with one button, months afterwards.
Switching tools
New theme or feed tool? The value sits in the attribute itself, so it travels with the product and not with the theme.
BEFORE ANYTHING GOES LIVE
1
The first pass writes to draft
Nothing is publicly visible.
2
You approve a sample
Two hundred products, in half an hour.
3
Only then does the rest go live
Or you flip it yourself.
Until that moment your shop is exactly as it was.
YOUR DATA
What we see, where it sits,
and what happens if you stop.
Access
An API key with only the permissions needed for products. No admin login, no access to orders or customers.
Where it sits
Processing and storage inside the EU. No catalogue goes to a party outside the EU.
What we keep
The log per field, so rolling back stays possible. Nothing else you do not already have yourself.
If you stop
Everything we wrote sits in your shop and stays there. We delete the log on request, within thirty days.
There is a data processing agreement and we sign it before the key is created, not afterwards.