D2C Stores in India: The COD, RTO & GST Setup That Protects Your Margin

Every D2C founder in India learns the same lesson in the first two quarters: revenue is not margin. A COD order that gets returned costs you shipping twice. A GST filing done by hand at month-end is a stress test with a deadline. The stores that win aren't the ones with the best ads — they're the ones that fixed these three things before scaling spend.

1. COD verification: stop shipping to ghost numbers

COD is still a big share of Indian online orders — and it's the category where stores bleed silently. The fix is a verification step before dispatch:

• Call/WhatsApp verification at order confirmation — one tap confirms the order and the address.
• Pincode & first-order limits — some pin codes are RTO graveyards; new customers get a first-order value cap.
• Customer scoring — repeat verified buyers get COD unlocked at higher values; repeat RTO customers get prepaid-only.

Done properly, COD verification typically cuts rejected orders by a third or more — every avoided rejection is two shipping fees and a product that came back stale. We build this into every store as a core workflow, not an add-on (the setup is detailed on our e-commerce services page).

2. RTO control: the leak most stores never measure

If you don't know your RTO percentage, you don't know your real margin. The operating rhythm that fixes it:

• Track RTO % per 3PL, per pincode and per reason (wrong number, fake address, customer refused, out of area) — the reasons, not just the number, tell you what to change.
• Run a reship/convert flow: a WhatsApp message to the customer at the RTO scan can convert a quarter of returns back into deliveries.
• Negotiate with 3PLs using your own RTO data — a store that shows its numbers gets better terms.

Stores that instrument RTO properly bring it from the double digits down into the low single digits within a couple of quarters. The tooling is unglamorous; the margin impact is not.

3. GST-compliant invoicing from day one

The most common D2C mistake is treating GST as a month-end problem. The setup that avoids the pain:

• Invoices generated by the store at order time — GST-compliant invoicing software with the right slabs (0/5/12/18/28%) per product, HSN codes, and state-wise tax split.
• E-invoicing from the threshold day, not after the first notice — IRN generation integrated into the dispatch flow.
• Reconciliation that runs itself — store sales vs invoiced vs returned vs cancelled, matched against 3PL settlement statements monthly, with Tally/ERP integration if you already run accounts in Tally.

When invoicing is structural, GST filing is a review, not a rescue. And when a customer asks for an invoice, it's a link, not a week of email.

The payment mix for Indian customers

UPI first (it's where Indian customers' trust is), cards and net-banking next, and COD — verified — as the fallback. Stores that push UPI with a small incentive measurably reduce returns, because prepaid orders are the ones customers actually want.

The store stack that handles all of this

None of this works as three separate tools bolted together. It works as one flow: store → verification → dispatch → invoice → reconciliation, with a WhatsApp bot handling the customer conversations in between. If you're choosing between Shopify and WooCommerce, or building custom, the decision should be made against this stack — read our e-commerce development guide for the full breakdown, and our cost guide for what each tier realistically costs.