beMerchant

First login and partner onboarding

Opening beMerchant for the first time presents a login screen that asks for a phone number and a password. The registration process is not available directly within the app. New partners must register through the be website or through the beFood partner program. Once registered, the partner receives login credentials. The app then asks for permission to access the device's storage and location. These permissions are required for uploading menu images and for order tracking. The app does not explain why these permissions are needed, which can be confusing. After logging in, the main dashboard loads. This dashboard shows a menu with options like "Orders," "Menu," "Profile," and "Reports." The interface is clean but sparse. There is no tutorial or walkthrough. New users must explore on their own. The "Orders" tab is the most prominent feature. It shows a list of incoming orders with status indicators: new, preparing, ready, delivered. Tapping on an order opens a detail view with customer information, items ordered, and delivery address. The "Menu" tab allows partners to add new dishes, update prices, upload images, and mark items as available or out of stock. The "Profile" tab allows adjusting operating hours and open/close status. The "Reports" tab shows sales data, successful orders, total revenue, and profit over selected time periods. The entire onboarding process can take up to ten minutes, assuming the partner already has login credentials.

For partners who want to streamline operations, the app offers an "Auto-accept orders" feature. This automatically accepts new orders without manual intervention. The feature is useful during peak hours. However, it also carries risks. If the restaurant is unable to fulfill an order, the partner must manually cancel it, which can lead to penalties. The app does not provide a way to set limits on auto-acceptance, such as maximum order value or maximum number of orders per hour. Partners must monitor the app constantly to avoid overloading their kitchen. This lack of customization is a common frustration among users.

When order management meets menu updates

The app's core value is enabling restaurant partners to manage orders and menus from a single interface. The order management system is the primary tool for this. A partner can view incoming orders, accept or reject them, prepare the items, and track delivery status. The system updates in real-time, showing the current status of each order. This works well when the internet connection is stable and the backend is responsive. However, the real test comes when a partner needs to update the menu while orders are coming in. Suppose a partner runs out of a popular dish and needs to mark it as out of stock. The app allows this with a few taps. The dish is removed from the menu immediately. In theory, this prevents customers from ordering unavailable items. In practice, problems arise when the menu update does not sync with the order system quickly enough. Some partners have reported that customers can still order items that have been marked as out of stock. This is likely due to a synchronization delay between the menu database and the order processing system. The app does not provide a way to force an immediate sync. Partners are left to manually reject orders for unavailable items, which frustrates customers and wastes time.

Furthermore, the app's handling of order cancellations is also problematic. The changelog mentions bug fixes, but partners have reported that orders are sometimes canceled after preparation, leading to food waste. The app does not provide a way to prevent this. Partners have to absorb the cost of wasted ingredients. This is a significant limitation for small businesses with tight margins. The original analysis here is that the app's architecture treats order management and menu management as separate modules. They are integrated at the UI level, but the backend synchronization is weak. When one module updates, the other does not reflect the change immediately. This is a design flaw that is not apparent from reading the Play Store description.

Real-world performance and common issues

User reports from various platforms paint a mixed picture of the app's stability. Some partners praise the app for its ease of use and the ability to manage orders and menus from a single interface. They appreciate the real-time order tracking and the sales reports. However, others report persistent issues with notifications. Several partners have complained that the app does not send notifications for new orders. They only see new orders when they open the app. This is a significant problem because it delays order processing and leads to customer dissatisfaction. The app does not provide a way to test notification settings or to troubleshoot notification issues. Partners are left to guess whether notifications are working. Some partners have also reported login errors, where the app fails to authenticate their credentials. This prevents them from accessing the app entirely. The app does not provide a clear error message or a way to reset passwords. Partners have to contact customer support, which is often unresponsive.

Another issue is the app's handling of order cancellations. Some partners have reported that orders are automatically canceled after a certain time, even if the partner has already started preparing the food. This leads to wasted ingredients and lost revenue. The app does not provide a way to prevent this. Partners have to manually monitor the app to ensure orders are not canceled. The app also lacks a direct complaint channel. Partners have to contact customer support through email or phone, which is often slow and unhelpful. This lack of support erodes trust in the platform. On the positive side, the app's sales reports are accurate and detailed. Partners can view revenue, successful orders, and profit over selected time periods. This data is useful for business planning. However, the reports are not customizable. Partners cannot filter by specific products or time periods. This limits the usefulness of the feature.

Storage permission and the changelog

The app requires storage permission to upload menu images. This is stated clearly during installation. However, the app does not explain why it needs location permission. Users are left to guess. The developer's changelog for the current version simply states: "Sửa lỗi và cải thiện hiệu năng." No specific bugs are named. No performance metrics are provided.