Docs
When a quote is created from Salesforce, the initial PDF is generated successfully. However, after updating the quote, the Generate Quote PDF action does not produce a new PDF. Merchants may expect versioning of PDFs, but no new file appears after changes are made.
The first quote PDF generates, but subsequent updates do not create a new PDF.
Users expect multiple PDF versions for the same quote.
Remote site settings or permissions may prevent successful PDF regeneration.
Salesforce does not create multiple PDF versions for Chargebee quotes. When a quote is updated and a new PDF is generated, the existing PDF is replaced, not versioned. This is the expected system behavior. If versioning is required, the PDF must be downloaded and stored externally.
If the Generate Quote PDF action does nothing, validate the remote site settings, Salesforce permissions, and package version to ensure the PDF regeneration works as expected.
After making any update to a quote (for example, product changes or expiry date updates), manually trigger Generate Quote PDF again in Salesforce.
Chargebee uses an S3 endpoint to deliver quote and invoice PDFs. Salesforce requires a remote site setting named CB_S3fileaccess to allow access.
To verify:
In Salesforce, go to Setup.
Search Remote Site Settings in Quick Find.
Confirm that CB_S3fileaccess exists and the URL matches the Chargebee S3 URL shown in any error message.
If missing:
Create a new Remote Site Setting.
Use the remote site URL referenced in the error message.
Save and retry generating the PDF.
The Remote site URL can be picked up from the error messages highlighted below. Sample screenshot:
Ensure the Chargebee for Salesforce package is on a supported version. Older versions may not fully support PDF regeneration workflows.
Confirm the Salesforce user has permissions to:
View the Quote object
Create attachments/files Missing permissions may prevent the PDF file from being updated on the quote record.
Salesforce does not support PDF versioning for Chargebee quote PDFs.
Each new PDF replaces the previous one.
Merchants needing version history must download and store earlier PDFs manually.
This is current expected behavior.
Was this article helpful?