Your catalogue is the product. Every channel is just an opinion about it.

You own the product data, and every marketplace wants it differently. TOVIA holds the canonical record, generates each channel’s version of it, and tells you what would be rejected before you submit.

Apply for founding access Email the team

Three shapes we recognise

Not case studies — we have no customers to write one about.

Own shop, Amazon EU, one marketplace per country

The same 4,000 SKUs described four ways, each with its own required attributes and title limit. The shop is correct, the marketplaces are approximately correct, and nobody can say which one is wrong until something is suppressed.

A second country, and the compliance surface doubles

An EPR registration per market, a responsible person per product, a CN code per variant — facts with a legal meaning and a different answer in each country. They belong on the variant, not in a folder of PDFs.

A campaign month, and three numbers

The shop says one thing, the marketplace another, the ad platform a third. You pick one to defend. Reconciliation is the module that fixes this, and it is planned rather than built — we would rather you knew that now.

Which modules apply

All four, and each with its state.

Product MasterBuiltlocal build · synthetic data
One record, variants with identifiers, attributes per locale, channel dialects generated.
Channel ReadinessBuiltlocal build · synthetic data
Rule sets per channel, run before submission. Compliance attributes as blocking checks are in development.
Inventory & OrdersBuiltlocal build · synthetic data
Availability per location and reservations on the local runtime; connector-fed sync is planned.
Import & ConnectorsIn development
The documented import contract — five entities, staging and preview, reversible commits.

FAQ

Two objections worth making

We already have a feed tool. Why would we add this?

A feed tool validates a format and pushes it. It does not hold the canonical record, it does not know your stock, and it does not treat an EPR registration number as a blocking condition. If your problem is “the feed failed”, a feed tool is enough. If your problem is “which version of this product is true”, it is not.

You have no live connectors. What can we actually do today?

Load a real catalogue through the import contract, hold it as one record, generate each channel's version of it, and run readiness checks before you submit — on a local runtime, against your data, with the team. What you cannot do is sync stock to a marketplace automatically. That is planned, and it is not live.

Bring the catalogue you argue about.

The one with the duplicate GTIN and the attribute nobody has maintained since 2024. That is the one worth looking at together.

Apply for founding access Email the team