# Managing the menu

[![image-1703105107104.png](https://docs.fasterorder.se/uploads/images/gallery/2023-12/scaled-1680-/image-1703105107104.png)](https://docs.fasterorder.se/uploads/images/gallery/2023-12/image-1703105107104.png)

[![image-1703105257249.png](https://docs.fasterorder.se/uploads/images/gallery/2023-12/scaled-1680-/image-1703105257249.png)](https://docs.fasterorder.se/uploads/images/gallery/2023-12/image-1703105257249.png)

At Faster Order we have following menu elements:

1. **Menus**: these create the headers in the menu and categorize items. For sample "Pizzas", "Starters", "Mains" are menus
2. **Menu Items:** these are the actual items that a customer orders. "Pancake", "Margerita", "Chicken Dumplings" are samples of menu items
3. **Extras:** extras can be extra toppings that you want to add to your pizza, or if you want a customer to in some way customize the menu item that they choose. If it's a hamburger meal it could be that they get to choose between fries and apple as a first choice, between a vegan burger or meat burger as a second choice and drink as a 3rd choice. Extras are just normal menu items. To configure the menus this is done in Faster Order's back office and can't be done via the API. Once you setup a group of different extras that can be setup for a menu item this is called an **add-on menu**.

The integration we have supports a 1 way sync, from your menu to ours and not vice versa.

<p class="callout info">First time you and a menu or a menu item you can set the name/description. These fields are not available in the update of an article. The reason is that the restaurant can setup a name and a description in Faster Order's backoffice that is more oriented to the end customer and we won't want synchronizations to overwrite this.</p>

### API endpoints

The POS API can be found here:

[https://pos-api.fasterorder.se/swagger/index.html](https://pos-api.fasterorder.se/swagger/index.html)