Skip to content
QuillWeaver

Why one bad row shouldn't ruin 200 receipts

QuillWeaver Engineering

• 3 min

Pre-flight batch check catching one missing email while finishing 199 valid documents

Anyone who has run a year-end charitable tax receipt or membership renewal mailing knows the moment: you export 200 rows from your CRM, kick off the merge, and discover an hour later that row 9 has a blank email address or "TBD" typed into a gift amount column.

Most merge tools fail in one of two ways. Either the entire batch aborts halfway through, or it quietly emails a broken, half-filled PDF with a blank total to a real supporter.

Validate every row before rendering page 1

Before rendering any PDFs, every row in your CSV, JSON, or SQL export passes through a schema check. Instead of a stack trace, you get the exact record and column:

SKIP  row=9  record=D009  missing required field "email" (held from email delivery)
SKIP  row=42 record=D042  invalid currency value "TBD" in column "gift_amount"

It also catches duplicate record IDs before two recipients can overwrite the same output filename.

Finish the 199 valid documents, hold the bad row

Rather than throwing away the afternoon’s run, QuillWeaver puts the invalid rows in a review list and finishes every valid receipt, writing a SHA-256 verification receipt next to each PDF.

If you send directly through your own Gmail, Outlook, or SMTP mailbox, bounce tracking records which recipients succeeded and which failed or were held back. You never risk emailing 199 people twice just to retry one address.

Fix row 9, re-run in seconds

When you open your CSV, fill in row 9’s email address, and run the batch again, QuillWeaver checks its local verification cache. The 199 unchanged receipts are reused immediately, byte-for-byte identical, and only row 9 is rendered, fit-checked, and queued for delivery.

You can try this layout on the charitable donation tax receipt template, read how pre-flight checks stop visual overflows in Catching clipped pages before you hit send, or see the full How it works walkthrough.

All posts
  • Layout fit report highlighting tight frames across a 500-record statement batch
    Layout craft • 4 min

    Catching clipped pages before you hit send

    Your template looks spotless on three sample rows, until client #418 has a four-line trust name. How pre-flight fit checks stop silent overflows.