Start here
For a recurring product catalog, keep one structured spreadsheet as the source of truth, map it into a reusable template, and validate a small export before publishing. A hosted catalog builder is the simpler starting point; InDesign automation makes more sense when layout control is central to the work.
Start with the publishing job, not the design app
A weekly wholesale price list and an annual brand book are different jobs. Write down how often prices change, who updates them, how many products appear, and whether customers receive different prices. A small business with one operator should count template maintenance and training as part of the cost. A beautiful layout that only one contractor can update may be a poor fit for weekly changes.
Before choosing software, collect the current spreadsheet and one real catalog. Mark every field that changes: price, pack size, availability, image, description, or ordering code. This reveals whether you need data publishing or simply a better document template.
Prepare a spreadsheet that can survive the next update
Give every sellable item a stable SKU. Keep product name, pack quantity, unit, currency, and price in separate columns. A price of 24 means little without knowing whether it describes one item or a case of twelve. Avoid merged cells, decorative headings inside the data range, and formulas whose meaning depends on a hidden sheet.
Keep image references stable and record which products should be excluded. Preserve a dated copy of the source data for each publication. If a customer questions a price later, you should be able to identify the exact sheet used for that PDF.
Two existing routes worth evaluating
Catalog Machine offers spreadsheet import, catalog templates, and an AI assistant. It is a useful first trial when you want a hosted workflow without building a publishing system. Test the actual update path, not just the first catalog creation.
EasyCatalog works inside InDesign and is aimed at data-driven publishing. Evaluate it when an experienced designer needs a controlled layout connected to product data. Ask who will maintain the template and what happens when a category becomes longer. A simpler layout may also be possible with InDesign’s own data merge; do not assume a specialist plugin is necessary for every catalog.
Run a deliberately awkward pilot
Use ten products with different conditions: a long name, a missing photo, a discontinued SKU, a decimal price, an unusually large pack, and a category boundary. Export the catalog, change three prices in the source, and generate it again. Verify that old prices have disappeared and that nothing has shifted outside the printable area.
If you produce customer-specific prices, run two customers through the same test. Check that file names and distribution folders cannot mix them up. This is a workflow check, not something an attractive demo can prove.
Make publication a repeatable checklist
Check SKU count, currency, pack units, missing prices, image quality, and the publication date. Open the exported PDF on another device and print a representative page if customers print it. Keep the previous version with its source sheet. Publish only after a human approves the business data.
AI can help map inconsistent column names and flag suspicious rows. It should not silently invent a missing price, guess a pack size, or decide which customer gets a discount. Those decisions belong in explicit rules or a review step.
Sources
- Catalog Machine features and plans
- EasyCatalog product documentation
- A small wholesaler describes the workflow
Updated October 30, 2026. Based on the linked documentation; the tools have not been benchmarked by NarrowTools. Editorial policy
