Market: a new integration type — yes, we took a bit of a risk

They say desperate times call for desperate measures. We will not lean all the way into the drama, but here is the honest version: we stepped past the usual “forms, chat, blog” stack and shipped something the product roadmap still labels experimental. The integration has a simple name — Market.

Why Market at all

The idea is to run a catalog of almost anything in Mailoo — not only a “classic” shop, but any structure with products or line items, variants, suppliers, and prices. We wanted it to work for people building a storefront and for teams piping data into a site, internal tools, or reports.

Content-first: we are not leaving that paradigm

For us Mailoo is still about content, and Market is built with the same logic. The integration has traits you do not expect from “pure” inventory: localization as a normal way of working, not a pile of hacks, and detailed, structured descriptions — so catalog entries can be authored and presented as real material for the site, API, and internal workflows, not reduced to short labels with no context.

Localization, descriptions, and price history

Two threads that, for us, hold Market together:

Localization and structured content — content-first in practice: names, descriptions, and related fields live across languages predictably, without “one spreadsheet for everyone” workarounds or manual duplication of entities.
Historical price data — so you see not only “what it costs now” but how the price changed over time: for analytics, supplier conversations, or simple transparency inside the team.

We really like how it is coming together in the product — even with “experiment” stamped on the roadmap.

What this means for you

Market is still experimental: the API and data model may evolve; documentation and use cases will keep growing. If you need a structured catalog with locales, proper descriptions, and price history — it is a good moment to open Integrations and try it in a test project. Feedback matters right now: it will shape what Market becomes next.

Instead of a closing line

Risk is not always a stunt; sometimes it is a deliberate bet that people need one coherent place for data, not “yet another service.” We hope Market is that place — for now, with the “experiment” caveat.

If you have tried it or plan to — tell us what you need first: flows, fields, export, front-end integration. We read it and put it on the backlog.