What was actually wrong.
Product data problems are rarely confined to one system. They show up in catalogue structure, enrichment work, ownership and the effort needed to prepare information for each channel.
Caterforce Group needed an ecommerce platform that could carry trade account ordering, repeat purchase patterns and operational reporting expected by a Food & beverage business.
Product data ownership, attribute structure and channel-specific feed rules were likely sources of operational friction, with brand, editorial and trading teams reconciling the same product record for each retailer.
Trade buyers and account customers needed account-based pricing, repeat ordering and visibility of their own purchase history without friction.
Product information was spread across teams and systems, making catalogue management harder to control and product content harder to reuse with confidence.
Enrichment work needed a clearer workflow, with ownership defined for the people preparing, checking and maintaining product information.
Attributes, product models and category structure needed common rules so the catalogue could stay consistent as products and channels changed.
What happens if it isn't fixed.
When product information is difficult to maintain, teams compensate with manual work. The result is slower onboarding, inconsistent content and less confidence in the catalogue.
When account-based pricing, repeat ordering and purchase-history visibility slip, trade and account customers lose confidence in the site and push work back onto sales and support.
Most relevant to Food & beverage teams running B2B operations and weighing similar platform decisions.
Poor product data makes teams work around the catalogue instead of improving it. Product onboarding slows down, enrichment becomes repeated manual effort and ownership stays unclear.
That creates catalogue drift and inconsistent product presentation. It also weakens confidence in the information each channel receives.
The longer those gaps remain, the harder it becomes to reuse product data across channels without another round of checking, correction and content rework.
Five things, in order.
Delivery is not just a list of features. The order matters, because the wrong sequence can turn technical dependencies into business risk.
- 01Audited the product data shape before changing workflowsMapped the existing product information, catalogue structure and maintenance work so the team could see where inconsistency and repeated effort entered the process.
- 02Defined ownership around product information and enrichmentSet clearer responsibility for creating, enriching, checking and maintaining product information across the teams involved.
- 03Structured attributes, categories and content rulesOrganised product models, attributes and category rules so the catalogue could stay consistent as the range and channel requirements changed.
- 04Connected product data to the systems and channels that needed itDefined how product information moved through Erudus Data, including which system owned each part of the product record.
- 05Put governance in place so the data could keep improvingEstablished maintainable rules for enrichment, content consistency and ongoing data quality instead of treating catalogue preparation as a one-off task.
Systems, one operational truth.
Where this could have gone wrong.
Measurable, not adjectival.
The useful proof is the shape of the product data work, the systems and channels involved and, where available, the numbers recorded from the project.
What the client said.
A client quote should support the case study, not carry it. The project story still needs to stay grounded in the work that was delivered.
Outstanding UK Ecommerce agency to work with. iWeb's leadership has always been attentive to our needs, and their team includes incredibly smart individuals.”
What moved into support.
Product data work continues after the initial structure is in place. Teams still need to enrich records, maintain quality, support new products and prepare information for changing channel needs.
The product data foundation moved into ongoing maintenance and improvement.
Support kept data ownership, enrichment workflows, catalogue structure and channel readiness visible as the product range changed.
That continuity gave teams a clearer basis for resolving data issues and improving product information without claiming an unverified outcome.
Surfaces from the live project.
Screenshots show how governed product information, content and assets are prepared for the channels and teams that use them.
Projects with a similar shape.
A buying group PIM project designed around catalogue scope, product data and governance.
catalogue scope supported by cleaner product governance and faster enrichment workflows.
An allergen data connector built around PIM automation, shared catalogues and product accuracy.
Allergen product data made easier to manage, share and scale across food industry catalogues.
A fresh food labelling connector built around store data, governance and product accuracy.
Fresh food labelling supported by cleaner product data and stronger in-store data governance.