What Happens When Someone Prints Your Pricing Page?

What happens when someone prints your pricing page?

Usually something embarrassing. Navigation and cookie banners take the first page, the plan comparison splits across a break, the coloured plan headers vanish because backgrounds do not print, and every call to action becomes underlined text pointing nowhere. The page that closes deals becomes unreadable at the exact moment it matters.

I know this because buyers keep showing it to me. In a B2B purchase the page does not stay in the browser. It gets printed, exported, or pasted into a document and circulated to people who will never visit your site, and it has to hold up without you in the room.

Almost nobody designs for that journey. It costs about an hour to fix and it is invisible until you look, which is a good description of most of the highest return work on a website.

Who is actually printing it, and why?

The person who has to get your invoice approved. They are assembling something for a manager, a finance team or a procurement process, and your pricing page is one exhibit among several. They are not printing because they love paper. They are printing because the approval happens somewhere your website is not.

That reframes the whole problem. The reader of the printed version is not your buyer. It is your buyer's boss, or a reviewer comparing three vendors, and they have no context and no patience. They will spend under a minute deciding whether this looks like a serious, legible option.

This is the same stage where deals quietly die for reasons nobody reports back to you, which I went through in why B2B deals keep stalling at procurement. A page that prints badly is a small tax on an already fragile process.

What breaks first on paper?

Four things, in a predictable order. Navigation and any sticky header consume space at the top. Background colours and gradients disappear, so anything whose meaning depended on colour becomes flat. Tables break across pages and lose their header row. And links become text, so every button reads as a word with no destination.

The plan comparison is where all four converge. It is usually the widest element on the page, the most dependent on colour to mark the recommended tier, and the most likely to split. What arrives on the reviewer's desk is a fragment of a table with no heading, which is worse than nothing because it looks like an error.

The second worst offender is the cookie or chat widget, which cheerfully prints itself onto page one of a document going to somebody's finance director. It is a small thing and it reads as carelessness.

What should a print stylesheet actually change?

Hide the furniture, force the colour, keep the table together. Print media queries are part of CSS and have been for a long time, so this is not exotic work. Remove navigation, cookie notices, chat widgets and footers. Ensure the plan names and the recommended tier read without relying on a background colour.

Then handle the table properly. Repeat the header row on each printed page and avoid breaking a row across pages. A comparison table that carries its own headings is legible on page three, and one that does not is a puzzle.

Set a sensible base size too. Screen typography that feels generous at arm's length is often too large on paper and wastes pages, and the reviewer notices a document that runs to six pages when it should run to two.

Where you put that stylesheet depends on your platform, so check its own documentation for where custom CSS belongs. The mechanics are the easy part. Somebody deciding to look is the hard part. If you want the long form version of the technique, I wrote a walkthrough in the print stylesheet tutorial for long form pages.

Should the URL appear on the printed page?

Yes, and this is the single highest value change on the list. On paper a link is just underlined text, so a reviewer holding your printed pricing page has no way back to you. Printing the destination next to important links, or at minimum putting the page URL in a print header, restores that path.

Add the date as well. A printed pricing page with no date is a document of unknown age, and if prices change between printing and approval you have an argument on your hands that a small line of text would have prevented.

Be selective. Printing every URL on the page produces clutter. The ones worth expanding are the ones a reviewer might act on: the pricing page itself, the contact route, and anything that constitutes terms.

What about the PDF a buyer builds by hand?

Treat it as the same problem, because printing to PDF uses the same styles. That is convenient: fixing print fixes export. What it does not fix is the buyer who screenshots three sections and pastes them into a slide, and you cannot control that.

What you can do is make each section survive on its own. If a plan comparison makes sense only alongside a paragraph two screens above it, any excerpt of it will be misleading. Sections that carry their own context are more robust to every form of copying, not just printing.

This is also an argument for saying the important thing in words rather than in layout. A recommended badge communicated only by a coloured border does not survive paper, a screenshot, or a text only export. The same claim written into the plan name survives all three.

Does this matter if your prices are not public?

It matters more. If your page explains your model without listing numbers, that explanation is doing the whole job, and it is the part that gets forwarded to people who will never speak to you. A printed page of vague positioning is a weak exhibit in an approval meeting.

When prices are hidden the printed version should make the process legible instead: what determines the price, what the next step is, and roughly how long it takes. Those three things let a reviewer approve a conversation rather than a number, which is all you need at that stage.

I worked through what belongs on that kind of page in what to put on a pricing page when prices are hidden. The print question is a good test of whether you got it right, because paper strips away everything interactive and leaves only what you actually said.

How do you test this in ten minutes?

Open your pricing page, press print, and look at the preview. That is the whole test and it is the reason this problem persists: nobody has ever done it. Then do the same on your homepage, your services page and your case studies, because those travel too.

Count the pages, check whether the comparison table survived, and look for the chat widget. Then hand the printed version to somebody who has not seen your site and ask them what you sell and what it costs. Their hesitation tells you what to fix.

Across six years and seventy plus projects I have never run this test on a site that passed it first time, including sites I had built myself. It is simply not in anybody's review checklist, which is exactly why it is cheap to be better at it than your competitors.

What should you do next?

Print your pricing page today and look at the preview honestly. Write down the four or five things that are wrong. Most of them will be elements that should be hidden, and hiding things is the easiest CSS there is.

Then add the URL and a date to the print output, and make sure your comparison table repeats its header. That is an hour of work on the document your buyer uses to argue for you when you are not there.

If you want someone to go through the pages that actually travel inside your buyer's company and make them hold up, reach out. Let's chat.