for brands and their agencies
Your products are already here. Someone else wrote them up.
Distributors retype. Resellers guess. Marketplaces copy each other's mistakes. You can put your own catalogue straight, in an afternoon, for nothing.
the difference
One product, two people describing it.
what a reseller sent us
- name
- HAND CREAM 50ml NEW *best price*
- volume
- —
- country
- —
- photograph
- a JPEG of a JPEG, 480 px wide
what you send instead
- name
- Hand Cream, 50 ml
- volume
- 50 ml
- country
- Poland
- photograph
- your own
Nothing is deleted. The reseller's version stays on the record — yours is the one we serve.
two ways in
Type it, or send it. Whichever suits you.
Both do exactly the same thing. Most brands start in the panel and add the API later, when it is worth automating.
In the panel
A form. Paste a barcode, pick the fields you want to state, save. Add a photograph from your own files. Write measurements however the pack does — “1.7 fl oz” is a perfectly good answer.
Over the API
One request per product, against the fields we already publish. Good for a catalogue that changes on its own schedule.
POST /api/v1/brand/products/00000000000017
{ "facts": { "volume": "1.7 fl oz" } }one brand, or all of them
A single label and a group of forty work the same way.
One brand
Claim it, publish, done. Nothing here assumes you are large.
A group
Every label you own on one account, one key, one screen. Nobody keeps forty logins.
An agency
Brands you do not own, on a roster that changes. Recorded as what it is, so when a contract ends the question of what happens to what you said has an answer.
why bother
It costs nothing
Reading the catalogue is what we sell. You improving it is not something to invoice you for.
Nothing waits on us
Send it today and it is in the record today. No approval queue between you and your own data.
You see what happened
Every field you send, and whether it is the value we now serve. Not a form that swallows things.
asked often
- Do we have to prove who we are?
- Once per brand. Send us something that names you — your own site will usually do — and a person checks it. You can publish while you wait, and verifying counts everything you have already sent as the manufacturer's.
- Can anyone tell it came from us?
- No. Your facts go out as “manufacturer” — the same name every brand wears. Nobody can work out which company keeps which brand's data.
- The problem isn't a field.
- A photo of the wrong product, a barcode filed under someone else's brand, a line you stopped making — write it in your own words and a person here reads it.
the whole surface
Five endpoints, and none of them are charged.
Authenticated with a key on your account, exactly like the reading API — and never metered, because reading is what we sell and publishing is you improving it.
- POST /api/v1/brand/products/:gtin
- State facts about your own product. Merged with every other source's; nothing is deleted and yours outranks a reseller's.
- POST /api/v1/brand/products/:gtin/images
- Send a photograph. Served from our own address, never yours.
- GET /api/v1/brand/products
- Everything you have published, and whether the value being served is yours.
- GET /api/v1/brand/analytics
- How often each of your products is asked for. Counts only — never who was asking.
- POST /api/v1/corrections
- The things nobody can state as a value. A person reads every one.
Start with one product.
Tell us who you are and which brands you look after — one or forty, it makes no difference to us. Accounts are opened by hand while the service is young, which takes a day at most.