One foundation under your product data, your shop and your administration
Eight modules on one data model. Switch on what you need and leave the rest.
What this is about
Magic Studio is not a separate package but the base 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. Around that you switch on the modules you need — imagery, logo, agents, reporting — and leave the ones you do not use.
What runs in it is not a demonstration model: 74,136 products, 61,693 variants with multilingual copy and 426,573 technique rules, with fifteen e-commerce environments on top. If you want to keep your current ERP, we connect instead of replace. That is not a footnote: it decides whether a project is about migrating or about connecting, and you notice that difference in the first month.
Who we built this for
Distributors, wholesalers and producers who today run a sales environment, a quoting system, an accounting package and a few spreadsheets that know nothing about each other. You notice it in three things: an article that lives in four places and is out of date in three, a quote retyped out of three systems, and a margin nobody can account for afterwards. Magic Studio is for companies that want to fix that by getting the data right once, not by buying a fourth system.
What actually happens
One data model sounds like technology, but you notice it in very ordinary things: who is allowed to change something, how long a second brand takes, and whether a figure can still be explained afterwards. This is what changes in practice once the data is right in one place.
An article exists once
There is one place per field and one owner per field. In most companies the price sits in the ERP, the copy in the web shop and the photo in a folder on a network drive; every change is three actions with two chances of an error.
A price agreement applies everywhere
What you agree with a customer applies in the sales environment, in the quote and on the invoice. Not because it was entered three times, but because it is recorded once.
An order is never retyped
From enquiry to quote to order to purchase order to invoice, on the same lines. Retyping is not only work; it is where most errors start.
A second brand is a configuration
A second brand, a second language or a second country does not cost a second system. The catalogue stays the same; what differs are the settings, the copy and the design.
Rights and roles
Who may see and change what, per site, per brand or per customer. That is what keeps a shared data model workable once more than five people work in it.
Connecting instead of replacing
If you would rather not replace, we connect to the ERP you already have through Magic Connect and the MCP servers in Magic Orb. Your data stays where it belongs.
The tools alongside also work on their own
Magic Logo, the image tools and Flowbuilder sit on the same data model, but work without Magic Studio as well if you only want that one tool.
What it is made of
PIM/DAM
The catalogue with variants, colours, sizes, copy and all the imagery. Eight supplier feeds come in here and are brought into line.
CMS
The pages, copy and company details per brand. Those details also fill the PDFs the system produces, so you change your bank details once and not in eleven templates.
E-commerce
One or more sales environments on the same catalogue, with search, a quote list and customer pricing.
ERP
Quotes, orders, purchasing, stock, technique pricing and invoicing in one chain, with your numbering, discount groups and VAT rules. Sales sits in here.
CRM
Customers, contacts, opportunities and the history of every enquiry, including what happened in the sales environment. See the CRM page for what still needs confirming there.
Magic Orb
Reporting on revenue, receivables, VAT and the document chain. It also holds the MCP servers that give agents access to your data.
Magic Agent
The agent that works enquiries up into draft quotes and enriches product data. The agent prepares, you decide.
Magic Connect
The connections to your ERP, your bookkeeping, your channels and your suppliers.
How it fits with the rest
Everything under Magic Studio uses the same data. That sounds obvious and is not: in most companies the price sits in the ERP, the copy in the shop and the photo in a folder on a network drive. Here there is one place per field and one owner per field. That is why a second brand, a second language or a second country costs a configuration rather than a second system.
The tools alongside — Magic Logo, the image tools, Flowbuilder — sit on the same data model and also work on their own if that is all you want. And if you would rather not replace, we connect: through Magic Connect and the MCP servers in Magic Orb we attach to the ERP you already run. Your data stays where it belongs, and you start with the part you are missing today instead of with a migration.
First a working demo on your own articles, then a conversation
We build a working demo on your own articles, in your own house style, and only then do we talk about working together. You click through it yourself before a penny has been spent on it, and you see what is left of your own data once it is properly in there.
Bring your current article file, or an export of it. That is the shortest route to an honest answer about what does and does not fit — including the part where we say you are better off keeping things as they are.