A buyer reads a product page from top to bottom: the application range, the specifications, a few photos from the floor or of a sample. It looks informative. At the end, where a price might have been, there are often four Chinese characters—价格面议, “price negotiable.” Below that sits another stock phrase, 欢迎来电咨询, “please call us,” or a button that simply says “inquire now,” with no further explanation. The buyer already suspects the product or solution might fit the project. What they want next is to request a quote. The page does not tell them where that request starts, whether they should prepare a model number, operating conditions or an order-of-magnitude quantity, who will reply, or whether what comes back will be a figure, a note on the solution, or an invitation to talk first. They have finished the information. They still do not know how to begin a quote request.
How a WeChat official account should publish content, how domestic search and content should connect to the website, how WeChat Channels generate leads, how to follow up after a trade show, and how official-account posts and website posts should divide the work—all have their own pieces, and this article will not reopen them. How a bilingual site should separately serve domestic and overseas buyers, what a buyer checks to verify that you are a real company, whether an inquiry can be completed inside the in-app browser of WeChat (微信), the messenger many sales teams in China use with buyers, and how to tell distributor inquiries from end-buyer inquiries are also outside the scope here. How to turn requests for samples, drawings and datasheets into trackable inquiries, which fields a form should keep, how to balance completion effort against lead quality, and what should happen after a submission is received, assigned and followed up, are likewise covered elsewhere. This article will not rewrite that field list, will not rewrite the four post-submit states, and will not rewrite how a technical-request entrance should be designed. Diagnosing a site that has traffic but no inquiries, checking a landing page, and how a service page should present range, evidence and the next step are also outside the discussion here. The narrower subject is this: many B2B companies cannot publish a price on the website that would match real deal conditions, because of project customization, volume tiers or channel policy. That is not a reason for the page to say nothing about how to request a quote, what kind of reply to expect, or what to prepare.
Not Publishing a Price Often Has a Legitimate Reason; What Turns People Away Is the Missing Path
In B2B, keeping a number off the page often makes sense. Change the configuration or the operating conditions on the same model, and the cost structure changes with them. A sample quantity, a small trial batch and a production volume do not close on the same terms. Some companies also work under different policies by region or by channel; a single published price list is liable to disagree with the deal that can actually be offered. What an end buyer sees may not be the condition a distributor buys at, and the terms that hold in one market may not hold in another. Project-based work is even less suited to a figure frozen on a page, because the number would have to cover a custom scope, installation conditions and a delivery rhythm all at once. Not publishing prices is not automatically a mistake, and it is not a requirement that every company lay every figure on the table. For many manufacturers, equipment suppliers and project-service firms, it is simply a way to avoid answering, with one number that will not fit, a question that can only be answered against specific conditions.
What tends to stop a buyer is not “there is no price printed here.” It is finishing the product page and still not knowing how to request a quote. They cannot tell whether to click a button, call a number that may no longer be staffed, or type “please quote” into a comment box that explains nothing. They also cannot tell what they need to provide for the reply to be useful: a model number alone, or operating conditions, a quantity range or a project window as well. More often still, the page is silent about what happens after submit—who will read the request, in what form a reply typically comes, and whether the team will actually receive it. So the buyer leaves, or takes the question to another supplier who is more willing to explain the process. Two companies may equally decline to publish a price. The one that writes the path down at least lets people see how a quote request begins.
“Price negotiable” and “please call us” are especially easy to mistake for a next step already written. They sound like an invitation to start talking, yet they do not say what happens after someone accepts the invitation. The buyer still has to guess: does “negotiable” mean leave a contact and wait for a callback, or must they first get through to a number on the page? Does “please call us” go to sales, a switchboard or an extension that is no longer in use? If the line is busy or unanswered, is there another way to send the request in? These phrases fall short not because they lack warmth, but because they only say “the price is not here” or “we welcome contact.” They do not offer a path that can be completed. A warm invitation is not a substitute for a path. A path answers where the entrance is, what to prepare, and what kind of reply follows a submission.
Spell Out the Entrance, What to Prepare, and What Kind of Reply to Expect
The entrance should sit where the buyer is already judging the product or solution—on the product or service page that states the range and the conditions of use—not only in a footer, or on a general contact page with no context. People decide to request a quote after they have asked whether the offering fits; if the entrance is far from that judgment, they have to hunt for “contact us” and re-explain the model they have just read about. The inquiry still happens on the service page. The quote entrance should be written next to the scope and the conditions, not left as a floating “please quote” with nowhere to attach it. How a service page helps a buyer see range, evidence and the next step is already covered in How to Write a B2B Service Page That Helps Buyers Take the Next Step; this article will not rewrite that structure. What has to be confirmed here is narrower: when a page has a legitimate reason not to publish a price, the same place should still make it visible how to start a quote request.
The path should also say what basic information the other party needs to provide if the request is to be taken seriously. For many industrial products and project-based deliveries, a useful starting point is not complicated: the model or solution of interest, the general operating or use conditions, and an order of magnitude—whether the conversation is about a sample, a small validation batch, or a volume that can already be discussed. With that, the person who receives the request at least knows which kind of conversation to open, instead of starting from a bare “please quote.” This is not an occasion to collect a complete customer file, or to demand a budget, a decision chain and an internal process at first contact. Which fields belong on a form, which should be required, and how to balance completion effort against lead quality is a separate subject, already covered in Which Fields Belong in a B2B Inquiry Form? Balance Effort and Lead Quality; this article will not rewrite that list. What has to be confirmed here is only that the basics needed for a quote request are written next to the entrance, and that what you ask for is what you actually use to reply.
The other thing that has to be clear is who will reply after submit, roughly in what form, and that the team will receive the request. The reply does not have to be a price precise to a decimal. Depending on how the team actually works, it may be a range that still needs conditions confirmed, a note that explains scope and fit, or a conversation to fill in what is missing. Any of those forms is legitimate, provided the page says what the team can really do, and provided you do not publish an “immediate exact quote” or “reply within ten minutes” promise the team cannot keep. The time range has to match real capacity. The submission should arrive in a place the team can see, not only in an unattended personal inbox or a private chat. How to confirm receipt, assign an owner, and distinguish qualified from pending is already covered in After the Form: Build a Reliable B2B Lead Handoff and Follow-up Loop. This article will not rewrite those four states, and it will not argue for any particular piece of software. It stops one step earlier: the person requesting a quote should be able to see that a team stands at the end of the path, not only a “we welcome your inquiry” with nothing behind it.
You Can Still Offer Information That Helps People Judge, Even Without an Exact Price
The absence of an orderable number on the page does not mean there is nothing to say except “negotiable.” Before requesting a quote, a buyer often still has to judge whether the question is worth asking: what range the product or solution is for, under which conditions it is not a fit, and whether their own operating conditions fall inside what you are prepared to take on. Stating the application range, the boundary and the cases you do not take on cannot replace a quote. It can reduce a common kind of wasted motion—in which the request is for a configuration you do not offer, or the proposal you send back does not match how they will use it. That kind of writing helps judgment, not pricing. It lets the quote request start inside a range both sides already recognize.
Minimum-order or volume logic can also appear as an explanation, without being written up as a public price list. You might say, for example, that a quote has to be discussed against configuration and quantity, because a sample, a small batch and a production volume do not close on the same terms; or that different regions or channels may follow different policies, which is why the page does not offer one number that holds for every visitor. Lead time works the same way. Rather than hanging a “standard lead time” the team cannot keep in every case, say that lead time is evaluated against configuration, whether customization is involved, and the current production schedule—and say what you need from the other party in order to evaluate it. If you accept requests for samples or drawings, the same page should note whether that path is open and how to start it; turning those technical requests into trackable inquiries is already covered elsewhere, and this article will not expand it. None of this is advice on how a company ought to set its prices, and none of it asks you to publish a number that should not be public. It is only a way, when an exact price is absent, to leave the buyer the non-price information that still helps them judge.
This information will not let a buyer place an order on the page. It can help them decide whether requesting a quote now is something they are ready to do. Ready, here, means they know roughly which model, which kind of operating condition and which order of magnitude they are asking about, and they know whether what follows submit is a range, an explanation or a further conversation. Without that, a quote request easily collapses into a bare “please quote,” and sales still has to start from the first question. Putting non-price information next to the entrance is a way to make the moment of asking line up with the reply that follows—not a way to fill the missing price with more adjectives.
Start With the Page People Visit Most
The next action can stay specific. Open the product or service page that currently draws the most visits, and look at what sits after “price negotiable” or at the end of the specifications: is there a quote path that can actually be completed? Does the entrance sit next to the range and the conditions? Does the page say that a model, operating conditions or an order-of-magnitude quantity will help? Does it say who will reply, and roughly in what form? Will the submission arrive where the team can see it? Do not let “please call us” carry the next step on its own, and do not use the occasion to add every other field at once—what else belongs in the first step still belongs to the field-design discussion. How requests are assigned and how their status is tracked after submit is covered in the form-to-deal article; this piece will not expand that. The entrance itself should still complete successfully; if the buyer opens the page inside WeChat, the request has to be able to go out first—that point has its own article, and this one will not expand it. To put “making the quote path clear” back into the larger question of being found, understanding the offer and starting a conversation, see our website acquisition guide. To compare which part of the path is currently stuck, the solutions overview shows what search, pages and technical work can each add. These are suggestions about how the work connects, not a promise of inquiry volume or conversion results.
VisioBound (增界) is operated by Shanghai Aigesihua Media Technology Co., Ltd. We help B2B companies with SEO, Google Ads and Baidu PPC management, GEO (AI-search visibility), on-site factory video production, and WordPress technical support. Based in Shanghai, we connect search, advertising, and content to clear service pages and inquiry paths for both domestic and overseas acquisition.
If you want to sort out how the website should present a clear path to request a quote when prices cannot be published, start with About VisioBound or contact us.
Frequently asked questions
Is it necessarily wrong not to publish prices on the website? Do we have to make every figure public?
No. When configurations differ, volumes differ, or regional and channel policies differ, a page of listed prices is liable to disagree with the terms that can actually close. Not publishing a quote often has a legitimate reason in B2B. It is not automatically a mistake, and it is not a rule that every company must disclose every price. What still needs to be written is how a quote request starts, what to prepare, what kind of reply follows submit, and that the team will receive the request. A clear path and a public price are not the same thing.
Why aren’t “price negotiable” and “please call us” enough to stand in for a quote path?
Because they do not tell anyone what happens next. The buyer still does not know which entrance to use, which basic information to prepare, who will reply, whether what comes back will be a range, a note on the solution or a further conversation, or whether the message will be received by the team. “Price negotiable” only says the price is not on the page; “please call us” only says contact is welcome. Neither one offers a path that can be walked to the end. Warm wording is not a substitute for those explanations.
Do we have to ask for budget, the decision chain and every technical detail before we can start quoting?
No. What a first quote request actually needs is often just the model or solution, the general operating or use conditions, and an order of magnitude. That is enough for the person who receives it to open the conversation in the right direction. A budget, an internal decision chain or a complete technical file is not a prerequisite for asking. Loading all of that into the first form can stop someone before they have decided to ask at all. How to choose fields, and which should be required, is covered in the form-fields article; this piece will not rewrite that list.
