PDF Generation: generate automatic PDF catalogs from product data
Before creating the automation, verify that both conditions are met:
Product attributes are configured and values are filled in for all languages you want to export. It is also important to already have a Completeness Marker applied to the products to include in the PDF catalog.
With the PDF Generation automation (powered by Cloud2Print), THRON generates updated PDF catalogs directly from the product data present on the platform. Any change to attributes or images is automatically reflected in the PDF at the next execution — without manual copy-paste.
Note: Currently, the automation supports product selection exclusively via Markers. Selection via advanced filters is being evaluated for future evolutions.
Don't have a Marker yet? → What are Completeness Markers and how to configure them
Create the automation
- Go to Platform Settings → Flows & Automations → Automations.
- Click on New and select PDF Generation (with Cloud2Print).
This choice determines the available configuration steps and sets the output format to PDF.
Configure the main metadata
| Parameter | Mandatory | Notes |
|---|---|---|
| Name | ✅ | Use a logical and recognizable name (e.g., Vendor Catalogue, IT Technical Catalog) |
| Automation Owner | ✅ | The selected user is impersonated during execution: their permissions apply to all operations and they appear as the author of the generated PDFs |
Configure the destination
Define where PDFs are saved and how they are linked to products.
| Parameter | Mandatory | Notes |
|---|---|---|
| Catalogue Destination Folder | ✅ | Library folder where the generated PDFs are stored |
| Catalogue Destination Media Attribute | ✅ | Product media attribute through which the PDF is made available. The catalog is not only archived: it is dynamically linked to products via this attribute |
Select export languages
In Export to the following locales select one or more locales (e.g. it-IT, en-US, de-DE).
The automation generates a distinct PDF for each locale, reflecting the localized values of the product attributes.
Set the execution trigger
Choose the automation execution frequency:
- Every day
- Every week
- Every first of the month
At each execution the system checks if there are variations that require the generation or update of the catalog.
Configure product selection
Selection via Marker
In Products to be used select the Marker to use as an inclusion criterion. You can use only one Marker per automation.
Set the condition on the Marker (e.g., Marker ≥ 80%): only products that meet the threshold are included in the catalog.
Note: The configuration is locale-aware. Each locale is validated separately. If the selected Marker is also present in the second language to be configured, the field is automatically pre-filled. If the Marker is not configured for a specific locale, the system reports an error.
Generate the catalog only if all attributes are filled
Activate the option Generate catalogue only if all attributes are filled in to avoid creating catalogs with empty fields.
Note: This option is automatically activated if you select a Marker set to 100%.
Select the PDF template
Choose the template
Select the template from the available library. Each template has a preview with fillable fields and the type of content accepted (image, text, etc.).
Templates available by default: Product Tag, Tabular Datasheet, Technical Data Sheet, Spare Parts.
Available templates are reference placeholders, designed to cover the most common use cases. If you have specific layout needs — custom structure, corporate branding, dedicated sections — click on "Request your custom template": the team will evaluate feasibility and details with you, and the template will be included in a dedicated automation.
Map attributes to the template
The mapping associates each template field to the corresponding THRON attribute. It is a mandatory step: without mapping, the system does not know what value to insert in each field.
Mapping rules:
- If the attribute is localized, the value in the local configuration language is taken by default.
- If the attribute is of type Media Gallery, specify the position of the asset within the gallery (integer indicating positioning).
- Fields left empty in the mapping are removed from the template: it is not mandatory to fill in all spaces.
⚠️ Warning: If products and attributes are not yet mapped to the template, the system shows a warning message. Complete the mapping before activating the automation.
How execution works
At each scheduled run, the system checks for variations requiring regeneration:
- Product attribute update → any modification compared to the last execution triggers regeneration.
-
Image update → the system checks
last modifiedandcontent ID; any variation leads to regeneration. - Adding new products → products meeting the criteria are automatically included.
- Versioning → in case of relevant modifications, a new version of the existing PDF is created, not a new separate file. Versioning is active from the second generation onwards.
Execution report
At the end of each run, THRON automatically generates a report:
| Field | Description |
|---|---|
| Product ID | Identifier of the processed product |
| Content ID | List of involved content IDs, if any |
| Generation outcome |
OK or Error
|
| Reason for error | Failure detail |
Possible errors: unable to access the product · unable to retrieve all attributes (when the full generation toggle is active) · PDF generation error received from the provider (Cloud2Print) · unable to save content in destination folder · unable to associate asset to media gallery.
Recommended Configuration
If you are configuring the automation for the first time, use this preset as a starting point:
| Parameter | Recommended Value | Why |
|---|---|---|
| Trigger | Every first of the month | Catalog updated every month without redundant executions |
| Marker Threshold | ≥ 100% | Only complete products enter the catalog |
| Generate only if all attributes filled | ON | Avoids PDFs with empty fields |
| Locale | Start with 1 language | Test the end-to-end flow before adding other locales |
| Template mapping | Fill in only critical fields | Leave optional fields empty until the flow is validated |