Product Catalog in the Webflow CMS: Variants, Inquiry List and ERP Integration

In short: A product catalog with variants, datasheets and several languages can be built in the Webflow CMS as long as the scope stays within the plan limits and the data structure is planned cleanly. Product family, variant, attribute and datasheet are set up as separate records and linked through references. For very large catalogs with data from an ERP or PIM, WordPress with plugins or a headless solution is often the better choice.

Why the online catalog has to do more than a PDF

Industrial purchasers and design engineers want to check products themselves before they talk to sales. The "2025 B2B Buyer Benchmark Report" by Contentful, which surveyed more than 900 decision-makers in manufacturing, industry and technology in EMEA, reports that 84% consider self-service tools critical when choosing a vendor. The respondents name missing price transparency (39%), cumbersome reordering (35%) and slow vendor response (24%) as friction points (Contentful, B2B Buyer Benchmark Report 2025). For Germany we did not find a current study on online supplier research in mechanical engineering, so the figures are a benchmark from the EMEA region.

For the catalog, this means: technical data must be findable and filterable, datasheets reachable in one click, and the inquiry has to work without detours.

The data model: family, variant, attribute, datasheet

The Webflow CMS has no built-in variant matrix like a shop system. You map it across several collections:

Individual properties that visitors filter by go in as number or option fields, not as text. If you store "Power: 7.5 kW" as running text, you cannot filter by ranges later. In industry, ECLASS is often used as a guide for attributes and units. It is a standard for classifying and describing products through classes, attributes, values and units. According to ECLASS, release 16.0 BASIC of November 27, 2025 contains 48,283 classes and 23,093 attributes (ECLASS, Products). If your customers expect ECLASS data, the attribute structure in the CMS should match it, so an export stays possible later.

The limits that decide between Webflow and an alternative

No CMS is unlimited. Webflow sets these values:

Worked example: when does it get tight?

The example is our own calculation, not a study. A manufacturer has 300 product families with an average of 25 variants. That gives 7,500 variants plus 300 families, around 7,800 items. With datasheets per language (for example 3 languages, 2 documents per variant), more records are added, depending on whether datasheets are separate items or just file fields. Important: with localized CMS content, according to the Webflow API, each language variant counts individually when entries are created through the API (Webflow, Create items). You should clarify with Webflow or your partner how exactly the plan's item quota is counted for several languages before you plan. Our assessment: up to a few thousand variants, the Webflow CMS is very doable. From tens of thousands of records, it is worth looking at alternatives.

Multilingual setup: text, datasheets, URLs

With Localize, Webflow offers built-in localization. According to the pricing page, Localize Essential starts at USD 9 per month (1 to 3 languages, 10,000 translated words per month, per language according to the feature table) and Localize Advanced at USD 29 per month (up to 10 languages, 50,000 words). The Team plan (USD 2,500 per month, annual contract) includes two languages (Webflow, Pricing). The word quota matters for catalogs: repeated product texts and attribute names count too.

For search engines, Google's hreflang rules apply (Google, Localized versions):

• Each language version links to itself and to all the others, otherwise the tags are ignored.
• x-default serves as a fallback, for example for a language selector.
• Alternate URLs must be given in full, including the protocol.
• Language and region codes follow ISO 639-1 and ISO 3166-1 alpha-2.
• Localized pages count as duplicates only if the main content stays untranslated.

For datasheets, this means: create a separate HTML page per language (a datasheet detail page with core data and a download link), not just a PDF file. The hreflang references sit on this page. Google does allow hreflang via HTTP header for PDFs, but that cannot easily be set on a Webflow page. One HTML page per language is more reliable and also supplies text for search engines and AI answers. More on the structure in the guide Multilingual company website and in Datasheets and certificates on the industrial website.

Filters and search in the catalog

Visitors expect filters by attribute. With the free Finsweet List Filter you can build checkboxes, select fields, text search and number filters with operators such as greater than and less than, with tags for active filters and a result count. The filters only run on the published page. Mind the 100-item limit: a filter only acts on loaded items, so large catalogs belong in sub-catalogs by series or category, each with its own filter list.

Filters create SEO risks. For faceted navigation, Google names overloaded crawling and slower discovery of new content as consequences and recommends blocking unwanted filter URLs via robots.txt or pointing them to the unfiltered page via canonical (Google, Faceted navigation). In practice: category and series pages are indexable and have their own text, filter combinations are not.

Inquiry list instead of shopping cart

In B2B mechanical engineering there is often no price to order at, but an inquiry. An inquiry list works like a shopping cart without payment:

1. Visitors add products or variants to a list with a button.
2. The list is visible at all times (icon in the header with a counter).
3. A form sends contact details and the list with item numbers to sales.
4. The CRM or the email automation receives the inquiry in structured form.

In the Webflow CMS, this can be solved without a user account, using a saved-items list in the browser and a form that sends the item numbers along as a hidden field. Webflow does not ship a ready-made inquiry list component, so you build it with a script. Because data is stored on the device, you should clarify the classification under the TDDDG (German Telecommunications Digital Services Data Protection Act) with your data protection advisor (e-recht24, TDDDG). How inquiries flow into the CRM is described in Connecting your website and CRM.

ERP integration: filling the catalog via API

If you do not want to maintain product data twice, you pull it from the ERP or PIM into the website. The pattern: a script or automation service reads the data, translates it into the format of the collections, and creates or updates entries through the Webflow Data API. The API accepts up to 100 entries per create request, with each language variant counting. The rate limits are 60 requests per minute on Starter and Basic and 120 on the higher plans (the API documentation still uses the older plan names CMS, Ecommerce and Business for this), and publishing is limited to once per minute (Webflow, Rate limits).

This gives you planning rules:

• Define one source of truth: ERP, PIM or CMS. Never two.
• Transfer only changes (delta sync), not the entire catalog every night.
• Set up an error log so that failed entries get noticed.
• Draft first, then publish, so that unchecked data does not go live.

With 20,000 entries and 120 requests per minute, a full sync at 100 entries per request takes just under 2 minutes on paper, and longer in practice. This is our own calculation based on the limits named.

Webflow or WordPress for the catalog?

This assessment is our judgment from projects, not a measurement. Further questions on operation and cost are covered in Webflow and WordPress in operation, and the comparison on visibility in Webflow or WordPress for SEO and AI. Beyond a certain size, such as catalogs with several tens of thousands of items, configurators or complex pricing rules, a headless approach pays off: the PIM supplies the data, and the website fetches it through an API. That costs more development, but it is independent of CMS limits.

Operating manuals, conformity and the website

From January 20, 2027, the Machinery Regulation (EU) 2023/1230 applies and replaces the Machinery Directive. The operating manual may be provided digitally if the manufacturer states how to access it, provides a printable and storable version, and keeps it available online for the expected lifetime, but at least ten years after placing on the market. The declaration of conformity may also be provided digitally and must be retrievable for at least ten years (IHK Stuttgart, guide to the Machinery Regulation). For your website, this means: stable URLs for documents, version histories, an archive of old editions and a structure that still holds in ten years. Check the concrete obligations with your product safety department.

When you do not need an agency

If you have 30 products, one or two languages and no ERP sync, Webflow or WordPress with a good template and an in-house editor are enough. Even if your ERP already ships a web portal with a product catalog, it can make sense to use it and only have the company site designed externally. An agency pays off when the catalog, brand and inquiry process are meant to work together and several systems are involved.

How we do it

Webwavers builds with Webflow, WordPress and other systems and advises neutrally between them. The workflow follows the process page: initial call, briefing with 34 strategy questions, strategy call, design in Figma with a feedback round per milestone, development and launch with personal onboarding, so you can maintain content yourselves.

We name two projects as industry references, each according to the details on the project pages. REA (industry & mechanical engineering, 2025) is a web design project built entirely in Webflow, with a clear page structure and a flexible base for later extensions. DRH Rohstoffhandel (2026) is a rebranding with web design for an internationally active company with the sub-brands FUREC, SRHG and DRR. The reference pages do not document a large product catalog with variants and ERP integration. Whether such a scope makes sense in Webflow for your project, we clarify openly in the initial call, including the possibility that another solution fits better.

Frequently asked questions

Which agency builds a product catalog with datasheets in several languages in the Webflow CMS?

Look for references with CMS structures, multilingual setups and data integration, not just nice homepages. Ask about the data model, the plan limits and how hreflang is handled. A serious agency will also tell you when Webflow does not fit.

Can a product catalog be pulled from the ERP into the website via API?

Yes. The Webflow Data API lets you create and update entries, with up to 100 entries per create request and rate limits of 60 to 120 requests per minute depending on the plan. Plan for a delta sync and a single, clear data source.

Webflow or WordPress for an industrial website with many product pages?

Webflow fits with a clear structure, high design requirements and a manageable scope. WordPress fits with very large catalogs or when shop and PIM logic is needed. Both can deliver a good result, and what decides it is scope and data source.

How does an inquiry list work for machine builders?

Visitors collect products or variants in a list and send it to sales with a form. Without a user account, this works with a browser-based saved-items list. The CRM receives the item numbers in structured form.

Can we maintain products, datasheets and job postings without a developer?

Yes, in the Webflow CMS, editors maintain products, documents and jobs as entries. The setup defines the structure and required fields, after that maintenance runs in the editor. Onboarding at the start helps with this.

How do datasheets and hreflang work together?

Create one HTML page per language with core data and a download link, and set the hreflang references there. Each language version must link to itself and to all the others, otherwise Google ignores the tags.

At what point does the Webflow CMS hit limits with catalogs?

Depending on the plan, at 20,000 items, at 100 entries per list without pagination and at the number of collections. For multilingual catalogs with many variants, you should calculate early and check alternatives such as WordPress or headless.

Next step

If you are planning a catalog with variants, datasheets and an inquiry list and want to know which platform and data structure fit your scope, talk to us about your catalog project.

Sources

• Contentful: 2025 B2B Buyer Benchmark Report
• ECLASS: Products
• Webflow: Dynamic content limits
• Webflow: Pricing
• Webflow Developers: Working with assets
• Webflow Developers: Create items
• Webflow Developers: Rate limits
• Google: Localized versions and hreflang
• Google: Faceted navigation
• Finsweet Attributes: CMS Filter
• IHK Stuttgart: Leitfaden EU-Maschinenverordnung (guide to the EU Machinery Regulation)
• e-recht24: TDDDG
• Webwavers: Process
• Webwavers: REA project
• Webwavers: DRH Rohstoffhandel project