Restaurant E-management Workflow:

1. A customer looks for the menu on the mobile device available on the table.
2. The customer selects the menu items and confirms them.
3. Customers can view the orders in the cart.
4. The order will be displayed on the devices available in the kitchen.
5. The customer has the option to modify the ordered item unless the chef starts preparing the item.
6. The item will be marked as Pending until the chef starts cooking it.
7. The chef starts cooking the food and marks the status as Preparing.
8. Chefs prepare the food item and change the status to Ready.
9. The servers will pick up the food from the counter and serves it at the appropriate table.
10. Customers can order the food many times. The above process will be repeated.
11. Also, customers can view the bill till now before generating the actual bill.
12. When the customer finishes, he selects generate bill option and pays the bill.
13. Customers will also have the option to fill in the survey.

System users

1. Customer
2. Chef
3. Waiter (Server)
4. Restaurant Manager
5. Inventory Manager

Functionalities of the users

Customer:

The customer enters a restaurant. The manager will look for empty tables with a specified number of people. The table will be allocated to the customer. The customer will have a device on the table through which he can order the food items.

Customers can browse through the menu. He can choose categories from appetizers, entrees, and desserts. There is also a sub-category for vegetarian non-vegetarian and vegan. Menu items are classified on these criteria.

Main menu page where a user can browse through different categories. The default section is the Appetizers as highlighted above.

Customers can browse through another section. Here the customer is in the Entrée section.

Customers can select the menu items and use the ‘+’ & ‘-’ signs to increase/decrease quantity respectively. Add those to the cart using the ‘Add’ option. The order of items will be the order in which they are added to the cart on the right.

Clicking on Add button adds the items to the cart on the right side.

Customers can see the top-selling items in the restaurant in each of the sections with a star mark on them.

Customers can view the bill and cart on the right side of the screen. It will contain a list of items selected by the customer. Once the customer clicks on ‘Place Order’ the items get added to the ‘Billed Items’ section. Customers can add or remove items from the cart using the ‘Edit Order’ button. Customers can also clear the entire cart by using the ‘Reset Cart’ option.

Items are added to the cart and then placed order items are under the Billed Items section.

Customers can view the total bill for the ordered items. When the customer clicks the ‘Place Order’ button, the items from the cart are moved to the ‘Billed Items’ section. These confirmed items are now displayed on the chef’s screen for processing.

Chef’s screen as and when the order is placed by the customer.

The customer can edit these items before the chef clicks the ‘Accept’ button. Once the chef accepts the items for preparation, the customer cannot update those items. The tax will be added to the total bill and the new amount to be paid will be displayed at the end. Edit Modal allows to increase/decrease the quantity of the items or delete the items from the order.

The Edit modal opens up when the user clicks on the ‘Edit Items’ button.

Customers can see the delivery time for the first item to be served.

Before paying the bill, the customer can provide a tip. Customers can also provide feedback on the service and food.

Bill Page shows the amount to be paid, adds a tip, and allows the user to pay the amount.

Feedback form available to the customer.

Chef:

When the Chef logs in, he first selects the number of chefs in the kitchen at present. This will be used for the delivery estimation of an item.

The landing page of the chef

When the customer clicks the ‘Place Order button, the chef’s screen will get the list of items to be prepared. The order of items will be the order in which the order is placed. The chef’s screen displays the queue of items that were ordered. The chef accepts the order by clicking the ‘Accept’ button. From this moment, the customer cannot edit the accepted items.

Chef’s screen with some orders that have been accepted and are being prepared. Some orders waiting to be accepted.

When the item is cooked, he will update the item to a Ready state. At this time, this item will be added to the waiter’s screen. The chef can view the list of total items ordered in that restaurant.

Waiter:

This screen will be accessible to the waiter so that, she/he can change the status from occupied to ready once she/he finishes cleaning the table after the customer leaves. Also, she/he will be able to select the menu which is displayed to the next visiting customer.

Chef’s screen with some orders that have been accepted and are being prepared. Some orders waiting to be accepted.

This screen will display the list of items prepared by the chef and which are ready for pickup. Once the waiter picks up the item and serves it at the table, he/she will change the status of the item to Delivered using the ‘Delivered’ button in the Edit modal. Then the items will have the delivered e-stamp on them.

Waiter’s screen with the list of ready orders.

Items have the Delivered e-stamp on the items that have been delivered.

Once the customer finishes ordering, the waiter can mark the order as complete.

In the end, the waiter can proceed with payment from the customer and will mark the order as paid.

Front Desk Manager:

She/he can update the status of the tables in the restaurant. Also, she/he can assign an appropriate table to the customers depending on the availability and number of guests.

The table status lists for the restaurant

Restaurant Manager:

She/he can add, delete or modify the information about the food items. Also, she/he can modify the information about the restaurant.

The restaurant Manager can view the weekly, monthly and annual sales for his/her outlet using the filters in the report section. This can be done using the Reports section where we have several reports to show the statistics pictorially.

Sales reports are visible to the people at the managerial level.

She/he can view the current inventory position of the restaurant. Also, the restaurant manager can update the inventory items. She/he can view the forecast of items in the inventory that are to be replenished.

Inventory chart for a quick update on the items in the repository.

Higher Manager:

She/he can view restaurant-wise weekly, monthly, quarterly and annual sales of the restaurant. Also, she/he can view the most popular items, average bills, and least popular items for further actions in menu management across the chain as well as per restaurant.

Screens

Table Screen

This is the first screen. The restaurant manager gets the list of table details with seats available and status in his restaurant. The guests will be allocated an appropriate table. When the table is selected, the status is changed to Occupied.

Controller Name: TableController

Page Name: TestTables

Menu Screen

This page displays the menu items. On the upper side, special offers are displayed. Menus are divided into 3 sections namely appetizers, entrees, and desserts. In each section, users can select vegetarian, non-vegetarian, and vegan items. By clicking on the item, the customer can view the food details. By pressing Add button, the item will be added to the cart.

The cart is displayed on the right side. The items in the cart can be modified before the place order button is clicked. The customer can see the total amount to be paid along with the taxes. When the item is delivered, the waiter will mark the item as delivered.

Controller Name: MenuItemListController

Page Name: Menu

Bill Screen

This page gets enabled when all the items in the order are delivered. This page will display the name, quantity, and amount for each item. The total will be displayed below it. Bill Page also has the option to provide tips. This will change the total amount. By clicking on the done button, the order is completed and the order will be closed.

If the customer wants to order more items, then the Back to cart button needs to be clicked. This will take the customer to the menu page.

At the end of the page, customers can give feedback;

Controller Name: Bill

Page Name: Bill

Chef Screen

This page displays the list of the ordered items by customers. The chef will click Accept button when he starts cooking the ordered item. After this moment, the customer cannot modify the item count that the chef has started preparing. When the item is ready, the chef will click on the Ready button. This will notify the waiter screen that the item is prepared. Now the waiter will serve the particular item.

Controller Name: ChefListController

Page Name: Chef_Pending_Orders

Waiter Screen

This page displays the list of food items that are ready to deliver. The waiter will pick up the items and deliver them to the table number specified with the item. He will click on the Pickup button when he takes the item.

Controller Name: WaiterListController

Page Name: WaiterPendingOrders

Business Background:

This Salesforce CRM Project is an Integrated Donations Management System Platform, which brings together Shelter Homes and their donors to a single platform.

The application makes it easier for shelter homes to access a large base of donors and provides the donors with a convenient way to identify the requirements of social establishments around them.

The application allows shelter homes and donors to create requests or pledges, respectively, and then view these entries and respond accordingly.

This provides an effective medium to match the requirements at the shelter homes to availability with the donors in the community.

We essentially aim to bring a market-place-based model to donations management at shelter homes.

Project Scope:

We have identified several gaps in the way shelter homes Donations Management System to collect donations:

1.     Difficulty in communicating immediate requirements to the society

2.     Time taken to request, and receive donations can be too high

3.     Donations may not reach where they are required the most immediately

4.     Donors may find it difficult to find an organization that could use their help

5.     Lack of a common platform to enable engagement between the shelter homes and the society

The application aims to address each of these issues systematically. Specific functionalities from within the Salesforce CRM have been utilized to build a system that caters to the requirements of both, donor and shelter home perspectives.

The Donations Management application needs to adhere to the following project goals:

1.     Users are able to log in as donors/shelter homes using web integration. Donors can register as either individuals or organizations

2.     Users are able to create pledges/requests for a specific category using web integration.

3.     Users are able to create pledges/requests in response to specific requests/pledges using web integration

4.     Allow the creation of campaigns to facilitate donations for a specific purpose (for ex, preparation for upcoming storm warnings, etc.)

5. System-generated reports help match pledges/requests based on selected categories, and their status is updated as such

6.     Analytical reports on activities on the platform

7.     Scheduled report provides frequent updates on open requests/pledges.

Limitations:

In the scenario where users do not provide an existing pledge/request name, the matching needs to be done by the administrator. This causes a manual intervention and may cause delays in the matching process

Reports from the application provide data on requests and pledges that are currently open. This information needs to be hosted and updated online separately. There is no convenient way to integrate this into the application

Future Scope:

Several functionalities can be added to the Donations Management application to enhance user experience, and achieve greater integration:

• Integration with Payment Gateway to enable cash donations
• Web API to integrate with business websites, helping create a corporate partnership
• Mobile application
• Automated alerts on matching pledges and alerts
• Greater integration with the transportation process, once pledges and requests are matched
• Categorize Donor organizations based on business type for focused engagement
• Implement Salesforce Communities to promote greater engagement
• Access to the Blackbaud Community
• Include a wider range of non-profit organizations

Infrastructure:

• Considering the upfront cost of hardware, it is better to go for cloud-based service than on-premise. Cloud-based services are scalable as per requirement.
• Software as a Service is preferred over Platform as a Service as the former needs licensing cost, and time software updates.
• A cloud-based Customer Relationship Management (CRM) service will be more beneficial as it reduces development and deployment time.
• Salesforce applications have the feature of API integration that can be used later in other applications.
• The Analytics service to create dashboards will help to get insights into different transactions

Business Requirement:

The below points describe the overall business objective the application aims to fulfill:

• Shelter Homes and Donors can register on a common platform
• Pledges and Requests can be created via web integration by donors and shelter homes respectively
• Ability to create campaigns to aggregate donations and run separate donation programs for donors or shelter home
• Pledges and Requests can be viewed and responded to. For example, donors can create pledges to fulfill a particular existing requirement
• Reports providing regular updates on open pledges/requests
• Perform analysis on platform usage, and identify major trends (top donors, etc.)

Process Flow:

• The user enters the ‘Welcome Page’ and chooses Member Type as ‘Donor’ or ‘Shelter Home’
• User redirected to log in page for Donor or Shelter Home as per selection in the first step. New users can navigate to the Registration Page and complete registration. Donors can register either as an organization or an individual
• Donors are immediately notified by email post account registration. Shelter Homes are verified for authenticity, until then, the Shelter Home account status is ‘Pending’
• Admin verifies the Shelter Home registration and updates status to ‘Approved’. Shelter Home contact is notified via email, and can now start using the account
• User creates new Pledge / Request. A Request / Pledge name can be provided on the Pledge / Request, respectively, using a Lookup field provided in the creation form
• A new request/pledge is created, and the status is updated as ‘Matched’, if Pledge Name / Request Name is provided by the user
• A new request/pledge is created, and the status is updated as ‘Open’ if Pledge Name / Request Name is not provided by the user
• Matches with new pledges/requests are identified based on reports generated in the application
• The status of matched pledges/requests is updated by the system admin with Salesforce access. The corresponding Donor / Shelter Home is notified of the change in status of their pledge/request
• The report is generated with the latest updated data on open requests/pledges
• Use Salesforce Reporting functionalities to identify Top Donors by the number of pledges, Top shelters by the number of requests, Top categories for which requests are created to enable targeted campaigns, and Shelter Homes with a high amount of open requests, to enable personalized assistance if required. These reports are generated and described in the ‘Reporting and Dashboards’ section

Management Dashboards

Apart from these transactional reports, there are various Management Reports, arranged into Dashboards, to provide a summary of the application.

Dashboard 1: Overview

The Overview Dashboard contains various reports providing important metrics regarding application usage.

The reports help us analyze:

1.     Top donors based on the number of pledges created

2.     Top shelter homes based on the number of requests created

3.     Number of Shelter Homes with pending verification vs number of verified Shelter Homes

4.     Distribution of donors by Individual and Organization Donors

Such details are important for Customer Management and Donor Management. For example, top Donors can be identified and personally acknowledged, which will help retain them on the platform.

Dashboard 2: Pledge Overview

This dashboard provides a brief summary of pledges logged in the system. The above reports provide important data including:

1.     Number of Matched vs Open Pledges

2.     Trend of Pledges created in the current month

3.     Categories Distribution for Open Pledges

These reports help identify trends of the pledges created. A systematic decrease in pledges can be detected and followed up by the management.

Dashboard 3: Request Overview

The dashboard provides a detailed summary of the Requests created in the system. The reports provide information regarding:

1.       Category distribution of Open Requests

2.     Number of Matched vs Open Requests

3.     Number of Open Requests by Shelter Home

4.     Number of Open Requests for each Category

These reports help us analyze which categories are more widely requested by shelter homes. This can help the platform organize targeted campaigns to satisfy the requirements.

Executive Summary

In this Project on CRM, we will discuss the strategies that are useful for an online bookstore. Then we will discuss five of the journals from different personalities. In which we have to discuss the relationship capabilities and the related links. Then we will discuss how the internet is changing the way of purchasing books. We will also ponder upon the point and discuss the way for buying the book whether it is for reading purposes or for gifts.

So, accordingly, we will arrive at a particular result that will either support the point that customer relationship management is totally helpful in integrating the customer whether it is a small firm or a big firm or will deduce that CRM does not play a significant role in the establishment of any Ecommerce industry, let it be an online book store Project. Customer relationship management strategies are creating so much profit for the company as they are continuously interacting with their customers. By sending electronic emails and other surveys we can take feedback from our consumers or customers. These points will also be discussed in the report. The prototype for an online bookstore will also be made.

Introduction

CRM is termed “Customer Relationship Management”. CRM is very important for starting any business model very efficiently whether it is an online bookstore. By using customer relationship management, we can make strategies for developing an online bookstore. So, when we are making a customer relationship management strategy, we have to focus on the needs of our clients or customers to make sure to complete their needs for books, etc.

A customer relationship management strategy will help to make a regular customer base for the increment in sales of the books and other products in the store, so they can increase their profits. Also, by using customer relationship management software, emails, and using social platforms to provide information to the customer so that they can at least visit or view the online store.

This way CRM is promoting the Online Bookstore. By promoting online, we can have more customers. So, more customers will give more profit. CRM using social platforms is also helping us to spread more information about online bookstores as compared to the normal ways, in other words, CRM is also advertising the bookstore online.

Online we can reach global customers so that they can also buy our products and this way we can have global customers. Customer Relationship Management will help in creating surveys to get more information about the customer’s supplies and needs. Also, customers can provide feedback about their experience of purchasing the product.

These types of surveys should be displayed on the store’s website or on its social media page so that the customers can see the reality. There is some customer relationship management software that can be used to manage the list of clients’ E-mails and other personal data that they insert during purchase.

This software can keep an eye on the success or failures of marketing campaigns of the company. Customer relationship management helps in reviewing the whole business plan and also CRM can give time-to-time statements for the monthly income. This will help in calculating the monthly expenses for the store.

Customer relationship management helps both the type of companies or firms whether it is small firm or big firm it helps to interact with the customers and build the company for the future so that it can run with a good base future.

Modeling:

Findings and Discussion

Here in this report on ‘Customer relationship management for online book stores, we find that CRM strategies are very useful in approaching the customer. These strategies will make sure to complete the needs of consumers on time. So, it is used to interact with the customers.

Maintaining and handling consumers is one of the most reasons to use CRM strategies. We can handle consumers individually by keeping an eye on their needs by sending them emails. We can take a review system by taking feedback filled up by customers. Here I find that these CRM strategies are very useful in making a business model very successful. CRM strategies are formed in such a way that they are very approachable to the consumers and help in finding their needs and supplies. CRM for online bookstores will lead us to a new way of selling books and a new experience for the buyers also. We also discussed here promoting the book online.

This promotion can be done on the basis of some recommendations and using all the social media platforms. By using social media platforms like Facebook, Instagram, etc. we can create a promotion campaign so that it can widely spread the information about the online bookstore. Another one is a recommendation which is just mouth publicity like talking about the books to our friends, family and relative, and other members so that they can at least approach the book. These all things will surely increase the profit percentage of the company.

Conclusion

A book is a bundle of pages that are bound together inside a cover so that we can change pages and go through them one by one. Here, their main aim is to identify the main factors which are influencing the purchase of fiction books. And we will test these factors when the book is purchased for personal use or gift purpose.

Fiction books are the most readable books in most countries. Customer relationship management helps in incrementing operational performance. Also increases the efficiency and profit percentage of the firm. Customer relationship management is helpful for both types of firms whether it is small firm or big firm.

In these both the firms. Customer relationship management strategies interact with the customer and take their feedback. So, customer relationship management strategies play a very important role in selling books from the store. Customer relationship management also gives monthly statements for the company. Customer relationship management helps in collecting the personal data of the consumers for future promotion of their products.

The order management system is a Salesforce app and environment meant to facilitate the creation and approval of orders generated by a firm’s clients. The firm’s order-handling team comprises employees in sales, business, and support roles. The system is meant to handle how an employee interacts with and handles order and client data while overriding the standard sales cloud utility with customizable lightning web components.

Scope

Inscope

1. Support user, Business User, and Sales User were given their own specific functionality as per the use case.
2. Order approval was automated.
3. Triggers were used to apply business logic.
4. Lightning Web Components used to create app home page and override actions(wrapped in aura component).

Outscore

1. Ensuring code coverage using test classes, to prepare for deployment was not done.
2. Batch apex jobs that could remove empty orders on a timely basis.
3. Limited salesforce license reduced the number of users.

Classes and Constituents

Users

Contains data such as EmailId, UserId, Password, Username, and utility controls such as profiles, roles, managers, and licenses, which are then used to configure sharing of data and utility.

Accounts

Contains data of the Clients such as their Contact information, related deals, and trade.

Orders

Contains order details to record client order data and facilitate order handling.

Invoices

It has payment data and progression details for an order.

Price books

Contains price lists and products

Products

Contains product details and stock details

Components

Lightning Web Components

Lightning Web Components were used to:

1. Creating an Order, using the lightning-record-edit-data form
2. Searching Products, using a Controller and an Apex imperative call
3. Adding Order Line Items, using a Controller and an Apex imperative cal
4. Generating the Order Summary
5. Overriding the New Order button on the Order home page, using a lightning Aura Component which calls a lightning web component.

Apex Triggers

1. Trigger on User Object:

Used to restrict the manager of a sales user to a business user. Also checks and restrains the number of accounts managed by a user based on profile.

2. Trigger on Account Object:

Sets email opt-out for an account’s contacts

3. Trigger on Order Object:

Used to control reversion of order stage

4. Trigger on OrderItem Object:

Used to maintain the stock quantity and update it

5. Trigger on Invoice Object:

Used to update the Order stage upon invoice generation

Approval Processes

Order Approval Process:

The order approval process works by directly approving orders having amounts under 100,000 dollars, and requiring a manager’s approval for orders above that.

Visit the Order Management System Salesforce Project Page, Download this project for reference purposes.