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

POS Software for Australian Retail and Hospitality: Custom or Integrated, Built Around How You Trade.

When to buy a subscription POS and when to build one, how it connects to Xero, card terminals and delivery platforms, and what GST, card surcharge and privacy rules ask of the software.

Buy or buildAn honest view before any code
GST and BASRecords designed in from the start
1 Oct 2026Card surcharge rules checked

A point of sale system looks simple until it meets a real shop. Someone has to reconcile the till against the bank, split a table bill four ways, push an order to the kitchen, keep stock honest across two sites and hand the accountant numbers that match the BAS. Most Australian retailers and cafes are well served by a subscription POS. Some are not, and this page is for them.

We build custom and integrated POS and ordering systems for Australian retail and hospitality businesses. Below we explain when a custom system pays off, what it connects to, how card surcharging changed on 1 October 2026, what GST record keeping asks of the software, and when you should simply buy an off-the-shelf POS. To talk through your venue, tell us how you trade today.

01

Off-the-Shelf POS or Custom: When Each Is Right

Start with the honest question: do you need custom software at all? A subscription POS is usually right when your business looks like most others in your category. It is already built, supported and connected to the common payment terminals, so you pay for it monthly and get on with trading.

Your situationUsually the sensible choiceWhy
One cafe, shop or salon with standard menus or productsA subscription POSThe features exist, support exists and switching later is manageable
Several venues with the same menu and the same rulesA subscription POS with multi-site features, checked on a trialCheck reporting and stock across sites before you commit
A POS exists but cannot talk to your accounting, stock or delivery systemAn integration layer built around itYou keep the till staff know and fix only the gap
Your pricing, booking, production or hire rules do not fit any POSA custom POS or ordering systemYou stop bending the business around the software
Ordering happens on your own app or site as well as in storeCustom ordering connected to a POSOne menu, one stock count, one set of reports

We say this plainly because a custom build is a bigger commitment: you own something that has to be maintained. If a ready product covers 90 percent of your needs, buy it and connect the rest. Our custom software development page explains how we decide between building and buying more generally.

02

When a Custom POS or Ordering System Pays Off

Custom POS earns its place where the way you sell is part of what makes the business work. These are the cases we see most often.

  • Unusual pricing. Weighed goods, made-to-order items, hire by the day, trade accounts with agreed prices or bundles that change by customer.
  • Ordering on several channels. In store, on a tablet at the table, through your own website and through delivery platforms, all drawing on one menu and one stock figure.
  • Workflow around the sale. Kitchen or workshop tickets, deposits and part payments, repairs and job tracking, loyalty rules that are not points per dollar.
  • Specific hardware. Scales, scanners, label printers, kiosks, or a terminal you must keep for your existing merchant arrangements.
  • Reporting the owner actually reads. Margin by item, wastage, staff and shift reports in the format your bookkeeper wants.

If none of these sounds like you, the buy-first path above is probably right. If two or three do, the cost of workarounds is often higher than it looks, and that is the conversation to have. For the wider picture of running a business on connected systems, see our business management software page.

03

Integrations: Xero, MYOB, Terminals and Delivery Platforms

A POS is rarely the only system. The value is in how cleanly it connects, so we start from the integrations and work back. Each row below states what the vendor documentation says, and we confirm the current detail again at scoping because vendors change their programs.

SystemWhat the documentation saysWhat it means for a build
XeroThe Xero Accounting API exposes Invoices, Payments, Items and Bank Transactions endpoints, secured with OAuth 2.0 (Xero OpenAPI definition)Daily sales, payments and items can post to Xero instead of being retyped
MYOBMYOB runs a developer program with its own API. We have not quoted endpoint detail hereWe confirm what your MYOB product exposes before promising any sync
Stripe TerminalStripe describes a custom POS integration with SDKs for Android, iOS, JavaScript and React Native, a server-driven option, and offline payments (Stripe Terminal docs)Online and in-person payments can sit in one system. Check Stripe's availability list for Australia and for your readers
TyroTyro's integrated EFTPOS docs describe a browser JavaScript library, a Windows .NET library and a Pay@Table REST API, and Tyro states integrations must be certified before production (Tyro integrated EFTPOS; Tyro Connect POS)Allow certification time in the plan if Tyro terminals are in scope
Uber EatsThe Marketplace APIs let a POS sync menus, set store status and receive, accept or deny orders. Uber states access to these APIs may require written approval (Uber Eats developer docs)Delivery orders can land in the same queue as in-store orders, subject to approval from the platform

Other terminals, scales and delivery platforms are possible. We open the developer documentation for each before we name a capability, and where a vendor only works with approved integrators we tell you that at the start rather than in week six. Related work on the connection layer is covered in our custom software development service.

04

Card Surcharging After 1 October 2026

Hospitality and retail teams used to add a card surcharge line to the bill. That has changed. The Reserve Bank of Australia's FAQ states that from 1 October 2026 surcharging is removed on eftpos debit and prepaid, Mastercard and Visa credit, debit and prepaid, and American Express credit cards, with PayPal following on 5 October 2026 (RBA frequently asked questions).

The same page says the networks, not the RBA, impose the no-surcharge rules, that card payments between businesses are not automatically exempt, and that weekend and public holiday surcharges, booking fees and service fees are outside these changes. It treats payment service provider fees for terminals and processing as fees for services, not surcharges.

If your POS or ordering systemCheck this now
Adds a percentage surcharge for card paymentsRemove or disable it for the card types the RBA lists, and test refunds
Charges a public holiday or weekend loadingKeep it as a separate, clearly labelled price line, not a card fee. Ask your accountant how to present it
Shows a price one way online and another in storeMake sure the displayed price is the price charged, whatever the payment method
Prints a receipt with a payment fee lineReview wording and totals so the receipt matches what the customer actually paid

This is general information from the RBA page, not legal advice. Ask your payment provider and adviser how it applies to your business. A custom POS has an advantage here: a rule change is a configuration or code update that you control, not a ticket to a vendor.

05

GST, BAS and Record Keeping in the POS

Your POS creates the records the ATO expects you to keep. The ATO's record keeping pages say GST records generally need to be kept for five years from when they were prepared or the transaction was completed, whichever is later, and that electronic records are subject to the same requirements as paper (ATO GST records; ATO record keeping overview). Records must be readable and retrievable when the ATO asks for them.

A POS therefore has to do more than total the day. In practice we design these behaviours in from the start:

  • A GST treatment on every product and service line, so each line is recorded as taxable, input-taxed or one of the categories the ATO treats as carrying no GST, with an audit trail when someone changes it.
  • Tax invoices on request. The ATO guidance we read notes a tax invoice is generally needed to claim a GST credit on purchases above $82.50 including GST, so a trade customer needs a proper invoice and not only a till receipt.
  • Refunds, voids and discounts recorded with who did them and why, and never silently deleted.
  • End-of-day and end-of-month exports that match what your bookkeeper or Xero needs for the BAS, in the periods you report.
  • Retention and backup so that records stay available for the required period even if you change POS vendors later.

We build the records; we do not give tax advice. Your accountant decides your accounting method and GST treatment, and we configure to their instruction.

06

Customer Data, Privacy Act and Breaches

A POS with loyalty or online ordering holds names, phone numbers, emails and order history. The Privacy Act 1988 and the Australian Privacy Principles apply to businesses above the small business threshold. The OAIC says a small business has an annual turnover of $3 million or less and is generally outside the Act, with exceptions such as providing health services or trading in personal information (OAIC small business). Many multi-site hospitality and retail groups are above that line, and some smaller ones choose to follow the principles anyway.

The practical design points follow the OAIC's principles summary (APP quick reference): collect only what you need, tell people what you collect, protect it with reasonable steps and know where it is stored. If a breach happens, the Notifiable Data Breaches scheme expects an assessment to be completed within 30 days of suspecting an eligible breach, and the OAIC expects it much sooner where possible (OAIC NDB scheme).

Design choiceWhat we usually propose
Staff accessRoles so a casual cannot export the customer list
Card dataCard details handled by the payment provider's terminal and SDK, not stored in your system
Customer recordsCollect an email or phone only when the customer opts in to loyalty or receipts
Hosting and suppliersA written list of every service that receives customer data and where it runs

This is general information, not legal advice. Ask your own adviser what applies to you.

07

How a POS Project Runs Without Stopping Trade

A POS project touches live trading, so it is staged. Our usual sequence:

  1. Walk-through of a real shift. We watch or ask how a busy hour runs: who takes orders, who handles cash, what breaks.
  2. Scope and proposal. What the first release does, what it connects to and what waits.
  3. Integration check. Accounting, payments, delivery and hardware confirmed against current vendor documentation, including any approvals or certification.
  4. Clickable screens. Staff try the order and payment flow on the actual device before code is final.
  5. Staging and test trading. We usually propose a staging environment and a quiet-hours trial with real devices and your terminals.
  6. Cut-over plan. Menu and product import, parallel running for a short period and a fall-back if the network drops.
  7. Handover. Documentation, accounts in your name and an agreed support arrangement.

Offline behaviour deserves its own mention. A POS that stops when the internet drops loses sales, so we ask what happens during an outage and design for it, using the offline modes that the payment tools support where they exist. Weekly demos and an NDA are usual if you want them in the contract.

08

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

We are a good fit ifA subscription POS is probably better if
Your pricing, ordering or production rules do not fit a ready systemYou run a standard cafe, shop or salon and a ready POS covers it
You need one stock and sales picture across store, online and deliveryYou want to be trading within days and have no integration needs
You want accounting, GST and BAS reports built around your processYou do not want to maintain any software of your own
You want to own the system rather than rent itYour budget is fixed and small and the monthly fee suits your cash flow

If you are unsure, tell us what you use today and what frustrates you. We will say whether a change of product, an integration or a custom build is the right next step. Our case studies show delivered work across the company, our Shopify development page covers online stores that connect to a POS, and our AI automation page covers reporting and back-office tasks that can sit behind it. Back to the Australia home page.

Straight Answers.

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

It is a point of sale and ordering system built around your pricing, workflow and reporting, connected to the payment terminals, accounting and delivery tools you use. We build custom and integrated POS systems for Australian retail and hospitality businesses. Your code lives in your repository from the first week.

Often yes. If a ready POS covers most of your needs, buying it is faster and carries less to maintain. We recommend custom work only where your pricing, ordering or reporting rules do not fit, or where the gaps between your systems cost more than the build.

Xero publishes an Accounting API with endpoints for invoices, payments, items and bank transactions, using OAuth 2.0. A POS can post daily sales and payments to it. We confirm the exact fields and limits at scoping.

Tyro documents integrated EFTPOS options and requires certification before production use. Stripe documents a Terminal SDK and server-driven integration for custom POS builds. We check availability for your terminals and plan time for any certification.

Possibly. Uber Eats documents Marketplace APIs for menus, store status and orders, and states that access may require written approval. Each platform has its own program, so we confirm eligibility early.

The RBA states that surcharging is removed on eftpos, Mastercard, Visa and American Express credit cards from 1 October 2026, with PayPal following on 5 October. Weekend and public holiday surcharges, booking fees and service fees are described as outside these changes. Check your own set-up with your payment provider and adviser.

The ATO pages we read say GST records generally need to be kept for five years from when they were prepared or the transaction was completed, whichever is later, and can be kept electronically. Your accountant confirms what applies to you.

It can. The OAIC treats a business with annual turnover of $3 million or less as a small business, generally outside the Act unless an exception applies. Larger businesses must follow the Australian Privacy Principles. Ask your adviser to confirm your position.

We ask this at the start and design for it. Some payment tools document offline modes, and the POS can queue orders locally. The plan sets out what works offline and what waits for the connection.

Yes. We usually set up hosting and accounts in your business name.

Yes. Often the better answer is a connection layer that links your current POS to accounting, stock or online orders. We tell you if the existing product cannot be integrated and a change is cheaper.

Tell us how you trade, which systems you use and the price range you have in mind for the build. We scope it on a short online call.
Australia

Tell us how you trade today

Describe your venue and the systems you use. Book a call and we will say whether to buy, connect or build.

  • 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