Ordering System Flowchart

Now I'll gonna teach you guys on how I planned to develop my Ordering System on my last post titled "Ordering System with Simple Database". Sorry, I know It should be posted with the project but I decided to post separately, to make its discussion separately to make it more understandable to others. On this flowchart represent a system with multiple menu's or buttons in just one form of a system. I also included the flowchart for the second form where will be then opened once you wanted to delete  a saved transaction in the database.

Ordering System Flowchart

 As what you see at the above flowchart there where words inside of each decision its "Sandwiches, Drink and Special" lets recall at the system itself of how it is been made. As you may see at the image below is the form or the actual ordering system having tabs, button and list boxes with it, try to get focus on the tabs name you'll read "Sandwiches, Drink and Special". But why? lets call it as categorizing in the flowchart same as in the system each of every tabs has different products to offer, that is why it is in decision because each customer has a right to choose whatever he likes. We used categorizing to easily navigate products in our form more specially if your having a lots of product list in your ordering system.

Ordering System Form

And as you may see even it is yes or no their is another rounds of decision in the "Ordering System Flowchart". You may think that is the foods in each category also a category theme self. The answer is no; why? Because you cannot consider it as also a category even its on decision. because every customer has also a right to choose whatever he likes to order from each product category. As you may see their is a "Remove" button at the bottom left of the form it meant to remove a selected order in the list if ever a customer change his/her mind to order it. the "Clear" button used to clear the entire cart or ordering list once a transaction has already done. Now lets jump at the main flow of the system, every-time a customer select an order for him he/she will then identify his/hers cash in hand. That will be inputted in cash input box name "Cash". When everything is already set the user must push the "Sell" button at the bottom part of the form. This button is also the save button we used to saved finish transaction of our ordering system.

Order list of saved transaction

Now lets go to the database part where the user can delete a saved transaction if every he/or she made a mistake on saving it. Remember that we only use a database just to saved important information such as finished transaction. Hope you enjoy reading this blog the ordering system that I used to demonstrate here in in VB Label section titled "Ordering System with Simple Database".