Context
In the fashion retailer's PIM workflow, product data flows to an external sales channel. It's critical that product card, price, stock level, and integration status are clear before errors impact publication.
At the intersection of PIM, connector, and external marketplace were ambiguous areas: which SKU is parent, which is item, what fields are needed for price and stock, where users see integration errors.
Business challenge
The category manager owns card accuracy, the e-commerce team owns product availability in sales channels, the PIM owner owns data rules. If an error remains in the technical layer, business sees only the outcome: product didn't publish or published incorrectly.
Without clear statuses, the team wastes time investigating where the issue lies: in product attributes, price, stock, classification, or message routing.
Challenge
The goal was to eliminate ambiguity in identifiers, reduce unnecessary fields in price and stock flows, and return statuses and errors where business users work with them: in the PIM workflow.
Business goal: increase predictability of product publication and quickly identify why a product card fails to reach the sales channel.
Review a similar project with an architect
Solution
The team separated parent and item SKU roles, clarified rules for prices, stock, and classification, and agreed which statuses the connector should return to PIM.
Validated ambiguous areas through limited pilot sends to prevent scaling errors across the entire product flow.
- Separated the meaning of two SKU identifiers.
- Defined the minimal dataset for prices and stock levels.
- Returned statuses and errors to the user-facing PIM workflow.
Metrics and business goals
Readiness metrics should answer: can business manage products in sales channels without technical investigation for each failure.
- success rate of product publications and card updates;
- number of exchange errors in identifiers, price, stock, and classification;
- diagnostic time: product data, field rule, or message routing;
- completeness of status return to PIM;
- number of retry sends after data corrections.
Result
The team gained clear exchange logic: business sees product status, integration team knows where to look for errors, and price and stock flows aren't burdened with unnecessary attributes.
This reduces the risk that integration problems will be discovered only after publication or product update failures.