A wholesaler occupies a distinct position in the supply chain: it neither originates product data nor markets on brand experience. Instead, it sources data from hundreds of suppliers, standardizes and enriches it, and redistributes it to retailers and B2B buyers. This intermediary role fundamentally shapes how a distributor should approach product information management.
Manufacturers author the record. They own specifications, dimensions, materials, compliance data, and variant logic, usually pulled out of PLM and ERP systems. Retailers curate a smaller assortment and polish it for conversion. Wholesalers sit between the two, and the job is different enough to need its own playbook. Most PIM advice online is written for one of the other two roles, so it quietly assumes clean source data or a small catalog. Distribution has neither.
There's a second reason the catalog carries so much weight in wholesale. Buyers do most of the work themselves before anyone from your side is involved. A Gartner survey of 632 B2B buyers found that 61% prefer an overall rep-free buying experience. When the buyer never calls, your product data is the salesperson. This guide is about making that data work for the wholesale case specifically.
Start Here: The Short Version
- Supplier onboarding is the core job, not a side task. Getting messy inbound feeds into one clean catalog is where a distributor earns its margin.
- Catalogs are wide and shallow. Enrichment and gap-filling turn thin supplier data into something a buyer can find and trust.
- B2B commercial data has to sit next to the descriptive data: contract pricing, units of measure, minimum order quantities, and multi-warehouse stock.
- Buyers search by manufacturer part number and expect cross-references, substitutes, and supersessions.
- You both consume and syndicate data, often in each customer's own format, so the integration burden lands on both sides.
Where Wholesale Sits In The Product Data Chain
At the source, a manufacturer maintains a narrow assortment with deep, tightly controlled data. A pump maker publishes a full datasheet for each model, including dimensional drawings, a dozen technical attributes, and compliance certificates. Because it owns the product, that data is authoritative and consistent.
A wholesaler inherits those same products without any of that consistency. Across hundreds of suppliers, data arrives as structured feeds, flat CSV price lists, PDF catalogs, and sometimes nothing more than part numbers and prices. Classification diverges too. One supplier maps to ETIM, another to eCl@ss, a third to a proprietary scheme or none at all.
Turning that into one catalog is a set of recurring tasks: mapping each supplier's classification onto a single internal taxonomy, normalizing attributes and units of measure, deduplicating against the manufacturer part number so the same item from multiple suppliers collapses to one record, and defining the minimum attributes an item needs before it can be published. Because supplier feeds change constantly, this reconciliation runs on every update, not just at onboarding.
Supplier Onboarding Is The Real Job
Our customers often turn to us with similar problems: a shared drive full of supplier spreadsheets, none of them alike, and a webshop or ERP that needs one coherent catalog behind it. Someone in the team spends their week copy-pasting and re-keying, and the catalog is always a little out of date.
A distributor's real product is order made out of supplier chaos. Everything downstream depends on getting that part right.
Here is what "none of them alike" actually looks like. Three suppliers send you the same kind of data, and no two agree on names, language, or units.
| Your unified field | Supplier A | Supplier B | Supplier C |
|---|---|---|---|
| Manufacturer part number | MPN |
Art-Nr. |
buried in description text |
| Brand | Brand |
Hersteller |
Make |
| Net weight | Weight (kg) |
Gewicht (g) |
missing |
| Pack unit | UOM = EA |
VPE = 10 |
missing |
Supplier B reports weight in grams while you standardise on kilograms, so an unmapped import is off by a factor of a thousand. Supplier C hides the part number inside a text field and never states a pack unit. Multiply that by three hundred suppliers, and you can see why manual handling never catches up.
A few things make onboarding survivable at scale.
Build a saved mapping per supplier, not one giant import. Each supplier speaks its own dialect, so keep a stored mapping for each one that translates their columns and units into your model. You configure it once, then every future feed from that supplier flows through the same rules. In the projects we've implemented on AtroPIM, this per-supplier mapping is the single change that takes the weekly re-keying off someone's desk.
It helps to put a rough number on why that matters. Take an illustrative case, not a benchmark: three hundred suppliers, each feed re-keyed by hand in about two hours, refreshed monthly. That's six hundred hours a month of pure data entry, before anyone has enriched or checked anything. Reusable mappings turn the monthly refresh into a largely unattended run, and the team handles only the records that fail validation. The saving isn't the interesting part. The interesting part is that the catalog is now current, because nobody has to find two hundred spare hours to make it so.
Separate staging from published. Raw supplier data lands in a staging area first. You validate it there and only promote items to the live catalog once they clear. Buyers never see a half-imported record, and a bad feed can't poison the catalog.
Set validation rules that reject early. Missing mandatory attributes, prices that look like typos, duplicate part numbers, weights that jumped three orders of magnitude, images below a resolution floor. Catch these at intake, because a wrong value spotted at import costs minutes, and the same value spotted by a customer costs a return.
Map every supplier's categories to one taxonomy. This is the part that can't be fully automated. A "ball valve" in one feed and a "valve, ball, brass" in another belong in the same place in your tree. A consistent taxonomy is what lets a buyer filter and search across your whole range instead of your suppliers' fragments of it.
Onboarding is also where deduplication happens. Two suppliers often carry the same manufacturer item under different descriptions. Matching them on manufacturer part number and brand keeps you from listing the same product twice at two prices.
Breadth Over Depth: Enrichment As A Differentiator
Wholesale catalogs run to hundreds of thousands or millions of SKUs, and much of the source data is thin. A manufacturer's own listing for a product is rich. The version that reaches you through a feed is often three fields and a stock number.
For a retailer, enrichment is polish. For a wholesaler, it decides whether the product is findable at all. An item with no attributes doesn't appear in filtered search, doesn't rank, and doesn't convert. The clearest evidence for what missing information does sits on the retail side: Akeneo's 2025 consumer research found that 65% of shoppers would abandon a purchase entirely when product information is missing. That's a consumer figure, and a B2B buyer sourcing a spare part behaves differently from someone buying a shirt. The read-across is directional, not exact. But the direction is the point: no data, no sale, whichever side of the counter you're on.
You can't enrich a million SKUs at once, so the work has to be measured and ranked. Scoring completeness makes that concrete. Take one product against the attributes its category requires.
| Ball valve, DN25 | Required | Present |
|---|---|---|
| Attributes filled | 14 | 6 |
| Completeness | 43% |
Missing here: body material, pressure rating, connection type, connection size, temperature range, media compatibility, weight, and certifications. At 43%, this item won't surface in a buyer's filtered search for "brass, PN16, threaded," even if you stock exactly that. If it's a top-hundred seller, it moves to the front of the enrichment queue. If it's a long-tail item nobody queries, it waits.
That prioritisation is the whole discipline. A few practical moves keep it manageable.
Prioritise by what earns money. Sales data and site-search logs tell you which thin records are costing you orders. Enrich the high-demand gaps first.
Hold suppliers accountable with a scorecard. Track each supplier's completeness over time and share it back. Some will improve their feeds once they can see they rank last, which reduces your own enrichment load.
Use AI to draft, use people to approve. Automated enrichment can propose attributes and descriptions from a datasheet or a part number. Keep a human check on anything that affects safety, compliance, or fit. Speed from automation, trust from review.
B2B Commercial Complexity Lives Next To The Content
Retail PIM mostly manages description and imagery. Wholesale has to carry the commercial mechanics too, and they sit right beside the descriptive data because buyers act on both at once.
Here is the data that has to live in or alongside a wholesale catalog:
- Customer and contract pricing.
Different buyers pay different prices. Volume tiers, negotiated rates, and account-specific lists all have to resolve correctly at the moment a buyer logs in. - Units of measure.
The same item sells as each, inner, case, and pallet, with different prices and barcodes per unit. Getting this wrong causes wrong orders and wrong invoices. - Minimum order quantities and multiples.
Some items ship only in packs of ten or on a full pallet. The rule belongs in the data, not in a rep's head. - Multi-warehouse availability.
Stock differs by location, and a buyer wants to know what's available near them, not a company-wide total.
On top of pricing and stock sits the search behaviour that defines B2B. Buyers know the part they want.
Buyers search by manufacturer part number, not by your internal SKU. If the cross-reference is missing, the search returns nothing.
Consider a maintenance engineer who enters a Festo cylinder code into your search bar. If your catalog links that manufacturer part number to your SKU, the search resolves to the product and the item can be added to a cart. If Festo has superseded the code, a supersession link should route the buyer to the current replacement. If neither link exists, the search returns nothing. A buyer who hits that empty result rarely calls to confirm whether the item is in stock; more often, they move to the next supplier. This is an observed pattern rather than a measured statistic, but it is consistent with how B2B buyers describe their own behavior: conducting research independently and engaging a representative only when necessary.
So cross-references, substitutes, supersessions, and kitting are core wholesale features, not retail nice-to-haves. Industrial, electrical, plumbing, and MRO distributors sell assemblies built from component parts, and each assembly needs its own record. None of this is central to consumer retail, and all of it is daily work in distribution.
You Syndicate As Hard As You Ingest
A wholesaler is dual-facing. Data comes in from suppliers, and it goes out to customers, marketplaces, and B2B buyers, often reshaped for each destination.
You carry an integration burden on both sides. Data comes in messy and has to go out in each customer's preferred shape.
One large retail customer wants your feed in their taxonomy with their attribute names. A marketplace demands its own required fields and image rules. Your own webshop needs something else again. The same clean catalog has to render in several formats without you maintaining several catalogs.
The way through is to keep one internal model and treat every output as a transformation of it. You author and enrich once. Export profiles, then map that single source into each channel's format on demand. A channel changing its requirements becomes a change to one export profile, not a redo of your data. This is the outbound mirror of the per-supplier mapping you built for intake.
Consistency across those outputs is where the money leaks quietly. When the same product shows different specs on your webshop, in a customer's feed, and in a rep's quote, buyers stop trusting all three. Gartner puts a number on how common that is: 69% of B2B buyers report inconsistencies between the information on a supplier's website and what its sellers tell them. A single source of truth feeding every channel is the direct fix for that.
Governance And One Source Of Truth
With data flowing in from hundreds of suppliers and out to dozens of channels, the question of who owns what stops being optional. A single source of truth only stays single if there are rules around it.
Decide which system is authoritative for each field. Price and stock may come from ERP. Descriptions and attributes live in the PIM. Nothing good happens when two systems both claim to own the same value and disagree.
Give records a workflow. New supplier items enter as drafts, get enriched, pass a quality gate, and only then publish. Roles decide who can approve. This keeps the catalog clean without slowing everyone to the speed of one reviewer.
Keep an audit trail. When a price or a spec is wrong, you want to know where it came from and when it changed. In a multi-source catalog, provenance is what makes problems fixable instead of mysterious.
When You're A Hybrid
These are archetypes, not walls. Plenty of companies blend two or three of them. A manufacturer sells direct to consumers and suddenly needs retail-grade content and SEO copy. A wholesaler runs a webshop that has to look and feel like a retailer's. A retailer private-labels its own goods and has to author manufacturer-style records for them.
If you're a hybrid, your requirements blend too. A wholesaler going direct to consumers still has the supplier-onboarding and breadth problems, and now also needs the marketing polish that retail demands. A flexible data model matters here because you extend the model you already have instead of rebuilding when the business shifts.
Practical Starting Points
If you run product data for a wholesaler and want to make it better, start where the pain compounds.
- Pick your ten worst supplier feeds and build a saved mapping for each, units included. That alone removes most of the weekly re-keying.
- Add a staging step and a handful of validation rules before anything reaches the live catalog.
- Score completeness on your top-selling items and enrich those first.
- Put manufacturer part numbers, cross-references, and supersessions into the catalog so buyers find what they search for.
- Move channel output to export profiles so a customer's format change is a small edit, not a project.
Wholesale PIM rewards the boring, structural work. Get intake, enrichment, commercial data, and syndication right, and the catalog stops being a liability and starts being the reason buyers choose you.