One platform, eight modules and sixteen tools that also work on their own
Magic Studio is the product. Inside it you switch on the modules you need and leave the rest. The tools alongside it also work without Magic Studio.
Magic Studio is the product, the modules are inside it
Magic Studio is not a package next to your existing systems but the foundation the rest stands on. Product data, e-commerce, quotes, orders, purchasing, invoicing and customer records all run on the same data. An article exists once. A price agreement applies everywhere. An order never has to be retyped.
Inside it are eight modules. They are not products alongside Magic Studio but parts of it: one data model, one login, one permission model. What runs in it is not a demonstration set: 74,136 products, 61,693 variants with multilingual copy and 426,573 technique rules, with fifteen live sales environments on top.
If you want to keep your current ERP, we do not replace it — we connect to it. Further down this page you can read how that works.
The eight modules of Magic Studio — one data model
They are listed in the order in which data moves through your business: from the catalogue to sales, from sales to administration, and from administration to the overview.
Sixteen tools that also work without Magic Studio
Alongside Magic Studio sit the tools. They connect to the same data model, but they are usable on their own: if you only need a logo tool, only want your imagery in order, or only want a portal for your dealers, you do not have to take the whole platform. Each tool has its own environment and its own connection, which is why it can sit next to a system you already run.
What they do share is the way they hang together. Magic Logo calculates with the print areas that Image Editor and PDF Editor supply. Magic Clean and Magic Background turn supplier imagery into imagery you can use. Flowbuilder records what an agent may do, and Widget Server and Meta Server carry that conversation to your site and to WhatsApp.
Would you rather not replace? Then we connect
Not every client wants to replace everything, and there is no need to. If you have an ERP that stays, an accounting package your accountant is used to, or a webshop that cannot go yet, we connect to it through Magic Connect. Every connection is a flow with steps, conditions and error handling, with a log per run. Per field we record who owns it, because two systems both claiming the same data is the most common cause of stock that does not add up.
For agents that access runs through the MCP servers in Magic Orb: the standardised layer through which an agent may request and report, with read and write rights recorded per connection. That is how an agent can pull a report from your own ERP in plain language without that ERP having to move. A new system means a new flow — no rebuild and no migration.
What is in the systems today
These figures were measured in the live databases on 20 September 2026; they are not estimates. We put them here because a product data platform cannot be judged on promises but on volume: a catalogue of tens of thousands of articles with variants, languages and print data behaves differently from a demo set of twenty products.
What is not here is missing on purpose. For some parts we do not know the number of live environments firmly enough to publish it, and you are better served by no figure than by one that is wrong.
We build a working demo on your own articles first
You pick one module or one tool to start with; we put your own articles in it, in your own branding. Only then do we talk about working together, because a demo on your data says more than a presentation about ours.
Not sure where to start? Send one supplier feed or one quote from last week and we will show you what is left of it once it has been through the chain.