In the morning, the question was on the table. By evening, the tool dispensing cabinet (GARANT Tool24, Hoffmann Group) was posting its own withdrawals to the ERP. Until then, a human kept the stock levels in abas up to date: every withdrawal, every return posted by hand — or not at all.
A fully automated interface that has been quietly doing its job ever since.
Every withdrawal and every return at the cabinet lands in abas as a stock posting within minutes — withdrawals as issues, returns as receipts, cancellations as automatic reversals. Accurate to the storage location, with an external document reference to every source movement, fully auditable.
If the abas stock level deviates from the cabinet stock, the interface corrects it with a stock adjustment — exclusively on the cabinet's storage location, without touching any other warehouses or master data. Discrepancies never get a chance to accumulate.
Every posting with its document and originator, failed postings visible at a glance — including articles that don't exist in the ERP yet. The entire configuration happens in the browser: polling interval, credentials, storage locations.
This is what the interface's daily routine looks like — shown here with sample data.
The posting journal: every movement with direction, quantity, originator and abas document. Failed postings can be retried at the push of a button — for example after a missing article has been created.
The article reconciliation reports cabinet articles still missing in the ERP and logs the nightly stock reconciliation including corrections.
No magic — just craftsmanship.
Every assumption is verified against the real API — in this project, the manufacturer's documentation deviated from reality in five places. We measured it instead of guessing.
Stock postings, stock adjustments, document chains, storage location control — via the REST interface, clean and auditable with an external document reference to every source movement.
Every posting is idempotent — nothing is booked twice, not even after an outage or restart. Errors are isolated, retried automatically and visible at a glance.
Runs on your existing infrastructure. No cloud requirement, no license fees per posting — your data stays in-house.
The tool cabinet is just one example. The same craftsmanship connects abas ERP with whatever produces or needs data in your company — anything with an API, a file or a database.
If you have been manually bridging a gap between some system and your abas ERP for years: tell us about it. Often it's a day's work.
Get in touch