Online Orders Not Syncing to Tally or ERP: Causes

Description

Troubleshooting Online orders not syncing to Tally or your ERP

Take one order that failed and compare it, field by field, with what the accounting side expects. The usual causes are a product, ledger or tax rate that does not exist on the other side, a rounding difference of a few paise, or the same order sent twice. If nothing arrives at all, check that Tally is open, the login is valid and the store's API version has not changed.

Get a technical assessment Last updated 2 October 2026

What the failure looks like

"Tally" on this page means TallyPrime, the accounting software. The same causes apply to any ERP or accounting package that receives orders from an online store.

Symptom

Look first at

Some orders arrive, some do not

Mapping (cause 1) and tax (cause 2)

Orders arrive with totals that are off by a small amount

Tax and rounding (cause 2)

The same order appears twice

Duplicate handling (cause 3)

Cancelled or refunded orders still show as sales

Duplicate handling and edits (cause 3)

Nothing arrives at certain hours

Connectivity (cause 4)

Nothing has arrived since a particular day

Credentials (cause 5) or an API change (cause 6)

Causes, in the order to check them

The first three can be confirmed from a single failed order, without technical access. Start there.

1. Mapping: something on the order has no match

Every order refers to things the accounting side must already know: each product, the customer or a default sales ledger, the tax ledgers, the unit of measure, the warehouse. A product added to the store last week with no matching stock item, or a code that differs by one character, is enough to make that order fail while every other order succeeds.

Check: open one failed order. For each line, find the product in the accounting software using the exact code the store sends. Then do the same for shipping charges, discounts and payment method.

2. Tax and rounding

The store and the accounting software can both be right and still disagree. A store often calculates tax on each line and rounds each line; accounting may calculate on the invoice total. Tax-inclusive prices, discounts spread across lines and taxed shipping all widen the gap. An accounting voucher has to balance exactly, so a difference of a few paise is enough for it to be refused or posted with an unexplained round-off. Interstate orders add a second version of this: the tax type depends on where the goods are going, so a wrong or missing state on the address selects the wrong ledgers.

Check: recalculate one failed order by hand, the way your accountant would. If your total differs from the store's by less than a rupee, this is the cause.

3. Duplicates and later changes

Stores resend. Shopify retries a failed webhook up to eight times in a four-hour period, and its documentation says an app may receive the same webhook more than once. A sync that creates a voucher every time it hears about an order will eventually create two. The opposite fault is as common: an order is edited, cancelled or refunded after it was posted, and the accounts never hear.

Check: search the accounts for the store's order number. More than one voucher for the same number means duplicates are not being detected. Then pick one refunded order and see whether a credit note exists.

4. Connectivity: the other side was not listening

A cloud store is always on. Accounting software installed on an office computer is not. Tally's integration guide lists the conditions: TallyPrime must be running, on the configured port (its example is 9000), with at least one company loaded. A computer that sleeps, a different company left open, or a firewall that blocks the port all stop the sync without any error on the store's side.

Check: note the times of the failed orders. Failures clustered at night, on Sundays or during a power cut point here.

5. Credentials and permissions

An API token can stop working when the app it belongs to is reinstalled, when the account it was issued to is removed, or when someone changes a password or rotates the key. A token can also be valid but lack permission for one thing, such as reading refunds.

Check: ask what changed on the day the failures began: a reinstalled app, a changed password, or a member of staff who left.

6. The API version changed

Platforms retire old versions of their API . As of October 2026, Shopify releases a new version every three months, supports each stable version for at least twelve months, and answers requests for a retired version with the oldest version it still supports. A connector nobody has updated can therefore start receiving fields in a shape it does not expect.

Check: if failures began on or just after the first day of January, April, July or October, ask whoever maintains the connector which API version it requests.

What a reliable sync needs

Whether you buy a connector or have one built, ask for these five things:

One reference per order. The store's order number travels with every voucher, so a repeat is recognised and skipped.

A queue with retries. If the accounts are unreachable, the order waits and is tried again. It is not dropped.

A daily reconciliation. A scheduled job compares the count and total of orders in the store with the vouchers posted, and lists the differences. Shopify itself recommends this, because deliveries can be missed.

Errors a person can read. "Stock item TSHIRT-BLU-M not found" in a screen the accounts team can open, not in a server log.

A mapping screen. New products, tax rates and payment methods can be matched without a developer.

WavX builds integrations this way; see Shopify to Tally integration, Tally integration and API and system integration services.

When you do not need a developer

If the cause is mapping, tax settings or a login, the fix is usually in the connector's own settings or with its support team, and costs nothing. If you post fewer than a handful of orders a day, a daily export from the store and an import by your accountant may be cheaper than any integration.

When to get help

Get help when the same cause keeps returning after you fix it, when you cannot see why an order failed at all, or when the accounts team spends time every day repairing entries by hand. Have ready: two failed orders and two that worked, the name and version of the connector, and the date the trouble began.

Frequently asked questions

Why do some orders sync and others not?

Because the failure is in the data of those orders, not in the connection. Compare a failed order with one that worked: the failed one usually contains a new product, a discount, a different state or a tax rate that the accounting side has no match for.

Why did the sync stop completely on one day?

Look for something that changed that day: a password or API token, the computer that runs Tally, a firewall or antivirus update, or a new API version on the store's side. Shopify, for example, releases a new API version on the first day of each quarter.

Can missed orders be recovered?

Yes. The orders still exist in the store, so they can be fetched again through its API for any date range and posted to the accounts. Before re-sending, make sure the sync can recognise an order it has already posted, or the recovery creates duplicates.

Do we need a custom integration, or will a ready-made connector do?

A ready-made connector is the right choice when your orders are simple: standard GST rates, one warehouse, no bundles, no partial refunds. A custom integration is worth it when the connector cannot express your mapping, or when failures have to be visible to the accounts team and retried without a developer.

Sources

TallyHelp: Pre-requisites for integrations · read 2 October 2026

TallyHelp: XML integration · read 2 October 2026

Shopify developer documentation: API versioning · read 2 October 2026

Shopify developer documentation: Troubleshoot webhooks · read 2 October 2026

Shopify developer documentation: Deliver webhooks through HTTPS · read 2 October 2026

Related

Shopify integrations

What is a webhook?

What is an API?

Build your own software — your way, your pricing.

WavX Solutions is here to create your own software in a fully custom way, built exactly how you work — with a pricing model that fits your business. Connect now and let's build it.

Contact Now helpwavx@gmail.com