How to Create a Product Catalog from Excel

patbensky
5 days ago
7 min read

You can create a product catalog from Excel by organising your product data into clear columns, cleaning the records, deciding how the catalog should be grouped, mapping spreadsheet fields into a page layout, and then publishing the result as a catalogue or price list. The key is to treat the spreadsheet as structured data, not just text to copy and paste.

Introduction

If your product information already lives in Excel, you are halfway towards a catalog. The hard part is turning rows and columns into attractive pages that people can actually read, use, and trust.

Many businesses start by copying product codes, descriptions, prices, and images from a spreadsheet into a document by hand. That works for a small list. It becomes painful when the catalog grows, prices change, or you need to produce a new version every month, season, or year.

A better approach is to build a data-driven catalog workflow. Your spreadsheet remains the source of the product information, while your publishing process turns that structured data into consistent catalog pages.

Why Excel is a good starting point

Excel is familiar, flexible, and easy to update. Most teams already know how to add rows, correct descriptions, filter products, and update prices. That makes it a useful starting point for product catalog publishing.

The problem is that Excel is not a finished catalog. It is a data source. A catalogue needs structure, hierarchy, formatting, section headings, page flow, image placement, and sometimes different versions for different customers or markets.

Excel works best when you use it for what it is good at: storing structured product information. A catalog publishing tool or workflow should then handle the job of turning that information into pages.

Prepare your spreadsheet before publishing

Before you try to make a catalog from Excel, check the spreadsheet structure. Clean data makes the whole publishing process easier, whether you are using CatBase, another database publishing tool, or a more manual workflow.

Use one row per product

Each row should usually represent one product, item, part, listing, or record. Avoid putting several products into one row, because that makes sorting, grouping, and formatting much harder later.

Use one column per field

Separate the information you may need to format separately. For example, do not combine product name, size, colour, and price into one cell if those details need to appear in different places in the catalog.

Useful columns often include:

Product Code: The unique item or SKU reference.
Product Name: The product name that should appear in the catalog.
Category: The section or group where the item belongs.
Short Description: A concise product description.
Long Description: Optional longer copy for detailed entries.
Price: Retail, trade, wholesale, or customer-specific price.
Unit or Pack Size: Useful for B2B catalogs and price lists.
Specifications: Dimensions, materials, compatibility, colour, finish, or technical data.
Image Reference: File name, path, SKU-based reference, or image identifier.
Sort Order: A field that controls the order of products within a section.
Status: Active, discontinued, seasonal, new, or excluded.

Keep categories consistent

Small spelling differences can create big publishing problems. If one row says “Accessories,” another says “Accessory,” and another says “accesories,” your catalog workflow may treat them as three different sections.

Before publishing, scan your category fields and standardise the names. This is especially important if you want automatic section headings or grouped product pages.

Check prices and effective dates

If your catalog includes prices, you might want to add an effective date or price-list version where possible. This makes it easier to know which data was used for the published catalog and helps avoid confusion when prices change later.

Decide what kind of catalog you need

Not every Excel-to-catalog project needs the same output. Before choosing a workflow, define the publication you are trying to create. For example:

Product catalog

A product catalog usually includes product names, codes, descriptions, categories, images, and sometimes prices. It may be designed for customers, distributors, sales teams, or internal reference.

Price list

A price list may be simpler than a catalog, but it often changes more frequently. It may need product codes, descriptions, trade prices, retail prices, customer groups, currencies, and effective dates.

Parts catalog

A parts catalog may need technical details, compatibility notes, diagrams, part numbers, categories, and cross-references. Data structure matters because readers usually need to find exact items quickly.

Directory or listing publication

Excel can also be used for non-product publications, such as supplier directories, membership directories, exhibitor guides, telephone directories, or advertiser listings. The same principle applies: structured records become formatted pages.

Choose a catalog structure

Once your spreadsheet is tidy, decide how the catalog should be organised. This is where the spreadsheet begins to become a publication.

Group by category

Most product catalogs are grouped by category, product range, brand, department, or application. If the category field is clean, it can drive the catalog structure.

Sort products intentionally

Do not rely on the accidental order of rows in the spreadsheet. Add a sort field if you need products to appear in a specific sequence. This gives you more control and makes future updates easier.

Decide what appears in each entry

A compact catalog entry might include only product code, name, and price. A more detailed entry might include an image, description, specifications, variant table, and notes.

This decision affects the spreadsheet too. If you want the catalog to show a specification table, those specifications need to exist as clean fields in the source data.

Map spreadsheet fields to catalog content

The next step is mapping each Excel column to part of the catalog. This is the point where data publishing becomes more powerful than manual copy-paste.

For example:

Excel column	Catalog use
Category	Section heading
Product Code	Product reference
Product Name	Product title
Short Description	Catalog description
Price	Price column or price line
Image Reference	Product image
Specifications	Technical details
Sort Order	Product sequence

Once the fields are mapped, the catalog can use the same logic repeatedly. Instead of formatting each product one by one, you define how product records should appear. If you are using a database publishing app, such as CatBase, you'll map the spreadsheet columns to the database tables and fields suring the importing process.

Add images without losing control

Images are often the part of catalog publishing that causes the most frustration. The spreadsheet should not contain the images themselves unless your workflow specifically supports that. It is usually better to store an image reference.

An image reference might be:

A file name, such as ABC123.jpg.
A folder path.
A product code that matches the image name.
A database image reference.
A URL or asset ID, depending on your workflow.

Whichever method you use, keep it consistent. If your product code is ABC123, do not let the image be called abc-123-new-final2.jpg unless you have a clear mapping rule.

Avoid common Excel-to-catalog mistakes

Mistake one: treating the spreadsheet like finished copy

Excel data should be structured so it can be reused. If you cram formatted paragraphs, prices, dimensions, and internal notes into one cell, the catalog will be harder to automate.

Mistake two: mixing live and old products

Use a status field to identify active, discontinued, hidden, or seasonal products. This makes it easier to exclude records without deleting historical data.

Mistake three: using inconsistent image names

Image naming should be boring and predictable. A consistent naming system saves time when the catalog is generated or checked.

Mistake four: forgetting version control

If prices change frequently, keep track of the spreadsheet version or effective date used for each publication. This helps when someone asks why a price in an old PDF differs from the current spreadsheet.

Mistake five: rebuilding the catalog manually every time

The biggest mistake is using Excel as the data source but still copying everything into pages by hand. If the catalog will be updated again, it is worth planning a repeatable workflow.

When a simple template is enough

A simple template may be enough if your catalog is small, rarely updated, and does not need complex sections or different versions. For example, a 20-item product sheet may not need a full database publishing workflow.

But a template becomes limiting when the catalog has hundreds of records, frequent price changes, multiple product groups, different customer versions, images, tables, or recurring editions. At that point, the spreadsheet needs to become part of a proper data publishing process.

How CatBase helps

CatBase is designed for data-heavy publishing projects where structured information needs to become formatted pages. If your product catalog starts in Excel, CSV, XML, or a database, CatBase can help you think about the workflow as data publishing rather than manual page assembly.

That means:

Using your spreadsheet or database as the source.
Organising records into sections and groups.
Mapping fields into catalog entries.
Supporting repeatable publication structures.
Making updates easier when product data changes.
Using similar workflows for catalogs, catalogues, price lists, directories, and parts lists.

The aim is not just to make one catalog. The aim is to make the next catalog easier.

Example workflow

Here is a practical Excel-to-catalog workflow using a database publishing application such as CatBase:

Audit the spreadsheet: Check columns, categories, prices, image references, and product status.
Clean the data: Remove duplicates, standardise categories, and separate mixed fields.
Import the spreadsheet into the database: Map the spreadsheet columns to tables and fields in the database. Here's how to do it with CatBase.
Choose the catalog structure: Decide sections, sorting, entry style, and required outputs. In catBase, this means setting up one or more Publishing Stylesheets.
Generate the catalog pages: Use a data publishing workflow to create consistent entries.
Review the output: Check formatting, images, prices, section breaks, and missing data.
Publish the catalog: Produce the required PDF, print, or production-ready output.
Reuse the workflow: Update the data and repeat the process for future editions.

Final thoughts

Creating a product catalog from Excel is not just about exporting a spreadsheet. It is about turning structured data into a useful publication.

If your catalog is small, a simple template may be enough. If it is large, changes often, or needs to be produced repeatedly, a database publishing workflow can save time and reduce errors.

CatBase helps bridge that gap: your data stays structured, and your catalog becomes easier to publish, update, and reuse.

Have an Excel file that needs to become a catalog?

If your product catalog, price list, or directory starts in Excel, CatBase can help you explore a more repeatable publishing workflow.

Why not ask us to help?

Book a free live demo! We'll do a screen-sharing session with you to show you how CatBase works and discuss how it could help with your project.