Work · 13 of 17 · Deep dive · 9 minutes
On this page
Enterprise commerce / Case study
Integrated Quoting: we were optimising the wrong engine
Integrated Quoting lets enterprise buyers request quotes from Amazon Business inside their sourcing platform. I worked on the response strategy and unit-of-measure interpretation. The workflow connects quote requests, volume pricing, a won quote with price lock and inventory reservation, ordering, and post-order reconciliation.
Amazon Business · 2022–2024 · from my work, written for public reading
Where quoting fits in the buying journey.
Prescription: From prescription to the next refill.
Clinical and billing checks may run in parallel. Controlled-substance checks and reporting are conditional branches, not a universal extra step.
- Receive & prepare. Prescription, patient and medication details enter intake. New Rx, transfer and renewal are separate entry paths. Supporting account
- Coverage & billing. Coverage and cost information are checked; early billing is a proposed sequencing branch. Early billing may overlap verification. Reversal or rebill is a controlled human/system action, not AI authority. Supporting account
- Verify, DUR & PDMP. A pharmacist reviews clinical signals; controlled-substance work follows applicable requirements. DUR; dose/allergy/interaction concerns; controlled-substance checks. Existing reporting detail remains below. Supporting account
- Order & readiness. The patient confirms applicable price and order details; readiness checks govern release. Customer ordering and pharmacy release are distinct states. Supporting account
- Dispense & deliver. Final checks, dispensing and delivery carry the prescription to the patient. Controlled-substance reporting is tied to applicable dispense/reporting requirements, not universally to delivery. Supporting account
- Care, report & renew. Patient questions, required reporting and renewal needs feed the next cycle. Care runs across all stages. Reporting and refill/renewal are parallel follow-through paths. Supporting account
Read the original prescription map
AI-assisted care: One contact. Context that leads to care.
Production console capabilities and the public agentic design study have separate evidence. Amazon Pharmacy SMS/OTP authentication launched. Automated wrap-up is a separate capability whose delivery status is unspecified.
- Contact & verify. A customer contacts Amazon Pharmacy care; an automated text/SMS code replaces the former manual verification step. Amazon Pharmacy customer-care authentication. Separate from Cigna health-plan enrollment and Kafka work. Supporting account
- Assemble context. Relevant order, prescription and prior-contact context becomes a useful brief. Retrieval and summarization help the representative; they do not grant authority. Supporting account
- Review & decide. A representative reviews the brief and chooses a permitted next step. End-to-end product leadership and key decisions span capabilities; individual implementation roles and shipped outcomes are specified separately. Supporting account
- Act & reconcile. The permitted action is executed and its actual result checked. Clinical escalation and billing explanations do not imply autonomous clinical or financial writes. Supporting account
- Explain & close. The customer receives an explanation and an appropriate next step. Different capabilities’ outcomes are measured separately. Supporting account
- Evaluate & improve. Quality review and feedback improve the next contact. Human review gates knowledge updates and any deployment. Supporting account
Procurement: From catalog setup to a reconciled order.
Hosted catalog, PunchOut and quote requests are alternative entry paths. They converge at approval and ordering; every purchase does not require a quote.
- Onboard & configure. Buyer and supplier agree account setup, content and integration requirements. Supplier and customer changes both re-enter configured review. Supporting account
- Browse & build need. A buyer uses a hosted catalog or a PunchOut shopping experience. Direct catalog shopping and PunchOut are distinct paths; Punch-in is separately preserved. Supporting account
- Source & quote. When quoting is needed, the seller matches demand and communicates price and terms. Quote creation and price-lock terms are distinct from award; award triggers inventory reservation. Quoting is optional; direct catalog purchasing can bypass this branch. Supporting account
- Award & order. Quote award triggers inventory reservation. After award, an award receipt is sent through integration. Order placement uses the applicable ordering interface. Award-triggered reservation and post-award integrated receipt apply to the quoting path. Direct purchases retain their applicable approval/order path. Supporting account
- Fulfill & inform. The seller fulfills the order and communicates its status. Retain the existing case’s quote controls and arithmetic demonstration. Supporting account
- Invoice & learn. Invoice, receipt and order context support reconciliation and future improvement. Feedback can improve catalog data, unit interpretation or partner onboarding. Supporting account
Payer & PBM: From plan design to care and reconciliation.
This is a capability map with branching paths, not a mandatory sequence. Employer/group and individual/family enrollment differ; medical, pharmacy and rebate processing have separate contracts.
- Client & plan. Plan configuration includes network participation and preferred-pharmacy choices where applicable at Rx level. Group and individual/family market paths remain distinct. Pharmacy network contracting and clinical governance have different responsibilities. Supporting account
- Enroll & identify. Open-enrollment intake, active enrollment setup and premium payment connect the IFP experience. Programs included ACA/Obamacare and Cigna participation in state-sponsored plans. Specific programs may differ. Supporting account
- Access & experience. A member finds care, checks benefits and uses digital or assisted service. Networks, digital experience, ID cards and ongoing care remain continuous capabilities. Supporting account
- Medical ↔ pharmacy. Medical and pharmacy claims follow different paths; a shared drug catalog supports pharmacy data and rule use. Formulary, step therapy, exclusion, prior authorization and MAC lists are nested catalog capabilities. FDA status is distinct from list inclusion. Supporting account
- Pay, explain & rebate. Rebate finance connects PBM/manufacturer contracts, pharmacy-claims calculations, invoicing, reconciliation and client sharing. Separate from provider payment/835 and member EOB. Sharing included 50/50 and fixed-sharing options; no other terms are implied. Supporting account
- Report, change & renew. Operational and financial feedback informs corrections, product changes and renewal. Actuarial/reporting, client feedback, IFP changes and member renewal remain connected parts of the product-leadership journey; specific decisions, delivery roles and outcomes are described separately. Supporting account
01
1 / 9 · Executive brief & flow
Respond to suitable matched demand, make the requested unit explicit, and connect a won quote to price lock, inventory reservation and ordering.
- Request
Enterprise RFQ arrives via cXML from the e-sourcing platform - Request → catalog match → pricing → quote response → win → order
- Diagnosis
Eligibility and representation, not the interface - Options
Console, eligibility, marketplace offer, more partners - Phase 1
Price lock, UOM fix, bid selection, reporting by April; EU and JP after
Product workflow, shown through the decisions and handoffs.
02
How it was tested
A proposed shadow comparison checks responses against buyer units and contract conditions before changing live routing.
Results and expansion
Because the marketplace offer does not depend on the quote engine, the same mechanism could launch in Europe and Japan directly after North America, an opportunity I sized in the tens of millions of dollars annually from ten partners and tied to the top long-term goal of quote-pricing automation. The commerce document series on this site walks the work from problem statement to review.
What I learned
A conversion problem can be an eligibility problem, a representation problem or a mismatch with the buyer’s job. We were optimising the wrong engine. Naming which is which is worth more than the next feature.
From my original account
03
What the funnel showed
The response strategy distinguishes catalog matching from quote routing and makes the buyer’s requested unit explicit. A pack price and an each price cannot be compared without their conversion factors. The local example below demonstrates that arithmetic; it does not represent a measured conversion rate.
The decision
The workflow begins with a quote request and volume pricing. When the quote is won, price is locked and inventory is reserved while the customer orders. Ordering API/XML handles order submission; Reconciliation/Invoice API supports the post-order workflow.
| Change | Effort | Effect |
|---|---|---|
| Unit-of-measure conversion on request and bid | About two engineer-weeks | Removes the “looks overpriced” rejection on pack-priced lines |
| Price lock and inventory reservation after quote win | Phase 1 core | Connect a suitable quote response to the buyer’s order |
| Automated bid selection via engine rank | Medium | Removes manual selection from the response path |
| Automated product enrichment | Phase 2 | Removes the ~3,000-a-week operations ceiling |
The integration advantage
Enterprise buyers do not shop. They procure — through platforms with names like Coupa, SAP Ariba, Jaggaer and Oracle, with approval workflows and purchase orders and a rule that the price on the invoice must be the price that was approved. At an enterprise-commerce business I owned the products that connected a marketplace to a range of those platforms, across the US, Europe and Japan.
The core integration lets a buyer punch out from a procurement system into a marketplace, shop and return the cart for approval. Integrated accounts were strategically important to the business. The product problem extended beyond adding capabilities: customers faced a lengthy path to useful adoption.
Integrated Quoting connects quote requests and volume pricing to a won quote, price lock, inventory reservation and order submission. Ordering API/XML and post-order Reconciliation/Invoice API have separate roles in that workflow.
Then there was quoting. The product that let a buyer request a quote through a sourcing platform was not converting, and the team was working on the quote engine. I pulled funnel data and separated product matches from requests eligible for the existing response path. The analysis also exposed a unit-of-measure interpretation problem: a price expressed per pack could look wrong to a buyer comparing individual units. These were different causes requiring different changes.
The response strategy considers suitable matched demand and explicit unit-of-measure conversion. Price lock and inventory reservation follow a won quote. Shadow comparison is an illustrative way to validate a routing change.
Integrated search taught the same lesson from another angle. Low conversion could not be understood from relevance alone: visibility within the buyer’s experience mattered. I used the available evidence to distinguish whether customers rejected the result or rarely saw it. You cannot fix what you have not measured, and you cannot measure what you have not instrumented.
Tools in this chapter Punchout / cXML · CIF catalogs · UNSPSC · Coupa · SAP Ariba · Jaggaer · Oracle · price-lock API · SSO · funnel analytics · WBR / QBR mechanisms
04
The situation
Integrated Quoting connects Amazon Business quoting with external sourcing platforms. Buyers request a quote from Amazon Business and third-party providers; the response path must make product match, availability and the requested unit clear.
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.