Interfaces and system integration
Most businesses do not have too little software, but systems that do not talk to each other. We build the connection in between.
What a good interface looks like
Our integrations have given us rules that we apply to every connection:
- Reading and writing are separate. Only what is explicitly released gets written, and only with the key of the person acting.
- Every import is repeatable. The same sale is never booked twice, even if the interface asks twice.
- Errors are visible. What could not be booked appears in a list, not in a log that nobody reads.
- Checksums before writing. If the sum of the lines does not match the total, nothing happens.
- A trial run with rollback before anything goes live.
Three examples from operations
- In testing
Vending machines to the ERP system
Sales, refills and withdrawals are booked in daily sessions, with rounding rules, deposit and tax.
Read the case study - In use
ERP system to the tax adviser
An export format with 41 fields, checked document by document against the source system.
Read the case study - In use
Telephone system to the voice assistant
A call is answered by the AI assistant, and the caller data comes from the ERP system.
Read the case study
Two systems that should work together?
Tell us both sides and what should happen in between. We will check how to build the connection in the simplest and safest way.
Discuss a project