What causes RFP pricing tables to break when exporting from Word to PDF
RFP pricing tables break during Word-to-PDF export mainly because of fixed table widths exceeding page margins, auto-fit settings that recalculate column sizes, embedded fonts that don't render, and row-splitting across page breaks. The PDF engine reflows content using different layout rules than Word's screen view, which shifts columns, clips numbers, and corrupts borders.
Why the export breaks tables
Word and PDF use different rendering engines. Word lays out tables dynamically based on your screen, zoom level, and printer driver. When you export to PDF, the conversion engine re-renders everything using the PDF page model. That mismatch is where pricing tables fall apart.
Most teams get this wrong by assuming "what I see in Word is what I'll get in the PDF." It isn't. The conversion is a re-layout, not a screenshot.
1. Table width exceeds the printable area
If a pricing table is wider than the page's printable region (page width minus left/right margins), Word may still display it fine on screen but the PDF engine clips the rightmost columns. This is the single most common cause of missing price or total columns.
Fix: Set the table to a fixed width that fits inside margins. Right-click the table → Table Properties → set Preferred width to a value below the usable page width (for US Letter with 1" margins, stay under 6.5").
2. AutoFit recalculates columns
Word's AutoFit to Contents and AutoFit to Window settings dynamically resize columns. During PDF export, the engine recalculates fit using its own metrics, which collapses or expands columns unpredictably—especially with currency values and long line-item descriptions.
Fix: Use Table Properties → AutoFit → Fixed Column Width. Lock every column width manually so the export has nothing to recalculate.
3. Rows split across page breaks
When a pricing row lands at the bottom of a page, the PDF engine may split it mid-row, pushing the price to the next page or hiding it behind the margin.
Fix: Select all rows → Table Properties → Row tab → uncheck Allow row to break across pages. Then enable Repeat as header row at the top of each page on your header row so column labels persist on every page.
4. Font substitution
If a table uses a font not embedded in the PDF, the viewer substitutes a fallback font with different character widths. Numbers reflow, decimals misalign, and totals push columns out of bounds. This is a frequent culprit on shared machines where contributors used different fonts.
Fix: Embed fonts on export. In Word: File → Options → Save → Embed fonts in the file. When exporting, use File → Export → Create PDF/XPS rather than a print-to-PDF driver, since the native exporter handles embedding more reliably.
5. Nested tables and merged cells
Nested tables and complex merged-cell layouts are fragile. The PDF engine doesn't always reconstruct merge spans correctly, leaving gaps, doubled borders, or misaligned subtotals.
Fix: Flatten the structure. Replace merged-cell pricing summaries with a single clean table. If you need grouped sections, use separate stacked tables instead of one heavily merged table.
Export method matters
Not all PDF conversions are equal. Three common paths produce different results:
| Method | Reliability | Notes |
|---|---|---|
| File → Export → PDF (native) | High | Best font embedding and layout fidelity |
| Print to PDF (driver) | Medium | Depends on printer driver metrics; can shift columns |
| Third-party add-in | Variable | Quality depends on the tool's rendering engine |
Use the native Word exporter first. If a buyer portal like SAP Ariba rejects your attachment, the PDF spec or file size—not just the table—may be the issue.
A reliable pre-export checklist
- Set table width below the printable area (≤6.5" for 1" margins on Letter).
- Switch every column to Fixed Column Width.
- Disable Allow row to break across pages.
- Enable Repeat header row on column labels.
- Embed fonts in the document.
- Flatten nested or merged-cell sections.
- Export via File → Export → Create PDF/XPS.
- Open the PDF and verify totals, decimals, and the rightmost column on every page.
Validate the exported file in a standalone viewer like Adobe Acrobat Reader, not just the browser preview—browsers sometimes render PDFs more forgivingly than the buyer's system will.
When the tool is the problem
If pricing tables break repeatedly across submissions, the workflow may be the real bottleneck. Word handles single-author documents well but struggles with complex, multi-contributor pricing sheets. Comparing Word vs Google Docs vs dedicated RFP software helps decide whether to keep fighting export issues or move pricing into a structured system that renders consistently. Formatting failures also compound deadline risk—broken tables are a fast path to a non-compliance disqualification if a reviewer can't read your numbers.
Key takeaways
- Word-to-PDF is a re-layout, not a screenshot—different engine, different rules.
- The top causes: oversized table width, AutoFit recalculation, row splitting, font substitution, and merged cells.
- Lock column widths, disable row breaks, embed fonts, and use the native exporter.
- Always proof the final PDF page by page before submitting, focusing on the rightmost price columns and totals.