Integrations
Every time someone retypes data from one program into another, time and accuracy leak away. We connect your systems so information is entered once and reaches everywhere it needs to: from the tills to accounts, from the warehouse to the online store, from the entry gate to the timesheet.
- Survives outages
- Every transfer logged
- Alerts with a reason
Our approach
The problem integration solves
In most companies, software piles up over the years. The tills come from one vendor, accounting from another, the warehouse runs its own program, the online store is on WooCommerce or OpenCart, and attendance is logged on a card reader whose data someone copies off with a USB stick. Each of these works fine on its own. The trouble is in the gaps between them.
In those gaps sits a person, retyping. Store stock is updated once a week and customers order things that are not there. Till sales reach accounts two days late. The payroll report is stitched together from three spreadsheets. Integration takes that middle step away: data moves automatically, either instantly or on a schedule, with a check that it actually arrived.
Before writing any code we answer a question nobody has usually asked: which system is the source of truth for each kind of data. Are prices set in the ERP and pushed to the store and tills, or the other way round? Is a customer created in the CRM or in accounts? Until that is settled, an integration just moves the mess around faster.
Benefits
What you get
Enter once, use everywhere
Data is entered in one place and reaches the other systems automatically.
Survives outages
A queue and duplicate-safe retries for when the other side does not answer.
Every transfer logged
You know what was sent, when, and what came back.
Alerts with a reason
When something fails, the right person gets the actual cause, not a generic error.
Works without an API
Scheduled exports, read-only database access, SFTP — whatever the system allows.
Badges, Face ID, GPS
We link access, attendance and tracking devices to your reports.
What we connect
This list comes from real jobs in retail, manufacturing, logistics and services:
- Tills and POS systems with a central database: sales, stock and prices in real time across every site.
- Warehouse and ERP with the online store: stock, prices and order status, with no manual updating.
- Online payments and financing: Stripe, bank modules and credit products, such as the TBI Bank integration we built for ITsector.bg.
- Accounting software: sales, purchases and payments flow across automatically and the totals are reconciled.
- Access control and working hours: NFC badges, readers and Face ID, tied into attendance and payroll.
- GPS units in vehicles, linked to fleet or delivery systems.
- Any outside service with an API: couriers, public registers, partner and supplier systems.
How we build the link
A good integration is boring. It runs and nobody thinks about it. Getting there means planning for the moments when things go wrong, because they do. The internet drops at one of the shops, an outside service stops responding, somebody enters an item code the other system has never seen.
So every link we write has a queue where messages wait if the other side is unreachable, and retries that never create duplicate records. Every transfer is logged: what was sent, when, and what came back. If something still fails after several attempts, the person responsible gets an alert with the specific reason, not a generic error.
We prefer REST APIs and webhooks where the systems support them. Where they do not, we use whatever is there: scheduled file exports, read-only database access, exchange by email or SFTP. From your side it all looks the same — data that turns up on time.
Access is planned too. Keys and passwords for outside systems are kept in protected server settings, never in the code. Each link gets its own account with the minimum rights it needs, so an integration that reads stock cannot delete an order. If a key expires or leaks, it is replaced in one place without stopping anything else.
Hardware: badges, readers, GPS
Some integrations are not between programs but between a program and a device. The NFC reader at the door, the face-recognition camera, the GPS tracker in the van: each has its own protocol and its own quirks. We work with the devices you already have, if they allow access to their data, and advise on choosing new ones if you are buying.
One example is attendance tracking. Staff badge in or are recognised by face, the data goes to the central system, and at the end of the month accounts receive a finished report with hours, absences and overtime. No downloading files and no cross-checking by hand.
What you get
The field map is worth more than it sounds. Years from now, when someone asks why a particular figure is in a report, the answer will be written down.
- A working link between your systems, with a queue and safe retries.
- A log of every transfer and alerts when something fails.
- Documentation of the API and a field map showing which field from which system goes where.
- The integration's source code, which belongs to you.
- Monitoring and support, 24/7 for critical links.
When one of the vendors changes something
Systems on the other side get updated without asking you: a new API version, a new format, a new address. Support includes watching for those changes and adapting the link before it breaks. If you decide to replace your till software or accounting package, only that side of the integration is rewritten; the rest stays as it is.
The process
How the work goes
Five steps, each with a result you see and approve before we move on.
Map the systems
We list your programs, the data each holds and where people retype by hand.
Map the fields
We agree where each field comes from, when it moves and which system is the source of truth.
Build and test
We write the link and run it on test data, including simulated outages.
Run in parallel
For a few days the old and new ways run side by side until the totals match.
Monitor
Logs, alerts and adjustments whenever the other side changes.
Technologies
What we work with
- REST API
- Webhooks
- PHP
- MySQL
- Stripe
- TBI Bank
- WooCommerce
- OpenCart
- NFC
- GPS
- Linux
Questions
Frequently asked questions
Our program has no API. Is this even possible?
Usually, yes. We work with scheduled file exports, read-only database access or SFTP exchange. If none of those is possible, we will tell you straight away, before you have paid for anything.
How much does an integration cost?
It depends on how many systems we connect, how many fields move and how well documented the other side is. Once we have seen your systems we give you a written estimate. Linking two systems with good APIs costs far less than a link that needs workarounds.
What if the internet goes down at one of our sites?
Data waits in the queue and is sent once the connection is back, without duplicates. If the outage drags on, the person responsible gets an alert.
Do we need permission from the other system's vendor?
Sometimes, for API access or a key. We help with the technical requirements and the conversation, but the request usually has to come from you as their customer.
Do you look after the link once it is live?
Yes. We watch the log, respond to errors and adapt the link when the other side changes version or format. Support for critical links is 24/7.
What do you retype by hand every week?
Tell us which systems you use and where the data does not flow on its own. We will tell you how to connect them.
- Phone
- +359 895 629 012
- office@enter.bg
- Address
- Pernik, 2 Krasnodar St, Bulgaria