B2B marketplace supplier catalogs: units, identity, and updates

B2B marketplace supplier catalog management starts with reconciling different suppliers' identifiers, specifications, units, and sales terms. Importing every row into one table does not make those records comparable.

The most important early decision is what a buyer is purchasing: one item, one pack, one length, or one quantity measured by weight or volume.

Work through a unit-of-sale mismatch

Imagine two suppliers list an illustrative fastener. One quotes a price for a box of 100. Another quotes per piece with a minimum purchase of 200. A catalog that displays both prices as a single-unit price will mislead buyers even if every other attribute is complete.

Keep product identity, pack quantity, order unit, minimum order quantity, and price basis separate. Preserve the supplier's original terms so a reviewer can reconstruct the normalized representation.

A conversion is safe only when the underlying meaning is known. A field labeled “quantity” may refer to stock, pack contents, or minimum order size. Ask for clarification before mapping it.

Scope identifiers to the supplier

Two suppliers can use the same SKU for unrelated products. Store supplier ID with supplier SKU and maintain a separate manufacturer identity when one is available.

Do not match products on a shortened description alone. Check the manufacturer, part number, revision, and attributes that determine compatibility. Replacement parts and complete assemblies can have very similar names.

Use duplicate detection to distinguish canonical product matching from repeated supplier offers. Multiple suppliers selling the same component can be useful supply, not duplicate clutter.

Create a category-specific specification contract

Your contract should state which values can be researched and which only the supplier can confirm. A public specification sheet can support dimensions; it does not prove the supplier has current stock.

Do not infer a certification or safety rating from a product description or similar model. Store the applicable documentation and route those claims to the appropriate review process.

Automate mappings before chasing every missing field

Start with repeatable transformations: known column mappings, explicit unit conversions, approved category crosswalks, and identifier cleanup. Then use research for exact-model specifications and document extraction for complex tables.

The supplier PDF workflow explains how to keep table context and footnotes. That matters when a single document covers several revisions or configurations.

Maintain seller-specific mapping versions. A supplier switching from per-piece to per-box prices should trigger review, even if the spreadsheet columns have the same names.

Design for updates and partial failures

Use stable source identifiers and idempotent imports so repeated uploads update the intended offers. Record missing and rejected rows with reasons. Do not silently delete a supplier's catalog because one import is incomplete.

Set a policy for stale price and availability data. Catalog enrichment can make a specification more complete while leaving commercial terms out of date. Those need different refresh schedules and owners.

Evaluate one supplier before expanding

Choose a supplier with representative complexity and a cooperative reviewer. Check correct unit-of-sale interpretation, exact product matches, blocked records, manual touches, and time to usable offers.

Goodfolk's intended role is to prepare cleaner supplier data and maintain evidence around proposed enhancements. The initial scope should name the categories, fields, supported sources, and downstream connection. A successful pilot should leave your team with fewer catalog corrections without weakening control over commercial or technical claims.