B2B quote approval: how to turn agreement into an accurate order
B2B quote approval should end not with an email saying ‘we’ll take it’, but with an order containing the products, prices and terms the buyer accepted. This requires a fixed version of the quote, clear authority for everyone involved and a controlled handover to the business management system. A button in the portal only initiates this transition: clicking it does not yet confirm that the order can be fulfilled.
This article is for manufacturers, distributors and wholesalers who agree on individual terms through a website, CRM and ERP. CRM manages customer relationships; ERP holds accounting and operational data. We will focus on one specific stage: how to approve a commercial quote and turn the accepted version into an order without re-entering it manually. Choosing a contractor to build an online store is a separate task.
Where the quote ends and the order begins
Separate three events: the seller authorised the terms to be sent, an authorised buyer accepted them, and the business management system registered the order. There may be waiting periods, further approvals and rejections between them. If everything is labelled with a single ‘successful’ status, the sales manager will not see why the customer is already waiting for delivery while the warehouse has no document to work from.
In the Dynamics 365 Sales documentation, a quote goes through drafting, activation and revisions; an activated document is read-only. This is an implementation example, not a requirement to use a particular CRM. For your own portal, the important principle is that the version received by the customer must not change unnoticed while they are making their decision.
Agree on status names with the teams. ‘Awaiting seller approval’ is not the same as ‘awaiting the buyer’s decision’, and ‘being transferred to ERP’ does not mean ‘confirmed’. For each transition, define who performs it, its completion condition and the next action if an error occurs. Then the status helps people work rather than merely decorating a report.
What data must be fixed before the customer responds
A commercial quote version is an agreed set of terms, not just a PDF. Save the number and revision, the purchasing company, line items, units of measure, quantities, currency, prices and discounts. You also need the address, payment terms, delivery, validity period and the source of the promised dispatch lead time. The document and the data in the portal must describe the same deal.
Price and availability have different owners
Determine which system is the source of customer-specific pricing and which confirms that delivery is possible. An inventory record does not in itself prove that stock is reserved for a particular buyer. If time passes between calculation and acceptance, you need a revalidation rule: what can be confirmed automatically, and what goes back to the sales manager. Do not promise stock reservation if it does not actually exist.
Taxes, rounding and delivery also affect the total. Check not only the overall amount but also the line items: the same total may conceal a different quantity or unit of measure. If ERP recalculates the document during import, comparison with the accepted version must reveal any discrepancy before the customer is told that the operation succeeded.
Changes to terms require an explicit decision
A product substitution, a new address or a different quantity may change pricing and logistics. Do not automatically apply the old approval to new content. Create a revision, show the differences and request confirmation wherever the changes are material under company rules. Keep the old document in the history; the new one must not appear to have already been accepted.
How to separate internal approval from the buyer’s decision
The seller may have separate approvers for a non-standard discount, deferred payment and technical configuration. Set rules according to the nature of the risk: a sales director should not replace an engineer when checking compatibility. At the same time, a standard repeat delivery should not be delayed by the same approval route as new, complex equipment.
There are different roles on the buyer’s side too. An employee may prepare a request without having authority to approve company expenditure. In the portal, distinguish viewing, editing, submitting for approval and accepting. When integrating with corporate accounts, check how permissions change when an employee leaves or moves to another department.
Do not confuse the buyer’s internal budget approval with acceptance of the seller’s terms. The first step may authorise the procurement process to continue without yet creating an order. Button text must explain the consequence of the action. Those responsible for contracts should agree on how the agreement is documented; a technical log is no substitute for that work.
In the Adobe Commerce Negotiable Quotes process, changes by the buyer to the items or quantities send the quote back to the seller for review. This is a useful reference for designing the workflow, but the specific statuses and available features depend on the platform and its configuration. In your own system, they must be checked rather than assumed.
How to transfer the accepted version to ERP without duplicates
Design quote-to-order conversion as a controlled operation with an outcome. Send the quote identifier, its revision and the agreed line items. Expect an order number or a specific reason for rejection in response. A server response acknowledging receipt of a message does not yet confirm that the document has been registered.
A retry must not create a second order
The customer may click the button twice, and the integration may retry the request after a connection failure. You need idempotency: the same operation with the same identifier must not create another document. Store the link between the accepted revision and the order, and check it before retrying. Disabling the button in the browser is not enough.
An uncertain response is particularly dangerous: ERP may have created the order, but the website did not receive the result. Do not blindly initiate creation again. First reconcile the status using the operation identifier. Until the situation is clear, show the buyer that the request is being checked and give the sales manager a task to investigate. Make separate provisions for ERP unavailability and a queue for deferred transfers.
In Microsoft’s instructions for creating an order from a quote, products, the price list and currency are copied. However, price locking depends on the integration configuration. The presence of a built-in conversion button therefore does not remove the need to check pricing behaviour in your particular environment.
If the credit limit, company details or product codes fail validation, do not silently alter the accepted terms. Record the rejection, the person responsible and the permitted way forward. For the broader order fulfilment architecture, see the separate article on choosing an OMS for an online store; here, the scope of control is the accurate creation of a document from agreed terms.
Which level of automation to choose
Not every seller needs a complex configurator. Compare solutions based on how repeatable the terms are and the cost of an error. You can start with a version register and controlled manual order creation. Automation is justified when the rules can already be described and manual data transfer has become a noticeable source of delays or discrepancies.
| Criterion | Register and manual transfer | Portal and integration | Specialised CPQ |
|---|---|---|---|
| Nature of the terms | Infrequent, individually negotiated agreements | Recurring products and customer-specific price lists | Complex configuration dependencies |
| Main control | Version checked by a sales manager | Permissions, prices and transfer to ERP | Configuration and calculation rules |
| Additional costs | Team time spent transferring data | Data exchange and error handling | Licences and rule maintenance |
| When to defer it | When the volume can no longer be controlled manually | When there is no data owner | When an ordinary catalogue is sufficient |
CPQ is a system for configuring products, calculating prices and preparing quotes. It can help with complex products, but it does not eliminate the need for good master data and integration. Do not buy it merely to replace sending files back and forth. First establish whether the problem really lies in configuration rather than the absence of an accountable approver.
Pre-launch validation sequence
Limit the pilot to a clearly defined segment: for example, repeat orders for standard products from existing buyers. This is a proposed test scenario, not a description of a client case. It requires real, anonymised documents and expected outcomes confirmed by the person responsible for sales.
- Describe the workflow from draft to order number. For each status, record its owner, permitted actions and transition conditions.
- Map the fields in the portal, CRM and ERP. Check product codes, units of measure, currency, rounding, addresses and company association.
- Reproduce standard approval and exceptions: an expired version, a quantity change, rejection due to a limit and an unavailable approver.
- Repeat the click, interrupt the connection during transfer and restore the queue. Make sure the outcome can be reconciled without creating another, duplicate document.
- Compare the accepted quote with the resulting order line by line. Check the buyer notification and the sales manager’s task when there is a discrepancy.
- Start a limited flow with the option to stop automatic transfers. Expand coverage after analysing errors, not after the first successful order.
Check access separately: a buyer must not see another company’s prices, documents or history. For the seller’s employees, restrict the right to change terms and approve their own exceptions. The log must explain who performed an action, on which version and when; define the data recorded and retention periods according to company policies.
Timelines, costs and limits of the expected impact
The duration of the work depends primarily on the availability of an ERP test environment, the condition of master data and agreement on the rules. First describe the process and data, then test data exchange, develop the portal and run the pilot. If no decision has been made on stock reservation or the buyer’s authority, adding developers does not remove that uncertainty.
Include analysis, the interface, roles, integration, test scenarios, monitoring, training and support in the budget. Assess licences, data cleansing and maintenance following ERP changes separately. Ask for a phased estimate with assumptions and acceptance criteria: a single total without clear responsibilities does little to explain future expenditure.
Measure the impact from acceptance of a specific version to order confirmation, separately from the time the customer takes to decide. Alongside this, track line-item discrepancies, duplicate documents and reasons for manual intervention. Compare comparable types of deals; the speed of a standard repeat sale is not a benchmark for an engineered product.
Start with a transparent transition between documents, not a promise to automate every negotiation. If you need a B2B portal with versions, roles and controlled data exchange, discuss developing a web system tailored to your sales process with GL.ua (Glyanets). For a meaningful assessment, prepare an anonymised quote, the corresponding order and a list of situations that currently require a manual decision.
Just one step to your perfect website
