TOVIA
English
Apply for founding access

Type to search. Legal placeholders and the admin are not indexed.

In development · founding partners onboarding from Q4 2026

Platform

One operating layer between your product data and every place you sell.

TOVIA is an ecommerce operations platform for European brands, distributors and franchise operators. It holds one canonical product master, generates every channel’s version of it, checks each listing against that channel’s rules before you submit, and — as the platform grows — reconciles what your shop, your marketplaces and your ads each claim happened.

Apply for founding accessEmail the team

Why we call it a control tower — and what that means in practice

A control tower does not fly the planes. It sees all of them at once, knows the rules of every runway, and says “not yet” before something goes wrong.

That is the whole product: one place where every product, channel and market is visible; the rules of each channel encoded; and a check that runs before a rejection, a stock-out or a mismatched number reaches a customer or an authority. Everything below is a concrete piece of that sentence.

Sources on the left, markets on the right, one record in the middle. Reconciliation is drawn dashed because it is planned, not built.
Control Tower · local build
The TOVIA Control Tower screen: a left navigation of modules with their state, a row of counters showing four product master rows, four needing review and zero blocked checks, and a worklist of synthetic operations reviews.
The actual screen, captured from a local build against synthetic data. Every module in the left rail carries the state it is in, and the counters are real reads of a local database — four rows, because four rows is what is there.

The four modules

Four modules, one record underneath them.

Builtlocal build · synthetic data

Product Master

Write it once. Every channel gets its own version.

One canonical record per product; variants carrying GTIN, EAN, SKU and MPN; attributes authored per locale, with channel-scoped values in development. Each channel’s version is generated from the master rather than stored as a second truth.

Explore Product Master
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.
Builtlocal build · synthetic data

Channel Readiness

Find out from us, not from the marketplace.

Channel rule sets run against each listing before submission, and a failing check names the attribute, the rule and the channel. EU compliance attributes as blocking checks are in development — that is the part a feed tool does not do.

Explore Channel Readiness
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 still in development.
Builtlocal build · synthetic data

Inventory & Orders

Stock you can promise, orders you can see.

Availability per location, reservations that hold stock while an order is decided, order intake and worklists an operator can work — on the local runtime today. Connector-fed sync is planned, and none is live.

Explore Inventory & Orders
Availability · reservations · worklistSynthetic data
AvailabilitySKU CFT-6C-INOX
LocationOn handReservedAvailable
Marbella · main1 240861 154
Bucharest · 3PL512144368
Warsaw · overflow96096
Worklist
  • ORD-2026-004182HeldReservation expired before payment cleared
  • ORD-2026-004190ExceptionLine SKU not in the product master
Interface preview. On-hand, reserved and available-to-promise are separate numbers, because a single stock figure is what oversells a listing.
In development

Import & Connectors

If you can export a CSV, you can start.

A documented import contract with staging and preview before commit, first; platform connectors second, deliberately — because a contract works for every platform on day one and a connector works for one.

Explore Import & Connectors
Import · staging and previewSynthetic data
Staging · products.csvNot committed
  • 5 214Parsed
  • 312Create
  • 4 881Update
  • 21Reject
  • row 1 942 · gtin8412345678900Check digit does not match — expected 4
  • row 2 118 · title.ro—Required for a variant sold on a Romanian channel

Preview only. Nothing is written until you commit — and a commit is reversible.

Interface preview of a screen in development. Nothing is written until a person commits, and a commit is reversible.

Designed, not shipped

Two modules that do not have a page yet, and why.

Planned

Reconciliation & Audit

When the shop, the marketplaces and the ad platforms disagree, TOVIA will show you by how much, line by line, with an audit trail of who changed what. Designed, not built.

In development

AI Review

Suggestions only. Nothing writes to your catalogue without a person approving it, and every approval is logged. There is no autonomous AI runtime in TOVIA, and none is planned before lineage, budget controls and audit exist.

Planned, not built. Drawn dashed for the same reason it carries a Planned badge everywhere else on this site.

Architecture

Built for a European mid-market operation, not for a demo

Multi-tenant, tenant-scoped by design
Every query is scoped to your organisation. There is no global fallback path.
Additive migrations only
Your data survives every release.
EU hosting
Provider and region named at launch. [to complete]
Import contract before connectors
Regional and custom platforms are first-class, not an afterthought.
Audit trail
Activity, audit and readiness are separate records, kept separately.

What is built, what is not

The whole list, including the parts that are empty.

One ledger, shown here and on the home page from the same source. TOVIA runs today on a local build against synthetic data: no production deployment, no live marketplace connector, no customer.

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.

FAQ

Questions people actually ask

Is TOVIA a PIM or an order management system?

Both halves of the seam. The product master and the readiness checks are PIM territory; inventory and orders are OMS territory. The point is that they share one record, so a listing that passes every content rule and has no stock is still shown to you as a problem.

Which platforms does it connect to?

Today, none live. The import contract — orders, lines, refunds, customers, products — comes first, so that any platform which can export a file can start; connectors follow. The connector directory lists every one with its state.

Does it replace my shop admin?

No. It sits above the shop, the marketplaces and the ad accounts, and reconciles what they each say. You keep running the shop where you run it now.

Where does my data live?

In the EU, tenant-scoped, with mandatory scoping on every query. The provider and region are named at launch; the Security & Trust page carries the current state of every control, including the ones not yet in place.

Can I try it?

Not self-serve yet. Founding partners get access first, on a real catalogue, with the team on the call.

What changes for you

What the platform changes, module by module.

One outcome per module that exists today, plus the one that does not — labelled, because an outcome resting on a planned capability is a promise and should read as one.

  1. The person who owns the catalogue stops being the integration between four systems.

    Catalogue / PIM manager

    BuiltProduct master with variants and identifiers

  2. A channel's rules live in the system rather than in the head of whoever opened that channel — so that person can take a holiday.

    Marketplace manager

    BuiltReadiness checks before submission

  3. When the shop and the marketplace disagree about what sold, you will be able to see by how much instead of choosing a number to defend.

    Head of ecommerce operations

    PlannedRevenue reconciliation across shop, marketplaces and ads

See it on your own catalogue.

Founding partners get the platform on their own data first, with the team on the call. If TOVIA is not the right answer for you yet, you will hear that from us.

Apply for founding accessEmail the team