Polymr
Workflow

A drawing in. A clean BOM and a vendor packet out, the same hour.

Inbound RFQs arrive as a PDF drawing and a STEP file attached to a one-line email. Estimating, engineering, and purchasing each open the same file separately, often days apart. Polymr collapses that loop. The file becomes a structured BOM proposal the engineer reviews next to the original. Approved rows go out as per-vendor RFQ packets, and the estimator’s draft quote lands on the same page. One source file, three roles, one approval.

The CPQ rule is the price. No hidden math, no carryover spreadsheet.

The view below shows the configured pricing logic for a brake hub: inputs on the left, the cost breakdown on the right. Material rollup pulls from the live BOM. Labour standard pulls from the routing master. Burden pulls from cost-centre settings the controller already owns. Every input writes a row; every change re-runs the breakdown.

CPQ.brake-hub.v6Rule preview
within band
Inputs
Material
A36 zinc
Geometry
PMR-4031.step
Tolerance
ISO 2768 fine
Finish
zinc B633
Qty
4
Derived price tree
material rollup$ 38.10
+ hub forging$ 22.40
+ bearings . bolts . seal$ 15.70
labour standard$ 9.40
burden + finish$ 5.40
cost / ea$ 52.90
quote @ 22% margin$ 64.55
Audit: rule v6 from CPQ template brake-hub, labour standard from routing master RT-218, refreshed 09:42.

One drawing in. A structured cut-list and a make-or-buy call.

A revised drawing lands and the engineer opens this view. The header shows the drawing revision and the changes from the previous one. The body is the cut-list extracted from the drawing, with every row tagged for material, finish, and whether to make it or buy it. The buy rows go out as per-vendor RFQ packets the same hour the engineer approves the diff.

app.polymr.tech/inbox/drawings/DWG-PMR-4031-v6

DWG-PMR-4031-v6 · brake hub assembly

Posted from PDM 2026-05-29 16:42 · prior rev v5 · CN-1187

Polymr ERP
Revision diff v5 → v6+ 2 lines- 1 line~ 1 spectolerance ISO 2768 fine · finish zinc B633
  • + bolt M8x24 A325 · qty 4 · A325
  • + lock washer split 8mm · qty 4
  • - bushing std · qty 1
  • ~ seal ring EPDM → FKM 38mm
Cut-list extraction8 lines · parser v8.2 · conf 0.92
LineDescriptionQtySpecM/BRoute
L01hub forging1A36 zinc · zinc B633buyRFQ-4844 → V-218, V-301
L02bearing race 38mm252100 · as-rolledbuyRFQ-4845 → V-201
L03cone insert1brass · plainbuyRFQ-4845 → V-218
L04seal ring FKM1FKM 75 ShbuyRFQ-4846 → V-244
L05bolt M8x24 A3254A325 · zincbuycat · V-301
L06lock washer split 8mm4spring steel · zincbuycat · V-301
L07finish + plating1 opzinc B633makeWC-FN-02
L08cure + assembly1 op-makeWC-CR-01 · RT-218 L2
3 new RFQs queued; awaiting engineer sign-off on rev-v6 spec change.approve → fan to 4 vendors

Three quotes side by side. The recommendation is on the row.

Open an RFQ and the comparison opens. Unit price, lead time, MOQ, payment terms, status badge. Polymr converts every quote to landed cost on the same incoterm so the buyer is comparing apples to apples. The "preferred" tag is a recommendation, not a hard assignment.

RFQ-4821 . quotesHex bushing 5/8 in . 3 vendors
Award pending
VendorUnitLeadMOQTermsStatus
Acme Industrial$4.2014d500NET-45Preferred
Northstar Components$4.5521d250NET-30Approved
Pacific Castings$3.9828d1,000NET-30New vendor
Audit: line items parsed from vendor email, normalised to landed cost FOB-dock, 2026-05-30.

A discrete shop with three customer engineering teams feeding the queue.

Anonymised engagement with a discrete contract manufacturer. Three customer engineering teams kept the inbound queue full of mixed drawing formats. Time from drawing arrival to approved BOM dropped from days to the same shift.

Anonymized engagement
Operations director, contract manufacturer of mechanical sub-assemblies
Situation
Drawings landed from three customer engineering teams across the week. Each revision triggered a full BOM re-type into the ERP, an RFQ packet build, and a sweep of open POs for downstream impact.
What was breaking
Of every ten revisions, two missed an affected open PO. Those misses surfaced 3–5 weeks later as the wrong rev shipped to a customer, a scrap event on the floor, or a vendor invoice that no longer matched the PO.
  • BOM extraction + RFQ
  • Engineering revisions
  • Quote-to-procure
Outcome · 6 weeks
100%
Revision-to-PO coverage
was 78%+22 pts
Illustrative, reflects this specific deployment. Outcomes vary by plant, stack, and scope.