Skip to content
Web Development17 min read

B2B Ecommerce Product Catalog: How to Organize Complex Product Data

How to organize a B2B product catalog: taxonomy, attributes and units, variants and pack sizes, documents, account catalogs, PIM and ERP sources and data quality.

01

Quick answer

A B2B product catalog works when its structure matches how buyers think and its data is complete and consistent. Organize categories by buyer logic, group variants into product families, define required technical attributes with units per category, attach documents such as datasheets and certificates, capture pack sizes, minimum order quantities and increments, control visibility with account catalogs, and handle discontinued products with replacements. Keep descriptive data in a PIM and commercial data in the ERP, and monitor quality continuously.

02

Why B2B Catalogs Are Hard

B2B catalogs often contain thousands to hundreds of thousands of SKUs, with technical attributes that differ by category, supplier data in inconsistent formats, multiple identifiers per product and rules about who can buy what. Catalog quality directly affects search, filters, product pages, feeds and order accuracy. In short, think of the four areas to structure: taxonomy, product data, catalog access and documents.

03

Taxonomy

Categories should reflect how buyers classify products, not internal departments or supplier structures. Many B2B buyers look by product type; others by application or industry. Use a primary hierarchy by type and add secondary navigation by application or industry where it helps. Validate with card sorting and search logs. See information architecture.

04

Product Families and Variants

A product family groups items buyers choose between: the same fastener in different lengths, the same glove in different sizes. Families simplify browsing and product pages. Separate products when variants differ in specification or application enough that buyers compare them as different products. Very large families may need variant grids or tables rather than dropdowns.

SituationStructure
Same product, different size or colourOne family, variants
Same product, different pack sizesVariants or order units, clearly labelled
Different materials or ratingsSeparate products or family with spec table
Hundreds of variantsFamily page with filterable variant table
05

Attributes and Units

Define an attribute set for each category: which specs are required, their units and allowed values. Normalize units so filters work (mm vs inches, kg vs lb), store numeric values separately from display text, and keep identifiers (SKU, manufacturer part number, GTIN, customer part numbers) in dedicated fields. Consistent attributes power filters, comparisons and search. See product data for AI search.

Pro tip

Start attribute work with the filters buyers need most in each category. A complete set of ten attributes beats an incomplete set of fifty.

06

Ordering Attributes

AttributeExampleUsed for
Pack size / unit of measureBox of 100Price display, quantity input
Minimum order quantity5 boxesQuantity validation
Order incrementMultiples of 5Quantity validation
Lead time3–5 daysAvailability messaging
Hazardous / restrictedYesShipping and access rules
07

Documents and Assets

B2B buyers often need documents before ordering: datasheets, certificates of conformity, safety data sheets, installation guides, CAD files. Store them as structured assets linked to products (with type, language and version), make them downloadable from product pages and searchable where useful.

Catalog data holding back your B2B store?

ZSpace Labs structures B2B catalogs, attributes and integrations so buyers can find and order the right parts.

Start a Project
08

Access: Account Catalogs and Restrictions

Many B2B businesses show different products and prices to different customers: contract ranges, regional availability, restricted products for licensed buyers. Model these as catalogs or rules assigned to companies or segments. Shopify B2B, for example, uses catalogs assigned to company locations to control products and prices.

The entitlement architecture behind account catalogs is covered in customer-specific catalogs.

09

Sources of Truth: PIM, ERP and Platform

Catalog data rarely starts in the ecommerce platform. Decide which system owns each field, sync in one direction per field and avoid editing the same data in two places. A common split is shown below; smaller businesses may keep descriptive data in the platform itself. See B2B ERP integration.

For PIM in depth, see ecommerce product information management; for system boundaries, PIM vs CMS.

SystemTypically owns
ERPSKUs, prices, stock, order rules, customers
PIMDescriptions, attributes, assets, translations
DAMImages and media (sometimes in PIM)
Ecommerce platformMerchandising, storefront presentation
10

Scale and Platform Limits

Large catalogs test platform limits and integrations. Shopify documents limits such as a maximum of 2,048 variants per product and restrictions on how quickly stores above a large variant count can add new variants on non-Plus plans; API calls are rate-limited, and pagination has limits. Plan bulk imports, sync jobs and catalog structure against current limits.

11

Discontinued Products and Replacements

Buyers reorder from old part numbers and old documents. Keep discontinued product pages where useful, mark them clearly, link to replacements and redirect when a page must go. Map old identifiers to new products in search.

12

Worked Example: Normalizing Supplier Data

An illustrative scenario: a distributor imports products from 40 suppliers. Lengths arrive as “40mm”, “40 mm”, “4cm” and “1.57in”; materials as “SS”, “Stainless”, “A2” and “304”. The team defines attribute sets per category with units and allowed values, maps supplier values on import (storing the original alongside the normalized value), flags products missing required attributes and prioritizes fixes by sales. Filters and search become consistent, and supplier onboarding includes a data template. See product feeds.

13

Catalog Presentation

Structure drives presentation. Category pages for technical products often work better as filterable tables than image grids, with key attributes as columns. Product family pages can show a variant table with specs, pack sizes, availability and quantity inputs. Keep images consistent and useful (product, dimensions drawing), and put documents where specifiers expect them. See product listing page UX.

14

Data Quality

  • Required attributes defined per category
  • Completeness monitored by category and supplier
  • Units and formats validated on import
  • Owners assigned for each data domain
  • Fixes made at the source system
  • Regular audits of top-selling products

Ready to organize your B2B catalog?

Talk to ZSpace Labs about B2B catalog and integration builds, B2B catalog UX and Shopify B2B.

Start a Project
15

Conclusion

A well-structured B2B catalog makes search, filters, product pages and ordering accurate. Organize by buyer logic, define attributes and units, attach documents, control access and keep data flowing from the right source systems. For how buyers find products in it, see B2B ecommerce search.

FAQ

Common questions.

The structured set of products a business sells online to other businesses: taxonomy, product families and variants, technical attributes, pack sizes, documents, and rules about which accounts can see and buy which products.

By how buyers classify products (type, application, industry), with product families grouping related variants, consistent technical attributes per category and clear rules for account visibility.

Technical specifications with units, dimensions and tolerances, materials, compliance and certifications, pack sizes, minimum order quantities, order increments and identifiers such as SKU, manufacturer part number and GTIN where relevant.

Often in a PIM for descriptive and technical data and an ERP for prices, stock and order rules, with the ecommerce platform receiving data from both.

Catalogs that control which products and prices a particular company or segment can see and buy, used for contracts, regional ranges and restricted products.

Group variants into product families where buyers choose between options, and use separate products when variants differ substantially in specs or use. Very large variant counts may need a different structure.

Keep pages available where useful, mark them discontinued and link to replacements, so buyers with old part numbers can still find the right product.

Define required attributes per category, validate units and formats, assign ownership, monitor completeness and fix issues at the source system.

Shopify supports B2B catalogs and large product counts, with platform limits on variants and API throughput that large catalogs should plan for. Check current limits against your catalog size.

This guide covers structuring the catalog data. The B2B search guide covers how buyers find products in it.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.