BeeXprss Service

The Onboarding Reality – What Happens When You Open It

You install the app, open it, and land on a registration screen. No guest mode. No tour. Just a form asking for your mobile phone number and address. You enter the details. The app checks if your number is already in the system. If you are an existing customer, it pulls up your activity history. If you are new, you complete the registration. The home screen loads. It shows totals for outgoing and incoming shipments. There are shortcut menus for pickup orders, tracking, COD statements, pricing checks, and rewards. The interface is functional but basic. It feels like a tool built for a specific purpose, not a polished consumer app.

The app works based on your phone number. Every transaction and activity is tied to that number. If you change your number, you must contact support to update it. There is no self-service option for this. The app also requires you to agree to receive SMS or phone calls with registration codes. This is a courier service app for Myanmar. The developer is based in Yangon. The company, BeeXprss Courier Service (UMG Logistics Co., Ltd), was licensed by the Ministry of Transportation and Communication in 2018. It delivers parcels across more than 200 cities in Myanmar. The app is the digital front-end for this operation.

The Clash Between Tracking and COD Management – A Workflow Analysis

The app has two core functions that should work together seamlessly: shipment tracking and Cash on Delivery (COD) management. Tracking shows you where your parcels are. COD management shows you how much money you have collected or need to collect. In theory, the tracking status should trigger COD updates. When a shipment is marked as delivered, the COD amount should appear in your receivable dashboard. In practice, this does not always happen. Users report that the tracking system is poor and outdated. It does not provide timely updates. This means the COD dashboard may not reflect the actual status of deliveries. You might see a shipment as "in transit" when it has already been delivered, or vice versa. This creates confusion about when COD payments are due.

The app also requires a two-step process for sending shipments. First, you create a draft shipment order (draft AWB). Then, you must separately create a pickup order. Only after the pickup order is made will a courier come to collect your shipment. This two-step workflow is not clearly explained in the app. Users may create the draft AWB and assume the courier will come, only to find that no pickup was scheduled. This adds friction to the process and increases the chance of errors. The app's design assumes users understand the logistics workflow, but it does not provide enough guidance for new users. This is a common issue with business apps that are built for operational efficiency rather than user experience.

What Actually Changed? The "Bug Fixes" Changelog Problem

The version history of BeeXprss Service follows a familiar pattern. The changelog for the latest version simply says "Bug Fixes." Previous versions show the same vague language. There is no specific information about what was fixed, which issues were addressed, or what improvements were made. The app has been updated multiple times in 2026. Version 3.0 was released on April 20, 2026. Version 3.2 followed on April 29. Version 3.3 came on May 21. Version 3.4 arrived on May 29. Each update brought a new version number, but the changelog remained the same: "Bug Fixes." This lack of transparency is a problem for users. They have no way of knowing if their specific issues have been resolved.

The app has a 2.89 rating from 229 reviews on Chrome-Stats. Users have reported problems with poor tracking, long waiting times, late deliveries, navigation issues, and bad customer service. Are these issues being fixed? The changelog does not say. The developer, BeeXprss Courier, is based in Yangon, Myanmar. The company has been operating since 2016. It is unfunded and operates as a B2B logistics technology platform. The app is free and has over 93,000 downloads. But the lack of detailed changelogs undermines user confidence. When a user encounters a bug, they cannot check if it has been fixed in the latest version. They must update and hope for the best. This is not a sustainable approach for a business-critical app.

The Bizarre Use-Case: Draft AWB and Pickup Order Separation

One of the more unusual features of the BeeXprss Service app is the separation of draft shipment orders and pickup orders. To send a parcel, you must first create a draft AWB (Air Waybill). This is essentially a shipping label with the sender and receiver information, package details, and service type. Once the draft AWB is created, you must then create a separate pickup order. Only after the pickup order is made will a courier come to collect your shipment. This two-step process is not common in consumer courier apps. Most apps allow you to book a pickup and create a shipment in a single flow. The separation adds complexity and increases the chance of errors.

This design choice seems to reflect the app's origins as a business-to-business tool. It may be designed for users who create multiple draft shipments in advance and then schedule pickups later. But for casual users, it is confusing. The app does not provide clear guidance on the workflow. Users may create a draft AWB and assume the courier will come, only to find that no pickup was scheduled. This can lead to missed deliveries and frustrated customers. The app's description on the Play Store mentions this process, but it is buried in the feature list. A more intuitive design would combine the two steps into a single "Send Shipment" workflow. Until then, users must learn the hard way that a draft AWB is not enough to get a parcel picked up.