If two systems need to talk, we connect them
Integration is a core skill of ours, not a side job. Any kind of integration that needs to be done — software to software, software to hardware, your system to a bank, a government platform or a marketplace — we do it. Data is entered once and arrives wherever it is needed, without anyone retyping it.
Systems that do not talk to each other
Most businesses run several good systems that know nothing about one another, with people and spreadsheets filling the gaps. These are the links we are asked for most often. The list is not a limit.
ERP, POS, warehouse & accounting
- POS sales posted to the ERP and the ledger
- Stock levels shared between warehouse, branches and tills
- Purchase orders, receipts and supplier invoices matched
- ERP systems such as SAP, Oracle, Microsoft Dynamics or Odoo
Hotel PMS interfaces
- Restaurant and outlet POS charges posted to the room
- Door lock systems and key card encoding
- IPTV welcome screens, billing and check-out
- PBX and call accounting
- Channel managers and booking engines
ZATCA Fatoora e-invoicing
- Fatoora integration for the ERP or POS you already use
- Invoices generated, signed and submitted from your system
- Responses and rejections fed back to your users
- Our ZATCA e-invoicing service
Payments, banks & payroll files
- Online payment gateways for websites, apps and portals
- Card terminals linked to the till, so amounts are not keyed twice
- Bank payment files in the format your bank requires
- Bank statements imported for reconciliation
- Payroll and WPS salary files produced from your HR data
HR & attendance devices
- Biometric and fingerprint terminals read automatically
- Attendance, lateness and overtime passed into payroll
- Several sites and device brands in one attendance record
E-commerce & marketplaces
- Online stores such as Shopify, WooCommerce, Salla or Zid
- Marketplaces such as Amazon or Noon
- Stock and prices pushed out from your inventory system
- Orders, returns and refunds pulled into stock and accounts
CRM & messaging
- CRM linked to sales, invoicing and support
- Email sent from your systems and logged against the customer
- SMS for one-time passwords, reminders and notices
- WhatsApp messages for confirmations, invoices and alerts
Microsoft 365, Google Workspace & identity
- Single sign-on, so staff use one account everywhere
- Directory sync: joiners, movers and leavers applied in every system
- Calendars, mailboxes and shared files linked to business software
Hardware, IoT & building systems
- Barcode scanners and RFID readers
- Weighing scales and weighbridges
- Receipt, label and kitchen printers, cash drawers and displays
- Sensors and other IoT devices reporting into your software
- CCTV and access control linked to attendance and security records
The right method for each system
There is no single way to integrate. We use whatever each system genuinely supports, and we build the missing piece when it supports nothing.
- APIs. REST and SOAP web services, in either direction.
- Webhooks. One system notifies the other the moment something happens.
- File and EDI exchange. CSV, XML, JSON or EDI files, sent and collected on a schedule and validated on the way in.
- Database level. Controlled reading or writing where no interface exists.
- Middleware. A layer in the middle that translates, queues and routes messages between several systems.
- An API for a system that has none. We build one in front of an older or closed application so that other software can reach it.
- Custom development. When no connector exists, we write it. See custom software development.
Failures you can see, data you can rely on
Monitoring and alerts
Each connection is watched. If it stops, a person is told, rather than the business finding out at month end.
Error handling and retries
A message that fails is retried automatically, then held in a queue for review. It is never dropped silently and never posted twice.
Audit logs
What was sent, when, by which system and with what result, so any transaction can be traced from end to end.
Data migration and cleansing
Moving from an old system to a new one: records are extracted, duplicates and errors cleaned, codes mapped, and totals reconciled before the switch.
Ongoing synchronisation
Customers, items, prices and balances kept identical in every system, with a clear rule for which system is the master.
We build business software, so we know both sides
We have been writing business systems since 2018. People AXIS for HR, IVMS for the warehouse, Right Numbers for finance, our POS and our guest CRM are our own products, and each one is built to exchange data with other software.
Just as often, neither system is ours. We integrate third-party software we did not build, including older applications whose original developer is no longer available.
One picture across every system
Once systems share data, you can report across all of them: sales from the POS, stock from the warehouse, cost from the accounts and hours from HR, on one screen.
- Dashboards and scheduled reports that span several systems
- Our advanced reporting service
How an integration project runs
The same steps apply whether we are linking two systems or ten.
Map the flow
We write down, in plain words, which data must move, from where to where, how often, and which system is the master for each item.
Examine each system
We check what every system really offers: an API, an interface module, file export or only a database. You hear at this stage what is possible and what is not.
Design & quotation
You receive the method, the field mapping, the rules for errors and the price in writing. Nothing is built until you have agreed it.
Build in a test environment
The integration is built and run against test systems or a copy of your data, never first against live operation.
Test & reconcile
Your team tests real cases, including the awkward ones: refunds, cancellations, partial deliveries. Totals in both systems are reconciled until they agree.
Go live, monitor & support
We switch on at an agreed time, watch the first cycles closely, hand over the documentation and keep monitoring if you want us to.
Three things that keep a project moving
Integration projects are rarely delayed by the code. They are delayed by waiting for access and information.
Access
- A user account or API credentials for each system
- Remote access to the servers or cloud tenancy involved
- Only the permissions the integration needs
Vendor documentation
- API or interface specifications from each vendor
- A contact at the vendor who can answer technical questions
- Any interface licence the vendor requires, confirmed early
A test environment
- A test or sandbox copy of each system, if the vendor provides one
- Otherwise a recent copy of the data to work against
- Realistic test cases from the people who do the work daily
What clients ask before starting
Yes. Most of our integration work involves at least one system from another vendor. We work from the vendor documentation, the published API or interface specification, or the database itself, and we deal with the vendor on your behalf where that helps. We do not need to have written a system to connect it.
Then we find another route. Depending on the system, that can be a scheduled file export and import, a direct and carefully controlled database connection, or a small API that we build in front of the system so that other software can talk to it. We tell you which route is realistic after looking at the system, before you commit to anything.
It is built and tested away from live operation first, in a test environment or on a copy of your data. It goes live at a time you agree, with a way to switch it off if something unexpected happens. Where an integration only needs to read, it is given read-only access.
Every integration we build records what it sent, what it received and whether it succeeded. A failed message is retried automatically, and if it still fails it is held in a queue and someone is alerted. Nothing is lost silently, and a transaction can be traced from one system to the other through the audit log.
Most integration work is done remotely over a secure connection. When hardware has to be installed or cabled, such as terminals, scales or door controllers, on-site work in Saudi Arabia is carried out with our local partners. Our hotlines are open 24/7 for the systems we support.
Name the two systems that should be talking
Tell us which systems you run and what your people are retyping between them. We will tell you how they can be connected and what we would need to do it.
Hotlines open 24/7 · GCC +966 53 664 1983 · Europe +34 631 322 291