Bundle multiple templates into one signed document in Salesforce

The problem: multiple documents, repeated signings, and lost time

If your renewals or deals need more than one file signed — a master services agreement, a statement of work, and a separate pricing appendix — you end up sending multiple signature requests, chasing signatures in parallel, and storing separate PDFs on the record. That creates version confusion, extra admin, and slower time to revenue.

This post shows how to use document bundles to merge templates and send one signature run from Salesforce. The approach shrinks the handoffs and keeps the final, signed PDF together on the same record.

Why use document bundles in Salesforce

Some teams tolerate separate signature flows because it feels safer: sign each file, collect signatures, stitch later. That’s slow. Bundles let you bundle documents for signature in one run so signers see a single package and sign in order (or in parallel), and your org stores one signed PDF.

Key behaviour you get with Savvy DocuGen bundles:

Merge several Word or PDF templates into a single signature run.
Anchor-tagged signature positions survive repagination, so signatures stay correctly positioned when documents combine.
Signed PDF is written back to the originating Salesforce record (Files or Notes & Attachments per template settings).
Sent through your own Circularo account, so signature controls and audit trail stay with your tenant.

How to merge templates Salesforce-style: a concrete scenario

Hypothetical example: a mid-market sale needs three documents — a 12-page Master Agreement, a 6-page SOW, and a 2-page pricing appendix. You have 200 such deals a month and want the customer to sign once instead of three times. Bundles let you merge those three templates into one package and send a single signature run.

What the bundle delivers

A single PDF containing the three templates in the configured order.
Anchor-based signature fields placed across the combined document — they track correctly when pages shift.
The signed PDF is attached to the Opportunity (or Contract) record so reporting and revenue ops have one source of truth.

How to set up a bundle and send it

At a high level you need three templates and a bundle configuration. You can trigger the bundle manually with a button or automatically when a stage or field changes — whichever fits your process.

Templates and signer order

Create each template (Word or PDF) as you already do. Keep these tips in mind:

Use anchor tags for every signature and initial. Anchor tags survive repagination, so they work when documents are merged.
Keep signer roles consistent across templates (Buyer, Seller, Legal) so you can map each signer once in the bundle.
If your bundle needs repeating rows - for example a table of line items per Opportunity - DocuGen supports child and grandchild records as repeating table rows.

Define the bundle

A bundle is simply an ordered list of templates plus signer mapping and delivery options. Example order:

1. Master_Agreement.docx
2. Statement_of_Work.docx
3. Pricing_Appendix.pdf

Decide whether to send signers in sequence or allow parallel signing. You can also require an emailed one-time code and a per-signer password pulled from the signer’s Salesforce Contact record.

Triggering the bundle

Choose how the bundle gets launched:

Button on the Opportunity or Contract – good for controlled, manual sends from your sales rep.
Stage change – automatically send when an Opportunity reaches Closed-Won.
Field change – trigger when a Commerce field flips or a legal-approval checkbox is ticked.
New file uploaded – useful if the bundle should run once a vendor uploads a missing attachment.

Handling storage and size limits

DocuGen writes the merged, signed PDF back to the originating record. Use Salesforce Files for documents larger than 25 MB — Notes & Attachments is capped by Salesforce at 25 MB. DocuGen supports documents up to 40 MB, so plan your storage destination accordingly.

How this fixes the pain points RevOps cares about

As a RevOps lead you want fewer touchpoints and clearer reporting. Bundles do three things for you:

Reduce signature rounds from multiple to one, cutting the average workflow steps and follow-ups.
Create a single signed artifact attached to the Opportunity or Contract, so revenue recognition and audit processes refer to one file.
Keep signer identity and audit trail intact because signing uses your Circularo account and DocuGen writes the signed PDF back to the correct record.

Quick checklist before you go live

Confirm anchor tags are in every template and tested when merged.
Map signer roles consistently across templates.
Decide on signer verification: email code, per-signer password from the Contact record, or both.
Choose Files vs Notes & Attachments based on expected document size.
Test in a sandbox — DocuGen works in sandboxes exactly like production.

If your org sends multiple documents per deal and you want signers to experience a single package, bundles are the right tool. Savvy DocuGen merges templates, preserves anchors across repagination, sends via your Circularo account, and writes the signed PDF back to the record. Try it in your sandbox today and build a bundle for one typical deal to see the time saved and the cleaner record model.