A guide to hiring a POS developer
A point of sale system is where a customer pays. In a shop it is the register, the card reader, the receipt printer and the software that ties them together. A POS developer builds and looks after that software. The job is more than a screen and a total. The system has to be quick, correct about money and stock and calm when something goes wrong, because a person is standing at the counter. If you run shops, a cafe, a salon or a pop-up stall and a ready-made system no longer fits, ask for POS experience by name.
What the job covers day to day
A POS developer works on the sale screen, on the back office where products and reports live and on the code that talks to devices and payment tools. Time also goes on bug reports from staff, testing on real tablets and printers, updates that must not disturb a busy shift and the questions managers ask when the numbers do not match. Much of the skill is in the odd cases: a refund with no receipt, a price change in the middle of a sale or a card that fails twice.
Ready-made, custom or a mix
Many businesses start with a ready-made system such as Square, Shopify POS, Lightspeed or Clover. These are separate companies and separate products, and each has its own tools for apps and connections. A developer who knows the one you use can add a feature, fix a link or build a small app for it. Others decide to build their own software because their way of selling is unusual or because fees add up across many tills. A good developer will tell you honestly which route fits, even when the answer is not custom work.
Payments and card data
Taking a card payment is the part to treat with most care. The usual approach is to let a payment provider’s reader or hosted tool handle the card, so your own code and database never see the card number. The developer then deals with the results: approved, declined, cancelled and timed out. They make sure a payment that fails halfway is not charged twice and not lost. The card industry has its own security standard, called PCI DSS, and your payment provider can tell you what it expects from you.
Offline mode and sync
Shop internet drops, and the queue does not wait. A strong POS keeps selling when the connection is gone, stores the sales on the device and sends them when the network returns. That sounds simple and is not. The developer has to decide how the device identifies each sale, how stock is handled while it is offline and what happens if two tills sold the last item. Ask candidates how they would build this, since it separates experience from theory.
Stock, products and tax
Each sale changes stock, and each return changes it back. Products may have sizes, colours, bundles or barcodes. Tax rules depend on the place and the product, and discounts can stack in ways that need a clear order. A developer sets these rules once, tests them with real examples and shows you the numbers. Our database developers can help when stock and sales data grow large.
Hardware that works every day
Receipt printers, barcode scanners, cash drawers and card readers all have their own quirks. The same app can behave differently on two tablets. A careful developer lists the devices you use, tests on each and writes down how to set one up again if it breaks. This is dull work and it saves many calls on a Saturday afternoon.
Connecting to the rest of the business
A till rarely works alone. It may share products and stock with an online store, send sales to accounting software, add points in a loyalty scheme or feed a report. The developer connects these through their APIs and keeps clear logs so you can see what was sent and when. Our API developers do this kind of work in general, and our Shopify developers know the online store side.
Reports a manager can trust
At the end of the day a manager wants one answer: does the money in the drawer and the card total match the sales? A good POS makes that quick. The developer builds a closing report that splits cash, card and other payments, lists refunds and voids and can be exported for the accountant. If the report is hard to read, the staff stop trusting the system.
When a custom POS is a good fit
- Your way of selling is unusual, such as table service, repairs, rentals or events.
- A ready-made system forces workarounds that slow your staff.
- You run many tills and monthly fees add up.
- You need the till to work closely with your own app or warehouse.
For one small shop with a plain way of selling, a ready-made plan is usually enough. If a developer tells you to skip custom work, take it as honest advice.
Questions to ask in the interview
- A card payment times out. What does the till show, and how do you check whether it was charged?
- How do you build offline mode and avoid double counting a sale after sync?
- Two tills sell the last item at the same time. What happens?
- How do you test a receipt printer you do not own?
- How would you handle a refund for an item bought a month ago at a different location?
Listen for a real project behind each answer. A candidate who can sketch a neat screen but goes quiet on the dropped network case may never have run this in a shop.
Run a short paid trial
Give each finalist the same small task from your own business, such as a split payment with a discount, or a report that has to match a cash count. Pay for the time. Then compare the output, the questions each person asked and how clearly they explained what they did.
The first weeks after you hire
Agree the routine early: how an update is tested before it reaches the shops, who gets the call when a till fails and how staff report a problem. A single page listing devices, accounts and set-up steps spares the next person a lot of time.
Mistakes to avoid
- Testing only with the internet on and a single tab of products.
- Storing card details in your own database or logs.
- Releasing an update in the middle of the busiest hours.
- Choosing on a resume alone when no shop has used the software.
Related help: our fintech developers suit work on payments and ledgers, and our Android developers suit work on the tablet app.















