Skip to contentv0.1.0
PIMgate
PIMgate StudioLIVE

Maintain the products your PIM does not have.

PIMgate Studio is the product editor inside PIMgate. Create products, variants, sets and catalogues, enrich products from your PIM without changing them, or run Studio as your only PIM — with versions, a review workflow and AI suggestions that a person approves.

Supplementary PIMStandalone PIMVersionedMultilingual

06 / 06 · Submit for review — saved as version 3

Illustrative sequence with fictional data (tenant MESSARA).

01 · The gap

Not every product belongs in the main PIM.

The central PIM is built for the core range and run by a small team. Everything around it ends up in spreadsheets, shop back ends and e-mails — without versions, without review and without a way into the portals.

01

Regional products

A country organisation sells products, sets or services the head office does not list. They never reach the main PIM, so they are missing in every portal and feed.

02

External catalogues

Products of suppliers and partners arrive as XLSX or CSV. Loading them into the main PIM is out of scope or takes a project; keeping them in a spreadsheet takes them out of sight.

03

Content the PIM cannot hold

Web texts, SEO fields, extra attributes, translations or images that only one channel needs — the PIM has no field for them, or its owner does not want them there.

04

Small teams without a PIM

A business unit or a smaller company needs structured product data, languages and a catalogue, but not a PIM project that takes a year to introduce.

02 · What Studio is

A second layer on top of your product data.

Studio keeps its own products and its own values in a layer of their own. Data from the PIM stays read-only; Studio adds to it. Every product shown in PIMgate is the merge of both layers, and every value says where it comes from.

Layer 0 · PIM
Products, variants, attributes, dictionaries, assets and categories from the export of your connected PIM. Read-only in Studio; replaced by every new export.
Layer 1 · Studio
Products that exist only in PIMgate, plus local additions to PIM products (overlays). Versioned and kept apart from the export, so a PIM import never overwrites Studio work.
One resolved product
Portals, the API, the shop and exports read the merged product. Each value carries its origin: PIM, local, gap-fill, override, inherited, class default, derived, fallback language or AI-assisted.
Layer model of PIMgate StudioThe PIM layer delivers read-only values, the Studio layer adds local values and fills gaps, and the resolved product combines both with an origin tag on every value.Layer 0 · PIMPressure range0–16 barMaterial—SEO title—Layer 1 · StudioPressure range—MaterialStainless steelSEO titlePT 40 transmitterResolved productPressure range0–16 barPIMMaterialStainless steelGap-fillSEO titlePT 40 transmitterLocal

03 · Three ways to use it

Next to your PIM, instead of a PIM, or as the way out of one.

Studio is the same module in all three cases. What changes is how much of your product data comes from a PIM and how much you maintain in PIMgate.

Next to your PIM

Your PIM stays the master for its range. Studio adds what is missing: regional products, external catalogues, sets and services, plus local values on PIM products. Both flow into one catalogue for portals, API and shop.

  • PIM values stay read-only; a policy per attribute decides what Studio may add
  • Regional and external products live only in PIMgate
  • After every PIM import Studio lists conflicts and matches — nothing is linked automatically
Three ways to use PIMgate Studio — Next to your PIMProducts from the PIM flow in read-only, Studio adds regional and external products on top, and both are merged into one catalogue that feeds portals, the API and the shop.Your PIMRead-onlyPIMgate StudioRegional · externalOne catalogueOrigin on every valuePortalsAPI v1Shop

04 · Structures

Take over your product structure — or define a new one.

Classes, attributes, dictionaries and catalogue trees are data in Studio, not code. You can start from what your PIM already has, build from scratch, or both.

A

Take over from the PIM

Studio reads the latest full export of your PIM and turns it into a starting point you then extend.

Taking over a PIM structureA read-only category tree from the PIM is copied node by node into a Studio catalogue, then two new categories are added that exist only in Studio.PIM · read-onlyStudio catalogueMeasuring instrumentsPressureTemperatureAccessories→ Copy from PIM nodeMeasuring instrumentsPressureTemperatureRegional · CHNewAccessoriesService kitsNewAttributes adoptedClasses suggested
  • Attributes: adopted with code, datatype and languages; a preview shows what is new, updated or stays local
  • Classes: one suggestion per filter template, completed by attributes used by at least 60 % of its products
  • Categories: a PIM category with its subcategories and products copied into your own catalogue
  • Dictionaries: PIM entries read-only, empty languages fillable as gap-fill
B

Define your own

Build the model your range needs, independent of any PIM — and change it later without a schema change.

Defining a new structureA catalogue tree and a product class are built from scratch: categories appear one by one, the class receives its attributes and a variant axis.CatalogueClassWebshop CHValvesBall valvesFittingsValvesDNPNMaterialVariant axis · DNLevels · product → variant
  • Up to three levels per tenant, e.g. product → variant
  • Class tree with inheritance: required, locked, variant axis, default, completeness threshold
  • Attribute types from short text to price, asset and reference, localizable, multi-valued or market-specific
  • Any number of catalogue trees per purpose, with static or rule-based categories

05 · Feature list

Everything Studio does today.

The complete list, grouped by task. Everything listed here is built; anything still planned is not on this list.

LIVE
01

Products and variants

Create and maintain products in PIMgate itself.

  • Four product kinds: standard, bundle, kit with option slots, virtual
  • Up to three levels; variants inherit their parent's values
  • Variant generator from the class's axes and a variant grid with paste from Excel
  • Copy any PIM or Studio product into a new Studio product
  • Immutable PIMgate-ID for every product and variant
  • Article numbers generated, manual, from import or ERP — with a set precedence and aliases
02

Data model

Classes, attributes, dictionaries and relations as configuration.

  • Attribute library with types from short and long text to price, asset and reference
  • Product classes with inheritance, required fields, locks, axes and defaults
  • Completeness threshold per class before a product can be published
  • Start classes suggested from the PIM export
  • Dictionaries with PIM and local entries; search before create
  • Relation types such as accessory or spare part, both directions
03

Next to the PIM

Local data on PIM products, without touching the PIM.

  • Overlays: local additions to PIM products
  • Policy per attribute: locked, gap-fill, local only, override
  • Reconciliation after every PIM import: conflicts, superseded gap-fills, matches
  • Origin shown on every value in the editor
04

Catalogues

Your own trees, with PIM and Studio products side by side.

  • Any number of catalogues with a purpose: navigation, catalogue, website, internal
  • Static categories or rules that keep their products up to date
  • Copy a PIM category with subcategories as a starting point
  • Draft, published, archived — portals and shops see only published catalogues
05

Languages and markets

Multilingual from the first product.

  • Localizable and market-specific attributes
  • Fallback languages, marked as such
  • Derived languages: de-CH from de-DE with «ss», never sent to AI translation
  • Translation suggestions from memory and glossary; XLSX for agencies
06

Media

Images and documents with the same metadata as in the PIM.

  • Upload to the tenant's media library: S3, MinIO or Cloudinary
  • Link a PIM asset without copying it
  • Role, alt text, legends, footnotes and validity per asset
07

Import, bulk edit, export

Many products at once, always with a preview.

  • Import CSV, XLSX, JSON or ePIM XML with mapping, transforms and dry run
  • Saved mapping profiles and XLSX templates with value lists
  • Bulk edit with a before/after preview per product and field
  • Export as ePIM XML, XLSX or JSON with saved profiles
  • Transfer published products to Ibexa DXP
08

AI assist

Suggestions with evidence; a person decides.

  • Fill empty fields from datasheets and related products
  • Every suggestion with confidence and a checked quote as evidence
  • Nothing is written until a person accepts it
  • Monthly budget per tenant and a cost estimate before every run
09

Workflow and history

Every change traceable, every action reversible.

  • Draft → in review → published, with return notes
  • A new version on every save, with before and after
  • Change sets: an import or a bulk edit of 500 products is reverted as one
  • Permissions per task, from viewing to publishing
10

Prices

Price lists for Studio and PIM products.

  • Price lists per market and currency
  • Prices by hand or from CSV and XLSX
  • Set and kit prices by rule: sum minus discount, fixed or manual
11

API and webhooks

Studio data for every system that reads PIMgate.

  • Studio products through API v1 by PIMgate-ID
  • Webhooks when a product is published or a change set is applied

06 · Part of PIMgate

Studio products go wherever PIMgate goes.

Studio is a module of the platform, not a separate tool. What you publish there is available to the other modules of your tenant.

Portals

Add a published catalogue to a portal, and its PIM and Studio products appear there under the portal's permissions.

Portals

Translation

Translation suggestions use the tenant's translation memory and glossary, the same ones as the translation module.

Translation

Commerce

A Studio catalogue can feed a shop catalogue in addition to the PIM categories and filters.

Commerce

API, exports and Ibexa

API v1, webhooks, file exports and the transfer to Ibexa DXP carry Studio products with their PIMgate-ID.

All features

Studio data is primary data: it is stored in your PIMgate tenant, isolated from every other tenant at database level, and leaves it only through the outputs you publish.

EU / CH hostingGDPRrevDSGTenant isolationAppend-only audit

07 · FAQ

Questions about PIMgate Studio

AvailabilityLIVE

See Studio with your own data.

In a demo we load an export of your PIM or a sample of your external catalogue and show the three ways side by side. Pricing will be published in Q1 2027.

LIVE

Translation

Product and content translation with memory, glossary and review.

LIVE

Commerce

A shop on top of your governed product data.

LIVE

Portals

Customer, sales and supplier portals on one catalogue.

Put a gate between your catalog and chaos.