IT for Melbourne Retail SMEs: POS, EFTPOS, Customer WiFi That Actually Works

Retail IT failures cost money by the minute. A POS crash during Saturday lunch in a Richmond cafe is two hundred dollars of lost trade in fifteen minutes. The retail stack is small but every component is load-bearing, and the difference between “fine most of the time” and “actually reliable” comes down to choices made early.

The four-layer retail stack

Retail IT for an independent Melbourne SME splits into four layers, and the design choices at each layer dictate how the others have to be configured. The four layers are POS, payments (EFTPOS), connectivity (internet and Wi-Fi), and back office. They need to be designed together, even if they are bought separately.

The most common pattern we see in struggling retail IT environments is that each layer was bought independently, the POS chosen by the owner, the EFTPOS bundled with the bank account, the Wi-Fi installed by a sparky during fitout, the back office sorted out years later. Individually each is fine. Together they create the support nightmare that ends with someone calling at 11am on a Saturday because the POS cannot talk to the EFTPOS terminal.

POS choices and where each one breaks

The POS market for independent Australian retailers has consolidated around four serious options, plus a long tail of niche systems for specific verticals. Each has a real sweet spot and a genuine failure mode.

The honest assessment is that there is no single “best” POS. The choice depends on what the retailer actually needs to do.

For a single-site cafe in Cremorne doing 200 transactions a day, Square for Retail is a sensible default, low setup cost, simple to operate, integrated payments, accepts the tradeoff of limited inventory features for speed of deployment. With Square the failure mode is almost always internet reliability, not the POS itself.

For an independent fashion boutique in South Yarra with 2,000 SKUs, a fitting room workflow, and seasonal markdowns, Square is not enough. Lightspeed Retail is the right answer, and the additional monthly cost is repaid in saved time on inventory and reporting.

For a hospitality venue with bookings, table management, and serious EFTPOS volume, Tyro’s integrated stack works well, particularly when bundled with a compatible POS like Lightspeed Restaurant or Impos.

The point is that the POS choice should follow the workflow, not the marketing. Most of the Melbourne retailers we end up helping after the fact bought the POS based on a slick demo and discovered the gaps three months in. The discovery exercise, what do you actually do twenty times a day, what do you do twice a year, where does the current process hurt, is worth doing before signing the contract.

EFTPOS failover: the part most retailers ignore

EFTPOS failure modes are predictable and the failover strategy should be designed for them.

Failure mode 1: terminal hardware fault. A specific terminal stops working. The fix is to swap to a spare unit, which means you need a spare unit. For a single-terminal cafe, this means a backup terminal kept ready behind the counter. The cost of the spare is recovered the first time the primary fails during a busy service. For a multi-terminal store, the spare can rotate between terminals.

Failure mode 2: internet outage at the store. Most modern EFTPOS terminals require an internet connection to authorise transactions. The standard 4G failover is built into many terminals as a backup, but it is worth verifying that yours has it and testing it during onboarding. Tyro, Smartpay and Square’s newer terminals all support 4G failover. Some older terminals do not.

Failure mode 3: payment processor outage. Tyro had a serious multi-day outage in early 2022 that left thousands of Australian retailers unable to process card payments. The structural fix is to have a secondary merchant facility through a different processor, for example, a Square reader as a backup to a Tyro primary, or vice versa. The monthly cost is the secondary facility’s fees (often zero if it is transaction-based) and the operational discipline to test it monthly.

Failure mode 4: power outage. A UPS on the POS, EFTPOS and internet equipment buys 15 to 30 minutes of trading during a brief power cut. This is enough to clear the queue and process pending transactions. Picture a small wine bar where a transformer fault takes out the street for forty minutes during dinner service: a UPS like this pays for itself the first time it happens.

None of these failover strategies are expensive. All of them are missing from many of the independent retail stores we see. The conversation worth having with your POS and EFTPOS vendors before signing is: what happens when (each failure mode), what is the recovery time, and what is the cost.

Customer Wi-Fi without a PCI nightmare

Customer Wi-Fi sounds like a freebie to offer, a nice gesture, a small acquisition tool, something the cafe next door is doing. It becomes a serious problem if the network design is naive.

The cardinal sin is putting customer Wi-Fi and POS/EFTPOS traffic on the same network. The Payment Card Industry Data Security Standard (PCI DSS) is explicit that systems handling cardholder data must be segregated from untrusted networks. A flat Wi-Fi network with the iPad POS, the EFTPOS terminal, and the customer browsing Instagram all on the same SSID is a PCI compliance failure and a real attack surface.

The correct design has at least three logical networks:

• POS / payment network: The iPad, the EFTPOS terminal, the receipt printer, the barcode scanner if networked. Isolated from everything else. No client isolation issues because it is a small trusted set of devices.
• Staff network: The back-office PC, the manager’s laptop, the staff phones if they need authenticated access. Connected to the internet but separate from POS.
• Customer Wi-Fi: Open or captive-portal authenticated, internet-only access, no visibility of any internal network. Client isolation enabled so customers cannot see each other.

The implementation does not require expensive equipment. A managed firewall and a managed access point that support VLANs and multiple SSIDs handle this entirely. The hardware cost is in the $1,500-$3,000 range for a single-store fitout, which is a one-off and lasts the refresh cycle of the equipment.

The mistake we see in audits is not that retailers do not understand this. The mistake is that the fitout sparky installed a single consumer-grade modem-router with one Wi-Fi network because it was cheap, and nobody has revisited the decision since. Picture a four-store bakery chain where a network audit finds that three of the four stores have customer Wi-Fi and EFTPOS on the same flat network. Remediation is typically a two-week job and removes a serious latent risk.

In-store vs back-office split

The IT environment in a retail store splits cleanly into two zones, and treating them as one is a recurring source of operational mess.

The in-store zone is everything that needs to work during trading. POS, EFTPOS, customer Wi-Fi, in-store music system, the staff iPad they use for stock checks, the digital signage at the front. The defining characteristic is that downtime during trading hours is expensive, every minute counts.

The back-office zone is the manager’s PC, the accounting system, the rostering app, email, file storage, payroll. The defining characteristic is that downtime during the day is annoying but not directly revenue-impacting. Most back-office work can happen at 9pm or on a quiet Monday morning.

The implications for IT design are significant. The in-store stack needs the kind of monitoring and SLA you would associate with a critical system, 24/7 monitoring, proactive alerting, fast response. The back-office stack can run on the same general business IT stack that most Melbourne SMEs use.

This is also where the SLA conversation gets real. A Saturday-trading SLA needs to commit to response time during weekend trading hours, not Monday-to-Friday business hours. Most generic IT support agreements offer the latter and pretend it covers the former.

What a Saturday-trading SLA should actually say

Retail businesses trade when other businesses are closed. The standard MSP agreement that promises “1-hour response during business hours” is fine for a law firm and useless for a cafe. A retail-aware SLA covers a few specific things.

Our standard managed IT services agreements for retail clients include all of the above explicitly. P1 response during trading hours is a real commitment, backed by 24/7 on-call and emergency support rather than an assumption. Same-business-day on-site response in the Melbourne metro footprint covers Saturday trading. The reason this matters is that a retail outage cannot wait for Monday.

What to ask your POS vendor before signing

Most POS contracts are signed without the operational questions being asked. Here is the checklist we walk retail clients through before they commit.

• What happens if the store internet drops? Does the POS continue to take cash and card transactions, or does it stop entirely? Some POS systems handle offline mode well, others fail completely.
• What is the support phone number during Saturday trading? If it goes to voicemail, the answer is “no real support during trading”.
• What hardware do you provide vs what do I buy? Receipt printers, barcode scanners, cash drawers, customer-facing displays, every component should be specified.
• What integration does it have with my chosen EFTPOS provider? “Integrated” can mean anything from “tightly coupled” to “they send each other receipts via email”. Pin this down.
• What does the data export look like? Can you get your transaction history out in a usable format if you switch providers? Ask to see a sample export.
• What is the contract term and the exit process? Some POS contracts have 36-month lock-ins. Some have month-to-month flexibility. Know what you are signing.
• How do refunds, voids and returns work? Run through a sample return scenario step by step before signing. The friction in this workflow defines a lot of your daily operations.
• What reporting does it provide and how do I get it into Xero or MYOB? The accounting integration is the difference between an hour a week on reconciliation and a Sunday evening of pain.
• What is the failover terminal cost? Building this into the original contract is cheaper than adding it later.
• What happens if I want to add a second store? Multi-store pricing and feature differences should be understood up front.

None of these questions are aggressive. They are operationally honest. A POS vendor who cannot answer them clearly is one to be cautious about.

Realistic monthly IT cost for a 1-3 store independent retailer

The actual monthly IT cost for a Melbourne independent retailer with one to three stores breaks down roughly as follows. Numbers are typical for the Melbourne market in 2026.

The numbers vary based on retail format, transaction volume, staff size and POS choice. The pattern is consistent: a sensible IT stack for an independent Melbourne retailer is in the order of $1,000-$1,200 a month per store all-in. Trying to do it for less typically means cutting on the parts that matter (support response, backup, segregated networking) and paying for it later in downtime.

Where retail IT pays back on security

The Australian retail sector has been hit hard by cyber incidents in the past three years. Most of the headline cases have been larger chains, but the underlying patterns affect SMEs too. Three things matter for retail IT security at the SME scale.

Payment data exposure. Modern POS systems mostly handle this well, card data does not pass through the merchant’s systems in most flows, it goes directly to the payment processor. But back-office mishandling (storing card numbers in spreadsheets, processing manual key-entry on shared computers) creates exposure. The fix is policy and training, not technology.

Customer data. Loyalty programs, email marketing lists, customer order histories. This is personal information under the Australian Privacy Act and the obligations apply to retailers above the small business threshold and increasingly to those below it. A breach of a customer database is reportable and reputational.

Staff account compromise. Retail staff turn over and accounts get forgotten. A previous employee’s email account that still works is a phishing toehold. Offboarding discipline matters more in retail than in many other industries because of the staff churn.

Our retail clients are typically on the same security baseline as our other Melbourne SME clients, phishing-resistant MFA, conditional access, Defender for Endpoint, structured backup, documented offboarding. The retail-specific layer is the POS and EFTPOS configuration, which we treat as part of the cybersecurity baseline rather than a separate workstream.

How TechAssist supports Melbourne retail SMEs

Retail is one of our core service verticals. We have built our operational rhythm around the specific demands of retail IT: trading-hours support, fast response, segregated networking, integrated POS and EFTPOS, sensible monthly cost.

Our 13 Melbourne-employed staff work across both our Tecoma head office and our Bourke Street CBD office, which is convenient for CBD retailers in particular. Trading-hours support is covered by our NOC in Tecoma and 24/7 on-call and emergency support. POS-down and EFTPOS-down incidents are treated as P1. Same-business-day on-site response for Melbourne metro store outages is standard.

The per-user fixed monthly pricing model works particularly well for retail because the user count is stable and the cost is predictable. The retail-specific cost components (in-store hardware, networking, POS integration) are quoted separately and transparently.

We support retailers across the inner Melbourne suburbs and the CBD. Where appropriate, we work alongside the retailer’s existing POS support relationship, we are not trying to replace Tyro or Lightspeed, we are trying to make sure the rest of the IT stack supports them properly.

Frequently Asked Questions

Can I run a small cafe POS without managed IT support?

You can, but the day the POS fails during a busy Saturday lunch you will wish you had not. For a single-site low-complexity cafe, the cheaper approach is a Square-based setup with good in-built support and a backup terminal. The middle ground, moderately complex POS with no managed support, is the worst of both worlds.

Do I need separate Wi-Fi networks for customers and POS?

Yes. This is a PCI DSS requirement, a security best practice, and easily achievable with modern managed access points. Anyone telling you a single flat network is fine is either uninformed or hoping you do not notice.

What is the right EFTPOS provider for an independent retailer?

Tyro, Smartpay and Square are the three serious options for independent Melbourne retailers. Tyro has the best POS integration story. Smartpay has competitive pricing. Square is the simplest to set up. The choice depends on volume, POS, and how much integration matters.

How quickly should my IT support respond on a Saturday?

For a P1 incident (POS down, EFTPOS down, store internet down), the same response target as a weekday: a real engineer, with same-trading-day on-site if remote resolution is not possible. Anyone offering you “1 hour response during weekday business hours” is not retail-aware.

What is the typical lifespan of POS hardware?

Three to five years for the terminals themselves, depending on use. iPad-based POS systems last as long as the iPad is supported by iOS updates, which is usually five to six years from release. Refresh planning should be part of the original budgeting conversation.

Can I integrate my POS with Xero properly?

Most modern cloud POS systems have direct Xero integration that handles daily sales summaries, payment reconciliation, and stock movements. The integration is rarely perfect out of the box and usually needs a few hours of configuration to map account codes correctly. Done well, it removes most of the manual reconciliation work.

The summary for retailers

The Melbourne retail IT stack that actually works is built around four things: the right POS for your workflow, EFTPOS with documented failover, segregated networking that keeps customers off the payment network, and trading-hours-aware support. Get those four right and the rest of the IT environment looks after itself.

The mistakes that hurt retailers are predictable: choosing POS based on price not workflow, ignoring EFTPOS failover until it bites, flat customer Wi-Fi networks, and generic IT support agreements that do not actually cover Saturday trading. None of these mistakes are expensive to avoid if they are addressed during the original setup or refresh.

If you are a Melbourne retailer looking at a fitout, a multi-site expansion, or a refresh of a tired IT setup, have a chat with us. We will give you a straight assessment of the stack you have, the stack you should have, and what it takes to get from one to the other.