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

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