Kiosk Menu Builds

Kiosk menu builds are often more complex and time consuming than you might at first expect. QikServe can’t start the build process until we have clean and clear instructions - please read the below thoroughly and make sure all points are covered off before sending us a menu to build.

After a menu is built, the menu review process will often bring up changes that QikServe needs to make - a lengthy review due to poor initial menu quality has the potential to put your launch date at risk.

Fundamentals for a kiosk menu

• Structure: outline the structure with Categories and Sub-Categories as you believe works best for a kiosk customer journey. The structure might be different to how it is on the POS - e.g. Perhaps you want to show a Best Seller category?

• Enrichment: menu data that comes from the POS isn’t likely to be ready for an enticing customer facing menu. Add customer facing item names, a full product description (including allergen info), and calories. Often we see spelling mistakes or inconsistencies in format which negatively impact customer experience

• Branding: a kiosk is a visual experience and in order to entice customers and increase average transaction value you need good imagery. Every category and item needs a good image and therefore Marketing teams should likely be included early in your menu build process

Branding/Imagery

Please have all files named according to the category or item that they refer to. http://Wetransfer.com can be helpful for large file shares.

Category and item imagery specs:

• 500x500 px

• max 200 kb

• png/jpg file type

• if you’re building a mobile ordering menu, the item specs are 590x393 px and category specs are 830x260 px

Teams involved

Please ensure your menu has been signed off by any team that would be included in a review. This will greatly speed up the menu review process once QikServe builds what we have been given. This includes Restaurant Managers, Operations, and Marketing.

As item imagery and branding is key - engage the appropriate department early so they can gather the assets needed.

Menu build - essential checklist

A menu cannot be passed to the QikServe Implementation team to build until it meets the following criteria:

• a structure

• relationship shown between items and option groups

• consistent and accurate formatting of customer-facing verbiage

• imagery for every category and item

• clearly defined availability restrictions if required

• a category

• a PLU/Item ID

• a customer facing name

• a description

• a price

• an image

• listed option groups with full information if applicable

• a combo meal ID

• a main item group + PLU(s)

• a side group + PLU(s)

Sending menus and assets to QikServe

Providing new menus

Menus should come to us in Excel format and fully enriched ready for QikServe to start work. Colour coding the modifier/option/condiment groups if they are available for more than 1 item is very helpful and assists us in understanding the structure. Please include a version number or the date in the name of the menu map file.
See an example Menu Map:

Open

Providing price updates

If you have previously provided a menu map to us and the items are staying the same but the price is increasing, you can reuse this spreadsheet and highlight items that have new pricing.

Updates to menus

Send any small menu changes to Support@QikServe.com, making sure to include all details for new items including imagery. Always include the date that you need the changes by and allow 3 working days minimum for menu changes.

Testing and Reviews

Any new items will need to be reviewed and tested on the kiosk. This will likely include your IT team, Ops and perhaps the Restaurant team. The idea is to make sure items add successfully to basket.

A LAB POS is preferred for this but we can take 1 kiosk from a live store and use it for testing, however the new items need to be made available on the POS.

If there are changes that need to be made after a review, please group them, rather than drip feeding them, along with all assets needed. Please allow time and resource for the testing and review period before going live.