Skip to main content
Have a project in mind? Let's talk
Book a call Tell us about your project Book a Call
UK
  POS Software

POS Software UK: Custom and Integrated Tills for Retail and Hospitality.

When an off-the-shelf POS is the right answer, when to build, and how a custom till connects to card payments, your accounts and delivery apps under UK VAT rules.

Buy or buildWe tell you when an off-the-shelf POS is the right answer
VAT-awareWe build the VAT rules for eat-in, hot and cold takeaway into your till
Your nameCode and accounts we usually set up in your name

A till is the one system a shop, cafe or restaurant cannot do without, and the market is crowded with subscriptions. Most UK businesses should start by checking whether an off-the-shelf POS does the job, because it usually does. Custom work earns its place only when your trading does something the packaged tills cannot, or when the till must sit inside a larger system you already run.

Devvista is a software development company that builds custom and integrated point-of-sale and ordering systems for UK retail and hospitality businesses. This page sets out when to subscribe and when to build, how a custom POS connects to card payments, accounts and delivery apps, and the UK tax and data rules it must respect. To talk it through, describe how you trade today.

01

Off-the-Shelf POS or Custom: How to Decide

The decision is about differences. If your trading looks like most shops or restaurants, a packaged POS has already solved it, and you pay a subscription for the work of many customers. If your trading is unusual, you can end up bending the business to fit the till, or paying for add-ons that only half work.

Your situationUsually the right answerWhy
One or two shops or a standard cafe or restaurant, normal menu, card and cashSubscribe to an off-the-shelf POSThe common cases are already built, supported and updated by the vendor
You want online ordering for collection onlyA packaged ordering tool firstCheaper to test demand before building anything
Unusual pricing: made-to-order items, rentals, deposits, split billing by ruleCustom or a configured platform with custom partsStandard tills handle the odd rule poorly
Many sites with central stock, recipes and one set of booksCustom or integrated systemThe till becomes one part of an operations system
A POS must feed an ERP, warehouse or booking system you already runIntegration work, sometimes a custom front endThe cost lives in the connections, not the till screen
A unique customer experience: kiosks, self-order, table QR with your own flowCustom ordering front end on a payment platformThe experience is the product

We tell you which row you are in after one call. If the answer is "subscribe", we say so, and we may still help with the integration, for instance posting daily sales to your accounts. For the wider approach, see our custom software development page.

02

The Five Jobs Inside a POS

A POS looks like one screen, but it is five jobs wrapped together. Naming them helps you decide which to buy and which to build.

PartWhat it doesBuild or buy
Order and checkout screenTakes items, modifiers, discounts and splits billsBuy unless your rules are unusual
Card paymentsTakes the money through a payment provider and a card readerAlways buy the payment service; build only the link
Menu, price and stockKeeps items, prices, allergens and stock levelsBuild if stock links to recipes or a warehouse system
Reports and taxDaily takings, VAT split, staff and product reportsBuy or build, but the VAT logic must be right
IntegrationsLinks to accounting, delivery platforms, loyalty and online ordersThis is where custom work usually pays off

Notice that payment handling is one to buy. Building your own card processing is a regulated, security-heavy job we would not suggest for a small business.

03

Card Payments and Terminals in a Custom POS

The usual way to build a custom POS is to keep the till and ordering logic yours and use a payment platform for the card side. Stripe's documentation describes Terminal as allowing businesses to accept in-person payments, with in-person and online payments managed in one system. It lists a custom POS integration option, an API-based integration plus SDKs for Android, iOS, JavaScript and React Native, and a feature for accepting payments with intermittent or no internet connectivity (Stripe Terminal documentation). It also points to availability by country, which you should check for your own reader and card types before choosing.

Square's Orders API is another example. Its documentation says it records items, calculates totals and tracks an order through fulfilment, with pickup, shipment, delivery and in-store fulfilment types and webhooks that tell your app when an order is created or updated (Square Orders API). The page does not state geographic availability, so we would confirm that for the UK before using it. Other card platforms exist, and we choose from what suits your reader, fees and country.

QuestionWhy we ask it
Which card readers and wallets must it accept?Reader and country support is set by the payment provider
What happens if the internet drops?Offline payment support varies and needs a designed fallback
Where do you want money reports to land?The provider's payout and fee reports feed your books
Do you need tips, deposits or pre-authorisation?Some flows are payment-platform features, not till features

We read the provider's own documentation before naming any capability to you, and we put a short list of what we confirmed in the written scope.

04

Linking the POS to Xero, Sage and Your Books

Accounts is where a POS pays back. If takings are keyed into the books by hand, the same facts are typed twice, and mistakes hide in the gaps. A good integration posts daily summaries, not every sale, so your bookkeeper sees clean figures.

Xero publishes an Accounting API on its developer site (Xero developer documentation). We would not state what a given integration can post until we have read the specific endpoint and checked it against your set-up, and the same applies to Sage and any other package. What we can say is how we plan it:

  • Agree the mapping. Which sales go to which nominal codes, which VAT code applies and where tips and refunds go.
  • Post summaries. One entry per day per site tends to be easier to reconcile than one per sale.
  • Keep an audit trail. Every posted summary links back to the till records it came from.
  • Make errors visible. A failed post shows on a screen and in an alert, not silently.

If you run a wider operations system, our work on Odoo ERP for manufacturers shows how we think about connecting front-line systems to the books.

05

Delivery Platforms and Online Ordering

Delivery apps send orders you must accept quickly. Some restaurants run a tablet per app, and staff re-key orders into the till. An integration pushes those orders into your kitchen flow and keeps your menu and availability in step.

The platforms set their own rules. Uber's developer documentation for Uber Eats says POS integration is its most common and valuable integration path, that access may require written approval from Uber, that production requires a 99 percent injection success rate and that a full POS integration takes about 4 to 8 weeks (Uber Eats developer docs). Its APIs cover menu, store, order, promotions and reporting. We have not read the developer documentation of other UK delivery platforms for this page, so we do not name what they allow. Before committing, we would open each one and confirm what access you can get as a merchant.

Point to checkWhy it matters
Who can get accessSome platforms approve integrations case by case
Menu syncPrices and availability must match, or orders bounce
Order acceptanceEach platform sets its own acceptance window
ReportingPlatform fees and payouts need to reach your books
06

UK VAT on Takeaway and Eat-In: What the Till Must Get Right

VAT is the UK rule that most often surprises a hospitality business, because the rate depends on how the food is supplied. HMRC's VAT Notice 709/1 says that hot takeaway food is standard-rated if it is "hot at the time that it's provided" to the customer and meets one of five tests, such as being heated to order or kept hot. It says cold takeaway food and drink is zero-rated, unless it is an item that is always standard-rated, such as crisps or sweets. For food eaten on the premises, it says you "must always charge VAT at the standard rate" (VAT Notice 709/1). The standard rate is 20 percent (VAT rates on GOV.UK).

Mixed supplies are the trap. The same notice says that where inclusive-priced items are sold for takeaway you have to work out the tax value of each item, and that items are usually mixed supplies if each can be bought separately from the menu. A hot item with a cold ingredient sold as one item is wholly standard-rated. If you cannot work out the right liability at the point of sale, you must keep satisfactory evidence for a fair apportionment.

Till design pointWhat the HMRC notice impliesWhat we build
Eat-in versus takeawayEat-in catering is always standard-rated; takeaway depends on temperature and the five testsAn order-type switch at the start of the order that sets the VAT code per line
Hot and cold itemsHot takeaway is standard-rated; cold takeaway can be zero-ratedItem attributes that mark hot, cold or always standard-rated
Combos and bundlesValues may need splitting across itemsA bundle rule that allocates price to each part, written down
Changing a takeaway to eat-inThe supply type changes the rateA visible change that re-prices VAT on the order
EvidenceIf liability cannot be worked out at the till, evidence is neededStored rules and an export your adviser can read

Rates and schemes change, and the notice itself carries temporary measures, so your accountant should confirm your VAT treatment. We build the till to follow the rules you set.

07

HMRC Record-Keeping and Making Tax Digital

A POS is also a record-keeping system. HMRC's VAT Notice 700/21 says you must generally keep business records for VAT purposes for at least six years. It says that if you use a retail scheme you must keep a digital record of your daily gross takings, and that underlying records such as till rolls or Z readings need to be kept but not necessarily digitally. It adds that all VAT-registered businesses must keep and preserve certain records digitally, in functional compatible software, and that data transfer must use digital links, with copy-and-paste not counting as one (VAT Notice 700/21).

So the design questions are practical: can the till export daily gross takings, can Z reports be reproduced, and does the data flow to your VAT software without retyping? We map the data flow with you and ask your accountant to confirm it works with your scheme.

08

UK GDPR for Orders, Bookings and Loyalty Data

A till may hold customer names, phone numbers for bookings, email addresses for receipts and loyalty data. Under UK GDPR you remain responsible for it. If a supplier handles it for you, Article 28 asks for a written contract, action only on your recorded instructions, confidentiality for the staff involved and deletion or return of the data at your choice (Article 28).

  • Collect little. Take a phone number for a booking, not for every sale.
  • Separate roles. Staff see what the shift needs, managers see reports.
  • Keep card data with the payment provider. Your system stores the result of a payment, not the card number.
  • Plan deletion. Decide how long loyalty and booking data stays.

We are developers, not lawyers, and your adviser should confirm what applies to your business.

09

How a POS Project Runs, Step by Step

A typical project, from first call to live trading, runs in these stages.

  1. Trading walk-through. We watch or hear how an ordinary day runs: the orders, the peaks, the problems.
  2. Subscribe-or-build verdict. We tell you which parts to buy and which to build, and why.
  3. Written scope and quote. Screens, rules, integrations and what is not included, in pounds sterling, with the budget range you have in mind taken into account.
  4. Clickable prototype. Staff try the order flow on a tablet before anything is built.
  5. Build on a test environment. A demo every week or two on sample menus.
  6. Pilot at one site, one quiet shift. Real orders with the old till beside it.
  7. Cutover and training. Staff trained, fallback paper process agreed.
  8. Handover. Documentation and access passed to you. Accounts and code sit in your name wherever the platform allows, and the proposal covers the details.
10

What Moves the Cost of a POS Project

Prices vary, because a one-site ordering tool and a multi-site stock system are different projects. We begin with a short call about your budget range, then propose a scope in pounds sterling that fits it.

What moves the quoteWhy
Number of sites and devicesMore tills and kitchen screens mean more set-up and testing
VAT and menu rulesHot, cold, combos and eat-in or takeaway logic need careful design
IntegrationsAccounts, delivery platforms and stock systems each add work
Offline behaviourTrading through a broken connection needs a designed fallback
HardwareReaders, printers and tablets are bought separately and must be supported
ReportingCustom reports and exports need their own specification
11

When Devvista Is a Good Fit, and When It Is Not

We suit UK retail and hospitality businesses whose trading does not fit a standard till, or that need the till to work with other systems. Examples include multi-site operators, businesses with made-to-order products and firms that want one set of figures across channels. Our AI automation work can add routine back-office steps behind a till, and our case studies show other delivered work.

We are a good fit ifWe are probably not if
Your pricing or ordering rules are unusualA standard cafe till would do the job
The till must feed your books, stock or ERPYou want to avoid any monthly platform cost at all
You want the code and accounts in your nameYou want a vendor to handle everything, hardware included
You welcome being told to subscribeYou want card processing built from scratch

See also our wider web development service for the website and online ordering side, and our UK home page for the rest of the range.

Straight Answers.

Still have a question?Send it over and we will answer personally.Send Your Question

Point-of-sale software takes orders, handles payment, records sales and tax and reports on trading. In hospitality it often drives kitchen screens and online ordering, and in retail it ties into stock.

Buy if your trading is standard. Build, or integrate, when your pricing rules are unusual, the till must feed your stock or ERP, or the ordering experience is the product. We tell you which after one call, even if the answer is to subscribe.

It depends on your menu, number of sites and what it must connect to, so we do not rank vendors here. We compare options against your trading and tell you if a packaged restaurant POS is enough.

Yes, through a payment platform. Stripe documents a Terminal product with SDKs and an API for custom POS integrations, and availability varies by country, which we check before choosing. We do not suggest building card processing yourself.

In principle, through their developer interfaces. We confirm what a specific integration can post by reading the vendor documentation and testing against your account before we promise it, and we usually post daily summaries.

Uber documents POS integration for Uber Eats, with access that may need written approval from Uber. For other platforms we open their documentation and confirm what a merchant can get before we plan the work.

HMRC's VAT Notice 709/1 says eat-in catering is standard-rated, hot takeaway is standard-rated if it meets its tests and cold takeaway can be zero-rated. The standard rate is 20 percent. Your accountant should confirm your treatment.

VAT Notice 700/21 says VAT records are generally kept for at least six years, a retail scheme user keeps a digital record of daily gross takings, and VAT-registered businesses keep certain records digitally using compatible software. We design exports around this.

Yes, where it holds personal data such as booking or loyalty details. Article 28 asks for a written contract with any processor, action only on your instructions, confidentiality and deletion or return of data. Your adviser should confirm your case.

It depends on sites, devices, VAT rules, integrations, offline needs and reporting. On a short call you tell us the budget range you have in mind, and we come back with a proposal in pounds sterling that fits it.

We build and integrate software. Hardware such as readers, printers and tablets is bought separately, and we confirm what your chosen devices support before building.
United Kingdom

Tell us how you trade

Describe your sites, your menu or range and what the till must connect to. Book a call and we will say which parts to buy, which to build and what the first release should contain.

  • 30-minute online call
  • Honest feedback on fit
  • No obligation
  1. Book a call30 minutes online. Tell us what you want to build.
  2. Get a straight answerHonest feedback on fit and scope.
  3. DecideYou choose the next step once the scope is clear.
Chat on WhatsApp