How to Create a Catalog Without an Account
● Local processing
This guide explains a repeatable workflow that works with the catalog maker and can also be applied to existing product data.
Start with a clear purpose
How to Create a Catalog Without an Account begins with defining the audience, the publication format and the action readers should take. A wholesale list needs compact SKUs and net prices, while a lookbook needs larger imagery and less text. Decide what must be visible on every product card before importing data.
Use a small test set first, verify the result and only then process the full catalog.
Prepare reliable source data
Use a stable identifier such as SKU, EAN or an internal ID. Keep names, categories, prices, descriptions, image filenames and links in separate columns. Consistent source data makes later price updates safer and prevents manual page corrections from being overwritten.
Use a small test set first, verify the result and only then process the full catalog.
Build and review the layout
Import the spreadsheet, verify the field mapping and select a suitable products-per-page layout. Check long names, missing images and unusually large descriptions. Lock pages that were adjusted manually before running automatic layout again.
Use a small test set first, verify the result and only then process the full catalog.
Export for the right channel
Use PDF for printing or email, PNG for individual pages and interactive HTML for searchable offline browsing. Review image resolution, margins, active links and the final file size. Keep the project JSON as an editable backup.
Use a small test set first, verify the result and only then process the full catalog.
Common mistakes
Typical problems include duplicate SKUs, outdated prices, promotional prices without a clear reference, inconsistent units and images with insufficient resolution. The catalog checker can identify many technical issues, but the author remains responsible for legal, tax and product information.
Use a small test set first, verify the result and only then process the full catalog.
Privacy and repeatable updates
The catalog can be built locally without uploading product data or images. When prices change, import a new spreadsheet in update mode and match rows by the same unique key. Review the difference report before applying changes.
Use a small test set first, verify the result and only then process the full catalog.
FAQ
Do I need an account?
No. The project is designed for local browser use.
Should I keep a backup?
Yes. Export the project JSON before clearing browser data.