Home › Systems & integration
Topic 4
Enterprise systems and integration
What the standard pieces of business software actually do, why they stop talking to each other, and what it costs when nobody planned for the joins.
The pieces, in plain language
Every one of these already exists at Lerato's. They are just being done by a person, a book, or nobody at all.
| System | What it is for | Who does it at Lerato's today |
|---|---|---|
| Point of sale (POS) | Records the sale as it happens: what, how much, to whom, paid how | The duplicate invoice book, plus the Yoco machine for card payments |
| Inventory management | Knows what is on the shelf, what it cost, and when to order more | A spreadsheet last reconciled in June, and Thabo's memory |
| Accounting | Turns trading into books: VAT, profit, what is owed and owing | A bookkeeper, monthly, working from a box of paper |
| Customer management (CRM) | Who the customers are, what they buy, what they owe, what they consented to | The exercise book and the owner's memory |
| Purchasing | What to order, from whom, at what price, and whether it arrived | A phone call, and delivery notes in a box |
| Reporting | What happened, so the owner can decide what to do next | A feeling, confirmed or contradicted by the bank balance |
| ERP | All of the above in one product, sharing one database | — (and almost certainly the wrong answer for a shop this size, for now) |
An Enterprise Resource Planning (ERP) system is a set of software that manages core business functions—inventory, accounting, pointofsale and customer records—inside one database. Many people misuse the word ERP to mean any business software. Real ERP needs a shared database for all operations.
Leratos already does every task: recording cash sales taking customer details tracking stock on shelves and calculating profits. The real question for Leratos is not whether to do these tasks but whether to use paper registers and separate spreadsheets or to use one integrated software application.
Deploying a traditional enterprise ERP is not suitable for a shop for reasons:
High Implementation & Maintenance Costs: Software licenses and consulting fees are above Leratos budget.
Protracted Rollout Timelines: Implementation can take months. Distract Leratos staff from trade.
OverRigid Processes: Complex ERP systems force workflows made for corporations creating work for Leratos small team of four.
An expensive ERP suite can be difficult for businesses. Small businesses can gain from systems. A module is a software component that handles one task—like pointofsale transactions or inventory tracking—. That connects to operational modules. Choosing a solution thats very good at pointofsale and basic stock tracking gives overall reliability and lower costs than buying a complex multifeature ERP suite where many features are hard to set up.
Islands of data
This is the single most common failure in small-business IT, and it is not caused by bad software. It is caused by buying good software one piece at a time, over years, with nobody asking how the pieces will talk.
Scroll sideways to see the whole diagram.
An island of data also called a data silo occurs when different software programs or handwritten records hold business information on their own without any synchronisation.
Think about how a small change in the price of a bag of cement can spread through records:
- The shop owner agrees to a price increase from the supplier. Writes R110 on a desk notepad.
- Meanwhile the front counter clerk keeps charging R100 at the cash register because the pointofsale price list has not been updated.
- The inventory clerk records the stock in a spreadsheet using R105.
- The accounting assistant enters R108 into the tax ledger based on a supplier invoice.
Because these systems are not connected one fact turns into four values across the business.
To fix this the business should use a Single Source of Truth (SSOT).
In an SSOT model every piece of business data—such as an item price— is defined in one place. Every other part of the business pulls information directly from that one place.
The main problem with data stores is not just duplicate information but a loss of trust in the system.
When people see numbers in places they stop trusting the software and start asking the owner for help.
For example if six different inventory sheets show six numbers, for cement the real amount is unknown which makes the tracking tools useless.
Four ways to join two systems
In rising order of cost and falling order of pain.
| Approach | How it works | Costs | Fails when |
|---|---|---|---|
| 1. Re-entry a person retypes |
Somebody reads one screen and types into another | R0 upfront hours every month, forever |
Immediately and invisibly. Typing errors, things done late, things skipped when it is busy. |
| 2. File export and import CSV between systems |
Export from one, import into the other, usually monthly | Low someone must remember |
The data is only as current as the last export, and nobody notices when the export stops working. |
| 3. Built-in integration the vendors already did it |
Two products that were built to connect, switched on in settings | Subscription little setup |
You are limited to what the vendors chose to connect, and tied to both of them. |
| 4. Custom integration an API and a developer |
Software written to move data between systems automatically | Highest plus ongoing maintenance |
The developer leaves, or one vendor changes their API and it quietly stops. This is the one that strands small businesses. |
Prefer option 3 and design around it. For a four-person business, choosing two products that already integrate is almost always better than choosing two "better" products and paying somebody to join them. The joined version is only better until the person who built it is unavailable.
An Application Programming Interface (API) is a way for different software applications to talk to each other.
Think of it like a counter at a hardware store: you do not go into the back to get what you need; you give a form to the person at the counter. They give you what you asked for in a way.
Knowing when data is moved is very important:
Batch Transfer: Data is updated at set times, such as every night or every week.
RealTime Transfer: Data is updated as it happens.
Batch updates are not good for inventory. If stock is only updated once a month batch updates cannot help with decisions because stock levels change all the time during the day.
There are data problems when systems are connected:
Semantic Inconsistencies: One system calls a "customer" a person who pays cash while the accounting system calls a "customer" a company that has a credit account.
Data Formatting Differences: Problems such as dates written as DD/MM/YYYY or YYYY-MM-DD or different ways to write phone numbers can cause errors if not fixed.
Conflict Resolution: If a customer’s phone number is changed at the register and at the time in the accounting system clear rules must say which one is correct.
Offline Resilience: Systems must be able to store sales when the internets down. Send the data back when the connection is restored.
Vendor Lockin Testing:
Vendor lockin happens when a software company keeps your data in a format that’s hard to move to another program.
To stop this business owners should check if the system can provide all records in a format like CSV or JSON without paying fees.
Choosing between products
Rather than naming a winner, here is the scorecard to take into a demonstration. Make the salesperson show you, not tell you.
| Ask | Why it matters | A bad answer sounds like |
|---|---|---|
| Can I export all my data, any time, without asking you? | It is the difference between a supplier and a captor | "Our support team can arrange that for you" |
| What happens when the internet is down? | This is South Africa. It will be. | "Our uptime is 99.9%" — that is not an answer to the question |
| What does it cost in year three, with four users? | Per-user pricing grows quietly | A price for one user, for the first year, excluding VAT |
| Does it connect to the accounting package my bookkeeper uses? | Avoids becoming integration number four | "It can be integrated" — by whom, at what cost? |
| Show me a tax invoice it produces, with VAT | SARS particulars are not optional | A generic template from another country |
| Can I see who changed a price, and when? | The audit question, which never comes up at a good moment | "Only administrators can change prices" — again, not the question |
| Where is my data stored, and who else can see it? | POPIA s.72 governs sending personal information out of the country | Vagueness. Verify the current s.72 position and cite it. |
| What happens to my data if I stop paying? | Shops do go quiet for a month | "Your account would be suspended" — and the data? |
Choosing business software requires a look at what software can do how software costs and the total cost to use software.
In South Africa local companies have options:
Sage Business Cloud Accounting (Checked: October 2026): A cloudbased accounting tool that starts at about R380 per month for businesses to handle VAT and local bank connections.
Yoco Point of Sale(Checked: October 2026): No fixed fees on plans a percentage for card payments which's useful for handling card payments at the front.
IQ Retail / IQ POS (Checked: October 2026): A local choice for hardware stores with stock control and direct account management.
Looking at the cost of software means checking the cost, not the price. The total cost covers buying hardware such as printers and scanners training staff, transactions when starting out and costs when moving to another system.
Experts should provide options that fit the business than forcing one choice. The decision should match what the owner can afford and what the owner needs.
What integration actually feels like
The hardest part of connecting two systems is almost never technical. It is discovering that the two halves of the business never agreed on what a word means. The counter thinks a "customer" is the person standing there; the bookkeeper thinks it is the account being billed. Both have been right for years. A system forces the question, and answering it is organisational work, not software work.
Implementing software requires time planning. For a hardware shop it usually takes weeks, not days. Most of the time is spent fixing naming problems cleaning up records and matching codes not setting up the software.
A key rule for moving data is: Garbage in garbage out. If old records are not checked they bring problems into the system making it expensive and full of data.
To avoid this companies should run the systems together for a time. This makes the work harder for the staff. Gives a backup if something goes wrong.
Measuring Success:
3 Month Success Indicators: Daily stock counts match the shelves. Checkouts are as fast or faster. Monthly money counts finish without work.
3 Month Failure Indicators: Staff skip the software. Use paper. Stock is still wrong. Managers use notes for choices.