Tax is where order sync usually breaks
Most of an order maps cleanly between Shopify and Zoho. A line item is a line item. A customer is a contact. Tax is the exception, because the two systems describe it differently.
Shopify records tax as a title and a rate on each line: VAT at 20%, GST at 5%, or CGST at 9% plus SGST at 9%. Zoho wants a specific tax record from your organisation's tax list, and for some regions a tax group or a tax with a particular type. If the connector guesses, you get documents with the right total and the wrong tax code, which is exactly the kind of error that surfaces at filing time.
Zync gives you a mapping table so the choice is yours, plus an auto-detect step so building the table takes a minute rather than an afternoon. This guide covers both, with the GST and VAT cases spelled out.
Two ways the app can pick a Zoho tax
There are two behaviours, and it helps to know which one you are relying on.
The first is matching by percentage. With no mappings at all, the app looks through your Zoho taxes for one with the same percentage as the Shopify tax, and uses it. If several qualify, it prefers a plain tax over a GST-specific one. If none exists, it creates a tax at that rate. This is how the app has always worked, and it is still what happens until you map something. The older write-up on automatic rate matching describes it.
The second is explicit mapping. You tell the app that a given Shopify tax becomes a given Zoho tax, and it stops guessing. This is what you want as soon as two Zoho taxes share a rate, or the tax type matters for your returns.
Both live under Orders, on the Documents & Accounting tab, in the Tax mapping section. Tax sync as a whole is the Tax checkbox under Order Settings. If that is unticked, no tax is sent to Zoho and the mapping section tells you so.
Start with auto-detect
Click Auto-detect from recent orders. The app reads the taxes that actually appear on your recent Shopify orders, on line items and on shipping, and loads your Zoho tax list. For each Shopify tax it finds, it suggests the Zoho tax with the same rate and adds a row to the table. When several Zoho taxes share that rate, it prefers one whose name resembles the Shopify tax title.
Three things to know about how it behaves:
- It only adds rows for taxes that have no row yet. Rows already in the table are left as they are, so it is safe to run again later.
- It works from real orders, so a tax you have never charged will not appear. Add those by hand.
- If no Zoho tax has the same rate as a Shopify tax, you get a warning naming the tax and its rate, with the instruction to add the tax in Zoho Books under Settings → Taxes, then run auto-detect again.
That warning is the useful part. It tells you about a gap in your Zoho setup before an order hits it.
Reading the mapping table
The table has four columns: Shopify tax, Rate, Zoho tax, and Fallback.
- Shopify tax is the title exactly as Shopify reports it.
- Rate is the percentage. It can show as any rate, which means the row matches that title whatever the percentage.
- Zoho tax is a dropdown of your Zoho taxes, each shown with its percentage.
- Fallback is a radio button. One row at most can be the fallback.
To add a row by hand, type the Shopify tax title, enter the rate as a percentage or leave it empty to match any rate, pick the Zoho tax, and click Add mapping. Use Remove to delete a row.
When an order syncs, the app looks for a row in this order: the same title with the same rate, then the same title at any rate, then the fallback row. The first hit wins. That gives you a tidy way to handle a tax whose rate varies: one row with the rate left empty covers every rate under that title.
GST: CGST + SGST and tax groups
Indian stores are the clearest example of why explicit mapping matters. An intra-state sale carries two taxes on the same line, CGST and SGST, each at half the total rate. An inter-state sale carries a single IGST at the full rate.
Zync treats several taxes on one line as one combination. The titles are joined with a plus sign and the rates are added, so a line with CGST at 9% and SGST at 9% appears in the table as CGST + SGST at 18%. You map the combination once, usually to a Zoho tax group that contains both components. Every order line with that combination then uses the group.
A typical GST table ends up with rows like these:
CGST + SGSTat 18% mapped to your GST18 tax group.IGSTat 18% mapped to your IGST18 tax.CGST + SGSTat 12% andIGSTat 12% for the lower slab, and so on for each rate you sell at.
If you type a combination by hand, use the same form, for example CGST + SGST. Auto-detect fills these in from real orders, which avoids typos.
VAT and single-rate setups
For VAT and sales tax, the table is usually short. A UK store might have VAT at 20% mapped to its standard rate tax and VAT at 5% mapped to its reduced rate tax. If you sell into several countries and Shopify reports each country's VAT under its own title, each one gets its own row and can point at its own Zoho tax.
Where the title is the same and only the rate differs, you have a choice. Map each rate to its own Zoho tax if your Zoho organisation separates them, or add one row with the rate left empty if a single Zoho tax should cover them all.
Shipping tax, zero tax, and inclusive pricing
Three options under the table deal with the cases that cause the most confusion.
- Send the tax Shopify charged on shipping. Off by default. Tick it if shipping is taxable for you and you want the shipping charge in Zoho to carry its tax.
- Send an explicit zero tax on untaxed lines. Turn this on if Zoho adds the item's own tax to orders Shopify charged none on. A Zoho zero-rate tax picker appears, and that tax is sent on every untaxed line so Zoho has nothing to fill in.
- Tax-inclusive prices need no setting. If the Shopify order was priced with tax included, the Zoho document is marked the same way.
What happens to an unmapped tax
One checkbox decides this: When a tax is not mapped, pick or create a Zoho tax with the same percentage. It is ticked by default.
With it ticked, an unmapped tax falls back to matching by percentage, so orders keep flowing while you finish the table. With it unticked, an unmapped tax is left off the line and the reason is written to the job log. That stricter setting suits finance teams who would rather see a document without tax, and fix it, than have the app create a new tax record in Zoho without being asked.
A fallback row sits between the two. If one row is marked as Fallback, any tax without a row of its own uses that row's Zoho tax, and the percentage matching never comes into play.
Check your work before it counts
You do not have to wait for live orders to find out whether the table is right.
- Run a Dry run from the Backfill tab over a recent date range. It writes what would happen for each order to Logs and creates nothing in Zoho. See the backfill guide.
- After real orders have synced, open Reconcile and compare a date range. Tax problems tend to show up under Amount differences, which the page itself describes as usually tax, rounding or an order edited after it synced. The routine is covered in reconciling before month-end.
Refunds use the same mapping. A credit note line carries the same Zoho tax as the order line it reverses, so a correct table keeps refund credit notes correct too.
Next step
Open Orders, go to Documents & Accounting, and click Auto-detect from recent orders. Resolve any warning about a missing Zoho tax, decide whether you want a fallback row, and choose how unmapped taxes should behave. The complete reference is in the tax mapping documentation, and the tax mapping overview shows how it fits into order sync.