Everything connects to your systems. Nothing leaves them.
ERPs are read in read-only mode. The engine runs on your premises. Results go back to each team.
Sources
- Entity ERPsRead-only: export, SQL view or web service
- Supplier price listsExcel, CSV or PDF received by email. A software-generated PDF is extracted then reviewed; a scanned PDF is rejected
- Discounts and special pricesBy country, by entity, with their validity
- Raw material indicesPrice indexation formulas
Buyvera engine
on your premises- 01ReadingExcel, CSV and PDF price lists
- 02Pre-checkblocks anything doubtful
- 03Matchingto ERP items
- 04Calculationweighted increase, delivered price
- 05Price checkagreed price at order date
Outputs
- PurchasingNegotiation files
- FinanceCheck of ordered prices
- Purchasing managementSecured savings, application delays
- Supply plannersBest price obtained in the group
- CSV exportsColumns allowed by profile
Six steps, each one checked, each one replayable.
Doubtful data is set aside with its reason; a blocking defect stops the file before any calculation. Every run is logged.
- Ingestion · doneExcel, CSV, ERP412 lines
- Check · doneblocking issues and alerts2 alerts
- Matching · doneERP items400 matched
- Calculation · doneweighted increase, delivered price412 net prices
- Price check · doneagreed price at order date€252 gap
- Delivery · donefiles and exports1 file
| Run | Trigger | Lines | Duration | Status |
|---|---|---|---|---|
| #2481 | Supplier C price list received | 412 | 38 s | completed |
| #2480 | ERP synchronisation · Lyon | 9,412 | 12 s | completed |
| #2479 | Supplier A price list · missing unit | 3 lines | 4 s | set aside |
| #2478 | ERP synchronisation · Porto | 6,120 | 9 s | completed |
Your data: one file, on your premises, yours to take back.
The engine keeps everything in a DuckDB base: a single file on your server, with no database service to run, no open port, no licence. It is the only truth: every screen is recomputed from it, nothing is copied elsewhere.
One writer, rights enforced server-side
The engine alone writes; the interface only reads views, through the engine, with the rights of each profile. Decisions are also written to a replayable log outside the base.
Backup and restore = a copy
Every night, a backup verified by the engine and copied to a second disk; an off-server copy to the storage of your choice is provided for by the kit. Restoring is a script, tested at every update.
Measured sizing
Up to 50 concurrent users per installation, under 1 s for reads and 2 s for writes (95th percentile), measured on a base of 5 million price rows. Writes go one at a time: that is the limit, and we say so.
Beyond that, or if your IT department requires it
The tables can be hosted in your PostgreSQL. And a read-only copy of the base is handed to you on request, to open with the tool of your choice.
Pinned version
The file format follows the engine version, shipped and pinned with every update, with its log and automatic rollback.
What we do not promise: a "high availability" database or several writing servers. Buyvera is an analysis engine installed on your premises, not a database service.