// Blog
PIMgate Studio: maintain the products your PIM does not have
Regional products, external catalogues, content for one channel: what you gain when that data stops living in spreadsheets and sits next to your PIM — or replaces one.
7 min readPIM Gate teamProduct data
Ask a manufacturer where its product data lives and the answer is "in the PIM". Ask where the Swiss subsidiary keeps its bundles, where the partner's accessory list is, or the SEO copy only the shop needs — and the answer gets longer. A spreadsheet on a shared drive. A shop back end. An email thread from last spring.
That is not a failure of the PIM. A central PIM is built for the core range, run by a small team and strict for good reasons. But everything that has no place there drops out of sight: no versions, no review, no translation — and no way into the portals, feeds and shops where your customers find products.
PIMgate Studio closes that gap. This post is less about what Studio does technically and more about what you gain from it as a customer.
1. No product falls through the cracks
The most common gap is geographic. A subsidiary sells products, bundles or services that headquarters does not carry. They do not belong in the central PIM — so they are missing from every customer portal, every feed and every price list.
In Studio you create those products directly in PIMgate, with their own markets. They sit in the same catalogue as the core range and go out through the same channels. For your customers that means: whoever searches the portal finds the subsidiary's whole offer, not only the part headquarters carries.
The same goes for external catalogues. Products from suppliers and partners arrive as XLSX or CSV. Studio imports them with column mapping, transformations and a dry run before anything is written. A spreadsheet nobody can find becomes a catalogue that appears in the portal, the API and the shop.
2. Your PIM stays as it is
The obvious concern: open a second data source next to the PIM and you get two versions of the truth. Studio is built so that this does not happen.
Studio works in layers. Layer 0 is the data from your PIM export; it is read-only in Studio and every new export replaces it. Layer 1 is the products and values you maintain in PIMgate — Studio products and local additions to PIM products. Portals, API, shop and exports read the merge of both layers.
For you that means two things:
- A PIM import never overwrites Studio work. The layers are separate, even when the PIM delivers a full export every night.
- Every value says where it comes from. PIM, local, gap filler, overridden, inherited, class default — the source is shown on the value. A policy per attribute decides whether Studio may fill gaps, override or only add local fields.
Your PIM team keeps control of the core range. The teams in the markets get a place for what the PIM does not hold — without anyone filing a ticket for a new PIM field.
3. A PIM without a PIM project
Not every organisation has a PIM — and not every one needs one big enough to justify a year-long rollout. A business unit or a smaller company needs structured product data, languages, a catalogue and a way to reach customers.
Studio can hold the whole data model itself. Product classes, attributes, dictionaries, catalogues and languages are settings of your tenant, not code. You define up to three hierarchy levels per tenant — product and variant, for example —, classes with inheritance, required fields, defaults and minimum completeness, and capture products by hand or by import.
What you gain: structured, multilingual product data from the first product — and the same portals, API and shop connection that larger customers with their own PIM use.
4. Take over what exists instead of reinventing it
If you already have a PIM, you do not want to start from zero. Studio starts from what is there:
- Attributes are taken over from the latest full export, with code, data type and languages. A preview shows what is new, what is updated and what stays local.
- Product classes are proposed from the PIM's filter templates, completed with the attributes most products of the class have.
- Categories are copied with their sub-categories and products into catalogues of your own.
- Dictionaries stay read-only for PIM entries; empty languages can be filled as gap fillers.
From there you develop the structure in Studio. This is also the route when a PIM is to be replaced: take over the structure first, then run the products as Studio products step by step — while portals and channels keep running unchanged.
5. Complete faster, without giving up control
Empty fields are the norm for products created outside the PIM. Studio helps fill them — but it does not decide on its own.
The AI in Studio proposes values for empty fields from data sheets and related products, and translations from your tenant's glossary and translation memory. Each proposal shows its confidence and its evidence. Nothing is written until a person accepts it.
Add bulk editing and imports with a preview, a version for every change and a review workflow that can be rolled back. You always see who changed what — and can undo it.
6. Maintain once, appear everywhere
Studio is not a separate tool but a module of the platform. What you publish there is available to every other module of your tenant:
- Portals: add a published catalogue to a customer, sales or supplier portal and its PIM and Studio products appear there — with the portal's permissions.
- Translation: Studio uses the same translation memory and glossary as the translation module. A term is defined once and applies everywhere.
- Commerce: a Studio catalogue can feed a shop catalogue, in addition to the PIM categories.
- API, exports and Ibexa DXP: API v1, webhooks, file exports as ePIM XML, XLSX or JSON and the transfer to Ibexa DXP deliver Studio products with their PIMgate ID.
Only published products go out. What is still being edited stays internal.
What changes for your customers
In the end what counts is what arrives on the other side. A customer who finds the subsidiary's bundle in the portal. A dealer who sees the partner's accessories in the feed. A shop that shows the same product data as the customer portal, because both read from the same catalogue. And a product team that knows there is no spreadsheet left somewhere that nobody can vouch for.
Your Studio data stays your data: it lives in your PIMgate tenant, separated from every other tenant at database level, and leaves it only through the outputs you publish.
The next step
The best way to see Studio is with your own data. In a demo we load an export of your PIM or an extract of your external catalogue and show the ways of using it side by side: next to your PIM, as your PIM, and as a way out of a PIM. Pricing for Studio will be published in Q1 2027.
// Related articles
8 min readMarketing & localization
The translation workflow in PIMgate: what you gain as a customer
Product data and CMS content in one flow: agency, AI and your team with clear roles, parallel orders, review rounds and a documented release. Seven benefits from the customer's side.
translationworkflowailocalization
8 min readIT & architecture
Your portals should outlive your PIM contract
PIM-native portals die with the PIM. A canonical layer plus a migration bridge lets you change the system underneath without touching a single channel.
architecturemigrationitportals