Tax Rules for Quick-Commerce & Instant Delivery Startups in Nepal
Kathmandu's 10-to-20-minute grocery and essentials delivery apps have grown fast, and with that growth comes a tax setup that's genuinely more complex than a traditional retail shop's. A quick-commerce operator isn't just selling products — it's simultaneously running a retail operation, a logistics/delivery service, and a network of gig-economy riders, each of which sits under a slightly different part of Nepal's tax code. Getting this separation right from the start avoids painful reconciliation problems later.
VAT on Delivery/Service Fees vs. Product Sales
A quick-commerce order typically bundles two economically distinct things into one checkout: the price of the groceries or goods themselves, and a delivery, convenience, or platform service fee layered on top. Both are subject to Nepal's standard 13% VAT rate (subject to the usual Schedule 1 exemptions for certain basic unprocessed food items), but they represent two separate taxable supplies — a sale of goods, and a supply of a delivery/logistics service — and should be accounted for as such.
Both components of a quick-commerce order are VAT-rated, but should be tracked separately
Keeping the two revenue lines separate on your invoicing and in your books matters for a few practical reasons: it makes your input VAT credit claims (on inventory purchases, packaging, dark-store rent, and rider-related costs) cleaner to reconcile against specific revenue streams; it gives you an accurate margin picture on the retail side versus the logistics side, which most quick-commerce businesses need anyway for unit-economics tracking; and it reduces the risk of a mismatch surfacing during an IRD VAT audit, where blended, undifferentiated invoicing is a common red flag.
Gig-Worker Rider Tax Treatment (Recap)
Delivery riders working for quick-commerce platforms are generally engaged as independent partners rather than salaried employees, similar to the model used by ride-hailing and food-delivery apps. This has a specific tax consequence: riders earn income in Nepali rupees from a domestic platform, which is fundamentally different from a freelancer earning foreign-currency income from an overseas client. That distinction matters because it means riders do not qualify for the 5% foreign-currency freelancer flat rate — their earnings are ordinary self-employment/business income, assessed under the regular progressive slabs, or under presumptive tax treatment if the rider's turnover qualifies as a small taxpayer under the applicable limits.
Riders are taxed as self-employed earners; e-billing obligations track cumulative annual turnover
As the platform operator, your obligation is generally to correctly document payouts to riders (many platforms structure this as a commission-based settlement after the platform's cut), rather than to withhold salary-style TDS the way you would for an employee. Whether any TDS applies to rider payouts, and at what rate, depends on how your specific contractual relationship with riders is structured — this is a detail worth confirming carefully with a CA, since getting it wrong exposes the platform to withholding-agent liability.
E-Billing Compliance for High-Volume, Small-Ticket Transactions
Quick-commerce is a volume game — hundreds or thousands of small orders a day, each worth a few hundred rupees. Individually, none of these transactions look tax-significant, but IRD's electronic billing (e-billing/CBMS) requirement is based on cumulative annual turnover, not per-transaction value. Once a business crosses NPR 10 crore in annual turnover (a lower NPR 5 crore threshold applies to hospitality-sector businesses like restaurants), it becomes mandatory to issue invoices through IRD-approved billing software that syncs in real time with the Central Billing Monitoring System (CBMS).
For a fast-growing quick-commerce operator, this threshold can arrive sooner than founders expect, precisely because of the sheer order volume even at a modest average order value. It's worth planning for CBMS-compliant billing infrastructure well before you're legally required to have it, both to avoid a scramble at the threshold and because real-time billing data is genuinely useful for your own operational visibility into sales by dark-store location.
Discussion