Delivery App Development in Kabul: Features and Challenges

Delivery app development in Kabul means building a system, not a single app: a customer app for ordering, a rider app for drivers, and an admin or merchant panel that ties them together, all designed around landmark-based addresses, cash payments and patchy mobile data. Getting those local details right matters more than copying the feature list of a global delivery platform.

Key Takeaways

• A delivery service needs three parts: a customer app, a rider app and an admin or merchant dashboard.
• Many Kabul addresses are described by landmarks, so combine a map pin, a written description and a phone number.
• Cash on delivery is normal; design rider cash reconciliation from day one.
• Rider apps must work on budget Android phones with intermittent data.
• Start with one category in a few districts before expanding.

What Does a Delivery App System Include?

A working delivery service needs at least three connected pieces, each with different users and priorities:

• Customer app: browse, order, choose a payment method, track status, contact support and reorder.
• Rider app: receive and accept jobs, see pickup and drop-off points, navigate, call the customer, mark orders as picked up and delivered, and record cash collected.
• Admin and merchant panel: manage menus or products, prices and stock, see incoming orders, assign riders, handle cancellations and refunds, and view reports.

Many projects underestimate the third part. The customer app is what people see, but the admin panel is where the business actually runs, and a weak one creates chaos as soon as order volume grows.

How Do You Handle Addresses in Kabul?

You handle addresses by combining a map pin with a free-text description and a verified phone number, because many locations are known by landmarks rather than formal street addresses. A customer might describe their home as near a particular mosque, school or bakery in a district such as Karte Char or Khair Khana, and the rider needs both the description and the pin.

Features that help in practice:

• Let customers drop a pin on the map and adjust it, instead of relying only on GPS, which can be inaccurate indoors
• A required directions field for landmarks, gate colour or floor number
• Saved addresses such as "Home" and "Shop" for repeat orders
• One-tap calling from the rider app to the customer, without showing personal numbers to more people than necessary
• Letting riders correct a pin after a delivery so the next order to that address goes smoothly

Which Payment Methods Should a Kabul Delivery App Support?

Most delivery apps in Afghanistan need to support cash on delivery first, with digital options added where customers already use them. Card payments are limited locally, while mobile money and bank transfers are used by part of the market; providers and terms change, so check what is currently available before you commit.

Cash creates its own workflow. The rider app should record the amount collected for each order, the admin panel should show how much cash each rider is holding, and there should be a daily settlement step. Our article on cash on delivery for online stores explains how to reduce refused orders and cash-handling risk.

If you serve Afghans abroad who send groceries or gifts to family at home, you will also need international payment options, which usually means a payment provider operating outside the country.

Designing the Rider App for Real Conditions

The rider app should be simple, fast and tolerant of poor connections, because riders use budget Android phones while moving through the city. Large buttons, few screens and clear status steps matter far more than visual polish.

Key design choices:

• Store the active job on the phone so a rider can still see the address and phone number when data drops
• Queue status updates and send them when the signal returns, as described in our guide to offline-first mobile apps
• Send location updates sparingly to save battery and data
• Support Dari and Pashto with right-to-left layouts, and pair text with simple icons
• Keep proof of delivery light: a confirmation tap and an optional photo, not heavy uploads

What Are the Main Challenges?

The main challenges are operational rather than technical: reliable riders, accurate addresses, cash control and consistent preparation times at merchants. Software can support each of these, but it cannot replace the process behind them.

Other issues to plan for:

• Traffic and road closures that make delivery estimates unreliable, so show time ranges rather than exact minutes
• Power cuts at merchants, which affect tablets and receipt printers
• Customer trust in a new service, built through phone confirmation and responsive support
• Peak periods such as Ramadan evenings and the days before Eid, when demand jumps
• Data costs for customers, so keep images light and the app small

How Should You Launch a Delivery App Step by Step?

You should launch narrowly and expand once operations are stable. A practical sequence:

1. Pick one category, such as food, groceries, pharmacy items or parcels, and a small set of districts.
2. Run orders manually through WhatsApp and a spreadsheet for a few weeks to learn real demand and real problems.
3. Build the admin panel and rider app first, then the customer app.
4. Bring on a small number of merchants and riders and train them in person.
5. Open to a limited group of customers and track delivery times and failed orders.
6. Fix the operational issues, then add districts and categories.

Some businesses start with a website and WhatsApp ordering and add native apps later. For background on couriers and routes, see our guide to ecommerce delivery in Afghanistan.

How Much Does a Delivery App Cost?

A delivery system costs considerably more than a single app because it involves three interfaces, live status updates, maps and payments. The budget depends on how many of those parts are custom-built versus kept simple at first, and on whether you need Android and iOS together.

Sheen quotes mobile apps on request after a scoping session. If you start with a web-based ordering store instead, our e-commerce packages begin from AFN 21,000, which can be a lower-risk first step before committing to native apps.

Work With Sheen

Sheen designs and builds delivery systems for Afghan conditions: customer and rider apps, admin dashboards, Dari and Pashto interfaces and offline-tolerant workflows. Explore our mobile app development service or book a consultation, or reach us at info@sheen.af or +93 784 966 018.