Common problems and patterns iWeb sees.
How this system fits next to commerce, PIM and ERP.
Questions we get asked.
What is a PIM and when is one worth it?
A Product Information Management system holds the master product model: attributes, media, categorisation, channel rules and enrichment workflow. It is worth introducing when product data quality is limiting growth, integrations or marketplace reach.
Which system owns which part of the product data?
Pricing, stock and accounts in the ERP. Product attributes, media, categorisation and channel rules in the PIM. The commerce platform reads from both and owns the buying experience.
Which PIM does iWeb implement?
Akeneo PIM is iWeb's default for B2B and operational catalogues. Where another PIM is already in place, iWeb integrates with it rather than mandating a switch.
How does PIM connect to ecommerce platforms?
The PIM exposes channel-scoped product data through a governed connector. The storefront reads enriched products from it, while pricing and stock continue to come from the ERP. iWeb has direct experience wiring this boundary into Adobe Commerce, Magento, Shopify Plus and BigCommerce, with marketplaces fed from the same source.
Can PIM feed marketplaces and other channels?
Yes. Marketplaces, print catalogues, sales tools and partner exports each get their own channel-scoped view from the PIM, with validation rules per channel.
When is PIM not worth introducing?
When the catalogue is small, attributes are consistent and only one or two channels are in play. The native commerce platform CMS and attribute model is often enough for that brief.
What are the typical PIM failure modes?
The model is built around the current spreadsheet rather than how the catalogue actually works, or governance never lands so quality drifts again within a year. iWeb names ownership and workflow alongside the technical build.
How does PIM connect to ERP?
Through connectors or middleware. The ERP keeps pricing, stock and accounts. The PIM keeps attributes, media and channel rules. The commerce platform reads from both.
Can iWeb take over an existing PIM?
Yes. The first step is reading the model, the workflows and the integrations in place, then writing down what to keep, stabilise or change. The first month on support is deliberately conservative on change.
How does iWeb decide whether to introduce PIM during a replatform?
By looking at the catalogue model, the channels in scope and the enrichment workflow already in place. Where PIM clearly earns its place it is brought in alongside the replatform; where it does not, iWeb will say so rather than add a system the team has to support.
Who owns the attribute model after launch?
A named owner on the merchant side, with iWeb supporting the model and the channel readiness rules under change control. Attribute models drift without ownership.
How is PIM kept in step with ERP price and stock changes?
It is not. The ERP owns price and stock; PIM owns enriched product data. The storefront reads both through governed boundaries rather than copying commercial data into PIM.