Most growing businesses run on several systems that were never designed to work together: a website, a CRM, accounting software such as Sage or Xero, an e-commerce platform, payment gateways, couriers and ad platforms. When they are not connected, people fill the gaps by hand, and data goes missing or out of date in between. Integration connects them so information flows automatically, accurately and once.
What problems do system integrations solve?
- Website enquiries and WhatsApp leads land in the CRM automatically, with their source, instead of in an inbox.
- Orders flow from the online store into stock and accounting without re-typing.
- Invoices and payments reconcile against orders and bank records.
- Ad platforms learn which clicks became paying customers, so budgets go to what works.
- Leadership sees one consistent view of sales, stock and cash instead of conflicting spreadsheets.
No-code tools or custom middleware?
| No-code tools (Zapier, Make) | Custom integration middleware | |
|---|---|---|
| Best for | Simple triggers between two apps | Many systems, complex logic or high volumes |
| Setup | Days, often by the business itself | Weeks, by developers |
| Cost | Monthly subscription that grows with usage | Build cost plus hosting and maintenance |
| Failure handling | Basic retries and email alerts | Designed retries, queues, monitoring and audit logs |
| Risk when it breaks | Low-value data may be missed | Built so orders, invoices and payments are never lost or doubled |
A sensible rule: use no-code tools for convenience connections, such as adding a newsletter sign-up to a mailing list. Use custom middleware where a missed or duplicated record costs money or trust, such as orders, invoices, payments and stock.
How do integrations exchange data?
There are two main patterns. With webhooks, a system sends a message the moment something happens, such as a new order, which is fast and efficient. With polling, the integration asks a system for changes on a schedule, which is useful when a system offers no webhooks, common with older accounting and ERP software. Many integrations use both: webhooks for speed and a scheduled check that catches anything a webhook missed.
What makes an integration reliable?
Every external system will occasionally be slow, down or send the same message twice. Reliable integrations are designed for that from the start:
- Idempotency: processing the same message twice has the same effect as processing it once, so a repeated webhook never creates a second invoice or charge.
- Retries with backoff: failed requests are retried automatically, waiting longer between attempts so a struggling system is not overwhelmed.
- A dead-letter queue: messages that keep failing are set aside for review instead of disappearing.
- Validation: data is checked and cleaned before it reaches systems that cannot handle bad input, such as older ERPs.
- Monitoring and alerts: someone is told immediately when a connection fails, rather than finding out from an unhappy customer.
- Audit logs: a record of what was sent, when and with what result, so problems can be traced.
Which system should be the source of truth?
For each type of data, decide which system owns it. Customer contact details might live in the CRM, stock levels in the ERP or e-commerce platform, and invoices in accounting. Other systems read from the owner rather than keeping their own competing copy. Without this decision, two systems overwrite each other and nobody knows which number is right.
What about POPIA and security?
Integrations move personal information between systems, so POPIA applies. Send each system only the information it needs, protect API keys and credentials, encrypt data in transit, restrict who can access integration logs that contain personal details, and keep a record of which systems hold what. When a third party processes data on your behalf, put a written agreement in place.
How should you plan an integration project?
- List your systems and draw how data should flow between them.
- Name the source of truth for each type of data.
- Rank the connections by how much manual work or risk they remove.
- Start with the highest-value connection, such as website leads into the CRM or orders into accounting.
- Build in monitoring from day one, and agree who responds to alerts.
- Add the next connection once the first runs reliably.
What do custom integrations cost?
Cost depends on how many systems are involved, how well documented their APIs are and how complex the business rules are. At Lulonke, bespoke software and integration work is scoped through a product blueprint; larger builds typically run R150,000 to R500,000 or more per release cycle. Many businesses start smaller, with one high-value connection. See integrations for how we approach it, and our guide to ICT solutions for how integrations fit into the wider technology picture.
Frequently asked questions
What is integration middleware?
Integration middleware is software that sits between business systems and moves data between them reliably: receiving messages, transforming data into the format each system expects, retrying failures and alerting when something breaks.
Is Zapier good enough for my business?
For simple, low-volume connections between two apps, often yes. For orders, invoices, payments and other data where a missed or duplicated record costs money, custom middleware with proper retries and monitoring is safer.
Can you connect our accounting software to our online store?
Usually, yes. Most accounting systems used in South Africa, such as Sage and Xero, and e-commerce platforms such as Shopify and WooCommerce offer APIs. Older on-premise systems may need a scheduled sync rather than real-time updates.
What is a webhook?
A webhook is a message one system sends to another the moment something happens, such as a new order or payment. It lets integrations react in real time instead of checking for changes on a schedule.
How long does an integration project take?
A single well-documented connection can take a few weeks; connecting several systems with complex rules takes longer. Starting with the highest-value connection gets results sooner.
