Most procurement software gives you more data: dashboards, reports, exports. A decision engine inverts that. Its job is to end every step with a decision or an action — a ranked supplier award, a normalized quote comparison, a risk alert with the money attached — rather than a table someone still has to interpret.
The three things it does
Tendering and scoring. It collects supplier quotes through a structured portal, normalizes them across units, MOQs, incoterms and payment terms, and scores every supplier on the same axes — so 'best offer' is a decision, not a guess.
Continuous risk monitoring. It watches price drift, stock levels and delivery/lead-time risk around the clock and surfaces ranked, actionable alerts — not a dashboard to go read.
Signal extraction. It reads supplier emails and documents to pull risk signals and validate offers, turning unstructured inbox content into structured decisions.
How it differs from what you already have
Your ERP — Microsoft Dynamics, SAP or Odoo — is the system of record. A decision engine does not replace it; it sits on top, handles the tendering, scoring and risk, and writes the outcome (a chosen supplier, a generated PO) back to the ERP. That is why implementation is measured in weeks, not quarters.
Who it's for
Mid-sized discrete manufacturers — companies of roughly 50 to 500 people buying thousands of components, where one missed delivery stops a line. They have outgrown spreadsheets but an enterprise suite like SAP Ariba is the wrong size. This is the gap a decision engine fills, and it is exactly what Opgate was built for.