Built-in PIM. No integration.
Attributes, variants, media, languages and channels live in the same platform as the store. You edit a product in one place and it is published everywhere — with no middleware, no sync jobs and no separate PIM subscription.
The whole catalogue in one view.
The PIM product list
| Item | Artikelnr | Varianter | Komplett | Stock | Status | ||
|---|---|---|---|---|---|---|---|
| Shell Tech Jacka | APP-221 | 12 | 412 | Publicerad | |||
| Merino Bas Långärmad | APP-118 | 18 | 1 240 | Publicerad | |||
| Regnbyxa Fält Pro | WRK-904 | 9 | 86 | Utkast | |||
| Softshell Vest Light | APP-330 | 6 | 208 | Publicerad | |||
| Arbetsjacka Vinter HD | WRK-512 | 14 | 0 | Not finished | |||
| Fleece Halfzip Nord | APP-076 | 10 | 655 | Publicerad |
Completeness is scored per channel, so you see straight away which products are missing fields before they publish.
From supplier file to published product.
Import
Read in supplier files, ERP data or API calls. The mapping is saved as a template and reused on the next run.
Enrich
Fill in attributes, variants, media and copy. Per-channel completeness rules tell you what is missing before publishing.
Publish
One button sends the product to the store, the feeds and the marketplaces with the right fields per channel and language.
Attributes, variants and languages side by side.
The product view
| Attribut | Värde SV | Värde NO | Kanal | Status |
|---|---|---|---|---|
| Material | 3-lagers laminat | 3-lags laminat | All | Klart |
| Vattenpelare | 20 000 mm | 20 000 mm | All | Klart |
| Passform | Regular | Regular | All | Klart |
| Skötselråd | Maskintvätt 40° | — | NO | Saknas |
| Certifiering | bluesign® | bluesign® | All | Klart |
| Ursprungsland | Vietnam | Vietnam | All | Klart |
What the PIM handles.
Capabilities
Your own attribute schema
Your own attributes, types and groups. Text, numbers, lists, colours, files and relations — with no development.
Variants in a matrix
Size, colour and fit in a matrix. Stock and price per variant, shared product data above.
Languages per market
Every field can be translated per language. Missing translations show up as discrepancies, not as blank pages.
Channel-specific fields
The store, a marketplace and a price comparison site need different fields. Completeness rules are set per channel.
Media and files
Images, video, size guides and datasheets on the product — with formats generated automatically for the web.
Relations
Accessories, spare parts, bundles and similar products are linked in the PIM and shown in the store.
Two systems to keep in sync
An extra subscription on top of the platform
An integration somebody has to maintain
A delay between edit and publication
Permissions and history in two places
The product is one and the same record
PIM is included — no extra licence
The edit is published the moment you save
The same roles govern product data and store
One activity log for the whole platform
Questions about PIM.
Common questions
Can we move data in from our current PIM?+
Yes. We import the attribute schema, products, media and translations. The mapping is done once and saved as a template, so a new supplier file can be read in the same way next time.
What happens to products missing a field?+
They are not published in the channel that requires it. The product stays as a draft with the gap visible in the list, so somebody can complete it.
Can the ERP own certain fields?+
Yes. You decide per attribute where the source lives. Fields owned by the ERP are locked in the interface so they cannot be overwritten by hand.
Can we edit several products at once?+
Yes, through bulk attribute editing. You select products in the list, choose the fields and run the change with a preview and the option to roll back.
Is there an API for the PIM?+
Yes. Read and write endpoints for products, attributes and media, plus webhooks when something is published or changed.
Bring an extract of your catalogue.
We load it before the demo and show your own data in the PIM — attributes, variants and completeness per channel.