Where Stibo Systems fits in the catalogue estate
How Stibo fits next to commerce, ERP and the wider data estate.
Questions we get asked.
Does iWeb implement Stibo Systems?
iWeb most often implements PIM on Akeneo. Where merchants already run Stibo for enterprise MDM and PIM, iWeb works alongside it on integration with commerce, ERP and channel surfaces.
Where does MDM end and PIM begin?
MDM holds the wider master data picture across entities (customer, supplier, product, location). PIM owns catalogue truth. Keeping the responsibilities separate is the design work, not the licence decision.
Is Stibo the right shape for our scale?
For enterprise estates with multi-domain master data needs, yes. For mid-market merchants Akeneo or Salsify usually fit more cleanly. iWeb will give an honest read rather than upselling.
Where does pricing live with Stibo?
In the ERP. Stibo holds descriptive and master data; commercial data stays with the ERP so finance numbers continue to tie out.
Can iWeb help us decide between Stibo and an alternative?
Yes. A short, paid platform decision read covers operating model fit, multi-domain need and total cost across five years rather than vendor advocacy.
Does iWeb claim a vendor partnership here?
iWeb is a UK ecommerce agency that supports merchants who run this vendor as part of the wider estate. Partnership status is held by the client where required; iWeb works alongside that arrangement honestly.
Where does this vendor sit relative to the commerce platform?
As a peer of the estate, not a parallel commerce stack. The boundary with commerce, PIM and ERP is named and versioned; the storefront reads what the vendor produces through governed APIs.
How is the vendor integration boundary kept observable?
Versioned APIs, governed contracts and observable telemetry. The boundary is one of the most important architecture decisions in an estate and is written down rather than implied.
Where does pricing and stock live?
In the ERP, not in this vendor. The vendor reads from the ERP boundary; commercial data stays with the system of record so finance numbers tie out.
Can iWeb take over an existing implementation?
Yes, where the brief fits. iWeb will give a senior, written read on what is working, what needs remediation and what is honestly fixable, and the first month on support is deliberately conservative on change.
How does iWeb decide whether this vendor earns its place?
Against operating model fit, integration risk and total cost across five years, not against a feature list. The read is written down with trade-offs rather than assumed.
How is governance handled around this vendor?
Approval workflows, decision logs, audit trails and named owners on both sides of the boundary so changes are reviewable and reversible rather than buried.