QR Code – Create an Order at Table System

How Can We Help?
< Back
You are here:


They are everywhere !

Plastic discs stuck all to an already undersized table.

If you are not careful you end up spilling your drinks over everybody.

Wouldn’t a QR Code that is FLAT be so much nicer ?

With OscarPOS Cloud you have options :

  • Scan to download the customer Mobile App
  • Scan to go to website where you can select service type and table number
  • Scan to go straight to the menu, where table number is already chosen

The first two are already covered in earlier articles.

The third we will look at i a bit more detail.


These will vary depending on your existing setup.

At bare minimum, you will need logically created ITEMS with images and descriptions, a correctly configured eSHOP that reflects your business, service type hours & a floorplan. Optionally create Time Slots to provide your customer with a realistic “make time”.

To take online payments, you will need an active gateway – which will have its own requirements ( such as Online Polices & SSL ) before it is enabled. Once enabled, it will need to be added to your STORE.

Please contact us with your needs and we will make sure everything required is available.

Data Type

We are linking to the eSHOP, which we can do using the type called URL.

However, we need to include a lot of other data for :

  • eSHOP
  • Tenant
  • Store
  • Table

Please reach out to us for the correct URL structure to use.

Create the QR Codes



Each Table will have its own QR Code.

Test the QR Codes

Yep – Always test before incurring any expenses.

Print & Distribute the QR Codes

How you do this is personal taste.

  • Printed on labels and laminated
  • Printed on sticky vinyl
  • On the table surface
  • On the table talker

Whichever you prefer, your customers can now scan the QR CODE, confirm their phone number ( if it is a new customer ), select their ITEMS and pay for them according to your preference/s.

Previous OscarPOS Cloud and QR Codes
Next QR Code – Direct Link to a URL
Table of Contents

About the author: Tim Atkinson