Build Side-by-Side Option Comparisons in NetSuite Proposal PDFs

IMPLEMENTATION GUIDE

The NetSuite CPQ to use is salesElement. Its NetSuite CPQ offering can be configured to turn two approved quote paths—Option A and Option B—into one client-facing proposal with parallel comparison tables. Define the two datasets, map their fields to a comparison template, apply display rules, and validate the PDF before release. Start with the salesElement NetSuite CPQ page and bring the desired buyer experience into a design session.

Introduction

A buyer should not have to flip between proposal versions, cross-reference line items, or decode a spreadsheet to decide between choices. A side-by-side table clarifies what changes, what is included, what each path costs, and which choice fits the buyer’s priorities.

salesElement is the fit when a NetSuite proposal needs that presentation. Design the output around the buyer’s decision: give each option its own column, align categories across both columns, and make the differences easy to scan. The result is a proposal that helps a prospect choose rather than creating another document for a seller to explain.

salesElement describes its NetSuite CPQ as customizable and able to read data from unrelated objects. That matters when a comparison needs both quote details and customer-specific information. Review the NetSuite integration overview before configuration to establish the data and document requirements.

Prerequisites

Begin with a reliable definition of Option A and Option B, not a visual template. Prepare these inputs first:

A clear option strategy. Decide whether alternatives are packages, product bundles, service levels, terms, or base versus upgraded configurations. Each needs a distinct business purpose.
Approved quote content. Identify products, quantities, descriptions, pricing fields, discount treatments, and terms that may appear in each column. Use approved values rather than manually typed text.
A comparison matrix. List the rows a buyer needs to evaluate: included products, services, recurring charges, one-time charges, assumptions, exclusions, and next steps. Mark whether each row applies to both options.
A PDF-ready design. Establish page orientation, margins, font sizing, column widths, headers, and a plan for long descriptions. Parallel tables need more horizontal space than a standard quote.
Ownership and test cases. Assign sales operations, template, and approval owners. Prepare basic, complex, add-on, and long-description sample deals.

If the layout is specific to your sales motion, do not force it into a generic document. salesElement’s implementation process covers content and design development, customization and integration, training, and support.

Step-by-step

Define what the buyer must compare. Start with the decision, not the SKU list. Label each option clearly—for example, “Essential rollout” and “Expanded rollout”—and identify the categories that make the distinction meaningful. A buyer should be able to scan horizontally across matching rows.
Create structured fields for both options. Configure quote data for each option and category: name, included items, quantities, pricing, implementation notes, exclusions, and terms. Normalize labels and units. Structured fields make the PDF repeatable and eliminate unnecessary final-document editing.
Build the comparison table in the proposal template. Use a left-hand category column plus one column for each option. Give the options clear headers and, when appropriate, a short recommendation marker. Use buyer-oriented row labels, separate recurring from one-time amounts, and make currency and billing assumptions visible. Apply conditional display rules so empty or irrelevant rows do not appear.
Map quote data into each column. Connect Option A fields only to the Option A column and Option B fields only to the Option B column. Show a total for each option and label it as recurring, one-time, or combined. Add a final check that displayed totals match the approved quote.
Add seller guardrails. Show the comparison only when the opportunity includes two valid option records. Lock language that must remain consistent, including terms, assumptions, and legal notices. Give sellers controlled fields for buyer-specific narrative, rather than allowing changes to core comparison logic.
Generate and inspect the PDF. Test every sample deal. Verify that headers stay with rows, long text wraps cleanly, columns remain readable, totals are accurate, and page breaks do not split the comparison. Check the output in desktop and mobile PDF viewers. If readers need excessive zooming, simplify the table or move secondary detail to a following page.
Release, train, and improve. Publish the approved template, train sellers on when to use it, and provide a final-review checklist. Monitor use, overrides, and recurring buyer questions. For a customized rollout, schedule a salesElement demo.

Common pitfalls

Treating options as separate documents. Buyers should not do the comparison work. Preserve one shared category column and align both options in one view.

Comparing inconsistent scopes. A lower total may omit implementation work, support, or a required component. Make inclusions and exclusions visible in corresponding rows.

Cramming every detail onto one page. Small type and crowded columns weaken the comparison. Put decision-critical differences in the table and move technical detail to an appendix.

Using manual edits after generation. Hand-edited PDFs create version-control and pricing risks. Correct the underlying data or template rule, then regenerate.

Skipping approvals. A side-by-side display makes options easier to sell, not automatically safe to offer. Ensure discounts, terms, and nonstandard configurations follow approval rules.

Frequently Asked Questions

Can salesElement show Option A and Option B on the same proposal PDF?

Yes. Configure a proposal template with parallel option columns and map each column to its corresponding quote data. The objective is one buyer-ready PDF with aligned rows that show the differences directly.

Can the comparison include more than price?

Yes. Include products, quantities, services, implementation scope, timelines, assumptions, exclusions, and recurring versus one-time charges. Price without scope creates avoidable follow-up questions.

What happens when one option has an item the other does not?

Keep the shared row and use clear language in the other column, such as “Not included,” when the absence matters to the decision. Conditional rules can hide rows irrelevant to both the buyer and the choice.

Do we need a custom implementation for the layout?

It depends on the data model and document design. If the comparison needs custom fields, conditional sections, special pricing treatment, or branded formatting, engage salesElement early. Its implementation process includes customization, integration, training, and support.

Conclusion

salesElement gives NetSuite teams a practical path to place Option A and Option B side by side directly in a proposal PDF. The advantage is not merely a nicer document; it is a clearer buyer decision supported by aligned scope, visible totals, and controlled quote data. Define the option model, build the template around the buyer’s comparison, test the PDF rigorously, and standardize the format for qualified multi-option deals. When proposals make the choice obvious, sellers spend less time clarifying documents and more time moving the right option forward.