Is a printed catalogue still worthwhile in B2B?

In many assortments yes, because it works where a screen is impractical: in the workshop, in the warehouse, on the construction site. **38 percent** (Bitkom) of companies still handle around half of their office and administrative processes on paper, only **15 percent** (Bitkom) work entirely paperless. On top of that, **67 percent** (Gartner) of B2B buyers prefer a rep-free buying experience - a catalogue opens up the assortment without a conversation. The decisive question is less whether than at what cost: if the catalogue is produced from the same source as the shop, the effort drops considerably.

Which fields are typically missing when shop data is to be used for print?

Four groups stand out regularly. First media: images exist in screen resolution but not in print resolution with a colour profile and bleed. Second copy: there is a long description but no catalogue text with a fixed character limit. Third order: the shop sorts by relevance, the catalogue needs a fixed catalogue order per assortment group. Fourth the trimmings: footnotes, legends, symbol explanations and index entries so far live in the heads of the people involved. These four groups belong in the source, not at the typesetter.

How do I stop catalogue and shop from showing different prices?

Through two rules. First: the printed price is the list price with a validity date, while the shop additionally shows the customer-specific price after login. That way the difference is explained rather than contradictory. Second: every catalogue page carries the edition marker the details come from. Whoever calls quotes that marker, and internal sales immediately sees which state is in front of the customer. Both presuppose that catalogue and shop read the same data set and that corrections happen only there.

What belongs in the printed price list and what does not?

In it belong the list price, the unit of measure per price, the validity start, the currency, the customer group and notes on additional costs, taxes and minimum order quantities. Out of it stay customer-specific terms, project-related special prices and discount tiers that were negotiated individually - those belong behind the login in the shop. The reason is practical and commercial at once: printed matter circulates uncontrolled, and negotiated terms lose their value once they are in circulation.

How long does the switch to a shared source take?

For a first assortment group as a pilot, a few weeks are realistic: clarify the field model, close the gaps, build the export, typeset one master page. The full catalogue follows the catalogue season, because data maintenance sets the pace rather than the technology. Experience shows the larger effort lies in reworking images and catalogue copy, not in building the export. Anyone completing the pilot before the next data freeze can use the findings in the same edition.

Do I need an additional system for this?

Not necessarily. What matters is that there is one leading source per field and that a repeatable export can be built from it. In smaller assortments the ERP with additional fields and an orderly media library is sufficient. As soon as several languages, many attributes, classifications and multiple output channels come together, a dedicated product information system pays off. The order stays the same: first the field model and the sign-off process, then the question of the tool.

Print Catalogue and Price List From Shop Data

The printed catalogue lies on the customer's table, the shop runs in the browser next to it - and the two show different prices. In technical wholesale and distribution this is everyday reality, because catalogue and shop come from separate sources: the catalogue is fed into the layout software from a spreadsheet, the shop is supplied continuously from the product data system and the ERP. The maintenance effort occurs twice, the message stays contradictory. Yet paper is far from obsolete in B2B sales: 38 percent (Bitkom) of German companies still handle about half of their office and administrative processes on paper, and only 15 percent (Bitkom) work entirely paperless. At the same time the digital channel has become the larger one: manufacturers and wholesalers generated 509 billion euros (ECC KÖLN) via online shops and marketplaces, an increase of 7 percent (ECC KÖLN) over the previous year. Together this defines a clear task: print catalogue and price list belong in the same data source as the shop. This article describes the data model behind that, the fields print needs on top of shop data, the released data set as a shared reference point and the path from data sign-off to the finished print file.

Key takeaways

Catalogue and shop need the same source: item master, copy, attributes, media and prices are maintained in one place, and print becomes an output of that source instead of a second data set.
Paper remains a working tool in B2B: 38 percent (Bitkom) of companies handle around half of their office processes on paper, and merely 15 percent (Bitkom) work entirely paperless.
The released data set is the actual instrument: a dated and versioned snapshot that catalogue page, price list, shop display and quotation all refer to.
A price list is not an extract but an object of its own with validity period, customer group, currency, unit of measure and volume tier - otherwise a printed price becomes a matter of interpretation.
A data set that follows an open classification standard with around 48,000 product classes (ECLASS) can additionally be exported as an electronic catalogue for customers' procurement systems.

Two truths: the catalogue from last season and the shop from today

In many companies the catalogue follows a fixed ritual: in spring, marketing pulls an extract from the ERP, adds copy from earlier editions and images from the file server, sends a spreadsheet to the typesetter and then corrects proofs for weeks. In parallel the shop is supplied continuously from the product information system and the ERP, as described in the article on product data and data quality in B2B. Both routes start from the same items and end with different statements, because four to six months pass between the extract and the delivery of the printed volume.

The first damage shows up in sales. Internal sales receives calls from customers holding the catalogue page and has to explain why the shop quotes a different price. Field sales leafs through a copy showing a discontinued version. The complaints desk argues about a detail that has been outdated since last autumn. No scandal arises, but a permanent background noise of queries that costs time and erodes trust - particularly when the customer notices the difference first.

The second damage lies in maintenance. Every description is written twice, every image prepared twice, every price change tracked in two places. Anyone looking for causes rarely finds them in technology alone: 50 percent (ECC KÖLN) of the B2B companies surveyed perceive technical questions around the shop as a major challenge, and 52 percent (ECC KÖLN) state that they do not know the needs of their target group precisely. Separate data routes aggravate both, because they double every round of coordination and blur responsibilities.

Catalogue, price list and electronic catalogue are three different things

The print catalogue is an advertising and reference medium with a fixed order, an index and page numbers. The price list is a commercial document with a validity period, a customer group and volume tiers; it can be enclosed with the catalogue or published separately. The electronic catalogue is a data delivery into the customer's procurement system, as described in the article on PunchOut and OCI catalogues. All three draw on the same data set, yet differ in scope, sort order and commitment - much as the digital spare parts catalogue is a view of its own on the same items.

Why the printed catalogue persists in B2B

The catalogue survives out of usefulness rather than nostalgia, because it works in the daily routine of customers. In the workshop, in the warehouse and on the construction site it lies next to the machine, survives dust and gloves and requires no login. The figures support this: among the German companies surveyed with 20 or more employees, 38 percent (Bitkom) still handle about half of their office and administrative processes on paper, 15 percent (Bitkom) work entirely paperless, and 30 percent (Bitkom) send faxes frequently or very frequently. Paper is therefore no fringe phenomenon in the German mid-market but a widespread working medium - and a catalogue is the form in which an assortment on paper stays manageable at all.

A purchasing behaviour pattern adds to this: 67 percent (Gartner) of B2B buyers prefer a rep-free buying experience. A catalogue serves exactly that, because it opens up the assortment without a conversation and prepares entry into the shop - through the item number, a short address or the index. The company online shop remains the important second step: online shops hold their ground with a share of 76 percent (ECC KÖLN) as an important sales channel for manufacturers and wholesalers. Print and shop therefore do not compete, they interlock - much as in turning trade show leads into B2B shop orders.

Aspect	Online shop	Print catalogue
Currency of data	State of today, continuously supplied	State at the data freeze, fixed in place
Price display	Customer price after login	List price with a validity date
Assortment	Search, filters, variants	Fixed order, index, page breaks
Image requirement	Screen resolution, browser colour space	Print resolution, colour profile, bleed
Copy length	Unlimited, expandable	Limited to column width
Correction	Published immediately	Possible until the print sign-off
Traceability	Version state in the system	Edition marker on the printed page

The table also shows where the data source has to deliver more than before. A shop manages with an image in screen resolution, print needs the same shot in print resolution with a defined colour profile. A shop may expand a long description, the catalogue column has a fixed character count. And while a reference to the data sheet is enough in the shop - as described in the article on data sheets and downloads on the product detail page - the catalogue page needs the key values typeset. That poor structure costs money in both channels is evident from where buyers drop off: in the assessment of the companies surveyed, potential new customers often abandon the purchase at the product listing pages, 27 percent (ECC KÖLN), or already after the first impression on the home page, 24 percent (ECC KÖLN).

One source, several outputs: the data model

The rebuild starts with the field, not with the layout. The guiding question is: where is each piece of information maintained as the leading source, and which output may use it in which form? Leading means that exactly one place exists where a value is created and changed; everything else reads it. For the print catalogue this means that no values of its own arise at the typesetter; a delivery arrives that is only arranged there. Six building blocks carry this model.

Item master

Item number, designation, packaging unit, unit of measure, successor item and discontinuation flag. The master record decides whether an item belongs in an edition at all.

Copy per channel

Short text, catalogue text and long text as separate fields with character limits. The catalogue text is written to column width, the shop text may be more detailed.

Technical attributes

Values with unit and tolerance instead of running text. Only structured attributes can be typeset as a table, filtered in the shop and handed to a procurement system.

Classification

A structure following an open standard: ECLASS offers around 48,000 product classes (ECLASS) and more than 23,000 properties (ECLASS).

Prices and terms

List price, volume tier, customer group, currency and validity period. The catalogue price is a view of this data, not a separate record beside it.

Languages and editions

Each language is a variant of the same item, not a copy. That applies to copy, units, number formats and legal notices alike.

Once this model holds, the catalogue becomes a query: take all items of an assortment group that are active on the cut-off date, sort them by catalogue order, and fetch the catalogue text, three attributes, one image and the list price for each item. Whatever is missing is missing visibly - and can be added before typesetting instead of during the correction loop. How such a source is connected to shop, ERP and output channels is described on our page on PIM integration.

What print needs on top of the shop display

A data set that supplies the shop does not yet cover print. Fields are missing that nobody misses on the web because the browser handles them: page breaks, order, resolution, colour space. These fields belong in the same source, otherwise they are created again at the typesetter - and with them a second data set that wants maintaining at the next reprint.

Images in print resolution with a defined colour profile and sufficient bleed, plus a note on which shot is approved for which channel
A catalogue order per assortment group, independent of the sort order in the shop, so that related items sit on the same double page
Catalogue copy with a fixed character limit, because a column, unlike a browser window, does not grow with the text
Footnotes, legends and symbol explanations as fields of their own, for hazard notes, minimum order quantities or differing lead times
Index entries: synonyms, trade names and former item numbers, so that customers find what they are looking for
Page and chapter assignment as a return channel, so that the shop page can later point to the matching catalogue page
An edition marker per item that appears on the printed page and makes queries clearly attributable

Quantity and packaging details are particularly sensitive. A price per 100 pieces is one line in the shop, a column heading in the catalogue and a footnote in the price list - change the reference quantity in one place and it has to change everywhere. How pack sizes, units of measure and minimum order quantities can be modelled cleanly is covered in the article on units of measure and pack sizes in the B2B shop.

The price list: validity, tiers, customer group

The price list is the part of the catalogue with the shortest shelf life and the strongest commitment. It therefore needs fields of its own: a validity start, optionally a validity end, the customer group it applies to, the currency, the unit of measure per price and a note on additional costs and taxes. If one of these fields is missing, room for interpretation arises - and room for interpretation costs money in a dispute, because the recipient invokes the reading that favours them.

Two observations from practice. First, a printed price ages faster than the paper it sits on: producer prices of industrial products in July 2026 were 3.0 percent (Statistisches Bundesamt) higher than in the same month a year earlier, while paper, cardboard and products made from them were 0.4 percent (Statistisches Bundesamt) cheaper over the same period. The procurement side therefore moves independently of the print medium. Second, volume tiers and customer-specific terms do not belong in the printed part but behind the login. How to map both in the shop is shown in the article on price lists and tier pricing in Shopware.

The catalogue shows the list price, the shop shows your price

A proven split: the printed catalogue states the list price with a validity date and refers to the logged-in account for the customer-specific price. That keeps the print file stable, keeps negotiated terms out of open circulation and gives the shop a task that paper cannot take over. A short note plus the edition marker on every catalogue page keeps it recognisable which data state the information comes from.

The released data set as a shared reference point

The key term in this workflow is not catalogue but released data set. It means a dated, versioned snapshot of the data: all items of an edition with copy, attributes, media and prices, fixed in place on a cut-off date. The catalogue is typeset from this snapshot, the price list from the same one, the electronic catalogue likewise. The shop keeps running on current data - but every printed page carries the marker of the state it came from. Every query can then be assigned to a data state instead of to a gut feeling.

Set and announce the data freeze: from this point changes flow into the next edition rather than the current one
Check completeness automatically: missing catalogue copy, images without print resolution, items without classification, prices without a validity start
Technical sign-off per assortment group by the responsible product manager, documented with name and date
Commercial sign-off of the prices by sales, separate from the technical sign-off and with a note of its own
Fix the snapshot in place and give it a marker, such as edition and version, which later appears on every page
Produce a proof, make corrections exclusively in the source and pull the snapshot again instead of patching the layout

The last point is the most uncomfortable and at the same time the most important one. As soon as somebody corrects something directly in the layout, two truths exist again - and the next edition starts with the same error. The same discipline applies at the interface to the ERP, as described in the article on ERP integration in B2B e-commerce: corrections belong at the leading source, otherwise the error travels in a circle and returns with the next synchronisation.

The core in one sentence

What gets signed off is not the catalogue but the data state - the catalogue is merely one of its outputs.

Layout automation: what the machine typesets and what people decide

Layout automation does not mean that a program designs a cover. It means that recurring pages are produced from rules: item tables, attribute blocks, price columns, chapter openers and the index. People decide on design, order and emphasis; the rule handles the repetition. In practice this means a manageable number of master pages from which the bulk of the volume is assembled - typically one master page per assortment logic, not per item. An assortment group with tabular variants needs a different master page than a group with one image per item.

The handover from the data set into the layout software runs through a structured delivery: a markup file per assortment group containing exactly the fields the master page expects, plus the images in print resolution and a sort file. This delivery is produced from the released data set and can be repeated as often as needed; that is precisely what makes reprints, industry-specific extracts and country editions affordable. How such handovers are built, logged and monitored is described on our page on interfaces and data handovers.

From the released state to the print file

At the end there is a file a printing house can accept. That calls for an output format with a defined feature set - commonly a PDF following the PDF/X standard - embedded fonts, an assigned colour profile, correct bleed including trim marks and a resolution matching the printing process. These specifications come from the printing house and belong in the same rule file as the master pages, so that they apply on every run and are not requested anew for every volume.

Two steps before that are worthwhile. First a soft proof for the editorial check and a colour-binding proof for signing off the colours; both are checked against the edition marker rather than against a memory of the last edition. Second, archiving: print file, data snapshot and sign-off record belong in one place. If a query about a printed detail arrives months later, the answer is then a search and not a reconstruction from recollections and mailboxes.

The same state also serves your customers' procurement systems

Whoever tidies up the data set for print has already done the groundwork for the electronic catalogue. Procurement systems at larger customers expect classified item data with attributes, units and prices. For that, ECLASS organises around 48,000 product classes (ECLASS) across four classification levels (ECLASS), so that an item can be filed unambiguously. The handover happens either as a catalogue file or as a direct connection to the ordering system, as described on our page on PunchOut and OCI.

The same data set carries further obligations. Product-related details on material, origin and service life are required by the digital product passport under the ESPR, while details on security properties and support periods are demanded by the rules of the Cyber Resilience Act. Both requirements presuppose structured fields - the very same ones the catalogue needs. Set them up once properly and one maintenance effort serves several purposes.

Rolling it out in stages

The rebuild can be managed within one catalogue season if it runs in the right order. The leverage is considerable: manufacturers and wholesalers already generate 12.1 percent (ECC KÖLN) of their total revenue via online shops and marketplaces. Every improvement to the shared data basis therefore acts on both channels at once - on the printed volume and on the channel that carries the larger part of digital revenue.

Take stock: which fields exist, where are they maintained, which ones only come into being at the typesetter? The result is a field list with one owner per field.
Close the gaps: catalogue copy with a character limit, images in print resolution, classification and catalogue order are added - initially for one assortment group as a pilot.
Introduce the sign-off process: data freeze, automated check, technical and commercial sign-off, snapshot with a marker.
Build the export: a repeatable delivery from the released data set into the layout software, plus the price list output and the catalogue file for procurement systems.
Extend and measure: connect further assortment groups, then compare lead time, correction rounds and queries coming from sales.

Sensible metrics are the time from data freeze to print sign-off, the number of correction rounds, the share of items that pass the automated check on the first attempt, and the number of queries relating to diverging details between catalogue and shop. Anyone printing several country editions additionally measures the effort per edition; the considerations for that are set out in the article on country-specific B2B shops. If you would like to move from separate catalogue maintenance to a shared source, we are happy to discuss the first step - get in touch.

Sources and Studies

This article is based on data from Bitkom, ECC KÖLN, ECLASS, the German Federal Statistical Office (Statistisches Bundesamt) and Gartner. The figures cited refer to the status at the time of the respective publication.