Polymr
Chemicals · case study

Quote-to-PO compressed from days to hours.

Buyers parsed inbound supplier quote PDFs and tallied them in spreadsheets before drafting POs back in Oracle. Quote-to-PO loop averaged three business days.

Outcome
85%

reduction in quote-to-PO cycle time.

Customer

Specialty chemicals producer, single facility

The source stack.

The systems Polymr reads from and writes back to for this workflow.

  • Oracle Fusion ERP
  • Outlook
  • Vendor portals

Measured outcome from a live customer deployment.

What Polymr automated.

Inbound quotes parsed across email and portal, scored on price, lead time, MOQ, and supplier reliability against a rolling baseline. Recommended PO drafted in Oracle for buyer signature.

A buyer's morning. Quote to PO inside an hour.

The narrative below is reconstructed from one real morning during the deployment. Three supplier quotes, one buyer, one PO out the door.

  1. 01T+0

    Quote PDFs arrive.

    Three supplier quotes land in the procurement inbox between 08:40 and 09:12. Each in a different layout.

  2. 02T+6m

    Polymr parses them.

    Price-per-unit, lead time, MOQ, payment terms, freight basis extracted across all three. Supplier reliability pulled from the rolling 12-month baseline.

  3. 03T+9m

    Scored against the baseline.

    Vendor 2 wins on landed cost; Vendor 1 wins on lead time; Vendor 3 ranked third on reliability. The trade-off is surfaced explicitly to the buyer.

  4. 04T+14m

    Draft PO in Oracle.

    Recommended PO drafted in Oracle Fusion with the winning vendor pre-selected. Buyer signs at T+22 minutes after a short confirmation.

22mfrom first quote in the inbox to a signed PO in Oracle. The prior baseline was three business days.

What this looks like inside Polymr.

The screenshot below is the live tenant view that powers the workflow described above.

/deals/pipelineQuote-to-PO pipeline view
Polymr deals pipeline showing quote-scoring step ahead of PO draft step