Why is Fast WMS not syncing to Tally?

The usual causes are Tally not being open, its ODBC/gateway connection being switched off, a missing store-to-godown mapping, or ledger and voucher settings that don't match. Fast WMS posts GRNs as purchase receipts and dispatches as sales vouchers, so both systems must be running and mapped for the sync to complete.

Does Tally have to be open for Fast WMS to sync?

Yes. Tally must be running with the correct company loaded and its ODBC/gateway server enabled (typically on port 9000). If Tally is closed or the port is blocked, Fast WMS cannot push transactions and they stay queued until the connection is available.

Will a failed Tally sync lose my warehouse data?

No. Warehouse transactions are recorded in Fast WMS regardless of Tally's status. A sync failure only delays the accounting posting; once Tally is reachable and correctly mapped, the pending transactions post without any loss.

Fixing Tally Not Syncing Errors

Fast WMS pushes warehouse activity into Tally automatically — a GRN becomes a purchase receipt, a dispatch becomes a sales voucher, and transfers or adjustments become stock journals. When that stops working, your warehouse data is still safe in Fast WMS; only the accounting posting is delayed. Here are the five causes we see most, and how to clear each.

Your stock is not at riskEvery GRN, pick, and dispatch is committed in Fast WMS whether or not Tally is reachable. A sync error is an accounting-posting delay, not lost inventory — once the link is restored, pending vouchers post.

The five most common causes

Tally isn't open. Tally must be running with the correct company loaded. If it is closed, there is nothing to receive the voucher.
ODBC / gateway is off. Tally's connectivity (typically port 9000) must be enabled and not blocked by a firewall.
Store-to-godown mapping missing. Each Fast WMS store must map to a Tally godown. An unmapped store has nowhere to post.
Ledger or voucher-type mismatch. The purchase, sales, or stock-journal voucher types and ledgers named in the mapping must exist in Tally, spelt identically.
Tax or item mismatch. A GST rate or item name that exists in Fast WMS but not in Tally can make a voucher fail validation.

Step-by-step fixes

Confirm Tally is open with the right company, and its ODBC/gateway server is running.
From the Fast WMS server, check the port is reachable and not firewalled.
Open your integration settings and verify every active store maps to a valid Tally godown.
Check the voucher types and ledgers in the mapping exist in Tally with matching names.
Reconcile item names and GST rates between the two systems for the failing document.
Re-trigger the sync for the pending transactions and confirm the voucher appears in Tally.

Watch for silent name mismatchesA godown, ledger, or item renamed in Tally but not updated in the Fast WMS mapping is the most common hidden cause. The link looks configured but every post fails validation. Keep both name lists in step.

For how the integration is designed and what maps to what, see Fast WMS Tally integration. Running SAP or Oracle instead of, or alongside, Tally? See Connecting to SAP or Oracle.

Sync still failing?

Our team can screen-share and fix your Tally mapping in one session.

Contact support