The delivery network that
works where roads don't.
A neutral logistics backbone for merchants, platforms, and carriers in markets where addressing is by landmark, payment is cash-on-delivery, and couriers go offline for days.
Rasaan is not another shipping API. It is a logistics operating system — an elastic core where every shipment is a sequence of ordered legs, every courier syncs when they can, every afghani of COD is tracked from doorstep to merchant ledger, and every participant operates under one neutral network instead of stitching together their own.
Delivery in Afghanistan is held together by phone calls and faith.
Every merchant, every platform, every carrier faces the same set of structural barriers — and each one is solving them alone, from scratch, every single day.
Here is what delivery actually looks like today:
- There is no standardized addressing. Destinations are described by landmarks, neighbourhood names, and phone calls to the recipient — not street numbers or postal codes. Every delivery is a negotiation.
- Cash-on-delivery accounts for over ninety percent of transactions, but settlement is manual. COD cash moves through couriers, hub operators, and informal ledgers with no reconciliation layer. Disputes are resolved by argument, not audit trail.
- Couriers go offline for days at a time. Rural routes, mountain passes, and power outages mean a courier can leave a hub and not sync again for seventy-two hours. No existing system accounts for this.
- There is no neutral delivery platform. Every merchant arranges their own couriers, negotiates their own rates, and builds their own tracking — or goes without. There is no shared infrastructure.
- Package tracking is done via WhatsApp. Merchants text couriers for updates. Customers text merchants. Status is whatever the last person said it was.
- No settlement engine exists. When a delivery is complete, there is no automated way to reconcile what was collected, what was delivered, and what is owed to whom. Every cycle ends with a manual count.
The cost of doing nothing:
- Merchants lose revenue to failed deliveries, disputed COD, and customers who simply cannot be found at unmarked addresses.
- Couriers operate without tools, without routes, and without a way to prove they did their job — so trust erodes and turnover stays high.
- Platforms that want to offer delivery must build everything from scratch or accept that logistics is a black box they cannot control.
- The entire delivery economy stays informal, fragmented, and impossible to scale — locking Afghanistan out of the e-commerce infrastructure the rest of the world takes for granted.
Rasaan exists because none of this is inevitable. Every one of these problems has a structural solution — they just need a shared platform to live on.
One elastic core. Every shipment, every leg, every afghani.
Rasaan models every shipment as a sequence of ordered legs — pickup to hub, hub to hub, hub to doorstep. Legs can be added, rerouted, or split without rebuilding the shipment. This elastic core is the foundation for everything else: fleet management, COD tracking, route intelligence, and settlement.
Network vision: A single neutral platform where any merchant can ship, any carrier can deliver, and every transaction is visible from pickup to settlement — regardless of geography, connectivity, or payment method.
What the network does
Six engines working as one. Each handles a structural problem that today is solved by phone calls, spreadsheets, or not solved at all.
Shipment Engine
Create, split, reroute, and track shipments as ordered sequences of legs. The elastic core means a shipment from Kabul to Badakhshan can gain a leg mid-transit without anyone rebuilding the record. Design now, activate later.
Courier Fleet
Onboard couriers, assign zones, manage capacity, and track performance — whether they are full-time employees, freelance riders, or partner carriers. One fleet view across the entire network.
COD Ledger
Every afghani of cash-on-delivery is tracked from the moment the courier collects it to the moment the merchant is settled. No more manual counts. No more disputes about who has what. The ledger is the single source of truth.
Route Intelligence
Landmark-based addressing meets computational routing. Rasaan builds route knowledge from every delivery — not from maps that do not exist. The more the network delivers, the smarter it gets.
Tracking Hub
Real-time shipment visibility for merchants, customers, and network operators. Status updates flow from couriers — even offline ones — through the hub and out to every stakeholder. No more WhatsApp chains.
Settlement Engine
Automated end-of-cycle reconciliation. What was shipped, what was delivered, what was collected, what is owed — calculated, verified, and ready for payout. Settlement cycles that used to take days now close in hours.
The shipment journey
Every package follows the same six-phase lifecycle — from merchant handoff to financial close.
Built for the courier who won't have signal for three days.
Most logistics platforms assume always-on connectivity. Rasaan assumes the opposite. The courier app, the manifest system, the COD collection flow, and the sync engine are all designed to work without a network connection — and reconcile cleanly when connectivity returns.
A courier leaves a Kabul hub at dawn with forty packages, rides into Logar province, delivers for two days with no mobile signal, collects COD in cash, and syncs everything — deliveries, failures, collections, signatures — when they reach the next hub. Nothing is lost. Nothing conflicts. The ledger stays whole.
Offline surfaces
Courier app
Full delivery workflow without connectivity. Scan packages, capture proof of delivery, record COD collection, mark failures — all stored locally with a seventy-two-hour buffer. Sync is automatic and conflict-free when signal returns.
Offline manifest
Hub operators load manifests onto courier devices before departure. The manifest includes delivery sequence, landmark directions, recipient phone numbers, and COD amounts — everything the courier needs, with no network required.
COD collection
Cash collection is recorded per delivery, per courier, per cycle — offline. Amounts, denominations, and receipt confirmations are stored locally and reconciled against the central ledger on sync. No cash goes untracked.
Hub sync
When a courier reaches a hub with connectivity, the sync engine uploads all pending events, resolves conflicts using last-write-wins with causal ordering, and downloads new assignments. The process takes seconds, not sessions.
Offline qualities
Conflict-free sync
Rasaan uses conflict-free replicated data types at the sync layer. Two couriers updating the same shipment from different locations will not corrupt the record — the system merges deterministically.
Seventy-two-hour buffer
Every courier device maintains a local store capable of holding three full days of delivery activity. Even extended rural routes are covered without data loss.
Bandwidth-aware
Sync payloads are compressed and prioritised. Critical updates — delivery confirmations, COD amounts — sync first. Media — proof-of-delivery photos, signatures — sync when bandwidth allows.
Power-conscious
The offline engine is designed for low-end Android devices with limited battery. Background sync is batched, GPS sampling is adaptive, and the app runs lean even on hardware that costs forty dollars.
Intelligence that learns from every delivery, not from maps that don't exist.
Rasaan's AI layer is trained on the network's own delivery data — actual routes couriers take, actual landmarks that work, actual transit times between hubs. In a market without reliable cartographic data, the network's operational history becomes the map.
Every AI feature operates under per-network budgets, human-in-the-loop overrides, and full auditability. No black-box decisions. No autonomous actions without operator approval.
Landmark route optimisation
Routes are built from landmark sequences, not GPS coordinates. The system learns which landmarks are reliable, which descriptions lead to failed deliveries, and which routes couriers actually prefer — then optimises accordingly.
Demand prediction
Forecast shipment volume by zone, by day, by season. Rasaan models demand patterns so network operators can pre-position couriers and hub capacity before the surge, not after.
ETA estimation
Delivery time estimates that account for road conditions, courier load, time of day, day of week, and historical transit durations on the same route. Honest ETAs, not optimistic ones.
Anomaly detection
Automatic flagging of shipments that are delayed beyond threshold, couriers who deviate from expected patterns, and COD amounts that do not match manifests. Problems surface before they become disputes.
Automated status updates
Customers and merchants receive delivery updates generated from courier activity — not typed by humans. When a courier scans a package at a hub, the customer knows. When a delivery attempt fails, the merchant knows why.
Network capacity planning
Model fleet size, hub placement, and route allocation against projected demand. Answer questions like: if volume doubles in Herat next quarter, how many couriers and hub shifts do we need?
AI governance.
- Per-network compute budgets — no operator pays for intelligence they did not request.
- Human-in-the-loop for all route changes and courier reassignments — AI suggests, operators approve.
- Full audit trail on every prediction, recommendation, and automated action.
- Model performance is measured against real delivery outcomes, not synthetic benchmarks.
- Bias monitoring for geographic and demographic fairness in route allocation.
- Operators can disable any AI feature per zone, per hub, or network-wide with one toggle.
From merchant handoff to financial close — every phase covered.
Rasaan is not a point solution for tracking or a bolt-on for COD. It covers the entire delivery lifecycle: creation, routing, dispatch, transit, delivery, collection, settlement, and reporting. Every phase is connected. Every handoff is recorded. Every afghani is accounted for.
Baseline operations
Shipment creation
Merchants or platforms create shipments via API, dashboard, or bulk upload. Each shipment is assigned a unique identifier, validated against addressing rules, and routed to the nearest pickup hub. The elastic core allows legs to be added or modified at any point before final delivery.
Routing and dispatch
Shipments are batched by zone, assigned to couriers based on capacity and route familiarity, and dispatched with offline-ready manifests. Route intelligence suggests optimal sequencing; hub operators confirm or override.
Last-mile delivery
Couriers execute deliveries using landmark-based directions, collect COD where applicable, capture proof of delivery, and record outcomes — all through the offline-capable courier app. Failed attempts are logged with reasons and automatically rescheduled.
Operational modules
Four modules that extend the baseline into a complete logistics operating system.
COD management
End-to-end cash-on-delivery lifecycle. Collection tracking per courier, per delivery, per cycle. Denomination recording, hub handoff verification, central ledger reconciliation, and merchant payout calculation. Every afghani has a paper trail.
Fleet operations
Courier onboarding, zone assignment, shift scheduling, performance tracking, and capacity management. Supports employed couriers, freelance riders, and third-party carrier integration. One view of the entire fleet regardless of employment model.
Tracking and visibility
Real-time and near-real-time shipment visibility for every stakeholder. Merchants see their outbound shipments. Customers see their inbound deliveries. Network operators see the full picture. Status flows from courier events, not manual updates.
Analytics and reporting
Delivery success rates, average transit times, COD settlement cycles, courier utilisation, route performance, hub throughput, and customer satisfaction — all computed from live operational data and available as dashboards or API exports.
Merchants, couriers, hub operators, network operators, customers, and platform integrators — every actor in the delivery chain has a role, a view, and a set of actions defined by the system. No one operates in the dark.
Measure everything. Guess nothing.
A logistics network that cannot measure itself cannot improve itself. Rasaan instruments every phase of the delivery lifecycle — from pickup scan to merchant settlement — and surfaces operational intelligence that turns raw activity into decisions.
Network coverage metrics
Three dimensions of coverage that define whether the network is reaching the people and places it needs to reach.
Geographic coverage
Percentage of addressable delivery zones with active courier capacity. Tracks expansion from city-centre density to provincial reach, identifying coverage gaps before they become customer complaints.
Merchant penetration
Number of active merchants shipping through the network relative to the addressable market. Monitors onboarding velocity, retention, and shipment frequency to gauge whether the network is earning — and keeping — merchant trust.
Settlement completeness
Percentage of completed deliveries with fully reconciled COD settlement within the target cycle. The gap between delivery and settlement is where trust breaks down — this metric keeps it visible.
Operational intelligence
Continuous monitoring of the signals that matter most to delivery network health:
- Failed delivery rate by zone, courier, and time of day — isolating whether the problem is addressing, courier performance, or recipient availability.
- COD discrepancy rate — the gap between collected amounts and expected amounts, tracked per courier and per cycle to catch leakage early.
- Courier utilisation and idle time — ensuring fleet capacity is deployed where demand exists, not where it was assigned last week.
- Sync latency — time between courier activity and central system update, critical for offline-heavy networks where delays are expected but must be bounded.
- Hub throughput and bottleneck detection — which hubs are processing shipments on time and which are backing up.
Key performance indicators
From a single city to a national backbone — deploy what you need.
Rasaan is not one-size-fits-all. The platform scales from a single-city courier operation to a multi-province logistics network, with licensing and configuration that match the operator's reality — not the other way around.
Deployment profiles
Single-city operator
A merchant cooperative or local courier company operating within one city. Core shipment engine, courier fleet management, COD ledger, and basic tracking. Fast to deploy, affordable to run, and ready to scale when the time comes.
Multi-city network
A regional logistics provider connecting multiple cities with inter-hub routing. Full shipment lifecycle, route intelligence, settlement engine, and analytics. Hub-to-hub transit management and courier handoff across zones.
National logistics backbone
A carrier or government logistics authority operating at national scale. All modules active, multi-tenant isolation for partner operators, API integration for e-commerce platforms, and full analytics suite. The infrastructure layer for an entire delivery economy.
Enterprise capabilities
Neutral brand
Rasaan operates as invisible infrastructure. Merchants see their own brand. Customers see the merchant's brand. The network is the plumbing, not the storefront. No operator is locked into advertising someone else's logistics company.
Modular licensing
Activate only the modules you need. Start with shipment creation and tracking. Add COD management when cash volume justifies it. Add route intelligence when the network has enough data to train on. Pay for what you use, not what you might use.
Multi-tenant isolation
Multiple operators can run on the same Rasaan instance with complete data isolation. Shipments, couriers, merchants, COD ledgers, and analytics are siloed per tenant. Shared infrastructure, private operations.
Built on open standards, not proprietary lock-in.
Rasaan integrates with the standards that the logistics industry runs on — and the ones that emerging-market operators will need as they formalise and scale.
GS1 labelling
GS1-compliant barcode and label generation for shipments, packages, and legs. Scannable at any hub, compatible with international carrier systems, and ready for cross-border logistics when the network grows beyond domestic routes.
EDI carrier integration
Electronic Data Interchange support for partner carrier onboarding. Exchange shipment data, status updates, and settlement information with third-party logistics providers using industry-standard EDI message formats.
PCI payment handling
Payment card industry compliance for any digital payment flows integrated alongside COD. Card data never touches Rasaan servers. Tokenisation and third-party payment gateway integration keep financial data where it belongs.
Open API for integration
RESTful API with OpenAPI specification for merchant platforms, e-commerce systems, and third-party integrators. Webhook support for real-time event delivery. Sandbox environment for development and testing.
ISO quality management
Operational processes aligned with ISO 9001 quality management principles. Documented procedures for shipment handling, courier operations, COD management, and dispute resolution — building the foundation for formal certification.
Data privacy and sovereignty
Merchant data, customer data, and COD records are stored within the operator's jurisdiction. No cross-border data transfer without explicit consent. Role-based access control ensures data visibility is limited to those who need it.
Standards are not a checkbox exercise. They are the foundation for trust — between merchants and the network, between operators and regulators, and between Afghanistan's logistics economy and the rest of the world.
Every actor in the delivery chain has a seat at the table.
Rasaan is designed for the full ecosystem — not just the merchant or just the courier, but everyone whose decisions, actions, and outcomes shape whether a package gets from origin to destination and whether the money follows.
The status quo is not a strategy. Here is how Rasaan changes each piece.
Every pain point in Afghan logistics has a structural answer. Rasaan does not paper over the problems — it replaces the informal systems with infrastructure that scales.
Infrastructure that compounds. Year by year, delivery by delivery.
Rasaan is not a product launch — it is an infrastructure programme. The network effect means every merchant, every courier, and every route makes the platform more valuable for everyone else. Here is what that looks like over time.
Year one
- Launch Rasaan in Kabul with a founding cohort of merchants and a managed courier fleet — proving the elastic core, COD ledger, and offline sync in live operations.
- Onboard fifty-plus merchants and two hundred-plus couriers onto the network, establishing the first baseline KPIs for delivery success, settlement speed, and courier utilisation.
- Achieve same-city delivery with forty-eight-hour average transit time and seventy-two-hour COD settlement cycle — benchmarks that no informal system can match.
- Open the API to e-commerce platforms, enabling delivery-as-a-feature for any marketplace or merchant tool operating in Kabul.
- Validate the offline courier workflow on multi-day provincial routes, proving that the seventy-two-hour buffer holds under real conditions.
Five-year vision
- Expand to all thirty-four provinces, operating as the national logistics backbone with hub-to-hub inter-city routing and partner carrier integration.
- Process one million-plus shipments per month across the network, with a ninety-four-percent delivery success rate and automated settlement for ninety percent of COD transactions.
- Enable cross-border logistics for Afghanistan's export economy — agricultural products, handicrafts, and manufactured goods moving through formalised, trackable supply chains.
- License the Rasaan platform to logistics operators in other emerging markets facing the same structural barriers: landmark addressing, COD dominance, offline couriers, and fragmented delivery.
- Build the delivery data layer that Afghanistan's commerce economy needs — addressing intelligence, demand patterns, route knowledge, and settlement infrastructure that any business can build on.
The network is ready. Are you?
Whether you are a merchant looking for reliable delivery, a carrier looking for a platform, or an investor looking at logistics infrastructure in emerging markets — we want to hear from you.