Information for an individual product in the warehouse includes: - product name; - quantity; - measure; - unit price; - total quantity value; - expiration date; - and date and time of registration. This makes it possible to store many batches with different expiration dates for one product. Product information (included from the Product's Store menu item on the home screen) is organized on two levels. The first level is product categories, for example, meat, vegetables, seafood, etc. And the second level is the products belonging to the given category. The activity - Product's Store serves to maintain the products in the warehouse and also: the list of product categories; - the list of objects (customers places) - these are the places in the restaurant with which the requested food orders are connected; - the list of measures such as: kg – kilograms, lt – liters; and the list of methods for preparing the products, for example "Boiling", "Baking at 180 degrees", etc.
From the menu of the activity - Product's Store, two functions are included: export and import of the supported lists. These functions are used if the staff delivering the products is working on their own mobile device and exports the information about the purchased products to a selected directory on the mobile device in a text file. After the export function is executed, a send image button appears (with an image of a paper swallow). This feature allows the processed list to be sent by email to the customer developing the restaurant menu, and he in turn imports it into the database on his mobile device. Export and import involves selecting a directory from the mobile device to export to and from where to import the data file. This activity also performs database export and import.
Products in the warehouse are tracked automatically (optionally) for the expiration date. Information on the quantities of expired products is sent to the archive once a day, and information on products with an unexpired date is also sent to the archive in parallel. This allows to include a function that shows statistics on the used quantities of products including in a graphical form, there is also a one-step forward estimated value calculated for used and unused products. Estimated values are made with a moving average of previous values with a step entered as an option. The archive can be deleted and, if necessary, start accumulating again.
The activity Restaurant's menu serves to maintain the restaurant menus. When creating a main folder, only its name is entered. When creating a new item - folder or restaurant menu item, its place in the hierarchy is first determined, this must be in a previously created folder - old folder. By pressing a button whether it is in front of an element of the old folder or only directly subordinate. A dialog appears to choose whether to create a folder or a menu item. When creating a folder, only its name is entered.
When creating a restaurant menu item (portion of food) it is more complicated. For the portion of food, the component products are selected one by one. As for the inclusion of a given composite product, its category is selected from a drop-down list, the product itself from a drop-down list of products for the category and the method of preparation from a drop-down list. For the product, the quantity is entered by looking at the measure for the product, which appears automatically and when focus is lost from the quantity field, the value of the composite product is automatically calculated in the price field. After pressing the Save line button, a line for the new ingredient appears in the ingredient list and the ingredient price is added to the total price of the menu item. By selecting an item from the ingredient list, its data can be deleted or corrected and saved again.
Two dates are selected for the menu item, the first when it is modified and the second by when this menu item should be available to customers. A date is selected from a calendar and when you click in the corresponding field, the date from the calendar is transferred to it.
An image for example .jpg or .txt with a description of the recipe for preparing the menu item or a photo of the food portion can be attached to the menu item from the file directory. In the hierarchy tree, the image appears before the menu item name and can be displayed for viewing by the client.
After all this, the menu item can be saved and returned to for updating.
The MenuAmountActivity serves to maintain the total amount of portions of cooked food - the number of restaurant menu items that can be offered to customers. When an order is fulfilled (served to customers) portions of food, this total quantity is reduced by the corresponding units. From this activity, a function can be performed to calculate the value of the cooked food for all menu items, by pressing the Show Bill button. Functions can also be performed: export and import of the total amount of cooked food with a similar purpose as described above. After importing the number of restaurant menu items, a function can be executed to see if they are provided with products - Show Products. Two options also appear - one is the required products and the other is the missing products. The thus prepared structure of the restaurant menus and the set quantities of the prepared portions can be sent to the waiters serving the customers by exporting the entire database; Expired product information can be archived automatically (optional).
.
The RequestActivity is designed to maintain requests for the amount of cooked food - the number of restaurant menu items connected and delivered to objects, creation of the account and export and import of requests. Each request is associated with an object selected from a drop-down list - described above.
Tables of possible menu items are also selected from a drop-down list formed by the main menu item folders - described above. In such a table, against the name of the menu item, the number of ordered menu items can be entered.
After the delivery of the portions of a given menu item, an indication of this is checked in the check box, the request is stored. And when this table is loaded again, in the request executed in this way, the menu item is colored red and setting the number is blocked. After saving such a gap in the completed requests through the menu item Save completed Request (Save completed request) of the activity and reloading the table, the corresponding menu items are unblocked and reset, with which a new request can be requested for them. With Save completed request, the following is done: - dialog asks if it is the beginning of the account, if to delete previous accounts for the object, if not the fulfilled request accumulates to an old account; - the number of the executed menu item goes to the account table; - deletes from the table of stored requests the number of executed menu item; - reduces the number of menu items prepared in the kitchen by the number of executed menu items.
The RequestActivity has a function to show the bill, it is executed with the Show bill button, the displayed bill can be saved with the Save button in a local .txt file on the mobile device and sent by e-mail .
From the menu of the initial activity, it is possible to optionally include whether to activate the possibility to archive expired products, and the same for the cooked menu item