Every Indian D2C brand on Shopify hits the GST billing problem within the first 18 months of scaling. Order volume crosses a threshold, manual invoice handling stops working, GSTR-1 + GSTR-3B filings start lagging, the accounting team asks for an automated pipeline, and the brand discovers Shopify's native invoicing was never designed for Indian compliance posture.
This is the architecture we deploy for D2C brands moving from "the accountant downloads CSVs every month" to "GST invoicing happens automatically + correctly + auditably". It covers the e-invoicing mandate, the integration spine with Tally / Zoho Books / NetSuite, the customer-PII discipline under DPDP, and the audit posture that survives the inevitable GST notice.
What changed in 2024-2026
Three regulatory shifts forced architectural rework for Indian D2C brands:
| Year | Change | Impact |
|---|---|---|
| 2024 | E-invoicing threshold dropped to Rs 5 crore annual turnover | Most mid-market D2C brands now mandated |
| 2024 | GSTR-1 filing tightened (Invoice Furnishing Facility IFF + reduced amendment windows) | Manual reconciliation no longer survives |
| 2024 | DPDP Act came into force | Customer PII on invoices needs lawful basis + minimisation |
| 2025 | E-invoicing extended to B2C transactions above Rs 5,000 | B2C order flow now in scope |
| 2026 | GSTR-3B auto-population tightened | Mismatch between IRN data + filed return triggers automated notices |
The compounding effect: brands that were filing GST manually through 2023 hit a wall in 2024-2025. Architectural rework became the only viable response.
The compliance surface
A clean GST billing architecture for Shopify D2C covers four discrete responsibilities:
Invoice generation
Every order produces a GST-compliant tax invoice with: invoice number per GSTIN per year sequential, buyer's GSTIN (if B2B), HSN code per line item, taxable value, IGST or CGST + SGST split based on inter-state vs intra-state, place of supply, reverse-charge applicability, e-invoice IRN (if applicable).
E-invoicing
For B2B transactions and B2C transactions above Rs 5,000 (current threshold), the invoice gets uploaded to the Invoice Registration Portal (IRP), which returns an Invoice Reference Number (IRN) + signed QR code. The IRN must appear on the invoice PDF.
GSTR-1 filing
Monthly (or quarterly under QRMP scheme) summary of outward supplies. Auto-populated from IRP for e-invoiced supplies; manually entered for B2C below threshold. Filed by the 11th of the following month (monthly) or 13th of the month following the quarter (quarterly).
GSTR-3B filing
Monthly summary return covering tax liability + input tax credit claimed + tax paid. Auto-populated from GSTR-1 + GSTR-2B (vendor uploads). Filed by the 20th of the following month.
Each of these has an architectural choice. Each choice has trade-offs.
The integration spine
The Dcrayons reference architecture wires four systems around a single source of truth:
Shopify (storefront + orders)
|
v
Accounting system (Tally / Zoho Books / NetSuite)
|
+--> IRP for e-invoicing --> IRN + QR code
+--> GSTR-1 summary --> GSTN portal
+--> Customer email --> invoice PDF delivered
Why the accounting system is the source of truth, not Shopify
Shopify generates orders. The accounting system generates invoices. Treating Shopify as the source of truth for tax data forces every downstream system (e-invoicing, GSTR filings, audit) to re-derive tax math from order data. That re-derivation drifts.
The cleaner pattern: Shopify pushes orders to the accounting system via API or middleware (Octoparse, Razorpay Magic, custom Zapier). The accounting system computes tax, generates the invoice number per the regulatory sequence, and becomes the authoritative source for all downstream reporting.
Picking the accounting system
| System | Strengths | Trade-offs | Right for |
|---|---|---|---|
| Tally Prime | Industry standard, every Indian CA knows it, GST modules mature | Desktop-first UX feels dated; multi-location sync awkward | Brands with established CA + desktop ops |
| Zoho Books | Cloud-native, modern UX, strong Shopify integration | Smaller ecosystem outside Zoho; pricing per user adds up | Mid-market D2C, comfortable with cloud + SaaS pricing |
| NetSuite | True ERP, multi-entity multi-region, deep customisation | High cost + implementation complexity | Multi-region or Rs 100 crore+ ARR |
| Marg ERP | India-strong, retail + wholesale modules | Smaller cloud presence; ecosystem narrower | Hybrid retail + online operators |
| Sage 50 / Sage X3 | Multi-country posture for India + GCC + UK brands | India localisation less mature than Tally / Zoho | Multi-region brands with EU / GCC anchor |
For most Indian D2C between Rs 5-100 crore ARR, Zoho Books is the operational sweet spot. Above Rs 100 crore or with multi-region needs, NetSuite earns the cost.
E-invoicing: the IRP integration pattern
What the IRP returns
For every invoice you upload, the Invoice Registration Portal returns:
- IRN (Invoice Reference Number). 64-character hash unique to the invoice
- Acknowledgement Number. IRP-side reference for the upload
- Acknowledgement Date. when the IRP signed off
- Signed Invoice JSON. full digital signature payload
- Signed QR Code. must appear on the invoice PDF
The invoice without the IRN is non-compliant. Shipping an order with a non-IRN invoice when IRN was required triggers GST notices.
How the integration actually works
The accounting system (or a middleware layer) calls the IRP API immediately after invoice generation. Common patterns:
- Direct API integration. accounting system calls IRP API directly. Right when the accounting system supports it natively (Zoho Books does; Tally Prime via third-party connectors).
- GSP (GST Suvidha Provider) intermediary. middleware (Masters India, ClearTax, Cygnet) handles IRP communication. Right when the accounting system doesn't speak IRP, or when you want a single ESP-style relationship across multiple compliance needs.
- Custom Python / Node middleware. your engineering team writes the IRP client. Right when you have niche requirements + engineering capacity. Most brands don't need this.
The Dcrayons default: Zoho Books native IRP + ClearTax GSP fallback. The native handles 95 percent of orders; the GSP catches edge cases (large file size, multi-vendor consolidated invoices, foreign currency).
Failure modes worth knowing
- IRP downtime. Government infrastructure goes down. Maintenance windows are announced; outages are not. The architecture needs a retry queue: failed IRN requests park, retry every 30 minutes, escalate to human review after 4 hours.
- Validation rejections. IRP rejects malformed payloads (wrong GSTIN format, mismatched buyer details, HSN code not in the master list). The fix is upstream in the catalog + customer data; the symptom shows up at IRP submission.
- Duplicate submissions. Retry logic must check whether the invoice already has an IRN before re-submitting. Otherwise the same invoice gets two IRNs and the second filing fails.
DPDP discipline: customer PII on invoices
The DPDP Act (Digital Personal Data Protection Act) creates lawful-basis obligations for customer PII processing. GST invoicing is a permitted purpose (legal obligation under the GST Act), but DPDP still requires:
Data minimisation
The invoice carries the buyer's name + billing address + GSTIN (if B2B) + email. It does NOT carry browsing history, marketing preferences, or behavioural data even though Shopify holds those. The accounting system should pull only the fields needed for the tax invoice.
Retention
GST records must be retained for 6 years (per Section 36 of CGST Act). DPDP requires retention only as long as the lawful purpose requires. The pattern: invoice records retained 6 years per tax obligation; associated marketing data deleted per its own retention policy.
Right to access + correction
Customers can request a copy of their invoice + correction of errors. The accounting system + customer service workflow must support this. Most accounting platforms handle it natively; the gap is usually customer service training + documentation.
Cross-border data flows
For Indian D2C brands selling to GCC or international customers, the customer's data may flow to GCC payment processors, GCC tax authorities, GCC fulfilment partners. DPDP requires lawful basis + adequate safeguards for these transfers. The pattern: a documented data flow map + contractual safeguards with each transfer recipient + customer consent where applicable.
Reconciliation: where compliance lives or dies
Three reconciliation pairs run weekly:
| Pair | What you reconcile | Where mismatch hits |
|---|---|---|
| Shopify orders vs accounting invoices | Every paid order has an invoice; every invoice ties to a paid order | Tax under-paid (missing invoice) or over-paid (phantom invoice) |
| Accounting invoices vs IRP IRN log | Every invoice above threshold has an IRN | Non-compliance notices from GSTN |
| Accounting GSTR-1 vs GSTN-side GSTR-2B (vendor side) | Your reported supplies match recipients' reported purchases | ITC mismatches, recipient claim disputes |
Weekly review owned by the finance lead, automated with anomaly alerts (any unreconciled order older than 7 days triggers escalation), and audited quarterly.
What does an automated GST workflow actually look like at scale?
For a Shopify brand at Rs 75 crore ARR processing 30,000-50,000 orders per month:
- Shopify webhook fires on order_paid
- Middleware (Zoho Flow / Make / custom) pushes the order to Zoho Books within 30 seconds
- Zoho Books generates the invoice, sequences the invoice number, computes IGST or CGST + SGST split
- For orders above Rs 5,000 (or all B2B), Zoho Books calls IRP API, receives IRN + QR
- Invoice PDF (with IRN + QR) emails to the customer within 2 minutes of order
- End of month: GSTR-1 auto-populates from IRP data; finance team reviews exceptions; files by 11th
- End of month + 9 days: GSTR-3B auto-populates from GSTR-1 + GSTR-2B; finance team reconciles ITC; files by 20th
The whole pipeline runs without manual touch under normal conditions. Manual review happens at exception handling, monthly close, and quarterly audit prep.
Production checklist
For a Shopify D2C at Rs 25+ crore ARR moving to fully automated GST workflow:
- Accounting system selected against the criteria above (default Zoho Books for mid-market, NetSuite above Rs 100 crore)
- Shopify-to-accounting integration validated full-scope (order_paid webhook to invoice within 30 seconds)
- Invoice number sequencing per GSTIN per year locked, no manual numbering
- HSN code master maintained in the catalog (PIM-driven if you have one)
- E-invoicing IRP integration tested + production-validated, fallback retry queue active
- DPDP data minimisation audit completed; only required fields flow to invoices
- Retention policy documented per data type (6 years for GST records; shorter for marketing PII)
- Reconciliation pairs running weekly with automated anomaly alerts
- GSTR-1 monthly filing automated, exceptions reviewed by 9th of following month
- GSTR-3B monthly filing automated, ITC reconciled by 18th of following month
- Quarterly audit prep: invoices + IRN logs + GSTR filings packaged for CA review
- CFO + tax-advisor governance review quarterly; risk register maintained
References + linked context
- Dcrayons glossary: oms, buy-box
- Dcrayons commerce reference architectures: Enterprise D2C on Shopify, Enterprise Shopify Plus
- Dcrayons subscription architecture: Recharge vs Stay AI vs custom
GST compliance is the part of the operating motion that gets less attention than it should until the day a notice arrives. If your Shopify D2C is hitting reconciliation pain, IRP integration questions, or DPDP migration uncertainty, reach out via the contact form for a 30-minute review of your current setup.
