pandadoc pricing table totals wrong after merge error

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