Composite pattern: a distributor fixing supplier data onboarding

Situation: range growth limited by supplier data

This is a composite pattern built from several PIMvendors selections, and it names no client or vendor. It describes a European wholesale distributor with a broad range from many suppliers. Range growth was a commercial priority, and each new product had to be listed in the webshop and printed catalogue.

Supplier data arrived as spreadsheets, PDFs and emails, each in the supplier's own structure. An onboarding team retyped and reformatted the data. The time from supplier file to sellable product was the main limit on range growth.

The cases overview lists the other composite patterns in this series.

Complication: the wrong problem in the brief

The first brief asked for a PIM, while the bottleneck sat in onboarding. The brief listed enrichment, workflows and channel publishing. It said little about how supplier data would enter the system.

Vendors answered the brief they were given. Their demos showed polished enrichment screens on clean demo data. None of them showed what happened to a messy supplier file.

The distributor also faced a duplicate problem. The same product often came from several suppliers, with conflicting values. Nobody had decided which supplier's data should win.

What the selection did differently

The selection split supplier onboarding into its own requirement area and tested it first. The method followed the house order of Data, Process, People and Tooling.

1. The team defined a target data model per product group, with mandatory attributes and units.
2. The onboarding process was mapped from supplier contact to webshop listing, with each manual step marked.
3. Source priority rules were agreed for products delivered by several suppliers.
4. Requirements were tagged by domain, with onboarding requirements under Integration and syndication.
5. The RFP asked vendors to price onboarding capability separately, including any portal add-on.

The supplier data onboarding guide covers these design choices in more detail.

Which scenarios decided the selection?

The decisive scenarios all started from a real supplier file.

Vendors had the files one week before the demo. That gave each vendor a fair chance to prepare, and it showed how much configuration each needed.

Outcome patterns

Onboarding capability varied far more between vendors than core PIM features did. Most shortlisted vendors handled enrichment and publishing well. Import mapping, validation feedback and supplier portals differed widely in maturity and in price.

Some vendors offered portals as separate products with their own licence. Pricing those add-ons early prevented a surprise in negotiation. The source priority rules, agreed before selection, became configuration requirements that every vendor could be tested against.

The onboarding team became the strongest advocates for the chosen system. They had written the scenarios and seen their own files work.

Where this pattern goes wrong

The pattern fails when onboarding is pushed to a later phase. Distributors that bought on enrichment features alone often found that supplier imports needed custom work after contract. That work then competed with the go-live plan for budget and attention.

Supplier engagement is a second failure point. A portal helps only when suppliers use it, and many suppliers resist yet another login. The distributors behind this pattern tested the portal with two or three cooperative suppliers before signing. A third risk is skipping source priority rules, which leaves the PIM storing conflicting values with no rule to choose between them.

Lessons for distributors in a similar position

Test the import before the enrichment screens. Four lessons recur across the engagements behind this pattern.

• Write onboarding requirements as a separate group, with their own weight in scoring.
• Use the worst real supplier files in demos, shared with vendors in advance.
• Agree source priority rules for duplicate products before selection.
• Price supplier portals and connectors as separate line items.

Manufacturers face the mirror image of this problem, sending data to distributors, as shown in the manufacturer pattern. Brands selling through marketplaces face the outbound side, covered in the marketplace expansion pattern.