Getting your point of sale to talk to everything else
3 min read
Your point of sale knows more about your business than any other system you run. It knows what sold, when, for how much, what is left on the shelf, and often who bought it. The trouble is that it usually keeps all of that to itself.
So someone exports a report, opens a spreadsheet, and types numbers into the accounting system, or updates stock on the website by hand, or copies customer emails into the newsletter tool. I spent years supporting point-of-sale software, and this is the most common pain I saw.
What a connection can do
A few examples of the work that comes up most:
- Sales into accounting. Each day's totals, taxes, and payment types are posted to QuickBooks or similar, so the books match the register without a Friday afternoon of copying.
- Stock onto your website. When the last one sells in the store, the website stops selling it too.
- Customers into marketing. People who agreed to hear from you go into your email tool automatically, with what they bought, so you can send something relevant.
- Counts and price changes from the floor. Staff update the POS from a phone or handheld instead of walking back to the office.
- Reports the POS does not have. A dashboard with the three numbers you actually check every morning.
How the data gets out
Every system is different, but there are really only four ways in. In order of how easy they are:
- A built-in integration. Check the settings and the "apps" or "integrations" page first. If the connection you want already exists, turn it on and you are done.
- A documented connection for developers (an API). Many modern systems have one. Building on it is reliable and usually the cheapest custom option.
- Scheduled exports. Some systems can save a report to a folder or email it every night. A small program can pick that up and send it where it needs to go.
- The database itself. Older and locally installed systems often keep everything in a database on the back-office computer. Reading from it, and carefully writing to it, is possible, but it needs someone who knows what must not break.
That last one is where a lot of developers stop. It is also where most of my own background is.
What to watch out for
- Do not let a connection change things it should not. Reading sales is low risk. Writing prices or stock back into the POS needs testing, a log of every change, and a way to undo it.
- Plan for the internet going down. The register should keep selling, and the connection should catch up on its own when the line comes back.
- Check your POS agreement. Some vendors limit what you can connect, or charge for access.
- Make sure you can switch it off. A connection should be one setting away from disabled if something looks wrong.
Where to start
Write down every place someone types the same number twice in a normal week. Put the one that takes the most time, or causes the most mistakes, at the top. That is your first project, and it is usually smaller than you expect.
If you want a second opinion on what your system allows, tell me what you run. I will tell you which of the four ways in it has, and what a connection would take.
Want the next one? Subscribe by RSS.