ERP add-on
A supplier performance layer on top of your ERP
Keep SAP, Coupa, Dynamics 365 or Oracle as the system of record. Add EvaluationsHub on top for the part ERPs leave thin: structured input from the people who work with suppliers, scorecards suppliers can see, and corrective actions that get closed.
Short answer: Your ERP already knows what was ordered, received and invoiced. It rarely knows what quality, the plant and the project team think of a supplier, or whether last quarter’s corrective action was done. EvaluationsHub adds that layer without replacing anything.
How the layer works
What stays in the ERP, and what the layer adds
| ERP (system of record) | EvaluationsHub (layer) | ||
|---|---|---|---|
| Supplier master, POs, invoices | Owns it | Reads it | |
| Delivery and price KPIs | Calculates them | Shows them in the scorecard | |
| Ratings from quality, plants, projects | Usually limited or manual | Structured surveys per segment | |
| Supplier-facing scorecard | Usually not | Supplier portal | |
| Corrective actions with owners and deadlines | Partly, often in quality modules | CAPA workflow with evidence | |
| Risk, ESG and document follow-up | Varies by module and licence | Included | |
| QBR preparation | Manual | Built from the scorecard |
Pick your system
- SAP S/4HANA, ECC and Ariba
- Coupa
- Microsoft Dynamics 365 (Supply Chain Management and Business Central)
- Oracle Fusion, E-Business Suite and NetSuite
Running something else, such as Infor, IFS, Epicor, Odoo or a homegrown system? The same pattern applies through the REST API or CSV.
How it connects
- REST API: push supplier master data and transaction KPIs in, pull scores and action status out.
- Scheduled CSV import and export: the quickest start, no integration project needed.
- Integration platforms: Zapier, Make or Microsoft Power Automate, calling the same API.
- Reporting: Power BI on top of the scores, next to your ERP reports.
Which method fits depends on your landscape. We agree the data fields and the direction of each flow with your IT team during onboarding.
A typical rollout
- Week 1: suppliers in. Export the active supplier list from your ERP (or connect the API) and segment it: strategic, critical, tail.
- Week 2: methods. Pick an evaluation method per segment and invite the internal raters who actually work with each supplier.
- Week 3–4: first cycle. Run the first evaluation, publish scorecards to suppliers and open corrective actions where scores fall short.
- After that: connect. Add transaction KPIs from your ERP and send scores back so buyers see them where they already work.
Questions buyers ask
Do we need to replace our ERP or its supplier module?
No. The ERP stays the system of record. EvaluationsHub reads from it and can write scores back.
Do you have a prebuilt connector for my ERP?
We connect via the REST API, CSV exchange or an integration platform. Ask us which method suits your landscape; we will not promise a connector that does not exist.
Can we start without an integration?
Yes. Most customers start with a CSV export of active suppliers and add API flows later.
Where is the data hosted?
In the EU. See the Trust Center for security details.
See the layer on your own suppliers
Bring a list of 20 suppliers from your ERP and we will set up a first evaluation cycle with you.
