Request a quote vs. add to cart: which should a manufacturer's website use?
Use a cart only where the price, the spec and the stock are all known before anyone at your company looks at the order: stocked parts at a list price, or contract pricing a logged-in account already has. Use a quote request for anything configured, made to print, priced per job or sold in volumes that change the price. Those that sell direct usually end up with both, and the split is decided product by product, not for the whole site.
The question usually comes up during a manufacturing website redesign. Someone has seen a competitor's site with prices and a cart, or a large customer has asked whether they can just reorder online, and the agency wants to know which button goes on the product pages.
It's tempting to treat that as a design choice. It isn't. A cart is a promise that the website can tell a buyer the right price, confirm the part exists in the quantity they want and take the order without a person checking it first. A quote request is an honest admission that a person has to look before any of that is true. The right button is whichever promise your business can keep for that product.
This page is about where each product's page should lead. How buyers find the product in the first place is a separate question, covered in category pages vs. parametric search.
Key takeaways
- Decide per product family, not per site, and let a buyer move from cart to quote without retyping the order.
- If distributors carry your line, a link to where to buy may beat both buttons. That call belongs to whoever owns the channel, not the web team.
- A cart is only as reliable as the ERP data behind it: prices, stock and units of measure from the system of record, not a hand-kept copy.
- Some large accounts won't use either button and need a punchout from their own procurement system. Ask before choosing a platform.
At a glance
Which of your products could go in a cart?
Start with the catalog, not the website. Go through it one product family at a time and ask whether a buyer could order that item with nobody on your side checking anything. For most manufacturers and distributors the honest answer splits the catalog in two.
If you sell through distributors, weigh a third option first: a product page that sends the buyer to a distributor who carries the line. Public prices and a cart on your own site can undercut those distributors and cut across their territories, so whether a family is sold direct at all is a call for whoever owns the channel. The website follows it.
A product family is cart-ready when all of these are true:
- It has a fixed part number. The buyer isn't choosing dimensions, materials or options that create a new item.
- The price is known in advance, either as a public list price or as the customer's own contract price.
- Stock or a firm lead time can be shown, so the buyer knows what they're ordering before they place the order.
- Freight can be calculated, or is simple enough to quote a rule for, at the quantities people actually order.
- Nobody would need to review the order for fit, compliance or engineering before it ships.
| Product family | What decides it | Path |
|---|---|---|
| Stocked couplingsFixed part | Fixed part number, a list or contract price, stock held in the ERP | Add to cart |
| Couplings by the palletVolume | The same part, but the quantity or the freight changes the price | Quote from the cart |
| Valves with option codesOptions | Built from a fixed set of options, priced by rule | Configurator, then quote |
| Manifold blocks to printCustom | Machined to the buyer's drawing and priced per job | Request a quote |
| A line distributors carryChannel | Whoever owns the channel decides whether it's sold direct at all | Where to buy |
What has to be true in your ERP before a cart works
A cart puts your pricing and inventory in front of customers with no one in between, so whatever's wrong in that data turns into an order you have to call back about.
Prices are the first test. A public list price is easy. Contract pricing is where it gets harder, because each account may have its own price list, discount or quantity breaks, and the site has to show the right one after the buyer logs in. The platforms can show account-specific prices: Shopify's B2B catalogs, for example, set prices and quantity rules for each B2B market, or on the Plus plan for each company location (Shopify Help Center, checked November 2026). But the platform only displays the price. The ERP still has to hold it correctly, and somebody has to keep the two in step.
Then stock, units of measure and accounts. If the ERP sells a fitting by the each and the website shows it by the box of 25, the first order is wrong. If a customer's ship-to addresses, tax status or payment terms live only in the ERP, the site needs them too, or the order stops at checkout. The line PIM vs. ERP draws applies here: the ERP owns price, stock and how a product is ordered, and the website should get those from it rather than keep a second copy.
The question to put to whoever builds the store is simple: which of these will the site read from the ERP live, which will it copy on a schedule, and what does the buyer see when the two disagree? If nobody can answer yet, the cart isn't ready to launch, however good it looks.
| What the cart shows | Example answer | Your answer |
|---|---|---|
| List and contract prices | Read live from the ERP when the buyer logs in | |
| Stock or lead time | Copied from the ERP on a schedule, with the last update shown | |
| Units of measure | The ERP's selling unit, so a fitting sold by the each shows by the each | |
| Ship-to addresses, tax status, payment terms | Read from the customer's ERP account at checkout | |
| When the site and the ERP disagree | The order goes to inside sales for review instead of failing |
What a quote request handles that a cart can't
A quote path isn't the fallback for companies that haven't got round to ecommerce. For configured and made-to-print work it's the correct design, because the price doesn't exist until someone reads the drawing, checks the material and looks at the schedule. The RFQ process covers what the buyer is weighing on the other side.
What separates a good quote path from a generic contact form is how much of the buyer's work it carries forward. Start the request from the product page, so the part or product family is already filled in. Ask for the quantity, the date and the drawing, and accept the file types engineers send. Leave everything else for the reply. The RFQ page entry has the detail on fields and uploads.
Where products are configured from a fixed set of options with rules behind the price, a product configurator or CPQ can sit between the two paths: the buyer builds a valid configuration, and the result goes to sales as a priced request rather than a blank form.
A message box. The buyer has to say which part, how many and by when, then email the drawing separately.
Sales knows which part it's about before reading a word.
- Product family
- Filled in from the page
- Quantity
- Asked
- Date needed
- Asked
- Drawing
- Uploaded with the request
- Everything else
- Left for the reply
Running both: add to cart for stock, request a quote for the rest
Where you sell direct, the useful setup is usually both, assigned product by product, and some items carry both: the cart for normal quantities, a quote above the volume where the price changes.
The part that's easy to get wrong is the handoff between them. A buyer with ten stocked items and one custom part shouldn't have to place an order, then retype half of it into a form. The major B2B platforms each have a way to put a price review between the buyer and the order, and they work differently; the three are listed at the end of this section (vendor documentation, checked November 2026). Our ranking of B2B ecommerce platforms compares them, but which products go down which path comes from your catalog and your ERP, not the platform.
Two more buyers to plan for. Some existing accounts only want order history, reorders and documents, which is closer to a customer portal than a cart. And some large accounts buy only through their own procurement system. If yours do, a punchout or an electronic ordering link like the ones in EDI vs. API is a requirement to scope early, because it changes which platform makes sense.
The buyer submits a quote from the shopping cart as a request to negotiate the price, then checks out once both sides agree. Needs the B2B extension with quotes enabled.
The buyer submits a quote at list price, a sales rep updates the offered prices, and the buyer checks out against the quote before it expires.
A company location can be set to submit every order as a draft for review, so the checkout button becomes Submit for approval.
How to decide for your catalog
Run the decision on real data, one product family at a time. These questions usually settle it in a single meeting with sales and whoever owns the ERP:
- Which product families pass every test in the cart-ready list above? Start the cart with those and nothing else.
- Of the quotes sales sent last quarter, how many were for stocked items at a price that was already set? That's the work a cart could take off their desk.
- Do repeat customers buy at list price or at contract prices? If contract, can the ERP export each account's prices cleanly today?
- Who will own the prices and stock figures in the cart, and how quickly does a change in the ERP reach the site?
- Do any of your largest accounts require a punchout or electronic ordering? Ask their purchasing team before choosing a platform.
- What does a buyer needing one stocked part and one custom part do on the new site? Walk through it before launch.
The same order, on two versions of the same site
A maintenance planner at an existing account needs 24 stocked couplings they've bought before, and one manifold block modified to their own drawing. They go to your website to order.
- Both product pages end in the same Request a Quote button and a general form.
- They fill the form twice, or email their rep, which lands in the same queue.
- Inside sales prices the couplings by hand from the account's existing contract price.
- Both quotes come back the next day, and the planner replies by email with a PO.
With parts ordered a day later than they could have been, and a rep who spent time pricing an item that already had a price.
- They log in and see their contract price and current stock on the couplings.
- They add 24 to the cart and check out against their purchase order.
- On the manifold page they upload their drawing and request a quote for one.
- Inside sales spends its time on the manifold, the part that needs an engineer's read.
With the stock order placed in minutes, and a quote request that already names the part, the quantity and the drawing.
Common questions
What is a quote for purchase?
A quote is the supplier's written offer to sell a specific item or job at a stated price, usually with a quantity, a lead time, terms and an expiry date. The buyer reviews it and, if they accept, issues a purchase order against it. On a website, a request a quote button starts that process: it sends the supplier what they need to price the order, rather than taking the order itself.
What's an RFQ in sales?
An RFQ, or request for quotation, is a buyer asking one or more suppliers to price something they've already specified, such as a part to a drawing or a quantity of a known product. The supplier replies with a quote. It differs from an RFP, where the buyer describes a problem and asks suppliers to propose a solution; RFP vs. RFQ covers that distinction.
What is the difference between "buy now" and "add to cart"?
Add to cart puts an item in a basket so the buyer can keep shopping and check out later. Buy now skips the basket and goes straight to checkout with that one item. On a B2B site add to cart usually matters more, because buyers tend to order several line items at once.
Should a manufacturer show prices on its website?
Show them where they're fixed and the same for everyone who sees them, such as stocked parts at list price. Keep contract pricing behind a login, so each account sees its own. For configured or made-to-print work there's no price to show until someone reviews the request, so a quote path is the honest answer there, ideally with a typical lead time or a note on what affects the price. If distributors carry the line, check with whoever owns those relationships before publishing any price.
Request a quote vs. add to cart: can one product page have both?
Yes, and it's common for products where volume changes the price. Normal quantities go through the cart, and above a set quantity the buyer requests a quote instead. Adobe Commerce, BigCommerce B2B Edition and Shopify's B2B features each have a way to route a quote or order to review before it's final (checked November 2026); they work differently, so test the exact flow before choosing.
Do we need ecommerce to let existing customers reorder online?
Not always. If repeat customers mainly want to see past orders, reorder the same items and download documents, a customer portal tied to the ERP can do that without a public store. If they also want to browse and buy new items at their contract prices, that's B2B ecommerce with logins, and the ERP pricing questions on this page apply.
Sources
- Shopify Help Center, "Catalogs and pricing" help.shopify.com/en/manual/b2b/catalogs
- Shopify Help Center, "Draft orders" (B2B checkout and orders) help.shopify.com/en/manual/b2b/checkout-and-orders/draft-orders
- BigCommerce developer documentation, B2B Edition "Quotes" docs.bigcommerce.com/developer/learn/courses/b2b-graphql/quotes-lists/quotes
- Adobe Experience League, Adobe Commerce "Negotiable Quotes" experienceleague.adobe.com/en/docs/commerce-admin/b2b/quotes/quotes