This sheet is for shop owners, café and restaurant operators, venue managers and hospitality groups. The day opens and closes on the point of sale — Square, Lightspeed or Shopify at the counter, Deputy for the roster, ResDiary or OpenTable for the book, Xero for the takings — and what sits between them is typed by hand. Ozwebnet builds websites, web applications, online stores, data platforms and integrations around what you keep: from scratch in Adelaide, for businesses across Australia, source code and IP assigned to you, one fixed quote.
Most run a point of sale first and everything else around it. Square, Lightspeed or Shopify take the sales; Deputy writes the roster; ResDiary or OpenTable holds the bookings; a delivery app or two brings in orders; Xero or MYOB keeps the books. Each does its own job well. The gaps sit between them: stock counted in one place and sold in another, takings re-keyed into the ledger, and the weekly numbers for several sites assembled in a spreadsheet.
Point of sale and card payments for shops, cafés and restaurants: an item library, tables and modifiers, basic stock counts, and a simple online ordering page. What it typically does not do is run a website written to your design, hold stock down to the recipe or the supplier order, or feed one report that also reads from your roster, your bookings and your ledger.
Point of sale for hospitality venues and retailers, with menus, floor plans, stock, supplier orders and reporting inside the product, across one site or several. Where it stops: a website or ordering front end of your own design, and a report that puts its sales beside the wages, bookings and takings held in other systems.
The online store and, with Shopify POS, the counter as well, so one catalogue sells in-store and online. Its themes and checkout decide the shape of the store; a front end built to your own design, and a stock model shared with a point of sale or a warehouse system it does not connect to, are custom work.
Rostering, timesheets and pay-rate rules for the floor and the kitchen, with shifts sent to staff phones and hours passed to payroll. It knows the roster and not the takings, so wage cost against sales, per site and per shift, is a spreadsheet unless something joins the two.
Table bookings, waitlists, deposits and the floor plan for restaurants and venues, with a booking widget you drop into a website. They hold the book and the guest list within their own product; joining that to your point of sale, your marketing list or your function enquiries is integration work.
Delivery and pickup orders from each app's own customers, each arriving on that app's device or feed. Bringing every order onto one screen and into one stock count, and keeping one menu that updates every channel at once, is what a build or an integration adds.
The books: sales, purchases, payroll and BAS, with bank feeds that match the card settlements. They record what the counter sold once someone posts it, and the daily takings summary, split by site and by tender, is the entry most venues still make by hand.
Takings, wages, bookings and stock, copied out of the products above into one workbook each week so an owner can see the sites side by side. It is where the numbers finally meet, and it is the part a data platform replaces.
PRODUCT NAMES BELONG TO THEIR OWNERS. WE CONNECT TO WHAT YOU KEEP; WE DO NOT RESELL ANY OF THEM.
A website for a shop, a venue or a group of them: menus, hours and specials that staff edit themselves, the booking widget in the page rather than a link away, a function enquiry form that lands somewhere useful, and a page per location with its own hours, menu and map.
MULTI-LOCATION WEBSITES →Internal tools for the back of house: stocktakes and supplier orders done on a phone in the cool room, function bookings with deposits and run sheets, opening and closing checklists with sign-offs, and a head-office screen where a group sees every site's day.
INTERNAL TOOLS →An online store or ordering page that sells what the counter sells: click-and-collect, delivery windows, gift cards and pickup orders from one menu that updates every channel at once, with stock and orders passing to the point of sale you already run.
THE ONLINE STORE SHEET →One place the takings, the roster, the bookings and the stock agree: sales by site and by hour, wage cost against takings, covers booked against covers served, and what sold against what was bought, read from Square, Lightspeed, Deputy and Xero and sent to the owner each morning.
DASHBOARDS AND REPORTING →The point of sale posting its daily takings to Xero or MYOB by site and by tender, delivery-app orders arriving in the point of sale instead of on a tablet, bookings and loyalty sharing one customer record, and stock moving between the store, the online shop and the supplier order without re-keying.
XERO AND MYOB INTEGRATION →Not sure which? Ten minutes on 1300 699 321 tells you — Mon–Fri 9–5 ACST.
Corrigan Ridge Estate is a concept build for a winery and cellar door: the estate, the wines with a note each, the cellar door and the terrace as an experience, a club described by what it includes, and a visit section that gets people up the road. Designed and coded from scratch in its own design system, the way a site for your venue would be.
Corrigan Ridge Estate is a fictional business. The page is a concept build, designed and coded by Ozwebnet to show the work — not a client project.
OPEN THE SPECIMEN →
One fixed quote, set in writing before the build and staged against milestones. The scope that sets it — the website, the ordering page, the reports, the connections to your point of sale and your books — is agreed at the specification stage, and you can stop at any milestone and keep a working system.
No. Most builds connect to the point of sale you keep, so a sale rung up once at the counter reaches the website, the online store, the reports and the books without being typed again.
You do. The source code is delivered at handover and the IP is assigned to you, so the system stays yours whichever point of sale, roster or booking product you run beside it.
Yes. A group is one build: a website with a page per site, reports with a line per site, and a connection to the point of sale at each, under one fixed quote staged against milestones.
Yes, Australia-wide. Adelaide first, remote-capable: discovery and every milestone review can run over a call, and the system is tested against the point of sale and the devices your staff actually use.
Call, or answer a few short questions — what you run, what breaks, when you need it working — and we reply within one business day. The quote is fixed in writing before any build starts.
