Build a Product Catalog Generator in Notion

{/ synced-from-notion — do not edit manually /}

A product catalog generator can turn the product details you already track in Notion into a repeatable PDF workflow. Set up clean product records, map them to a catalog template, then generate a file when you need one.

Step 1: Decide What Your Product Catalog Needs to Show

Start with the reader and the job the catalog must do. A wholesale buyer may need product codes and case details. A customer-facing catalog may need clear descriptions, prices, and a way to find more information.

Write down the fields before you build the database. Common choices include a product name, SKU, description, price, category, and image. Add discounts or tags only when they help someone choose or identify an item. A short catalog for a sales meeting may need fewer fields than a full seasonal range.

Keep the source data tidy. Use one record per product, and give each property a clear name. If details live in a spreadsheet, clean up its column headers and remove duplicate rows before bringing the data into Notion. You can import spreadsheet data into a Notion database, then review each field and set the right property type.

A product catalogue template in Notion’s template gallery can help you think through how product records might be arranged. Treat it as a starting point. Your fields should match the questions your buyers ask.

Think about updates, too. If prices or descriptions change, decide who edits the Notion record and who checks the next PDF. A generated file reflects the data used when it was made, so plan to create a fresh version after a meaningful change.


Milestone: You should have a short field list and a clear rule for who keeps each product record current.

Step 2: Build a Product Database in Notion

Make one database the source of truth for the catalog. Add a product page for each item, then create properties for the fields you chose in Step 1. For example, use a title property for the product name, a text field for the description, and a number field for price.

Bring in spreadsheet rows when that saves manual entry. Before importing, check that each column has a single purpose. A column called “Price” should not mix prices with notes such as “ask for quote.” Keep those values in separate fields so the catalog layout can handle them consistently.

Set up extra databases only when the information is shared or has its own workflow. You might keep suppliers in a separate database and link each product to its supplier. In Notion, a relation connects records across databases. A rollup displays selected information from related records, such as a supplier name. PDFOutput can work with connected databases and relation or rollup properties in an output.

Use a status property to track the catalog work. For instance, records can move through “Draft,” “Ready for review,” and “Approved.” That gives your team a simple check before anyone produces a customer-facing PDF. It also helps staff spot items with missing descriptions or prices.

Set up a filtered view for products that are ready to include. Then test the view with a few records. If a field is blank or formatted in an odd way, fix it in the database before you design around it.

A reusable layout works best when the source is organized. See our document template guide for more on reusable layouts.

> 💡 Pro Tip: Keep the property names steady once you begin mapping them. Renaming a field can mean you also need to update the matching placeholder in your template.

Milestone: You should have a small set of test records with consistent product data and a clear review status.

Step 3: Create a Catalog Template with Product Placeholders

Build the page layout before connecting the automation. A catalog template sets the order and style of information, while placeholders mark where Notion values should appear. PDFOutput accepts templates as a Notion page, Google Doc, Word file, or existing PDF.

Plan a repeatable product block. Put the product name near the top, followed by its description and key facts. Leave room for the image and price if those belong in your catalog. For a long product range, use the same order for every item so readers can scan each entry quickly.

In the template, add placeholders in double curly braces using the exact database property names. If the property is named Product_Name, use {{Product_Name}}. The same rule applies to spaces, capitalization, and underscores. A placeholder with a different spelling may not match the field you intended.

For example, a product block could include {{Product_Name}}, {{SKU}}, {{Description}}, and {{Price}}. Keep fixed labels such as “Item number” outside the placeholder. That way, the template controls the wording while Notion supplies the changing value.

PDFOutput’s template approach uses matching placeholders to replace template text with database values. You can see the available PDFOutput document templates for examples of reusable layouts, including a product specification sheet. Keep the design readable at the size people will view or print it.

AI can help draft product descriptions or suggest shorter headings, but treat those drafts as copy to review. Confirm claims, product specs, and prices against your source records. A polished sentence cannot fix a wrong product fact.


Milestone: Your template should have a consistent product layout, plus placeholders that match the Notion property names exactly.

Step 4: Trigger Catalog Generation from Notion with PDFOutput

Connect the database and template in PDFOutput, then map the product fields to their placeholders. Choose the database that holds the catalog records. If the template uses data from related databases, connect those too and check the relation or rollup fields you plan to include.

Set up the output details, including the file name and where generated files should be stored. PDFOutput can return generated files to a Notion database property. It can also save output in Google Drive when that option is set up. Use a file name that helps your team identify the catalog, such as a catalog title or edition name.

PDFOutput uses Notion database controls to start document generation. A database button can trigger a file when someone needs it. The GeneratePDF status property can also start generation when you set a record to “Ready to Generate.” This is useful when a staff member finishes checking a product and wants to make its catalog file from the record.

Other status options support different outputs: “Generate Page” converts a Notion page to PDF; “Generate PDF and Doc” creates a PDF and Google document; “Generate E-Signed Doc” creates an e-signed PDF; and “Preview” creates a Google document preview before PDF generation. Choose the status that fits the document you need, rather than asking every team member to follow a different manual process.

PDFOutput’s site describes the product as a PDF generator for Notion using Google Docs, PDF, and Word templates.

Before you switch on the workflow, generate a preview from a record with real product data. Check the layout and confirm that each placeholder shows the right value. Fix field names or source data before you process more records.

Milestone: You should have one working test file and a trigger your team can use from the Notion database.

Step 5: Generate, Review, and Share Catalogs at Scale

Once the preview looks right, generate a few records and inspect the results. Check product names, descriptions, prices, and any details pulled from related databases. Look for blank fields or text that runs past its space. Correct the source record or template, then generate the file again.

When the layout is stable, process a larger set of records. PDFOutput supports batch PDF creation, PDF merging, and work across multiple databases using relations and rollups. That can help when a catalog combines products with supplier details or other linked information. Review a sample from each group before sharing the whole set.

Keep the approval step clear. A staff member can mark records ready only after checking the product information. Another team member can review the generated PDF before it goes to buyers. This small pause helps catch a changed price or an old description before the file leaves your team.

For a catalog that needs videos, slideshows, or shopping buttons, plan those as part of a separate digital viewing experience. A generated PDF is suited to a fixed document layout. You can still use the template to present product details in a clear order, but don’t assume that a video or slideshow will behave like an interactive web page inside the PDF.

Share the finished PDF through the channel your buyers already use, such as an email attachment or a shared file link. If you need a QR code, make sure it points to a current destination and test it before printing or distributing the catalog. If product data changes later, make a fresh PDF and replace the old copy wherever your team shares it.

A product catalog generator is most useful when records change often or staff need the same layout for many products. If you make a one-off catalog with only a few items, a manual document may take less setup. For recurring catalogs, our guide to choosing PDF creator software for Notion can help you assess the document workflow you need.

Milestone: You should have a review rule, a repeatable trigger, and a clear way to replace outdated catalog files.

FAQ

Can I make a product catalog from a Notion database?

Yes, you can use a Notion database as the source for a catalog PDF. Add product properties, make a document template with matching placeholders, then connect the database and template in PDFOutput. Generate a preview first. That lets you check the mapped values and layout before creating files for more records.

Can I import product data from a spreadsheet into Notion?

Yes, you can bring spreadsheet data into a Notion database and use the imported rows as product records. Clean the sheet first so each column holds one kind of data. Then check the imported property types and correct any values that landed in the wrong field before you map them to the catalog template.

Can the catalog update when a Notion product record changes?

A generated PDF is a document made from the record values used at generation time. If you change a product record later, generate a new file to reflect the updated details. Set a team rule for when to regenerate catalogs, especially after changes to price, product availability, or key descriptions.

Can PDFOutput generate several catalog PDFs at once?

Yes, PDFOutput supports batch PDF creation. You can also merge PDFs and use information from connected databases through relations and rollups. Test the template with a few records before a larger run. That helps catch a field-mapping or layout issue before it affects a full batch.

Can a Notion catalog PDF include videos or shopping buttons?

A PDF is a fixed document, so don’t plan on it working like an interactive catalog website. Use the PDF for a stable, shareable product document. If buyers need video, slideshows, or shopping controls, plan those in a separate digital experience and make sure the PDF points readers to the right place.

Conclusion

Build the database and template around the product details your buyers need, then test one PDF before scaling up. If your team already works in Notion, set up a small PDFOutput workflow with a few records and review the output before using it for a full catalog.