Product reference
A connected operating system for delivery work.
The sections below describe capabilities available in the product today.
Parcels and labels
The parcel record is the spine of the system. Every related event remains connected to it.
- Parcel booking
- Capture sender, recipient, township, and COD amount, with a per-parcel pickup address that defaults to the merchant's.
- Bulk import
- Download the CSV template, preview the rows before committing, and import a full day of parcels at once.
- Label templates
- Define your own label layouts, then generate print jobs you can download and reprint.
- Status history
- Every status change is recorded with who made it and when.
- Assignment history
- See every run, hub scan, and partner handoff a parcel has passed through.
Field operations
Pickup, hub, and delivery, each driven by scanning rather than typing.
- Pickup runs
- Assign parcels to a driver and vehicle, scan collection at the merchant, then start and complete the run.
- Pickup requests
- Merchants request a pickup against a parcel, and dispatch turns those requests into runs.
- Hub scanning
- Scan parcels in at the hub and work the pending queue until nothing is left unscanned.
- Sorting
- Create sort assignments that route each parcel onto the correct onward run or branch.
- Delivery runs
- Build the run, scan deliveries and returns as they happen, and close the run when the driver reports back.
Cash and payouts
The part that decides whether the day actually balanced.
- COD collections
- Record what each driver collected, with variance approval when the cash does not match, and voiding for corrections.
- Merchant payouts
- Queue pending payouts per merchant, then approve, process, or void, with the parcel lines behind every amount.
- Payment channels
- Record the channel used for each payment, including cash, bank transfer, or mobile wallet.
- Township pricing
- Set delivery rates per township, and vary them by customer tier.
Partner network
For parcels you hand to another delivery company to finish.
- D2D partners
- Keep a record for each door-to-door partner you work with.
- Handoffs
- Scan parcels into a handoff batch and confirm it with the receiving partner.
- Settlements
- Settle the parcels a partner carried, record their payments, and confirm the settlement.
Books and reporting
Operational activity lands in the ledger instead of a separate spreadsheet.
- Chart of accounts
- Accounts and account categories, each with a running ledger.
- Journal entries
- Double-entry postings behind the operational activity.
- Fiscal periods
- Open and close periods so historical books stay fixed.
- Reports
- Export delivery, collection, driver, merchant, partner, payout, daily summary, and pivot reports.
- Dashboards
- Separate operations and financial dashboards for the day's numbers.
Access and administration
Who can do what, and a record of what they did.
- Roles and permissions
- Grant access by role, down to individual permissions.
- Branches
- Run multiple branches under one company account.
- Audit log
- A searchable record of actions, filterable by entity type and action.
- Sessions
- See active sessions for a user and revoke them.
- Per-user language
- Each user works in English or Burmese, independently of everyone else.
Company onboarding
Discuss your delivery operation.
Send your company details for a scoped account and price. For workflow or migration questions, contact the team first.