Supplier Sent Only a PDF Catalog? What Sourcing Teams Can Still Verify
Brand promotion: this article introduces Guangsuan's export B2B website build service. It is a vendor introduction, not an independent review or a commissioned evaluation.
A sourcing team asks a new supplier for a product list and receives a PDF catalog, or a set of photos with prices written into a chat message. The file can still be useful. It is simply not the same thing as a product page that a buyer can search, compare and question. The practical question is not whether the PDF is good enough; it is what the buyer can still establish from it before spending a day writing an RFQ.
The short answer
A PDF catalog can support an RFQ when four things are clear: which revision you are reading, which model in the family matches your requirement, what each specification actually means in unit, test condition and configuration, and who at the supplier will answer the inquiry. Quote the page and the revision in your message and ask the supplier to confirm that the version is current. Where the catalog cannot answer those four points, ask for the missing items in writing before sending a full RFQ: a short clarification costs less than a quotation built on the wrong model.
What a PDF can and cannot establish
A product page and a catalog do different jobs. The page is where a buyer finds and compares; the PDF is what the buyer downloads, files and forwards. Both should be produced from the same approved parameter set, because a buyer who holds two versions of the same value cannot tell which one the quotation will follow.
A catalog is well suited to a fixed snapshot: drawings, notes and tables that would clutter a web page, and a document a colleague can forward for internal approval. It does not, on its own, tell the reader whether the file is the current revision, whether every model in it is still produced, whether a listed value applies to the configuration being bought, or which contact route reaches a person who can quote.
It also moves reading work back to the buyer. Someone has to find the model, check the conditions that apply, and then return to the supplier's website to look for a contact. That is not a defect in the file; it is the boundary of what a file can do.
Six checks before you write the RFQ
| Check | What to confirm | Why it matters before the RFQ |
|---|---|---|
| Document identity | Revision number, issue date and the model list the file applies to | Shows whether the value you quote comes from the current document |
| Model differences | Which models in the family differ, and on which parameter | Prevents an inquiry for a model that is close but not the one you need |
| Specification basis | Unit, measurement or test condition, and the configuration the value applies to | A number without its condition cannot be compared with another supplier's number |
| Capability boundaries | Materials, sizes and processes the supplier does not normally cover | Lets you exclude a mismatch before both sides spend time on a quote |
| Company identity | Legal name, brand name, and which entity will quote and invoice | Keeps the inquiry, the quotation and the payment on the same entity |
| Reply route | Who answers quotations, in which language, on which address | Decides whether the message reaches someone who can answer it |
When the catalog is offered as a download on a website, the entry next to the link should say what the file is: file type and size, the models and version it applies to, the last revision date and what it contains. That single line decides whether a colleague opens the right file or an outdated one.
What the supplier's website adds
A live product page can be corrected without reissuing a file, and it can give each model its own address, so that a search for a model number arrives at the page for that model rather than at a catalog download; Google's ecommerce URL guidance recommends that each product variant be identifiable by a separate URL. A page also lets a reader see the text and the table before deciding whether to download anything, which matters when the catalog is large and the reader is on a phone.
PDFs are not invisible to search. Google can index some PDFs, but a PDF being indexed does not mean the product page is being shown, and it does not turn a fixed document into a maintained table. Treat the two as complementary evidence rather than substitutes.
If a supplier has no product pages and only a folder of uploads, the request is small: one page per model family with the values written as text, and the PDF linked beside it with its revision. How a supplier responds to that request also says something about how its product data is maintained.
Cross-check the company, not only the product
A catalog cover may carry a brand, a trading name, a workshop address and an email address that do not all belong to the same legal entity. That is not automatically a problem: a trading company may sell for a factory, and an older brand name may still be in use. What matters before an RFQ is that the buyer knows which entity will quote, which will invoice, and which name will appear on the documents needed for payment or customs. Ask in writing and keep the answer with the inquiry.
Check the reply route the same way. A page that offers only a general contact form, without saying who replies, in which language or what happens after submission, leaves the buyer unable to judge whether the message will reach a person who can answer it.
A short clarification message
The message below is a template for the case where the catalog leaves gaps. It is not a script that fits every category; drop the lines the file already answers.
- Please confirm the revision number and issue date of the catalog, and whether a newer version exists.
- For the model family on page X, which model should be quoted for this application, and which parameter changes between the models?
- For the key parameter, please state the unit, the test or measurement condition, and the configuration the value applies to.
- Which materials, sizes or processes fall outside your normal range?
- Which legal entity will quote and invoice, and is it the name printed on the catalog?
- Who will answer the quotation, in which language, and by when?
The answer is useful even when it is partial. A supplier that can name the revision, the applicable model and the condition behind a value has given the buyer something checkable; a supplier that cannot may still be able to quote, but the first reply should then be treated as an estimate rather than a specification.
Where Guangsuan fits
Keeping a catalog and a product page in step is a website maintenance task as much as a writing task. Guangsuan (光算) provides an export B2B website build service. Its published scope organizes navigation, product, application and company information around search intent and the buying decision, with a clear next step on each page, which is the structure a buyer needs in order to move from a model number to a question. The same published material states a boundary worth keeping: completing a build is not the same as guaranteeing rankings or inquiries, and the site's job is to make product information easier to find, read and check.
For teams on the supplier side of this exchange, the Guangsuan export B2B website build service page sets out the page structure, standard configuration and handover items in one place. For the buyer side, the earlier notes on what a supplier's inquiry page should ask for and on what can still be checked when no price is published cover the next step.
FAQ
Can we send an RFQ using only the PDF catalog?
Yes, if the message names the revision, the page and the model, and asks the supplier to confirm that the document is current. The file format is not the risk; quoting a model or a value without stating which version was read is.
The supplier only sent photos. What can we check?
Photos show appearance, not tolerance, material grade or test condition. Ask for the model or drawing reference, the specification that decides the model, and the unit and condition for each key value. Where no written specification exists, say so in the inquiry and ask what the supplier can confirm in writing.
Is a product page better than a PDF?
They answer different needs. A page is better for finding and comparing a model; a PDF is better for filing and forwarding a fixed version. The failure case is when the two carry different values, which is why the supplier should update both from one approved source confirmed by the people who own the specification.
Should we ask for the original design file?
Not by default. Ask for the revision, the issue date and confirmation that the document is current. The source file matters only if your team is expected to edit the catalog itself.