In this guide 7 sections
Connecting Shopify to Tally means turning orders, refunds and payouts into vouchers. Decide first whether you post each order or a daily summary, then map taxes, ledgers and stock items. Shopify tells you not to rely on webhooks alone, so add a periodic job that fetches orders and compares totals.
Decide what Tally needs to see
Many stores do not need every order in Tally. A daily sales summary with tax split, refunds and fees may be enough for the books, while order detail stays in Shopify.
Post each order as a voucher when you need customer-wise ledgers, GST invoices tied to individual buyers or item-level stock movement in Tally.
Ask your accountant which level they want first. Changing it later means reposting history.
Map items, taxes and ledgers
Every Shopify product variant needs a matching stock item in Tally, or a rule that groups them. Unmatched SKUs are the most common reason a sync stops.
Taxes need their own mapping. Shopify reports tax lines on an order, and the integration must choose the right GST ledger and place of supply. Check the rate and the treatment with your accountant, not with the developer.
Shipping, discounts and gateway fees each need a ledger. Without them the voucher will not balance.
- Variant SKU to Tally stock item
- Tax line to GST ledger
- Shipping and discount ledgers
- Gateway fee and payout bank ledgers
Refunds, returns and payouts
A refund is a separate event. It should post as a credit note or sales return linked to the original order, not as an edit.
Payouts are where books and bank statements disagree. The gateway pays a net amount after fees and holdbacks, so one bank credit may cover many orders. Record the payout as its own entry and clear the order receivables against it.
For cash-on-delivery orders, the courier’s remittance arrives later. Treat it as a separate receipt too.
How the connection actually runs
Shopify can send webhooks when an order is created or changed. Its developer documentation says delivery is not always assured and ordering is not assured either, so duplicates and gaps will happen.
The same documentation recommends reconciliation jobs that fetch changed records through the API periodically. Build one: fetch orders updated since the last run and compare with what was posted.
On the Tally side, a middleware program posts XML to Tally’s HTTP server. Tally’s help pages describe that gateway, which is off until you switch it on in the configuration.
Test before you trust it
Run the sync on a copy of the company file. Post a week of orders, then compare totals by day against the Shopify sales report and the gateway statement.
Keep a failure log that someone reads. An order that fails to post should raise a visible alert, not wait silently.
Plan for Tally being closed or the machine being off. Queue the vouchers and retry in order.
Shopify to Tally mapping sheet
A three-tab sheet. The first tab lists variants with SKU and Tally stock item. The second lists tax, shipping, discount and fee lines with their Tally ledgers. The third lists payout and refund scenarios with the voucher type, date rule and who approves exceptions.
Open a blank worksheet to printQuestions owners ask
Should every Shopify order become a Tally voucher?
Not always. Daily summaries work for many stores. Post each order when you need customer-wise ledgers or item-level stock in Tally.
Do webhooks alone keep Tally in sync?
No. Shopify says delivery is not always assured, so schedule a job that fetches recently updated orders and compares them with what you posted.
Where do payment gateway fees go?
To an expense ledger you create for them. The payout then books the net amount to the bank, and the fee clears the difference.
Is a ready-made connector better than a custom one?
Often yes for a standard store. Custom work makes sense when your tax mapping, bundles or multi-warehouse stock do not fit a connector.
Sources
- TallyPrime Help: Getting Started with Tally Integrations — verified 8 Nov 2026
- TallyPrime Help: XML Integration — verified 8 Nov 2026
- Shopify developer docs: About webhooks — verified 8 Nov 2026