Shopify, Bizmitra and Tally
Shopify and TallyPrime never talk to each other. Every claim of "Shopify to Tally sync" is really a claim about something sitting in between. In this architecture that something is Bizmitra, and this guide is explicit about which hop does what.
Last reviewed against the implementation on
At a glance
- Architecture
- Shopify → Bizmitra → Tally
- Direct Shopify ↔ Tally
- Does not exist
- What is pushed
- ERP documents, not store orders
- Last hop
- The Bizmitra Tally Connector
The actual shape
Shopify and TallyPrime have no connection to each other. Nothing in the Shopify integration knows that Tally exists, and nothing in the Tally connector knows that Shopify exists. They are joined by Bizmitra sitting in the middle, and every honest description of this architecture has three boxes, not two.
Orders, payments and refunds happen here. This is the system of record for all three.
Turns them into ERP documents — sales orders, invoices, receipts, credit notes — with GST, HSN codes and your own voucher numbering.
A Bizmitra TDL add-on loaded into your own TallyPrime handles the exchange with Bizmitra.
Your accountant opens the same company they always have.
What this is not
This is not Shopify ↔ Tally synchronization. Tally does not receive your Shopify orders; it receives the accounting documents Bizmitra raised from them. If a Shopify order never became an invoice in Bizmitra, there is nothing for Tally to get.
Why there is a middle step
It is not an architectural compromise. A Shopify order is not an accounting document and cannot be posted into Tally as one — it has no voucher number in your financial year, no party ledger, no GST breakdown against a sales account, no HSN codes, and no stock movement.
Something has to turn a line like "2 × Blue Kurta, ₹4,720, paid by card" into a numbered sales invoice against a ledger with the tax split out correctly. That is the work, and it is what Bizmitra does before Tally is involved at all. Anything claiming to skip that step is either doing it invisibly somewhere, or not doing it.
What gets pushed
Bizmitra can push these voucher families to Tally. The ones a Shopify store actually generates are marked.
| Voucher | From a Shopify order? |
|---|---|
| Sales invoice | Yes — the invoice raised from the order |
| Receipt | Yes — the receipt posted when the order is paid |
| Credit note | Yes — posted when a refund is created |
| Debit note | No — purchase-side |
| Purchase | No — purchase-side |
| Payment | No — money out, not store-generated |
| Journal | No — manual adjustments |
| Contra | No — internal transfers |
So the Shopify-driven path into Tally is three documents: the invoice, the receipt that settles it, and the credit note if money goes back. Those map exactly onto what an order becomes and what a refund becomes.
How the push works
Bizmitra builds the Tally-ready payload from the stored voucher and hands it to the sync bridge. A Bizmitra TDL add-on loaded into your TallyPrime handles the Tally-specific part on your own machine, so you are not generating Tally XML yourself and not maintaining any Tally scripting of your own.
Each voucher family has its own path on the bridge; the voucher body itself is forwarded as-is. That is a deliberate property: a voucher pulled out of Tally can be pushed straight back without being reshaped in between.
Setup is per Tally company
The add-on is loaded into the TallyPrime company you want the store's sales to land in, and paired with the matching Bizmitra company. That pairing is what decides which books a Shopify order ends up in — worth getting right before the first sync rather than after.
What happens when Tally is unreachable
Tally runs on a desktop. Desktops get switched off, and Tally is often closed overnight — so "the destination is unavailable" is a normal operating state here, not an exception.
A push that the bridge does not accept raises an error rather than reporting success, so the calling operation can roll back instead of recording a voucher in Bizmitra that never reached Tally. The documents remain in Bizmitra, which is the point of the middle step: your books are complete in Bizmitra whether or not Tally is switched on. Tally catches up.
The practical consequence
Shopify orders are never waiting on your accountant's machine being turned on. The Shopify → Bizmitra half runs continuously; the Bizmitra → Tally half runs when Tally is available.
What this is not
- Not a Tally-to-Shopify path. Editing a voucher in Tally does not change your storefront, your Bizmitra stock, or the order.
- Not automatic bookkeeping. Bizmitra raises the documents a store order implies. It does not reconcile your Shopify payouts, post your gateway fees, or close your books.
- Not a replacement for your accountant. It removes the re-typing, not the judgement.