As staff you can order drinks or meals for your customers via an easy-to-use table-side and in-resident-room order flow.
Use the shortcut [Add a request] in the Dining cube or go via the back office flow to Dining>Request. Click on ' Add a request'.
Are you working on a tablet? Click the icon in the right corner on top to enlarge to full-screen mode, hiding the Cubigo menu and side panels.
First, select the customer (via name or apartment number) in the list for whom you want to order drinks. In case you want to order for an occasional visitor (who has no Cubigo account yet), please select an anonymous visitor account you created for this kind of order.
You can also select team members from the list.
The date picker is the default setting for today. You can also place orders for future days. Use the arrows right/left or click the exact date in the calendar.
If your community supports multiple locations, then you need to select the location before proceeding with the order.
Choose the right timeslot for when this order is asked. You can choose between Breakfast, Lunch and Dinner. This selection is kept for the next order. This information is collected in the order detail is available in the grid via Dining items. You can't combine multiple timeslots in one order, this has to be registered per timeslot.
Next, you click on the appropriate meal category. We offer meal categories that are available in your community. Within a category, you see the meal items that are offered. Tab on a tile to select a meal for this order. You can combine several meal categories within one order. You cannot combine meals for different time slots within one order. In this case, you first finish a one-time slot order before you continue for another time slot.
You can also add accompaniments for the meal items by checking the boxes:
To remove the item or accompaniment, use the 'trach can' or 'pencil' icons.
The meal or drinks you selected are put into the shopping cart. Here you can adjust the volume per item. Click on the trash icon to remove an item from the shopping cart.
Do you want to add a comment to this order? Click on the posted icon next to each meal item in the shopping cart. Here you can add a comment or special request that relates to this item.
The shopping cart shows the details per item (price and volume) and the total amount with corresponding payment status.
The payment option is configurable for your community. Choose the right payment option for this order. This information is kept in the order detail and available in the dining order grid. Use this filter in this grid to generate a .xlsx file on unpaid items per month/week or resident.
The handling options are configurable for your community. Choose the right handling option for this order. In case a service fee is valid for delivery, this amount will be added to the final order price. You can manage this fee via the Dining item creation.
Choose the right order status according to the process that has to be handled for this order. An order for drinks in the bar can be fulfilled in the 'Confirmed' status as drinks will be offered immediately. An order for meals to be delivered needs the status 'Requested'. You can change this status via the button. The default state here is ‘requested’.
Save and exit
Click this blue button if you want to leave this order flow and return to the back office. The current checkout is closed. You are guided to the Dining grid to see the result of this order.
Save and next day
If you register multiple meal orders for the same resident for a series of days in a row (doing it once in a week for the whole week), you can select this option. If a request is saved with ‘save & next day’, all settings in the form are kept (user, menu slot, payment, handling), but the date is automatically set to the next day. The item selection is cleared.
Save and new order
Click this green button if you want to stay in this order flow. The current checkout is closed. You can start entering a new order by selecting the customer, timeslot and items in a category. All settings as a payment option, timeslot, handling, etc are remembered in the request form. The user is not kept! So if I am dining staff that mostly works in a POS setup, I only have to select ‘restaurant’ once as handling option, and request status ‘completed’ once as default.