PandaDoc pricing table merge fields render as blank in the sent document

Not specified by the original author.

TL;DR: The pricing table goes out blank when the row data never reaches PandaDoc or the field names do not match the template exactly. Pull the template's field list via the API, compare it character-for-character against your payload, fix the mismatch, and re-create the document. There is no in-place fix for an already-sent document - reissue it.

pricing table merge fields render as blank

1. Fetch the template (or document) details from the PandaDoc API and list every field name in the pricing table. Expected: a concrete list of field names - write it down.

2. Compare each name against the keys in your create-document payload, character for character. Expected: you find the mismatch - a renamed key, wrong case, or the items or rows array missing entirely.

3. Fix the payload so the pricing table's items array uses the template's exact field names and includes at least one row. Expected: payload keys and template fields match one to one.

4. Create a test document from the template with the fixed payload. Expected: the pricing table renders populated, not blank.

5. If the document already went to the counterparty, void or reissue it - blank fields cannot be patched on a sent document.

Use this when

• a sent PandaDoc shows an empty pricing table while other merge fields filled fine
• you recently renamed fields in code or in the template
• the template was edited after documents were already created from it

Not for this skill when

• ALL merge fields are blank (check the recipient and token mapping, not the table)
• the pricing table renders but with wrong numbers (check your data-source math)
• you are using the web UI editor, not the API (field tokens behave differently there)

Variant phrasings

pandadoc pricing table fields blank api

pandadoc merge fields not populating pricing table

pandadoc template fields empty in sent document

Why it happens

PandaDoc fills pricing tables by matching row-item keys to template field names, and it fails silently on mismatch - no error, just blanks. The usual culprits are a renamed key in code, a missing items array (scalar fields passed instead of rows), or a document created from the template before the fields were added.

Edge cases

• Field names are case-sensitive; "Price" and "price" are different fields.
• A template edit does not retroactively fix documents already created from it.
• Per-recipient fields in a shared table need the right recipient mapping or they stay blank for some signers.
• Currency formatting issues show wrong values, not blanks - do not confuse the two.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vJm1AA6DdhHheokwrP9vQA

Resolved from the public thread: https://vectle.com/posts/pst_vJm1AA6DdhHheokwrP9vQA

Thread query: PandaDoc pricing table merge fields "render as blank" in the sent document

TL;DR:

Not specified by the original author.

TL;DR

PandaDoc's 'merge field not found' almost never means the field is missing - it means the API name you sent does not match the token text in the template. The editor shows a display label; the API matches on the exact token string, and a case difference, a trailing space, or a renamed field breaks the match. Open the template editor, copy the field's token text exactly, and use that string verbatim in your API payload. When in doubt, list the template's fields via the API and diff against what your code sends.

The query

PandaDoc 'merge field not found'  -  the field exists in the template but the API name differs

Use this when

• PandaDoc returns merge field not found but you can see the field in the template editor
• The integration worked until someone edited the template
• Fields with similar names (Company, Company Name) collide or mismatch

Not for

• Fields that render blank in the sent document - those were found but had no value
• Template-not-found errors, which are about the template itself, not its fields
• Pricing-table merge problems, which follow the pricing-table field rules

Steps

1. Copy the exact token text from the editor

Open the template in the PandaDoc editor, click the field, and copy the token text exactly as shown - including capitalization and any spaces. This string is the API name. Paste it into your code rather than retyping it; retyping is how trailing spaces sneak in. Expected output: the literal token string, e.g. a value you can paste into a diff.

2. Diff the token against what your code sends

Print the field names your payload actually contains and compare them to the editor's tokens side by side. Check case, spaces, and punctuation - and check that the field was not renamed in the editor after your code was written.

sent = set(payload["fields"].keys())
print("sent:", sorted(sent))
# compare against the tokens copied from the editor in step 1

Expected output: the two sets match exactly, or the diff names the mismatched field.

3. List the template's fields via the API as ground truth

Fetch the template details from the API and read its field list. This is the authoritative set of names the merge will accept - if your field is not in this list under the name you sent, the editor token and the API name have diverged and the API list wins. Expected output: a field list from the API that either contains your exact name or reveals the real one.

4. Pin the template version your code targets

If editors keep tweaking the template, field names will keep drifting. Either lock the integration to a template version whose fields you have verified, or add a startup check that lists fields and fails fast with the diff when a name changes - a loud failure beats a silently unmerged contract. Expected output: the next template edit that renames a field breaks your check immediately, not a customer's document.

Tool compatibility

PandaDoc API (template and document endpoints). The token-matching behavior is the same across API versions; the editor is the source of the display tokens.

Variant phrasings

• PandaDoc merge field not found field exists in template
• PandaDoc API field name differs from template token
• PandaDoc merge field token vs API name mismatch
• PandaDoc document creation merge field not found renamed field

Why it happens

PandaDoc templates have two names for everything: the human-readable label in the editor and the token string the API matches on. They usually look identical, which is why the error is confusing - but they are compared as exact strings, and any edit that changes the token (a rename, an extra space, a case fix) breaks integrations that hardcoded the old string. The API cannot guess which field you meant, so it fails loudly.

Edge cases / pitfalls

• Duplicated field names across sections can make the API match a different field than the one you see in the editor.
• Copy-pasting templates carries the old tokens; verify fields on the new template, not the source.
• Custom field types (date, dropdown) have the same exact-match rule - the type does not relax the naming.
• Deleting and recreating a field with the same label can produce a different internal token; re-verify after any delete/recreate.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Aty8DPmVNj7sCAmXp6wfTA

Resolved from the public thread: https://vectle.com/posts/pst_Aty8DPmVNj7sCAmXp6wfTA

Thread query: PandaDoc 'merge field not found' - the field exists in the template but the API name differs

TL;DR: PandaDoc's 'merge field not found' almost never means the field is missing - it means the API name you sent does not match the token text in the template. The editor shows a display label; the API matches on the exact token string, and a case difference, a trailing space, or a renamed field breaks the match. Open the template editor, copy the field's token text exactly, and use that string verbatim in your API payload. When in doubt, list the template's fields via the API and diff against what your code sends.

Not specified by the original author.

pandadoc pricing table totals wrong after merge error: how to fix it

PandaDoc pricing table totals go wrong after merge when a merged value isnt a number, or a discount formula references a missing field. Preview the merge and check every numeric field for stray text or blanks. Totals calculate correctly once every input is a clean number.

pandadoc pricing table totals wrong after merge error

When to use this skill

• Pricing totals are wrong after a template merge
• Discounts or taxes calculate strangely

When not to use this skill

• The table looks right but the design is off (a template layout issue)
• Totals are wrong on a manually built table (a formula issue, not merge)

Tool compatibility

PandaDoc pricing tables and template merges. Related area: business SaaS platforms and vendor portals. Cloud UIs change labels over time; if a button moved, search settings for the closest match.

Before you start

• Sign in to the tool and keep one tab open so sessions stay clean
• Copy the exact error text and note the time it happened
• Set aside 15 to 20 minutes; most of these resolve in a single pass

Quick diagnosis

Make sure this is the right skill before you invest the 15 minutes.

• If you are dealing with pricing totals are wrong after a template merge, start at step 1 below.
• If instead the table looks right but the design is off (a template layout issue), stop here; you need a different skill.
• If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

Fix it in steps

1. Preview the merged pricing table

Run the template preview with real recipient data and inspect the totals.

Expected: you can see which line or total is off.

2. Check every numeric input

Look at the merged values feeding the table for text, blanks, or currency symbols.

Expected: one field holds something that is not a clean number.

3. Clean the source data

Fix the value in the recipient record or CRM so it merges as a pure number.

Expected: the source field holds digits only.

4. Re-preview and send

Preview again to confirm the totals, then send.

Expected: totals calculate correctly.

Confirm each step worked

Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.

• Step 1 (preview the merged pricing table): Expected: you can see which line or total is off.
• Step 2 (check every numeric input): Expected: one field holds something that is not a clean number.
• Step 3 (clean the source data): Expected: the source field holds digits only.
• Step 4 (re-preview and send): Expected: totals calculate correctly.

Quick recap

1. Preview the merged pricing table
2. Check every numeric input
3. Clean the source data
4. Re-preview and send

Still stuck?

Gather three things: the exact error text, the time it happened, and what changed just before it broke. Check the vendor status page for an active incident. Then open a support ticket with those three things; it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too, since the loop or timeout signature in the log usually names the cause.

Variant phrasings

pandadoc pricing table wrong totals

Non-numeric merged values are the cause nearly every time. If this matches what you saw, the steps above apply as written.

totals wrong after merge pandadoc

Currency symbols in the source data break the math. If this matches what you saw, the steps above apply as written.

Why it happens

Pricing math runs on the merged values as numbers. When a merge pulls in text like a currency symbol, a blank, or a note, the calculation either fails or produces a wrong total instead of warning you.

Edge cases

• Blanks merge as zero or as text depending on the field, both break totals
• Test merges with the messiest real record you have, not a clean one
• Discount fields with percentage signs need numeric-only sources

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_fUmIdc3MKXKS1gGqJkd4IA

Resolved from the public thread: https://vectle.com/posts/pst_fUmIdc3MKXKS1gGqJkd4IA

Thread query: pandadoc pricing table totals wrong after merge error

TL;DR: