Skip to content
UseQR
ESC

Jump to

↑↓MOVE↵OPEN50 places

Ecommerce & retail

QR codes for wholesale catalogues

A wholesale catalogue works harder when every SKU carries a QR code linking a prefilled order line: SKU and pack size in the URL, landing in your B2B portal's order form. Buyers reorder from the printed page in seconds, and codes generated from the same spreadsheet that builds the catalogue stay in sync.

View as MarkdownPaste this page into any AI assistant. It is plain, portable Markdown.

The reorder gap in printed B2B

Printed catalogues persist in wholesale for a good reason (a buyer flipping a line sheet at a desk or a trade-show table moves faster than any website), but they end at the worst moment: the buyer has chosen, and now must retype SKUs into an email or portal. Every retyped SKU is a delay and a transcription error waiting to become a mis-shipment.

The per-SKU QR code closes the gap. Next to each product entry, a small code carrying the SKU into your order flow:

orders.example.com/add?sku=KT-2041&pack=6

Scan, and the B2B portal opens with that line prefilled, quantity picker, live price for the logged-in account, stock position. The buyer works through the catalogue scanning what they want; the printed page becomes the order form. For buyers without portal accounts, the same URL can fall back to a quote-request form with the SKU already in it.

Generating codes that stay in sync

The catalogue and its codes must come from the same source of truth, or a reprint will ship codes pointing at dead SKUs. The workflow that holds up:

  • The product spreadsheet that feeds the catalogue layout also generates the code URLs, one column concatenating the order-URL pattern with the SKU.
  • Run that column through the bulk generator or the spreadsheet workflow; at scale, POST /api/v1/qr/batch takes up to 1,000 items per request and returns images your layout tool places by filename.
  • SVG output for print catalogues: codes get resized during layout, and vector survives what raster does not.

Size: catalogue pages are read at 30–40 cm, so 2 cm codes work; going below 1.5 cm to save layout space starts costing scans, per the 10:1 rule. Keep payloads short: the SKU parameter, not a full product description.

Three catalogue variants, one system

  • The annual catalogue: full range, long shelf life. URL discipline matters most here: catalogues live on buyers' shelves for years, so order URLs must be stable paths you maintain, with discontinued SKUs redirecting to their replacement, the permanence rules apply to B2B print in full.
  • The line-sheet PDF, emailed seasonal sheets. The same codes work on screen (a phone scanning a laptop display) and the PDF's own links can carry the same URLs; adding codes to a PDF covers the mechanics.
  • The trade-show edition, the catalogue that walks away from your stand. Tag its codes with a distinct campaign parameter so post-show orders attribute to the show; the trade-show playbook covers the wider stand setup, and offline-to-online measurement covers what the numbers mean.

What not to encode

Do not put prices in the code or on its landing page unauthenticated: wholesale pricing is account-specific and confidential, and a catalogue code that exposes trade prices to anyone who scans it is a real leak. The code carries the SKU; the portal shows prices after login. Verify a printed proof of the final catalogue before the run, one wrong URL pattern multiplied by 400 SKUs is an expensive reprint.

FAQ

An order URL carrying the SKU and pack size, landing in your B2B portal with that line prefilled for the logged-in account. Buyers order from the printed page without retyping SKUs, which removes transcription errors.

How do I generate hundreds of SKU codes for a catalogue?

From the same spreadsheet that builds the catalogue: a column of order URLs run through a bulk generator or batch API, output as SVG for print layout. Single source of truth keeps codes and pages in sync across reprints.

Should prices be visible behind catalogue QR codes?

Not without login. Wholesale prices are account-specific and confidential; the code should carry the SKU only, with the portal showing prices after authentication. An unauthenticated price page is a leak to competitors.

How big should QR codes be in a printed catalogue?

2 cm square for a page read at arm's length, with a full quiet zone. Below about 1.5 cm scan reliability drops, and dense pages tempt exactly that mistake: budget the space per SKU entry from the start.

Try it: free, no signup

Related