In development · founding partners onboarding from Q4 2026

Every product, every channel, every market — and it tells you what’s wrong before the marketplace does.

TOVIA is an ecommerce operations platform for European brands, distributors and franchise operators. One product master feeds every channel, readiness checks catch the problems before a listing is rejected, and your numbers reconcile across shop, marketplaces and ads.

Built in the EU, for sellers who are not only on Shopify.

Channel readinessSynthetic data
Readiness · Amazon DE, FR, ES2 blocking · 1 to check
  • BlocksDEEPR packaging registration number missingLUCID number required before listing · 41 SKUs affected
  • BlocksFRGPSR responsible person not setEU economic operator required on the offer · 41 SKUs
  • CheckES · es-ESCN code missing on 2 of 6 variantsNeeded per variant for the flat customs duty
  • ReadyDE · de-DETitle within channel limit55 / 200 characters
  • ReadyAllGTIN present and check-digit valid8412345678904
Interface preview, drawn from TOVIA’s own design tokens. The product runs today on a local build against synthetic data; there is no production deployment and no live marketplace connector.

What it costs today

None of this is a software problem until it is only a software problem.

A listing is rejected and nobody notices for four days. Stock sells that isn’t there. At month end the shop says one number, the marketplace says another, the ad platform says a third — and you have to pick one to tell your partner.

On two channels in one country, a person absorbs all of that. On five channels in four countries, nobody can hold it, and the cost stops being time and starts being suppressed listings and decisions made on the wrong number.

What you are doing instead

You already have options, and most of them are free.

A spreadsheet. Your shop admin plus five browser tabs. An agency. One more person in operations. We think TOVIA beats those once you are past roughly500 SKUs on more than two channels in more than one country — and below that, we will tell you so.

  1. 01

    A spreadsheet

    Free, flexible, and the reason most catalogues are correct at all. It stops working when two people edit it and when a channel needs its own version of a field.

  2. 02

    Your shop admin plus five browser tabs

    Fine on two channels. On five, in four countries, nobody can hold what is missing where.

  3. 03

    Each marketplace’s own seller dashboard

    Authoritative for that marketplace and blind to the others. It tells you after the rejection, not before.

  4. 04

    A feed tool or channel manager you already pay for

    Good at pushing data out. Not the place your product master lives, and not where compliance attributes get resolved per market.

  5. 05

    An agency

    Buys you attention and expertise. You keep paying for it, and the knowledge leaves when they do.

  6. 06

    One more person in operations

    The honest comparison, and often the right one. A person absorbs exceptions software cannot describe yet.

  7. 07

    Doing nothing, and fixing it when it breaks

    Genuinely rational below a certain size. Most sellers are below it.

Why TOVIA

Three things, and we will show you all three.

01Builtlocal build · synthetic data

Write it once. Every channel gets its own version.

One canonical product master, with variants and identifiers, feeding N channel dialects, per locale. Title limits, attribute names and required fields differ per channel; you should not have to hold that in your head or in a second spreadsheet.

  • Variants with GTIN, EAN, SKU and MPN
  • Attributes resolved per locale and per channel scope
  • Channel field mapping, generated rather than retyped
Product master → channel dialectsSynthetic data
Product masterSKU CFT-6C-INOXGTIN 8412345678904
  • Shop · es-ESCafetera italiana de acero inoxidable, 6 tazasmaterialacero inoxidable 18/1046 / 255
  • Amazon · de-DEEspressokocher Edelstahl 6 Tassen — induktionsgeeignetbullet_point_1Induktionsgeeignet, spülmaschinenfest55 / 200
  • Marketplace · ro-ROEspressor manual din oțel inoxidabil, 6 ceșticaracteristicicompatibil inducție45 / 120
Interface preview. One SKU, three channels, three locales — the same record, described the way each channel requires.
02Builtlocal build · synthetic data

Find out from us, not from Amazon.

Checks run against each channel’s rules before you submit, so a rejection becomes a task rather than a surprise. Plenty of tools validate a listing. The difference is what is treated as a blocking check andwhere it has to be true.

  • EU compliance attributes as readiness checks rather than as a PDF — EPR registration numbers per market, GPSR responsible person, CN codes per variant (in development)
  • Rule sets per channel, not one generic validation pass
  • Every failing check names the rule and the fix

The compliance checks are in development; the readiness engine they run on is built.

Readiness · before submissionSynthetic data
Readiness · Amazon DE, FR, ES2 blocking · 1 to check
  • BlocksDEEPR packaging registration number missingLUCID number required before listing · 41 SKUs affected
  • BlocksFRGPSR responsible person not setEU economic operator required on the offer · 41 SKUs
  • CheckES · es-ESCN code missing on 2 of 6 variantsNeeded per variant for the flat customs duty
  • ReadyDE · de-DETitle within channel limit55 / 200 characters
  • ReadyAllGTIN present and check-digit valid8412345678904
Interface preview. The two blocking rows are EU compliance attributes rather than content rules — the part a feed tool does not do, and the part still in development.
03Planned

When your shop, your marketplaces and your ads disagree, we show you by how much.

Reconciliation across sources, with an audit trail of what was matched and what was not — so month end produces a number you can defend rather than a number you chose.

This is designed and not built. It is on the roadmap, it is not in the product, and we would rather you knew that now than after a call.

Revenue reconciliationSynthetic data
Revenue reconciliation · July 2026Planned
SourcePeriodNet revenue (EUR)Δ vs shop
ShopJul 2026184 210,40
MarketplacesJul 2026179 884,15−4 326,25
Ads platformJul 2026188 002,90+3 792,50

Every difference opens to the orders and line items that produce it, with an audit trail of what was matched and what was not.

Interface preview of a planned screen. It does not exist in the product today.

What changes for you

Three things stop being your problem.

Written as consequences rather than features, and each one names the capability it rests on and the state that capability is in. Nothing here is a number, because on a pre-launch site every number is invented.

  1. A listing rejected on amazon.de is found by your marketplace manager before submission, not by a customer four days later.

    Marketplace manager

    BuiltReadiness checks before submission

  2. Your catalogue team writes a product once and stops maintaining it in four exports.

    Catalogue / PIM manager

    BuiltChannel dialects and field mapping

  3. At month end the number you give your partner is the reconciled one, with the differences listed rather than averaged away.

    Head of ecommerce operations

    PlannedRevenue reconciliation across shop, marketplaces and ads

What scaling actually costs

From two channels to ten markets, at the same team size.

Not a productivity claim and not a number — a property of the data model. What multiplies when you add a country is the number of rule sets, not the number of catalogues, and rule sets are the thing a system holds well and a person holds badly.

Add a market on the right and a source on the left; the middle does not change. That is the whole argument, and it is why there is no percentage in this section.
  • A new market means a new copy of the catalogue, maintained by whoever opened it.

    A new market is a set of rules applied to the record you already have.

  • A new channel means a new export, a new spreadsheet and a new person watching it.

    A new channel is a projection and a rule set. The record does not fork.

  • Growth adds work proportional to channels × markets, and it lands on the same team.

    Growth adds rule sets. The catalogue work stays where it was.

Why now

Three things changed, and all three land on your product data.

Customs1 July 2026

The €150 duty-free threshold is gone.

A flat customs duty of €3 applies per item on low-value consignments, assessed by tariff classification. The Commission’s own worked example: five T-shirts are one classification and cost €3; one T-shirt and one watch are two, and cost €6. From 1 November 2026, Product Identifiers must be declared. Your CN codes stopped being paperwork and became a per-variant liability.

European Commission · Taxation and Customs Union
Packaging12 August 2026

The Packaging Regulation applies directly in every Member State.

Regulation (EU) 2025/40 replaces the national transpositions of the old directive. Producer registration is per market, and an authorised representative is required where you sell into a country without being established there. Which registration numbers you hold, per market, is now listing data.

Regulation (EU) 2025/40 · EUR-Lex
Product safetySince 13 December 2024

An online offer without the operator details comes down.

Under the General Product Safety Regulation every online offer must carry the manufacturer and the EU responsible person, with warnings in the language of the market. The Commission’s 2025 Safety Gate report records the highest number of alerts on record and a rise in follow-up actions including marketplace delistings.

European Commission press release IP/26/537

We do not use the Digital Product Passport as a reason to act. No delegated act has been adopted for a general product group; the only firm date is the battery passport on 18 February 2027, and it does not apply to most sellers.

What is built, what is not

The whole list, including the parts that are empty.

TOVIA runs today on a local build against synthetic data. There is no production deployment, no live marketplace connector and no customer. Everything below carries the state it is actually in.

Product data

  • BuiltProduct master with variants and identifiersOne canonical record; GTIN, EAN, SKU and MPN on the variant.
  • In developmentAttributes per locale and per channel scopeThe same product, described differently in each place you sell it.
  • BuiltChannel dialects and field mappingEach channel gets its own version, generated rather than retyped.

Readiness and compliance

  • BuiltReadiness checks before submissionChannel rule sets, local/synthetic runtime.
  • In developmentEU compliance attributes as blocking checksEPR registration per market, GPSR responsible person, CN code per variant.
  • In developmentAI review — suggestion only, human approval, audit trailNothing writes to your catalogue without a person approving it.

Operations

  • BuiltAvailability, reservations and order intakeOn-hand per location, reserved, available-to-promise; orders land in worklists. Local runtime.
  • In developmentDocumented import contractOrders, lines, refunds, customers, products. If you can export a CSV, you can start.
  • PlannedLive marketplace connectorsNone is connected today. The import contract comes first, deliberately.
  • PlannedInventory and order syncConnector-fed, after the read-only path has been proven.
  • PlannedRevenue reconciliation across shop, marketplaces and adsDesigned, not built.

Recently shipped

It moves, and you can check.

5 more in development.The whole roadmap and changelog

  1. PIM backbone direction adopted
  2. Product foundation merged
  3. Public website foundation

Founding access

Apply, and we will tell you if it is not for you.

Founding partners get pricing locked, direct access to the team and influence over what gets built next. In exchange we need catalogues that are genuinely hard — several channels, more than one country, real compliance attributes.

TOVIA is pre-launch. It runs today on a local build against synthetic data. There is no production deployment, no live marketplace connector and no customer. Every capability on this page is labelled built, in development or planned, and every screenshot is synthetic.

Who this is for
Brands, distributors and franchise operators past roughly500 SKUs, on more than two channels, in more than one country.
Who this is not for
A single shop on one channel in one country. A spreadsheet is still cheaper and faster, and we will say so.
What happens next
A written reply, not a sequence. If it looks like a fit, a call; if it does not, a sentence explaining why.

Seven fields, one screen

The form is not connected yet. Until it is, emailhello@toviahq.comwith the same information and it reaches the same place.

  1. 01Work emailWhere the reply goes.
  2. 02Company
  3. 03Shop URLSo we can look before the call.
  4. 04Channels you sell onShop, Amazon, eMAG, Kaufland, Bol, Zalando, other.
  5. 05Roughly how many SKUsUnder 500 · 500–5 000 · 5 000–50 000 · more.
  6. 06Countries you sell into
  7. 07Your biggest current painoptionalOptional.

Tell us about your catalogue.

Seven fields. If TOVIA is not the right answer for you yet, you will hear that from us rather than find it out in month three.