The problem: too many PDFs, too many signature steps
If your quote-to-cash involves a proposal, a 60-page master services agreement and a one-page pricing annex, you want the customer to sign once, not three times. Bundles let you merge several templates into one signature run so the signer sees a single PDF and you get one clean signed file back on the Opportunity or Contract.
This post explains how to plan bundles in Salesforce, what to include, and the practical limits you need to watch for when you automate signature runs from Opportunity, Quote or Contract records.
When to use document bundles in Salesforce
Use a bundle when multiple documents are logically part of a single commitment. Typical cases:
- Proposal + T&Cs + pricing annex for a closed-won Opportunity.
- Statement of work split into sections that are maintained as separate templates.
- Renewal pack: renewal cover letter, updated pricing schedule, amended contract.
Bundling is not the right choice when documents have different signers or widely different signing timelines. If the pricing annex needs internal approval after customer signature, keep it separate.
How Savvy DocuGen bundles work and what that changes
Savvy DocuGen merges several Word or PDF templates into one signature run and produces a single signed PDF that is written back to the same Salesforce record. Anchor-tag driven signature positions survive repagination, so your signature fields stay correct even when page counts shift between templates.
Key points to remember:
- Templates can pull data from the primary record and up to five levels of parent lookups, plus child and grandchild repeating rows. That makes it straightforward to include line items from Quote or custom Quote_Line__c records.
- Signed PDFs are stored on the triggering record. Documents up to 40 MB are supported; Notes and Attachments is capped at 25 MB, so use Files for larger bundles.
- Bundles can be triggered from a button, a stage change, a field change, or by uploading a file. That makes them easy to wire into Opportunity stage automation or a Renewal flow.
Designing bundles for predictable signing
Good bundle design reduces questions from sales and legal. Follow these rules:
- Order templates explicitly. Put a short cover sheet first, then proposal, then legal docs. The signer sees a logical sequence.
- Keep signer fields consistent across templates. Use the same anchor tags for the same signer role so signature placement is stable.
- Avoid duplicate signature blocks. If the same party signs multiple templates, include a single signature block on the last page of the bundle unless your legal team requires per-document signatures.
- Use repeating table rows for line items. If you need a pricing table in the proposal and a separate annex with the same data, drive both from the same child records so they stay in sync.
Template naming and versioning
RenewalPack_Cover_v2.docx
RenewalPack_Proposal_v2.docx
RenewalPack_Terms_v3.docx
Include the bundle name and a version number in each template filename. That makes it obvious what went into a signed PDF when you're troubleshooting a dispute later.
Practical scenario: a monthly renewal bundle
Hypothetical scenario: your org runs 200 renewals a month. Each renewal bundle contains a one-page cover, a 12-page renewal proposal and a 60-page amended contract. You trigger the bundle from the Opportunity when Stage changes to "Ready to Renew".
- Trigger: Opportunity.StageName = 'Ready to Renew'
- Templates: Renewal_Cover, Renewal_Proposal, Renewal_Contract
- Signer flow: customer signs first, then internal counterparty signs (saved to the Opportunity)
Two operational notes from that scenario:
- Storage: 200 signed PDFs per month will fill Files quickly if each PDF is large. Archive older signed files to a Document Management system if retention policies require it.
- Signature reliability: use anchor tags for signature placement. If the contract grows from 60 to 75 pages the anchor tags will still find the right signature location.
Signer authentication and workflow choices
Savvy DocuGen supports per-signer requirements: emailed one-time codes and per-signer passwords read from that signer’s Salesforce Contact or User record. Choose the level of authentication your legal team requires and apply it per signer.
Decide whether you need sequential signing or parallel signing. For bundles where the customer signs first and internal approvals follow, configure sequential signing. For multi-party customer scenarios, parallel signing can cut elapsed time.
Common pitfalls and how to avoid them
- Missing data at merge time. Fix with a pre-check step in your Flow: block the bundle if required fields or child records are empty, and show the sales rep a clear error.
- Large combined file size. If the bundle might exceed 25 MB, write to Files not Notes and Attachments, or split non-essential attachments into a post-signing package.
- Template drift. Put legal-owned templates in a central folder and use naming/version rules so sales can't pick an old template by mistake.
Trigger patterns that work well with bundles
Bundles are flexible. Common triggers:
- Button on the Opportunity for ad-hoc sends.
- Stage change automation to kick off a bundle when Opportunity.StageName becomes 'Contracting'.
- A Flow that checks approvals and then runs the bundle only if all approvals are present.
- An inbound file upload that merges the uploaded document as the first item in a bundle.
Wrap up and next step
If your goal is one clean signature event for a set of documents—proposal, contract and annexes—bundles are the right tool. They keep the signing experience simple for customers and produce a single signed PDF that you can file back to Opportunity, Quote or Contract.
Savvy DocuGen handles the merge, anchor-tag signature placement, per-signer authentication and writes the signed PDF back to the record. Try building a Renewal bundle in your sandbox today and test a stage-change trigger from an Opportunity.
Try it now in a sandbox: create a bundle, point it at an Opportunity, and send a test signature run.
Read next