demo · your ERP
Your ERP stays the system of record. What it doesn't record - a field purchasing asked for, a supplier's certificate, the spreadsheet a customer sends - Verarbo keeps beside its rows, where your people already look.
Adding that to the ERP itself means a change request, a customization and a retest at every upgrade. Here, none of it is in the ERP, so the next upgrade changes nothing.
video · narrated, with captions
Prefer to read? The same five moments, below.
01 / 05
Products, vendors and inventory come straight from your ERP's database, the moment a page opens. Nothing is copied, so there's no second copy to keep in step, and nothing in the ERP is changed.
Lists, searches and reports work on those rows as they are: inventory by location is grouped and summed in your database.
02 / 05
Purchasing wants each product's country of origin and its spec sheet. The ERP has no column for either.
Your administrator adds both in a few minutes. They appear on the product's page, below the ERP's own fields, and people fill them there. The product list shows the country beside the ERP's columns, and the ERP's table is exactly as it was.
03 / 05
Some things the ERP doesn't hold at all. Quality keeps each vendor's certificates: who issued them, when they expire, which products they cover.
A certificate refers to the vendor and the products in your ERP, picked from the ERP itself, so a vendor's name is always the one your ERP has.
04 / 05
A customer sends their own sheet: where is each product made? Usually that's an ERP export, a copy into their file, and the countries typed in by hand.
Verarbo fills their file in their columns: product numbers and prices from the ERP, the country of origin from Verarbo. Every value is checked against the file's own lists before anything is written, and a product with no country yet says so. The supplier certificates register quality asked for comes out the same way.
05 / 05
Look at the ERP's database afterwards: the same tables, the same columns. Everything added is in Verarbo, with who changed what and when, on which product and which vendor - and a mistake can be undone.
At the next upgrade of the ERP, all of it still works, because none of it is in the ERP.
and
Your ERP stays as it is: its screens, its reports, its upgrades. Verarbo only reads its database and never writes to it; your DBA can give it a login that can only read.
Verarbo doesn't replace your ERP or move its data. It keeps what the ERP doesn't, next to what the ERP has.
Manufacturers whose ERP runs on SQL Server or PostgreSQL, and the ERP partners who serve them: when the ERP can't hold what customers, auditors or your own teams ask for, and a customization is the only other answer. Ask us to show it on your own ERP.