IT for Melbourne Hospitality: POS, Reservations and Compliance Without the Headache

Hospitality IT is a niche of its own. A Friday 7pm POS failure is a revenue event. A dropped EFTPOS during Saturday service costs you walk-outs, comped meals, and angry reviews. Technology decisions venues make casually, based on what the previous chef used, set the operational ceiling for the next five years.

This guide is the practical version for Melbourne hospitality operators. We will walk through the actual POS landscape (Lightspeed, Square for Restaurants, Hub by Now Book It, Impos), the reservations platforms (SevenRooms, OpenTable, Now Book It), the payments stack (Tyro, Mx51, Square), the customer Wi-Fi versus staff Wi-Fi separation that catches almost every venue out, RSA and compliance data storage obligations, and what after-hours support actually costs when you do the maths honestly. Plus the four big hospitality IT traps we see in every second venue we onboard.

TechAssist supports a number of Melbourne hospitality clients across Carlton, Fitzroy, South Yarra, and the CBD. Our managed IT services Melbourne team treats hospo as its own discipline because the failure modes are different. P1 incidents are responded to in under 15 minutes from our 24/7 NOC at Tecoma, and same-business-day on-site coverage across Melbourne metro is standard. For Friday and Saturday service, that is the only response window that matters.

The Melbourne Hospitality Stack: What Actually Gets Used

Let us start with the realistic landscape. We are not going to list 47 vendors. We are going to list the platforms that we genuinely see deployed in Melbourne venues, the size of operation each fits, and where each one shines or struggles.

POS Platforms

Lightspeed Restaurant remains the dominant cloud POS for Melbourne mid-tier venues. Sit-down restaurants, gastropubs, mid-sized cafes. Strong reservations integration, decent inventory, solid reporting, and a maturing payments stack. Where it struggles: large multi-venue operators with central kitchen workflows, and any venue that needs deep table management with floor plan complexity beyond moderate.

Square for Restaurants is the price leader and is genuinely good for cafes, casual dining, and bar-led venues under about $1.5 million revenue per year. The hardware ecosystem is clean, the back-of-house is intuitive, and payments are baked in (which is a feature for some operators and a constraint for others). Where it struggles: high-volume Friday-Saturday service in venues that need granular table management or complex menu modifiers.

Hub by Now Book It is the Australian hospitality platform that has been quietly winning the multi-venue mid-market. Especially strong in venues that prioritise reservations as a strategic capability. Reservations and POS are in one ecosystem, the Australian support is genuinely responsive, and the reporting is built for owner-operators. Where it struggles: venues that have already committed to a different reservations platform and do not want to consolidate.

Impos remains a serious option for venues that need on-premise resilience and deeper customisation. It is the option we see most often in established Melbourne CBD restaurants that have been running for ten-plus years and want offline-capable hardware. The Australian provenance is real and the support is local. Where it struggles: greenfield deployments where the operator wants a cloud-first stack with minimal hardware on premises.

Reservations Platforms

SevenRooms is the platform of choice for venues that treat guest data as a strategic asset. The CRM, the marketing automation, and the guest profiling are deeper than the alternatives. Used by most of the higher-end Melbourne dining group operators. The cost reflects the depth, and the platform is overkill for cafes or casual venues.

OpenTable is the global brand with the broadest discovery reach, especially for international visitors. The booking funnel converts well and the diner-facing experience is polished. The downside is the cover fee model, which adds up quickly for high-volume venues, and the integration depth is shallower than SevenRooms.

Now Book It (the reservations product, separately from Hub POS) is the Australian-grown option with strong local support and a fee model that suits high-volume operators better than OpenTable for many configurations. Good ecosystem integration including with Hub POS.

The reservations decision is less binary than POS because most venues run one reservations platform integrated to whichever POS they chose for other reasons. The integration quality between your POS and your reservations platform matters more than which reservations brand you choose.

Payments

Tyro is the dominant Australian merchant for hospitality. Integrates cleanly with Lightspeed, Hub, Impos, and several others. Reliability has improved significantly since the 2023 outage that affected a chunk of Australian hospo overnight, and the surcharge and fee structure is reasonable. The integration with Xero for end-of-day reconciliation is good.

Mx51 is the increasingly serious challenger, particularly for venues that want flexibility on the back-end acquirer relationship. Better suited to multi-venue operators with banking arrangements they want to preserve.

Square’s integrated payments work well for Square POS users and not at all for everyone else. If you are on Square POS, this is the natural answer. If you are not, it is irrelevant.

The honest take on payments: the difference between the major providers on rate is a few basis points. The difference on reliability and the failover story for when the integrated terminal stops working is huge. Always have a backup terminal that is not on the same network and not on the same provider. We will come back to this in the traps section.

Customer Wi-Fi vs Staff Wi-Fi: The Separation Almost Every Venue Misses

This is the most common Melbourne hospitality IT failure mode we see. The previous IT person or the NBN installer set up one Wi-Fi network. Staff use it, guests use it, the POS uses it, the EFTPOS uses it, the music streaming box uses it, the kitchen printer uses it, and the smart fridge thermometer uses it. Everything sits on the same flat network, and one compromised guest device can poke at everything else.

The correct configuration is three logically separated networks. Each on its own VLAN, with firewall rules between them.

That is the baseline. A venue with this structure has, in one configuration change, removed the most common Melbourne hospo network risk: an attacker pivoting from customer Wi-Fi to the POS network and capturing card data, or to the EFTPOS terminal and capturing transaction streams.

The cost to deploy this for a typical 80-seat Melbourne venue is roughly $3,500 to $5,500 in UniFi hardware plus six to ten engineer hours. The cost of not deploying it is, eventually, a card data incident, an insurance claim, and a regulator conversation. We covered the realistic cost of an incident in another article: for a venue, the productivity and revenue loss from a multi-day outage of POS or EFTPOS during peak service is brutal.

Our cybersecurity services Melbourne team treats network segmentation as table stakes for any hospitality client. Read our zero trust security model explained guide for the broader framework view.

RSA and Compliance Data Storage

Hospitality venues store more regulated data than they realise. RSA compliance records, ID verification records (especially for late-night venues), staff working hours under Fair Work, guest data including reservations preferences and dietary requirements, and CCTV footage of both staff areas and customer areas.

Each category has its own retention rules and access controls. The traps we see most often:

One. CCTV footage stored on a DVR with a default password, with no retention policy, and with access for anyone who knows the office PIN. The Australian Privacy Act applies to the CCTV footage in most venue configurations because the venue is collecting personal information about identifiable individuals. The retention should be defined (typically 28 to 90 days), access should be controlled, and there should be a process for handling subject access requests if they come up. They do come up, especially after incidents involving staff or patrons.

Two. Staff records stored on the kitchen office PC, with a shared password, and never backed up. This is a multi-failure scenario. The records are required for Fair Work compliance. If the PC dies (and the kitchen office PC always dies eventually because of the kitchen environment), the records are gone. The fix is moving staff records to a cloud HR platform like KeyPay, Tanda, or Deputy, which gives you backup, access control, and audit trails for free.

Three. Guest data being treated as the property of whichever staff member set up the reservations platform. When that staff member leaves, the data either goes with them or becomes inaccessible. The fix is treating the reservations platform as a business system with ownership clarity, admin access controlled by the operator, and exported backups on a regular cadence.

Four. Tip records, payroll exports, and EFT batch files stored on shared drives without access control. Anyone with the office Wi-Fi password can read or modify them. The fix is moving these to a properly permissioned cloud storage location with audit logging, and ensuring only operations and finance staff have access.

For the broader privacy framework, see our Australian Privacy Act for SMBs guide. Most hospitality venues fall under the Privacy Act because they collect personal information about identifiable individuals at scale, and the data handling expectations are not different from other industries even though the venue context feels different.

The Four Hospitality IT Traps

These are the four traps we see in roughly every second Melbourne hospo venue we onboard. None is exotic. All are preventable.

Trap One: Shared Admin Passwords

The POS admin password is “Manager01” or the year the venue opened. Every manager has it. The departing dishwasher had it. The casual who worked one shift in 2022 had it. There is no audit trail of who used it for what, and changing it is a multi-week project because no one is sure where it has been written down.

The fix is structural. POS admin access should be per-user, with named manager accounts and a clean offboarding process when staff leave. Most modern POS platforms support this; the venue just has not configured it. Add MFA on the POS admin login wherever the platform supports it. Change the back-of-house Wi-Fi password every time a manager-tier staff member leaves, or move to certificate-based device authentication so passwords are not the trust anchor.

Trap Two: The Cousin Who Set It Up

The venue’s IT was set up by the owner’s cousin, who is good with computers, did it as a favour during the fit-out, and is now uncontactable on a Saturday night when the POS server has stopped responding. There is no documentation, the admin credentials are in the cousin’s head, and the network diagram is on a sticky note that came off the wall in the kitchen renovation.

The fix is engaging an MSP for the structural work and accepting that the cousin saved the venue some money during fit-out but is not a sustainable operational answer. The fit-out IT is about 5 to 10 percent of overall fit-out cost in most Melbourne venues. The ongoing IT is the part that determines whether Friday service runs smoothly for the next decade.

Trap Three: No Failover EFTPOS

The venue has one integrated EFTPOS terminal per POS. When the integrated terminal stops talking to the POS (due to a software bug, a network issue, or a bank-side problem), the venue has no way to take payments. Saturday night service becomes a queue of customers who cannot pay, walking out, or paying via tap-to-phone on the manager’s personal Square reader, which then creates reconciliation headaches.

The fix is having at least one non-integrated, non-network-connected terminal as a failover. A mobile EFTPOS that connects via 4G, not via the venue Wi-Fi. Test it monthly. Have a written procedure for the duty manager to switch to manual mode and reconcile at end of day. Cost: roughly $30 per month for a standby Tyro mobile terminal. Cost of not having it: half a Friday night’s revenue, easily $8,000 to $25,000 depending on the venue size.

Trap Four: Wi-Fi From the Modem the NBN Guy Left

The venue is running on the NBN-provided modem-router with its single Wi-Fi network, default admin password, no VLANs, and no QoS. Every device in the venue shares one collision domain. The POS, the EFTPOS, the kitchen printer, the music streaming, the manager laptop, the guest phones. When 60 patrons all join guest Wi-Fi at 8pm, the POS terminals start dropping payments.

The fix is replacing the NBN modem-router with a proper small-business gateway and access point setup. UniFi is the most common choice for SME hospo: a Cloud Gateway, one or two access points sized for the venue, and a managed switch if there are wired devices. Total hardware cost typically $3,000 to $5,500 for a single-site venue. The performance and reliability difference on Saturday night is immediate.

The After-Hours Support Cost: The Realistic Maths

Hospitality operates outside of business hours, and any IT support model that does not is dangerous. Here is the realistic maths on the three common after-hours support arrangements we see.

The honest economics: for any venue with three or more POS terminals and an integrated payments setup, the managed service maths beats break-fix the first time a Friday or Saturday incident occurs that gets resolved in 15 minutes instead of 90. The peace of mind for the venue owner is worth more than the dollar value.

TechAssist provides this for Melbourne hospitality clients out of our 24/7 NOC at Tecoma. We have 13 Australian engineers and operate two offices (Tecoma and 575 Bourke St CBD) which is the response window that actually matters for a 7pm POS incident at a Smith Street venue. Our pricing is per-user fixed monthly, so the venue knows what it costs.

A Real Melbourne Example: 110-Seat Venue in Carlton

A 110-seat Italian restaurant in Carlton engaged us in mid-2024 after the third Friday-night POS outage in six months. The previous IT person was a friend of the head chef, was reachable about 30 percent of the time outside business hours, and had set up the venue with a flat network running on the NBN-provided modem.

The discovery surfaced the typical issues. One Wi-Fi network for everything. POS admin password was “Carlton2018” and known to every current and former manager. Integrated EFTPOS on the same network as guest Wi-Fi. CCTV DVR with the manufacturer’s default password and footage retained indefinitely. Staff records on the kitchen office PC, which had not been backed up since the bookkeeper changed in 2021.

The remediation took three weeks of evenings and one full Sunday installation. We deployed a UniFi stack with three VLANs (corporate, customer, AV/IoT), moved staff records to Tanda, rebuilt POS user accounts with named manager logins and MFA, added a 4G failover EFTPOS terminal, replaced the CCTV system with a network camera setup behind authentication, and put the venue on our managed service with 24/7 NOC monitoring.

Project cost: $14,800 one-off plus per-user fixed monthly managed service. Saturday-night incidents in the eighteen months since: two, both resolved remotely in under 25 minutes. Friday-night POS outages: zero. The owner has the maths in the venue’s annual review pack and brings it up at every fit-out conversation he has with other operators.

The Fit-Out Decision: Get It Right Before Service Day One

The single highest-leverage moment in venue IT is during fit-out, when the cabling, the network gear, the POS, the EFTPOS, and the CCTV are being installed at the same time. Decisions made (or not made) during this window are baked in for the next three to five years.

The fit-out checklist that we recommend for any new Melbourne venue:

Cat6A cabling to every POS terminal location, every CCTV camera location, every wireless access point location, the office, and the bar. Wi-Fi is the operational backbone but POS terminals on hard-wired connections are dramatically more reliable than Wi-Fi-only terminals. The cost of running an extra few cables during fit-out is trivial. The cost of running them after fit-out is enormous.

Two power points at every POS location, on different circuits where possible. POS failures during service are often power failures, not software failures, and dual circuits buy you resilience.

A dedicated comms cabinet with cooling, in a location that is not the kitchen and not the cellar. We see comms cabinets in walk-in cool rooms (humidity kills gear) and over the stove (heat kills gear). A small wall-mount cabinet in the office is fine.

A proper small-business gateway and managed switch, not the NBN modem-router. Specify this in the fit-out scope so it gets installed by the network installer alongside the other gear, not bolted on three months later.

CCTV running over IP through the same managed switch infrastructure, not on a parallel coax system. The cost difference is small, the maintainability difference is large.

4G backup for the gateway. A USB 4G dongle attached to the gateway is enough. When the NBN goes down (and it will), the POS and EFTPOS keep working on the 4G backup until the NBN comes back.

For multi-site operators, talk to us about managed IT services Melbourne as a programme rather than a per-venue arrangement. The economics improve significantly once you have three or more venues in the portfolio. For venue owners who want an internal manager handling the day-to-day and our team covering the structural and after-hours work, our co-managed IT support model works well.

What This Costs for a New Melbourne Venue

A realistic IT budget for a new Melbourne hospo fit-out, separated into capital and operational.

Total capital IT investment for an 80-seat venue: typically $30,000 to $48,000 including cabling and CCTV. Total operational IT cost: typically $1,200 to $2,800 per month before payments fees. These numbers scale roughly linearly with seat count up to about 200 seats, where the economics start to shift slightly in favour of larger systems.

Frequently Asked Questions

Can we just use Square for everything?

For a cafe or casual dining venue under about $1.5m revenue, yes, and it is a sensible choice. For mid-tier and higher venues, Square POS becomes constraining once you need deeper reservations integration, multi-venue reporting, or complex table management. The economics shift around the $1.5m revenue mark.

How important is 4G failover really?

Very, and the cost is negligible. About $30 to $60 per month for a 4G data plan that sits on the gateway as a backup path. When NBN goes down during peak service (and it does, every venue eventually), the POS and EFTPOS continue working on the 4G fallback for the 90 minutes or so it takes for NBN to recover. The first time it saves a Saturday night, it has paid for years.

Do we need PCI compliance?

If you process card payments through an integrated POS, you have PCI obligations, but most modern integrated payments setups (Tyro, Mx51, Square) push most of the technical compliance burden onto the payments provider through tokenisation and point-to-point encryption. The venue’s obligations are operational: not storing card data, controlling who has access to the POS, and following the payment provider’s compliance attestation process. A managed IT provider should handle the attestation work as part of the relationship.

What about CCTV in the kitchen?

Kitchen CCTV is legal under Victorian law with appropriate signage and a documented purpose (usually safety and incident review). The Fair Work and privacy obligations apply: staff should be aware, the footage retention should be defined, and access should be controlled. We recommend kitchen CCTV for venues that handle insurance claims involving slips, burns, or workplace incidents, because the footage is often determinative.

How do we handle staff using the office PC for personal browsing?

Either accept it and treat the office PC as a low-trust device (cloud HR system, cloud accounting, no sensitive data on the local drive), or lock it down and provide a separate staff break area device. The middle ground (a shared office PC with sensitive data on it) is the worst option because it eventually leaks data either deliberately or accidentally.

How do we find a hospitality-experienced IT provider?

Ask the question directly. How many Melbourne hospo clients do they support? What is their response time for a Friday 8pm POS incident? Have they integrated each of the major POS platforms? Do they understand the fit-out window? Most general MSPs do not have hospo experience and will treat your venue like an office, which is the wrong mental model. Reach our team via the contact page and we will arrange a venue walk-through. For broader provider selection, our how to choose an MSP Melbourne and top managed service providers Melbourne guides cover the framework.

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. We have onboarded several Melbourne cafes on Square and the failure mode is almost always related to 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. For a Port Melbourne wine bar we look after, this paid for itself in the first month when a transformer fault took out their street for forty minutes during dinner service.

None of these failover strategies are expensive. All of them are absent in most independent retail stores we audit. 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. We rebuilt the network for a Box Hill bakery chain across four stores in early 2025 and the audit found that three of the four had customer Wi-Fi and EFTPOS on the same flat network. The remediation took two weeks and removed 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. The sub-15-minute P1 response that applies during normal business hours extends to trading hours for retail, which is a real commitment backed by the 24/7 NOC in Tecoma rostering for it. 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 been supporting independent Melbourne retailers since 2014 and 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 Australian-employed engineers work across both our Tecoma headquarters and 575 Bourke Street CBD office, which is convenient for CBD retail clients in particular. The 24/7 NOC in Tecoma covers the trading-hours support need. Sub-15-minute P1 response applies to POS-down and EFTPOS-down incidents. 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, with concentrations in Richmond, South Yarra, Hawthorn, Cremorne and the CBD itself. 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 time as a weekday — sub-15 minutes to 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.

If you need an engineer physically standing in your server room or next to a user’s desk, the honest answer depends on which suburb you’re in. For most of Melbourne metro we’ll be on-site same business day, and for inner-CBD and inner-east clients we’re usually there within two hours of a P1 call.

This post lays out the actual numbers — suburb by suburb — rather than the usual “we cover all of Melbourne” line that every MSP website carries.

Why suburb-level honesty matters

Every Melbourne MSP claims metro coverage. Most of them operate from a single office, usually somewhere in the inner east or the CBD fringe. That’s fine if you’re in Richmond or South Yarra. It’s a problem if your warehouse is in Dandenong South, your shopfront is in Werribee, and your head office is in Hawthorn — because the same engineer can’t realistically reach all three in a day from a single base.

For on-site IT support Melbourne wide, response time is a function of three things: where your engineer starts the day, how Melbourne’s traffic behaves at the time you call, and how many other tickets are already in the queue ahead of you. The first one is the only variable an MSP actually controls, and it’s the one that gets glossed over in sales conversations.

TechAssist runs two offices on purpose. Our main workshop is in Tecoma in the Dandenong Ranges foothills, which puts us inside the east and outer-east catchment. Our second office is at 575 Bourke Street in the CBD, which covers the city, inner north, inner west and bayside. With 13 Australian-based engineers split across the two, we can actually answer the question “how fast can you get to my suburb?” with a real number instead of a marketing platitude.

The two-office model, briefly

We’ve written about the reasoning behind inner Melbourne versus outer-east MSP office location in a separate post — that one is about the strategic call. This one is about the operational consequence: where each office gets to first, and how the two catchments overlap.

Quick summary of the geography:

• Tecoma office — sits on the Burwood Highway / Belgrave train line corridor. Natural catchment runs from Box Hill out through Ringwood, Croydon, Lilydale, Mooroolbark, Mount Evelyn, Wonga Park, the Dandenongs themselves and the Yarra Valley. Also covers the south-east through Glen Waverley, Mulgrave and Dandenong with reasonable times.
• 575 Bourke Street office — sits in the legal/finance precinct of the CBD. Natural catchment runs through the CBD itself, Docklands, Southbank, South Melbourne, Port Melbourne, then inner north (Carlton, Brunswick, Northcote), inner west (Footscray, Yarraville, Williamstown), inner east (Richmond, Hawthorn, Camberwell) and bayside (St Kilda, Brighton, Sandringham).

The two catchments overlap heavily through the inner east — Camberwell, Hawthorn and Kew can be served quickly from either office depending on traffic and who’s free. That overlap is deliberate. It’s also where most of our managed services clients are concentrated, so it tends to be the busiest patch.

Response-time table by suburb cluster

The table below shows realistic same-business-day arrival times for a P1 (production-down) ticket logged before 3pm on a normal weekday. Times assume the closer office has an engineer available — which is the case roughly 90% of the time given the team size. P2 and P3 tickets follow the same routing but are scheduled rather than rushed.

A few things worth calling out:

• P1 response is sub-15 minutes — that’s the time to a human engineer on the phone or remote session, not the on-site arrival. The table above is specifically about feet-on-the-ground times once we’ve established remote work won’t fix it.
• About 70% of what gets logged as “needs on-site” turns out to be solvable remotely once an engineer actually looks at it. The on-site numbers above are for the genuine remainder.
• Traffic in Melbourne is what it is. Burnley Tunnel between 7:30am and 9am, Monash between 4pm and 6:30pm, Westgate basically any peak — these can push the headline numbers out by 30 to 45 minutes. We dispatch from whichever office has the better run at the time.

A concrete example: multi-site retailer

Last year a homewares retailer with six shops came to us after their previous MSP — a single-office shop based in Mount Waverley — kept missing on-site SLAs on the western stores. Their footprint:

• Head office and warehouse in Box Hill
• Flagship in the CBD (Bourke St Mall)
• Shopfronts in Doncaster, Chadstone, Highpoint (Maribyrnong) and Werribee Plaza

The previous arrangement had every on-site call dispatched from Mount Waverley. Box Hill, Doncaster and Chadstone were fine. The CBD store got served eventually. Highpoint and Werribee routinely waited four to six hours, because the same engineer had to clear the eastern tickets first and then drive across town in afternoon traffic.

We took it on under a split-routing model: Box Hill, Doncaster and Chadstone get served from Tecoma. The CBD, Highpoint and Werribee get served from 575 Bourke Street. The Werribee store, which used to be a six-hour wait, now sees an engineer inside two and a half hours. Highpoint is usually under 90 minutes. None of it required us to hire extra staff — just to dispatch from the office that was actually closer.

This is the kind of thing that doesn’t show up in a tender response, but it matters a lot once you’re three months into a contract and your Werribee store manager is calling head office for the fourth time that week.

Where we’re slower — and why we’ll tell you

There are parts of Melbourne metro where we are not the fastest option. We’d rather be upfront about it:

• Frankston / Mornington Peninsula — we cover this for existing clients who have a head office inside our normal catchment and a satellite site down south. We don’t take on standalone Frankston-only clients because we can’t promise sub-three-hour on-site, and there are good local MSPs who can.
• Outer north (Craigieburn, Mickleham, Wollert) — covered, but expect two to three hours on-site rather than 90 minutes. Same applies to Sunbury and Diggers Rest.
• Geelong and the Bellarine — not in scope. We have clients with Geelong branches that we service via remote-first plus pre-booked monthly site visits, but it’s not a P1-response area for us.
• Bendigo, Ballarat, Latrobe Valley — same as Geelong. Project work and managed services yes, urgent on-site response no.

That’s a list of about a dozen postcodes out of the hundreds we cover. The vast majority of Melbourne metro — and certainly the postcodes where most SMEs sit — falls inside the same-business-day window.

What “same business day on-site” actually requires

The reason most MSPs can’t honestly commit to same-business-day on-site across all of Melbourne metro comes down to maths, not effort. To consistently hit it you need:

1. Enough engineers — if you have three field techs covering 200 clients across 50 suburbs, you’re going to miss. We run 13 engineers (most of whom do both remote and on-site work) split between the two offices, which keeps the load per engineer reasonable.
2. Geographic spread of those engineers — one engineer who lives in Berwick, another in Footscray, another in Eltham, and so on. We deliberately hire across the metro rather than concentrating in one area, because home-base proximity matters for early-morning P1s.
3. A dispatch process that actually looks at the map — not “next available” but “next available who’s closest to the site”. This sounds obvious but plenty of helpdesks still dispatch on availability alone.
4. Two physical bases — so that morning starts and stockpiled spares don’t all originate from the same postcode.

We’ve had the two-office model in place since the Bourke Street office opened. Before that we were Tecoma-only, founded in 2014, and we genuinely couldn’t make the same response promises for the western suburbs that we make now.

How the dispatch decision actually gets made

When a P1 ticket comes in, the dispatcher looks at three things in order:

1. Postcode of the site (which office is geographically closer)
2. Current location of available engineers (one of them may already be near the site for another job)
3. Time of day (a 4pm Westgate Bridge run from the CBD to Werribee is worse than a 4pm Tecoma-to-Glen Waverley run, even though the latter is technically further)

It’s not complicated, but it does require the dispatcher to know Melbourne. Our service desk team is all based in Australia — that’s not an idle boast, it’s a functional requirement, because someone in Manila isn’t going to know that the Burnley Tunnel just shut and the Eastern is the better call.

Where this fits with remote support

This post is about on-site response specifically. The broader question of when on-site is the right answer at all is covered in our piece on remote IT helpdesk versus on-site support — short version: most issues should and do get fixed remotely, and the value of on-site is that it’s there for the issues that genuinely need hands-on work.

What’s worth saying here is that fast on-site coverage doesn’t make remote support less important. The two work together. A good MSP triages remotely, fixes what it can remotely, and dispatches an engineer only when a remote fix isn’t viable. The on-site response time matters precisely because by the time we’re driving to your office, we’ve already established the issue can’t be resolved any other way.

What we cover in each direction

If you want a more detailed look at how we handle the eastern suburbs in particular — which is where the bulk of our outer-metro client base sits — we’ve written that up separately under IT support eastern suburbs. The general overview of our delivery model is under on-site technical support and the broader managed services context is under managed IT services Melbourne.

For the office locations themselves: Melbourne (575 Bourke Street) office, Tecoma office, and the full list of locations with maps and hours.

FAQ

Do you cover regional Victoria?

For existing managed services clients with regional branches — Bendigo, Ballarat, Geelong, Albury, Shepparton — yes, on a planned-visit basis combined with remote-first daily support. For standalone regional businesses where the head office and the only site is regional, we generally won’t be the best fit, because we can’t promise same-day on-site at the prices that work in those markets. Happy to refer you to MSPs we trust in those areas.

What about the Mornington Peninsula?

Covered on a planned basis for clients whose primary site is within our normal metro catchment. Mount Eliza and Mornington itself we can usually reach in around 90 minutes from 575 Bourke Street; Rosebud and the southern peninsula will be closer to two hours. We don’t actively target Peninsula-only businesses because the response times don’t compare favourably with local MSPs based in Frankston or Mornington.

Do you offer after-hours on-site?

Yes, for clients on a managed services agreement that includes after-hours coverage. The on-site response window outside business hours is longer — typically two to four hours rather than the daytime targets above — because we’re calling out an on-call engineer rather than dispatching from a staffed office. P1 phone and remote support is 24/7 for all managed services clients.

What’s the difference in response time between a P1 and a P2?

P1 means production is down — a server has fallen over, the internet is out, no one can log in, an attack is in progress. P1 phone response is under 15 minutes, on-site is per the table above. P2 means a meaningful problem but the business is still running — one user can’t print, a non-critical system is slow, a backup didn’t run. P2 on-site is same business day but scheduled around other work rather than rushed.

Can I get a faster response by paying for a premium SLA?

The targets above are what we deliver under standard managed services agreements. For clients with unusually high uptime requirements — typically those with revenue tied directly to a single point of failure — we’ll sometimes agree custom SLAs that include on-site standby arrangements. Those are uncommon and we’ll only quote them honestly when we can actually deliver, which usually means the client’s site is close to one of our two offices.

A reasonable next step

If you want to know specifically what we can promise for your suburb — or your collection of suburbs across head office and branches — the easiest thing is to send through the postcodes. We’ll come back with the realistic on-site numbers from each of our two offices and tell you straight if we’re not the right fit. Reach us via the contact page or call 1300 028 324. We’re also listed under our main IT support Melbourne page for general enquiries.

The fundamental question — “how fast can you actually be here?” — deserves a specific answer, not a vague metro-coverage claim. The table above is ours.