Retail IT support in Melbourne should cover three things for a multi-site operator: the hours your tills are open, the scope at each individual site, and the boundary between your provider and every vendor who touches a store. The hours are the easy part, and they are published already. inSUPPORT lists a Retail support tier at $100 per user per month: the office week, then through to 9:00pm on Thursday and Friday, with Saturday morning until noon. The other two you write down yourself.
If you run more than one store, you have had the hours conversation already. You asked, somebody said they could be flexible, and the agreement came back with an office week in it. Nobody put a list in front of you of what is actually covered at store four on a Thursday night.
The reality is that managed IT is priced per user, and retail runs on shared things. A till is not a person. A back-office machine three people sign into belongs to the shift rather than to any one of them, and the stockroom scanner belongs to nobody at all. Cover written for a head office counts your people. Your exposure sits in the things they share.
So treat this as a working brief. Everything below is a question you can put to whoever is quoting, in words that will survive being written into an agreement rather than said across a table. Take it into the meeting.
What to settle before you sign
- ✅ Hours get published. Scope does not. Ask for a per-site list of what is covered, store by store, before anything is signed.
- ✅ A till, a kiosk and a stockroom scanner have no named user. Ask how shared devices are counted, and how they are cleared between shifts.
- ✅ Every store still running its own point-of-sale or stock vendor is an exception, and exceptions are where the next incident starts.
- ✅ $100 per user per month is the support component. Backup, cyber insurance and security-awareness education are quoted as their own line items.
Contents
- Write the Coverage Down Store by Store
- One Stack Across the Stores, or an Exception Per Store
- What Sits Inside the Fee, and What to Ask For
- Multi-site questions worth asking out loud
Write the Coverage Down Store by Store
Start with a sheet per site rather than a sheet per company. For each store, list the systems that take money: the point of sale, the card terminals, the network link that reaches pricing, and the back-office machine somebody uses to reconcile the day. Then write down who at that store would notice a fault first, and what they are allowed to do about it. A head-office list tells you none of that. This is the point at which retail IT support in Melbourne stops being a price comparison. It becomes a specification.
Write down where your job stops and your provider's starts, which systems each of you can get into, and by what route. Then keep that list current as stores open and systems change. The Australian Signals Directorate (ASD) tells buyers of managed services to do exactly that. For a single office it is one paragraph. For a store network it is one paragraph per site, and the one you skip is the shop with the forgotten switch in the back room.
Shared devices are where a per-user model meets a shop floor. Microsoft has a way to handle this, and it calls it shared device mode: on a phone or a tablet, one person signs in, works, then signs out, and the company data goes with them so the next person starts clean. Two limits before you lean on it. It covers Apple and Android handhelds only, so it does not reach a Windows till or a Windows back-office machine at all. And it holds only in the apps built for it. The services page does list packages for shop-floor staff: the devices themselves, the system that manages them, and the accounts behind them. How a shared till or scanner is counted on your quote is still the ask.
- Build one coverage sheet per site, naming the systems that take money and the person on the floor who would see the fault first.
- Ask which devices without a named user are in scope, and how a till, a kiosk and a stockroom scanner are each counted on the quote.
- Get the access boundary in writing for every location: which systems the provider can reach, by what route, and who keeps that record current.
One Stack Across the Stores, or an Exception Per Store
Multi-site retail drifts, and it drifts quietly. A store opens, the fit-out contractor installs a terminal, somebody local arranges the broadband, and three years later you run two stock systems and four versions of the same point of sale. Each one arrived with a vendor attached, and each of those vendors keeps the support hours its own agreement sets rather than the ones your trading calendar needs. Nobody chose that. It accumulated.
So the hours question has a second half. When the terminal at store six stops talking to the back office, somebody has to work out whether that is the network, the application or the payment provider, then ring the right one. Somebody has to, and fast. The pricing matrix lists vendor management as one of its rows. It is a single list of inclusions, not split by band. In plain terms, your provider is the one who deals with the software companies, keeps the licences straight and chases the people who built your point of sale. That is what vendor management buys you: the triage call stops being yours to make. Confirm it sits in the band you are quoted. Then ask who makes that call, and what they are allowed to change at seven in the evening.
Standardising is the uncomfortable half, and it is worth being straight about why. Every exception is one more arrangement somebody has to remember at seven on a Thursday night. Expect push-back from the store that wants to keep its own. Outsourcing moves the work, not the obligation. The Office of the Australian Information Commissioner is explicit on this. Hand your customer data to somebody else to store, and if you can still get at it and change it, the Commissioner's guidance says you still hold it. The customer records on store six's system are yours wherever they sit.
- List every point-of-sale, stock and payment vendor by site, with the support hours each of them actually keeps.
- Name the single party who triages a fault across that chain, and get the authority they hold written into the agreement.
- Decide which store-level exceptions you are keeping on purpose, and have somebody sign off each one in writing.
What Sits Inside the Fee, and What to Ask For
The fee has a published shape and an unpublished one. Published: support is priced per user per month, the Retail band at $100, the office week at $68 and round-the-clock cover at $135. The remediation an onboarding audit finds sits inside that support fee rather than arriving later as a separate project. Also published, and the line-by-line version is worth reading: backup, cyber insurance and security-awareness education are separate, clearly-quoted items. A monthly support fee is not the whole bill. Treating it as one makes your budgeting harder, not easier.
What is not published is the part a multi-site operator most needs. Which band gets you what, how fast somebody has to answer you at each one, and whether anybody comes back to a store once onboarding is done. None of that is on the price list. The pricing page does say onboarding includes a site visit to document how you operate. The services page describes the support as remote-first. For one office that is fine. Across a store network it is worth knowing in advance who comes out to a shop, and on what trigger. Put the onsite question in writing before you sign.
ASD's advice is to get security into the contract rather than the sales conversation. Ask a candidate provider for evidence of how it administers a customer network, and require notification clauses so you are told when an incident could reach you. Ask for the contact details of other customers you can speak with openly. ASD publishes a second list as well, five questions long, and the last one asks whether the provider is ready and able to respond when an incident happens. Run both lists past whoever is quoting you. What comes back in writing is the only part of the cover you can hold anyone to. The rest is conversation.
- Get the entitlement list for your own band in writing, not the general inclusions matrix that covers all three.
- Ask how fast somebody has to answer you at each band, and what happens when two sites go down in the same hour.
- Walk your own site list through with them: what the fee already covers, and what would come back later as a separate quote.
- Ask whether anyone attends a site after onboarding, and on what trigger.
Multi-site questions worth asking out loud
What should a multi-site retail IT support agreement actually cover?
Three layers. The hours, which should match the hours your tills are open rather than an office week. The scope at each site, written per store, naming the systems that take money and the devices nobody owns. And the vendor boundary, so one party triages a fault across the point of sale, the network and the payment provider. Retail IT support in Melbourne is sold on the first layer. It lives or dies on the other two. Ask for all three in writing before you compare prices.
Do we need a provider who knows retail, or will any Melbourne firm do?
Either a provider has built trading-hours cover into what it sells, or it has not, and the price list tells you which. Where a provider's own history is retail, the extended hours were designed in rather than bolted on later. That is the case inSUPPORT makes: the group it belongs to started as Retail Innovation Group Australasia, and the Thursday and Friday nights are on the published list for that reason. Its client wall carries retail names including Sheridan, BONDS, MUJI, T2 Tea Australia, Bras N Things and Champion. Read that honestly, though. A logo wall tells you who the customers are, not which support band each of them buys.
How long before every one of our stores is on the same controls?
Nobody can answer that from the outside. A provider who gives you a date before auditing your environment is guessing. What you can get upfront is the sequence. Ask which site goes first and why, what has to be true at a store before it counts as done, and how the work is staged around trading so a changeover misses your busiest afternoon. Then ask what the audit would have to find for the plan to slip. A named order with named dependencies is a real answer. A single number is not.
Where do we start if we have five stores and no documentation?
Start with the environment, not the contract. The contract conversation keeps stalling on facts nobody has. A Cyber Strength Audit documents what is actually configured across identity, patching, backup, email and endpoint, then ranks what it finds by what would hurt the business first. Take your per-site coverage sheet into it and you get both halves at once: what is running at each shop, and which of it nobody is contracted to look after. The remediation that audit identifies sits inside the support fee once you are on a plan.
Bring the list of stores. A Cyber Strength Audit documents what is configured across identity, patching, backup, email and endpoint. It names the settings that have drifted since anyone last looked, and ranks what it finds by business impact rather than technical severity. Where a store turns out to be running a system that sits outside everybody's agreement, you want to find that on a list rather than on a Thursday night with the tills queueing. You should finish the conversation able to say, for every site, what is covered and who answers.
Book a Cyber Strength Audit →Citations
- "How to manage your security when engaging a managed service provider, Australian Signals Directorate", ASD's guidance for organisations buying managed services. It says to know where the boundaries sit between you and your provider, to identify clearly which systems each provider can access and how, to keep that record up to date, to get cyber security expectations into the contract including incident notification clauses, and to provide least-privilege and attributable accounts. Published 21 December 2018, last reviewed 5 April 2023, read 16 November 2026. cyber.gov.au
- "Questions to ask managed service providers, Australian Signals Directorate", The five questions ASD recommends putting to a managed service provider, covering better-practice security, secure administration, monitoring, regular assessment, and whether the provider is prepared for and able to respond to cyber security incidents. Published 24 March 2017, last reviewed 24 March 2023, read 16 November 2026. cyber.gov.au
- "Guide to securing personal information, Office of the Australian Information Commissioner", States that an entity which outsources the storage of personal information to a third party, but keeps the right to deal with that information including to access and amend it, holds that information. Carries a notice that the page is being updated for the new APP 11.3, under which reasonable steps include technical and organisational measures and which applies to information held after 11 December 2024. Publication date 5 June 2018, read 16 November 2026. oaic.gov.au
- "Shared device mode overview, Microsoft identity platform, Microsoft Learn", Describes the Microsoft Entra ID feature for sharing one device among several employees, scoped to iOS, iPadOS and Android devices: one sign-in reaches every supported app, a single sign-out logs the person out of the device and all supported apps, and that assurance holds provided the apps clear any cached user data. Shows a last-updated date of 16 July 2025, read 16 November 2026. learn.microsoft.com
Related Reading
- Retail IT Support
- Managed IT Services
- IT Support Pricing
- Why Your IT Support Closes When Your Shop Is Busiest
- Cyber Strength Audit
About the author: Kane Nawrocki is the founder and CEO of inSUPPORT. He has spent more than 25 years in IT and built inSUPPORT to give Australian businesses managed IT, security and compliance as one model, with the remediation an audit finds included in the support fee rather than billed back as a surprise project.
Content reviewed by Probably Genius for accuracy and relevance.
inSUPPORT provides managed IT and cyber security services. It is not an insurer, insurance broker or underwriter and does not hold an Australian Financial Services Licence. Where cyber insurance forms part of a plan, it is arranged through licensed insurance partners and underwritten by the insurer. Cover is subject to the insurer's assessment, the policy terms and the Product Disclosure Statement and Target Market Determination. This article is general information about IT and security practice, not financial product advice, and it does not take account of your objectives, financial situation or needs.
CLICK HERE


