Product card vs PDF catalog is a routing decision, not a design argument. One answers a question about a single SKU in under a minute. The other answers questions about the whole range and costs the buyer an evening. Send the wrong one and the reply you get back is "can you send more details" — the buyer asking you to do the work twice.
The decision is usually made for you before you open the design tool. Gmail caps attachments at 25 MB for personal accounts. Outlook.com caps them at 25 MB. WhatsApp accepts documents up to 2 GB. Your catalog is designed for the first two channels; the buyer reads it on the third.
This is the practical split: which file answers which question, the fields that belong on a single-SKU card, the checks to run before you hit send, and the cases where the 60-page PDF is still the right answer.
What a product card actually is
A product card is one page for one SKU: product name and code, measured or stated dimensions, the photos or diagram that show the shape, the commercial facts a buyer asks for (MOQ, lead time, finish options, price basis), and one clear way to reply. It is a document with one product in it, not a page inside a bigger document.
That definition matters because four different things get called "the product card" in export sales:
| What people call it |
What it really is |
Who owns it |
| Product card |
Single-SKU page with specs, visuals and a contact action |
You, and you can send the link |
| Catalog page |
One page inside a multi-SKU PDF |
You, but it is buried on page 74 |
| Marketplace listing |
A listing on someone else's platform, governed by their image rules |
The platform |
| Spec sheet / technical drawing |
The engineering or production document behind the numbers |
Your technical team |
The card is the only one of the four that is both single-SKU and yours to send. That is its entire advantage.
The 25 MB wall: the format question is a delivery question
Here is the mechanism most sales teams miss. When a Gmail attachment exceeds the account limit, Gmail does not fail — it removes the attachment and replaces it with a Google Drive link. The buyer now has to open a second app, on a phone, to reach a file you thought you had sent. Outlook.com behaves the same way at 25 MB and pushes you to OneDrive for anything larger.
Read that table as a budget. Email gives you 25 MB. A full-line catalog with photography, 120 SKUs and four languages does not fit in 25 MB, so the link substitution fires, and the buyer's first impression of your company is a permissions request.
The second-order effect is worse than the file size. A link in an email is forwardable to anyone; a 25 MB attachment is not. When the buyer forwards your card to their product manager, the specification travels with it. When they forward a Drive link, the product manager sees a folder and has to ask which file.
Product card vs PDF catalog: nine differences that change the outcome
| Dimension |
Product card |
PDF catalog |
| Number of SKUs |
One |
Dozens to hundreds |
| Time to answer one question |
Under a minute |
Find page, zoom, guess the column |
| Behaviour on a phone |
Fits one screen width |
Pan and zoom, column headers lost |
| Email deliverability |
Usually a link, no attachment |
Hits the 25 MB cap quickly |
| Forwarding inside the buyer's team |
Link or screenshot, context intact |
Whole file, context buried |
| Price visibility |
One price basis, one validity date |
Price list that goes stale in every copy |
| Edit cost when a spec changes |
One page |
Re-export the whole file, re-send |
| Best moment to use it |
After the buyer names a SKU |
Before the buyer knows what exists |
| Failure mode |
Too thin to answer the next question |
Too heavy to open, so it is never read |
The last row is the one to remember: the catalog fails by being unread, the card fails by being incomplete. Those are opposite failures, which is why the two formats are not competitors.
Where the PDF catalog still wins
The product card vs PDF catalog question gets settled by the buyer's stage, not by file size. Three cases, and they are common enough that deleting the catalog would cost you orders.
Range selection. A buyer sourcing a category does not know your SKU list yet. A catalog lets them scan 80 options in ten minutes and shortlist four. No card can do that job; a card assumes the SKU is already named.
Tender and quotation packets. Some buyers, especially in public procurement and large retail, ask for one document set with page numbers and a version. A folder of 40 links is harder for them to file than a single PDF, and their process may require a signed, paginated document.
Print and showroom leave-behind. A printed catalog on a table at a trade fair still works because the buyer takes it away. The digital version is the backup, not the main event.
Keep the catalog for these three. Then stop using it for the fourth case, which is the one that quietly costs the most: answering a specific question about a specific product.
Where a product card wins
After the buyer names a model. This is the highest-value moment. They have two candidates and need to compare wall thickness, packed weight and lead time. A card lets them do that without opening a 40-page file twice.
Replacement parts and aftersales. A spare part enquiry is one part number, one dimension, one photo. Sending the full catalog here is a small cruelty.
Chat handoff. WhatsApp's 2 GB document limit means the file will send, but the limit is not the constraint — the screen is. A one-page card is readable at phone width; a catalog is not.
Internal forwarding. The person who approves the purchase is rarely the person who received your email. A card travels as a link with the product name in the URL, so the second reader knows what they are looking at before they open it.
The 12 fields of a card that survives a forward
This is the template to copy. Every field earns its place because a buyer asked for it at least once.
| # |
Field |
What to write |
Why it matters |
| 1 |
Product name + your SKU |
Buyer-facing name plus the code used in the quotation |
The code is how the buyer's ERP and your order desk agree |
| 2 |
One-line application |
"For 3-seat waiting areas in clinic reception" |
Places the product without a paragraph of marketing |
| 3 |
Measured dimensions |
L × W × H with units, plus tolerance if known |
The number that causes returns when it is missing |
| 4 |
Assembled vs packed |
Both sets of dimensions, labelled |
Freight and door-width checks use different numbers |
| 5 |
Net and gross weight |
kg, per unit and per carton |
Decides freight cost and manual handling |
| 6 |
Material and finish |
Substrate plus finish, e.g. "18 mm plywood, oak veneer, PU clear coat" |
Finish complaints are usually a naming mismatch |
| 7 |
Packing |
Units per carton, carton dimensions, pallet quantity |
The buyer prices inbound freight from this line |
| 8 |
MOQ and lead time |
MOQ in units, lead time in working days, from what trigger |
"From order confirmation" vs "from deposit" changes the plan |
| 9 |
Marks and certificates that apply |
Only the ones you can produce on request |
An empty compliance claim is worse than none |
| 10 |
Price basis and validity |
FOB / CIF / ex-works, port, currency, valid-until date |
The line that prevents a renegotiation thread |
| 11 |
Visual set |
Full view, detail, scale reference or measured diagram |
Shape and proportion are hard to describe in words |
| 12 |
Contact action + revision |
One way to reply, plus "Rev. 2026-10-21" |
A card without a date becomes a wrong card in a month |
Field 3 and field 11 are where most cards break. A photo without a scale reference cannot answer "will it fit". A dimension line placed by eye is not a measurement — if the size matters, the number has to come from a tape, a drawing or a verified sample, and the card should say which.
Nine checks before you send
The fifth check is the one people skip. If the card is 31 MB and you "just send it", Gmail quietly turns it into a Drive link and your buyer meets a permissions screen instead of your product.
The handoff sequence that gets a reply
- Send the range first: catalog or category page, no dimensions, one question — "which three models are you pricing?"
- When they name the three, send three cards, one per SKU. Same template, same field order.
- Put the card revision into the quotation, so a later spec change has a paper trail.
- On chat, send the card link rather than the file, and name the SKU in the message.
- Log which card was opened or forwarded where you can. A card that never leaves your outbox is a pricing problem, not a format problem.
Step 2 is where the format decision pays. Three cards answer "which of these fits my room" faster than any catalog page, because the buyer compares three files with identical field order instead of hunting three different pages.
Where the card stops
A card is a presentation document, and presentation has limits worth stating plainly.
It does not certify anything. Certificates, test reports and declarations come from the body that issued them; a card can only point to them.
It does not replace a sample. Colour, texture and joint quality are still judged in the hand.
It does not fix a wrong measurement. If the dimension on the card came from a marketing brochure instead of the drawing, the card makes the error travel faster. Generated visuals have the same limit: a rendered scene or a 3D view shows shape and context, not true size. Measured numbers have to come from a real measurement.
Nor does it replace the quotation. The card holds the stable facts; price and validity still belong in the quote, where they can be revised without reissuing the product page.
FAQ
What is the difference between a product card and a PDF catalog?
A product card covers one SKU and is built to answer a specific question fast; a PDF catalog covers a range and is built for selection. The card is a decision document, the catalog is a browsing document, and the mistake is using one for the other's job.
What should be on a product card for a B2B buyer?
Twelve fields cover most enquiries: product name and SKU, application, measured dimensions, assembled and packed sizes, net and gross weight, material and finish, packing quantities, MOQ and lead time, applicable marks, price basis with validity, a visual set, and a contact action with a revision date.
Is a PDF catalog too large to email?
Often, yes. Gmail and Outlook.com both cap attachments at 25 MB, and Gmail replaces anything larger with a Drive link rather than failing. A photography-heavy, multi-language catalog reaches that ceiling quickly, which is why a single-SKU card or a deliberately shared link works better for follow-up.
Can I send a screenshot of the catalog page instead?
You can, and buyers do it to each other. What breaks is the context: the page number, the price list header and the revision date all disappear, so the screenshot answers one question and creates two more. If a page is worth sending repeatedly, rebuild it as a card.
Next steps
Three routes, depending on where the bottleneck is.
If buyers keep asking questions the catalog already answers, the problem is the reading experience, not the content — start with five cards for the five SKUs that generate the most enquiries, and keep the catalog for range selection.
If the bottleneck is that nobody has time to lay out cards, a workspace that locks measured dimensions onto the product photo and exports a shareable one-SKU page is one option among several; so is a template in your existing design tool, or asking your factory for a drawing you can reuse. See how a spec sheet layout for export quotations is structured before you build your own.
If the bottleneck is the handoff itself, fix the sequence first: range, then shortlist, then cards. That single change does more for a stalled enquiry than any redesign of the product card vs PDF catalog argument. The QR code product sheet used at trade shows is the same logic in a different room, and the WhatsApp Business catalog image size rules decide whether your card is legible on the channel where it will actually be read.
One more distinction worth settling before you build anything: a card is not a technical drawing. The difference between a spec sheet and a technical drawing decides which document your buyer's engineer will accept.
Sources & References
