Library · Evidence · 6 minutes
Quote funnel · Integrated Quoting
Where the demand was lost, and what the fix changed.
Explore the Integrated Quoting workflow and local routing examples. Follow the commercial workflow, then try the illustrative eligibility inputs and unit-of-measure calculation.
01
QUOTING · REQUEST THROUGH ORDER
Before v2: the engine decided who got an answer.
Rounded proportions
Before: engine-eligible only
- Quote request The buyer requests volume pricing from Amazon Business and third-party providers
- Catalog match Identify the requested product and available inventory
- Quote routing Select an appropriate pricing response for suitable demand
- Quote response Return pricing in the buyer’s requested unit
- Won quote Lock price and reserve inventory while the customer orders
After: answer every matched request
- Requests received
~100%
Unchanged - Catalog match Unmatched lines can inform catalog follow-up
- Response path
Illustrative routing separates bulk quoting from other matched demand - Bid returned on time
design intent
Automated bid selection removes the operations ceiling
The confirmed workflow locks price and reserves inventory after quote win. Ordering API/XML handles order submission, followed by Reconciliation/Invoice API. The routing thresholds below are local policy examples, not measured funnel results.
02
Unit of measure · a fix sized in engineer-weeks with a high conversion impact
Why a correct price looked wrong.
Requests arrived with every line’s unit of measure defaulted to “each”, so a pack price looked like a unit price and Amazon appeared overpriced. The fix: take the buyer’s unit, compute the product quantity, and return the price in the unit they asked for.
Interactive local examples · Integrated Quoting
Amazon Business · Integrated Quoting
From a quote request
to an order.
Volume pricing becomes an orderable commitment after the quote is won.
After the quote is won ↓
Commercial workflow. Local eligibility and unit conversion examples are illustrative, not measured results. Select a labeled step for an overview and process details.
Read the complete process
Quote request
Enterprise buyers request quotes from Amazon Business and third-party providers inside their sourcing platform. The response path makes product match, available inventory and the requested unit explicit.
Process note: The request form is simplified. It contains no buyer identifier, historical conversion rate or recorded quote.
Volume pricing
Catalog match and availability inform a suitable response. A pack price and an each price cannot be compared without conversion factors. Illustrative arithmetic: $4.25 × 12 ÷ 6 = $8.50 per case of 12.
Process note: Illustrative eligibility: more than 1,000 units OR more than $10,000. Exactly 1,000 units and $10,000 does not meet either strict threshold. The existing local calculator remains the place to try inputs.
Quote won
After a quote is won, the workflow locks price and reserves inventory while the customer orders. This is the commercial transition between quote response and the order path.
Process note: No win rate, completed pilot, lock duration or reservation duration is asserted.
Lock price + reserve
Price lock and inventory reservation follow quote win and support the customer while they order. The two objects in the illustration are parallel commitments in this same state.
Process note: The lock and stock specimens show function. They do not imply a specific time limit or inventory quantity.
Submit the order
The customer submits the order through Ordering API/XML. This order-submission role follows the won quote and its price lock and inventory reservation.
Process note: The XML page is a conceptual artifact; it is not an actual API schema or customer payload.
Post-order follow-through
Reconciliation/Invoice API supports the post-order workflow. Its role is distinct from Ordering API/XML, which handles the submission of the order.
Process note: The invoice specimen is illustrative. No invoice amount, fulfillment rate or reconciliation outcome is added.
Explore the workflow and illustrative routing
Quote request through order
Commercial quoting workflow
After a quote is won, price is locked and inventory reserved while the customer orders. Ordering API/XML handles submission; Reconciliation/Invoice API follows the order.
Read the routing example
Illustrative routing distinguishes bulk quoting from other suitable matched demand. Product match, availability and the requested unit are explicit. These examples describe policy choices and arithmetic, rather than measured funnel results.
Who gets a response?
Try an illustrative policy that separates bulk quoting from other matched demand.
Read the eligibility rules
In this local policy example, bulk eligibility is strictly more than 1,000 units of one product OR more than $10,000 total. At exactly 1,000 units and $10,000, a matched request uses the other offer path. An unmatched product needs catalog follow-up. Inputs must be finite and positive.
What does the price mean?
Return the price in the requested unit, with the conversion factor visible. Quantity uses the selected buyer unit.
Price in the buyer’s unit
$8.50per case of 12 · factor 12 ÷ 6 · 960 sold units for 5,760 individual unitsRead the conversion arithmetic
Price in the buyer’s unit = price per sold unit × buyer unit factor ÷ sold unit factor. The example is $4.25 × 12 ÷ 6 = $8.50 per case of 12. Quantity and price, both factors, and the calculated results must be finite and positive.
Inputs are local examples; nothing is submitted or stored. Commercial workflow, illustrative policy and conversion arithmetic are identified separately.