In short
- A good Shopify Tally integration moves four things: orders as sales vouchers, refunds and RTOs as credit notes, gateway and COD settlements as receipts, and fees as expenses with GST.
- Shopify does not produce a GST-compliant invoice on its own, so decide early whether invoices are generated in a Shopify app, in Tally or in a middleware layer.
- TallyPrime accepts data through XML over HTTP and, from TallyPrime 7.0, native JSON, which makes reliable automated posting possible.
- Ledger and tax mapping (state-wise CGST/SGST versus IGST, HSN, shipping and discounts) matters more than the choice of connector.
- Reconcile at settlement level using gateway UTRs so every rupee received in the bank can be traced back to Shopify orders.
A Shopify Tally integration should automatically turn Shopify orders into GST-correct sales vouchers, refunds and RTOs into credit notes, and payment gateway or COD settlements into receipts matched to those orders. Done well, your accounts team stops re-keying data and closes the books from reconciled figures instead of spreadsheets.
This guide covers what to sync, the integration options available as of September 2026, and the mapping decisions that make or break the setup.
- Sync four flows: sales, returns, settlements and fees.
- Decide where GST invoices are generated, because Shopify does not create them by itself.
- Use TallyPrime's XML or native JSON interface for reliable posting.
- Reconcile by settlement UTR, not by eyeballing daily totals.
What a Shopify to Tally integration needs to move
| Shopify or partner event | Tally entry | Key details |
|---|---|---|
| Order placed or fulfilled | Sales voucher (invoice) | Customer or cash ledger, HSN, tax split, shipping, discount |
| Refund, return or RTO | Credit note | Link to original invoice number, stock-in if received |
| Gateway settlement (Razorpay, Cashfree, PayU) | Receipt voucher | Settlement UTR, orders covered, fees and GST deducted |
| COD remittance from courier or aggregator | Receipt voucher | Remittance ID, AWBs covered, freight or COD charges deducted |
| Gateway and courier fees | Journal or purchase entry | Expense ledger plus input GST, subject to eligibility |
Most "Shopify to Tally" tools only handle the first row well. The real value, and most of the effort, sits in rows two to five.
Step 1: Decide where the GST invoice is created
Shopify's own help page on India GST states that it does not create a GST-compliant bill and recommends a local GST invoicing service or app (Shopify Help Center). You have three choices:
- Shopify invoice app: a GST invoicing app generates the customer invoice, and the integration posts the same invoice number and values to Tally.
- Tally as the source: the integration creates the sales voucher in Tally, and Tally's invoice becomes the legal document. This suits brands with a strong accounts team and more B2B orders.
- Middleware or OMS: an order management system or custom service generates invoices and pushes vouchers to Tally.
Whichever you choose, keep one invoice number series per GSTIN and make sure the number on the customer's PDF matches the voucher in Tally exactly.
Step 2: Get the ledger and tax mapping right
This is where most integrations fail quietly. Before any code is written, agree a mapping sheet with your CA covering:
- Sales ledgers: one per GST rate and supply type (intra-state and inter-state), or one sales ledger with tax classification, depending on how your Tally is set up.
- Tax ledgers: CGST and SGST for orders shipped within your state, IGST for other states. Place of supply comes from the shipping address state.
- HSN codes: Shopify stores HS codes in the product's shipping section, and its help page notes the field expects at least six digits; shorter codes can be held in metafields.
- Shipping and COD charges: decide whether these are separate income ledgers and how GST applies to them.
- Discounts: order-level discounts must be spread across line items so each tax rate is calculated on the discounted value.
- Customers: B2C orders usually go to a common cash or "Shopify customers" ledger; B2B orders with a GSTIN need their own party ledger.
Rates also changed recently. The 56th GST Council meeting moved most goods to 5% or 18% slabs, with a 40% special rate, from 22 September 2025, so check that your product tax overrides in Shopify and your stock item GST rates in Tally agree.
Step 3: Choose an integration method
| Option | Best for | Watch out for |
|---|---|---|
| Ready-made connector app | Simple catalogues, one GSTIN, mostly B2C | Limited returns and settlement handling, rigid mapping |
| OMS with Tally sync | Multi-channel brands (website plus marketplaces) | Cost, and Tally sync is often a secondary feature |
| Custom middleware | Brands with specific ledgers, multiple GSTINs or heavy COD | Needs someone to own monitoring and fixes |
Under the hood, all three talk to TallyPrime the same way. TallyPrime acts as an HTTP server (port 9000 by default) and accepts XML requests to import vouchers and masters, as documented in TallyHelp's XML integration guide. From TallyPrime 7.0, it also supports native JSON for importing and exporting data (TallyHelp). If your team is on an older release, XML still works fine.
A typical custom flow looks like this: a Shopify webhook fires on order fulfilment, the middleware validates and enriches the order (HSN, ledger, tax split), queues it, and posts the voucher to Tally. Failures go to an error log that the accounts team can see and retry. Shopify's own developer docs warn that webhook delivery is not guaranteed and recommend a reconciliation job as a fallback, so run a nightly check that every fulfilled order has a Tally voucher.
Step 4: Automate returns and RTO credit notes
Returns are messy because the money and the stock move at different times. Build separate rules for:
- Prepaid refunds: a Shopify refund event creates a credit note against the original invoice, and the refund appears as a deduction in a later gateway settlement.
- COD returns after delivery: the credit note is raised when the return is approved, and the refund is paid by bank transfer or UPI, so record that payment separately.
- RTOs: the parcel never reached the customer. Your accounting treatment depends on whether an invoice was issued at dispatch. Agree the approach with your CA, then automate it consistently.
Also bring stock back into the right godown in Tally only when the warehouse confirms receipt, not when the refund is issued.
Step 5: Reconcile settlements, not daily totals
Gateways settle in batches. Razorpay's standard domestic cycle is T+2 working days (Razorpay docs), and Cashfree and PayU document T+1 or T+2 cycles depending on configuration. Each settlement has a UTR and a list of payments, refunds and fees.
- Pull the settlement report or API data for each UTR.
- Match each payment ID to the Shopify order's transaction.
- Create one receipt voucher per settlement, crediting the customer or clearing ledger for the gross amount, debiting bank for the net amount and booking fees and GST separately.
- Flag anything unmatched: payments with no order, orders with no payment, or refunds in the wrong period.
COD remittances from couriers follow the same pattern using AWB numbers. We go deeper into this in our guide to payment gateway reconciliation in this series.
Worked example: a month of Shopify data in Tally
Take a hypothetical brand shipping 4,000 orders a month, 60% prepaid and 40% COD, with one GSTIN in Delhi. With order-level posting it creates about 4,000 sales vouchers, a few hundred credit notes for returns and RTOs, around 20 to 25 gateway receipt vouchers (one per settlement day per gateway) and a handful of COD remittance receipts. Without automation, that is days of data entry each month. With it, the accounts team reviews exceptions only, typically a small list of unmatched payments and edge-case refunds.
Don't forget B2B orders and e-invoicing
If your aggregate turnover is above the e-invoicing threshold, B2B orders need an IRN. TallyPrime can generate e-invoices and QR codes after the voucher is recorded and can send e-way bill details with them (TallyHelp). Route B2B Shopify orders (those with a buyer GSTIN) through this path so compliance happens automatically. Our companion guide on GST for Shopify sellers covers thresholds and settings in detail.
For a broader view of which finance and operations tasks to automate alongside Tally, see the Shopify automation stack for 2026.
Get a Shopify Tally integration that your CA trusts
The connector is the easy part. The hard part is mapping, returns logic, settlement matching and error handling that stand up at audit. TNM builds Shopify to Tally automations for Indian D2C brands, from mapping workshops with your accountant to monitored, retry-safe posting. Explore our Tally automation service to scope your setup.
Frequently asked questions
Tally Solutions does not publish a first-party Shopify app as far as we could verify. Integrations are built by third-party connector apps, OMS platforms or custom middleware that uses TallyPrime's XML or JSON interface. Evaluate any connector on ledger mapping, GST handling, returns support and error logging rather than on its feature list alone.
Order-level posting gives a clean audit trail, matches GST invoice numbers and makes reconciliation easier, but it creates many vouchers. Daily summary posting keeps Tally lighter but hides detail. Many D2C brands post B2B orders individually and B2C sales as order-level vouchers only if invoice numbering must match. Agree the approach with your CA before building.
An RTO order was never delivered, so treatment depends on whether an invoice was issued at dispatch. If it was, most accountants record a credit note and bring stock back into inventory when the parcel is received. If invoices are issued only on delivery, the order may simply be cancelled. Confirm the method with your CA so GST returns stay consistent.
Yes. TallyPrime has connected e-invoicing that generates the IRN and QR code after you record a sales voucher, and can send e-way bill details along with the e-invoice. This matters only if your aggregate turnover crosses the e-invoicing threshold and the order is B2B. Consumer orders do not need an IRN.
For live posting over HTTP, TallyPrime must be running with its HTTP server enabled and reachable from your middleware, often through a secure tunnel or an on-premise agent. If that is not practical, you can use file-based imports on a schedule instead. Both approaches work; the right one depends on how your accounts team runs Tally.
