Catalog automation 9 min read

How to Build a Product Catalog from Excel with InDesign Data Merge

Three hundred products, one spreadsheet, zero desire to copy and paste for a month. Here is how Data Merge turns Excel into catalog pages, and where it stops being helpful.

Illustrative catalog page layout with repeating product blocks

Picture the situation. Your price list lives in a spreadsheet with 300 rows. The new catalog needs every one of them: photo, name, article number, three specifications, price. Someone suggests “just paste it into InDesign”. Four hours later you are on product number 23, the sixth typo has just been found, and the supplier has sent a new price file.

This is the moment Data Merge was made for. It is a tool that has been sitting inside InDesign for years, and most people have never opened it. This guide walks through how a catalog is built with it, where it saves days of work, and where it quietly falls apart.

Menu names below follow current versions of InDesign. Older versions may label things slightly differently.

Is your catalog even a good fit?

Data Merge likes repetition. If your catalog is a grid of identical product cards, where only the text and the picture change, it will feel like magic. Spare parts, electronic components, fasteners, apparel line sheets and distributor price books all fit.

If every page is a one-off composition, with big photos, stories and custom layouts, skip it. You would spend more time fighting the tool than designing.

A simple test: sketch one product card on a napkin. Can you imagine 300 copies of it with different words inside? Then keep reading.

Step 1. Make the spreadsheet boring

Here is the uncomfortable truth: most Data Merge disasters start in Excel, not in InDesign. A “boring” spreadsheet is the goal.

  • One row, one product. No merged cells. No empty separator rows. No category titles squeezed between products.
  • One fact per cell. If “12 V, 2 A, IP65” sits in one cell, it will stay glued together on the page.
  • Short, plain column names. SKU, Name, Power, Price. Skip line breaks and exotic symbols in the header.
  • Values, not formulas. Copy and paste as values before saving, so InDesign sees exactly what you see.
  • One style of numbers. Dot or comma, units in the header or in the cell. Pick once and stick to it.

Save the file as CSV. If accented or non-Latin letters turn into hieroglyphs after the merge, save it again as tab-delimited Unicode text. That fixes the encoding problem in most cases.

Step 2. Teach InDesign where the pictures live

Data Merge can drop product photos into frames on its own. It needs two small things from you.

The header of the picture column must start with @. So @Image, not Image. That single symbol tells InDesign “this is a file, not a word”.

Each cell holds the full path to the file. Windows and macOS write paths differently, so build the column with a formula in your spreadsheet and test one record before merging all of them.

A few habits that pay off later:

  1. Put every image in one folder and name each file after its SKU.
  2. Shoot or crop products in one consistent size on one consistent background.
  3. Do not rename or move the folder afterwards. The document links to files, and moving them breaks the links.

Step 3. Build one card, not three hundred

Open a new document with the final page size and margins, then:

  1. Go to Window → Utilities → Data Merge.
  2. Choose Select Data Source and pick the CSV. Your column names appear in the panel.
  3. Draw the frames for one product card: an image frame and text frames for name, SKU, specs, price.
  4. Drag each field from the panel into its frame. Text turns into <<Name>>-style placeholders, pictures into linked placeholders.
  5. Apply paragraph styles and object styles to everything now, before merging. Styles are what keep the finished catalog consistent and fixable.

Tick Preview and click through the records. This is when you meet the one product whose name is three times longer than the rest. Better to meet it now than on page 87.

Step 4. Press the button

Click Create Merged Document. Three areas in the dialog matter:

  • Records. Choose Multiple Records if you want several cards per page, and decide which records to include.
  • Multiple Record Layout. Set margins and the gap between cards. InDesign tiles your single card across the page.
  • Options. Keep Link Images on, choose how pictures fit their frames, and consider Remove Blank Lines for Empty Fields so missing values do not leave holes.

You get a new, separate document. Keep that in mind, because it leads straight to the next section.

Where Data Merge lets you down

It is worth knowing the weak spots before you promise anyone a “fully automatic catalog”.

  • It does not understand sections. There is no “category” concept. A heading like Hydraulic pumps means a separate merge per category, or a script.
  • It does not think. “Show a SALE badge only if there is a discount” needs extra work.
  • Cards have a fixed height. They will not stretch to fit a long description. The text overflows instead.
  • Tables of different lengths are awkward. A product with 3 spec rows and another with 15 will not share one neat layout.
  • The result is frozen. Change the data and you merge again. Hand edits inside the merged file disappear on the next run.

When a catalog needs these features, people reach for scripts, XML import with tagged styles, or a hybrid approach: Data Merge builds the bulk of the pages and the rest is finished by hand.

A workflow that survives the next price change

Teams that update their catalog every season usually end up here:

  1. The spreadsheet is the boss. Every price and spec change happens there. Never in the layout.
  2. The template is its own file, with locked styles.
  3. Merge category by category, so each section starts on a fresh page with the right heading.
  4. Hand work comes last. Cover, intro and special spreads are touched only after the final merge.
  5. Export at the very end: print PDF and web PDF.

Do it this way and a price update becomes “edit one column, run the merge, check the pages” instead of reopening 200 pages one by one.

Quick fixes for the usual suspects

SymptomUsual causeWhat to do
Red question marks instead of photosWrong path, or the header has no @Check the first record’s path by hand, then fix the column
Text turns into random symbolsEncoding mismatchSave again as Unicode text
Text spills out of its frameLong names or spec listsAllow two lines, shorten the data, or use a smaller style for long values
Gaps where a value is missingEmpty cells in the dataTurn on Remove Blank Lines for Empty Fields or fill the column
Badly cropped picturesInconsistent source photosStandardize image sizes or adjust the frame’s fitting

Do it yourself or hand it over?

For one catalog of 60 products, learning Data Merge over a weekend is realistic. For 500 products that change twice a year, the real work is the template and the data rules. A shaky template turns every update into a small crisis, and the saved hours become lost hours.

We build data-driven catalogs from Excel, CSV and ERP exports, with templates your own team can reuse. See how it works on the catalog automation page, or send the catalog brief with a sample of your spreadsheet and we will tell you what is realistic.

Keep reading

Related services and guides

Catalog layout from ExcelHow to prepare product data for a catalogSpare parts catalog design
Have a project?

Let’s discuss
your project ?

Tell us about the task. We will clarify the requirements and recommend the most suitable format.

Privacy Policy