Start with operating decisions, not the install button
The software can connect Shopify and TallyPrime, but the merchant still needs to decide what each system owns. Make those decisions before copying a production order.
Write down the intended behavior for these workflows:
- Which Shopify orders are eligible to become Tally Sales Vouchers?
- Which Tally company receives them?
- Which ledgers represent sales, GST, shipping, discounts, round-off, parties, and refunds?
- Does Shopify or Tally own each product field?
- Which active Shopify location corresponds to the supported Tally inventory context?
- Who resolves mapping failures, uncertain voucher writes, and inventory conflicts?
A connector cannot safely invent these answers from similar names.
Prepare the Shopify, Windows, and Tally environments
Use a Shopify account with permission to install and authorize Tally Connect. Product write access is needed only when the team plans to create or update Shopify products from reviewed Tally data.
The local connector requires a supported Windows 10 or Windows 11 computer. The same signed-in Windows user should run TallyPrime, install the Agent, and own the scheduled Agent task. Keep that computer available during discovery and any live work that needs TallyPrime.
In TallyPrime, prepare a disposable test company before experimenting with real voucher writes. Enable local HTTP/XML access on port 9000 and open the intended company. Do not expose that port to the internet.
Pair the private Windows Agent
Open Tally Connect → Setup inside Shopify Admin and generate a one-time pairing code. On the Tally computer, run the official Tally Connect Setup application and enter the code before it expires.
The setup flow checks three boundaries before pairing finishes:
- the Tally Connect cloud is reachable;
- TallyPrime responds on the local loopback address; and
- a company is actually loaded for the same Windows user.
After pairing, return to Shopify Admin and confirm the device shows a fresh heartbeat. If it appears offline, repair connectivity before moving to mappings.
Bind the exact Tally company
Select Discover companies while the intended company is open in TallyPrime. Choose a company from the discovered result instead of typing a name from memory.
Tally Connect binds both the company name and GUID. It also requires state and GST identity for the current accounting workflow. If the identity is missing or invalid, correct the company in TallyPrime and discover again.
This binding protects later commands. If a different company is loaded when a write arrives, the Agent refuses the operation rather than posting into the wrong books.
Discover masters before mapping them
Run master discovery after binding the company. The Agent reads the relevant Tally ledgers, godowns, Stock Items, Stock Groups, and units supported by the current compatibility path.
Mappings should point to discovered records, not guessed names. Refresh masters after important changes in TallyPrime so the connector can invalidate stale evidence rather than continuing with an outdated view.
For large catalogs, discovery is a bounded background workflow with visible progress. Keep TallyPrime available and avoid changing the source catalog during the scan.
Map accounting ledgers deliberately
Open Mappings → Accounting ledgers and select the Tally ledger used for each required accounting role. The exact set depends on the order, tax, shipping, discount, and refund behavior being used.
Do not map several meanings to a convenient catch-all ledger just to make the readiness check green. Ask the person responsible for the books how each amount should appear in reports and GST review.
Tally Connect calculates money using integer paise and blocks a voucher when its accounting shape cannot be balanced with the configured mappings.
Confirm product identities and ownership
Every Shopify variant that participates in order or inventory work needs a confirmed mapping to a Tally Stock Item. Review the item identity, SKU, base unit, and conversion ratio.
Product sync is review-driven in both directions:
- Shopify-to-Tally changes show the source, current discovered Tally values, and proposed values before approval.
- Tally-to-Shopify discovery can prepare a new Shopify product as a draft or propose changes to an existing mapped product.
- Missing or archived records follow explicit lifecycle choices rather than being deleted automatically.
Use field ownership to decide which system may update title, SKU, HSN, group, unit, and other supported fields. Ownership is a policy, not a bulk-copy button.
Map the supported inventory location
Choose the active Shopify location and the discovered Tally godown used by the current inventory workflow. Tally Connect's current automatic Tally closing balance read is aggregate, so readiness requires exactly one matching confirmed location mapping and proof of the supported single-godown configuration.
If the merchant needs multi-godown automatic inventory, keep the feature paused until location-specific Tally behavior is implemented and proven. Website copy and sales promises should preserve this boundary.
Establish reviewed inventory baselines
For each mapped product, compare Shopify physical stock with the Tally closing quantity and approve the shared starting point. Confirm any unit conversion with values that produce whole units in both systems.
Inventory automation remains paused when a baseline is missing, stale, or invalidated by a company, mapping, compatibility, or unit change. This prevents old evidence from silently authorizing new writes.
Run previews and the approved setup test
Before enabling live writes, preview representative paid orders. Include discount, shipping, tax, multiple line, and intentionally blocked examples.
The separately approved setup test creates a real small-value voucher in the selected disposable company. Run it only when the test company is open. Inspect the voucher in TallyPrime and confirm that Tally Connect records verified evidence.
Do not use the setup test as general permission to post production orders. Move back to the intended production company, discover and bind it, refresh masters, and re-check mappings.
Enable one workflow at a time
Turn on live behavior gradually:
- Start with order previews.
- Enable Sales Voucher writes after the accounting test passes.
- Watch initial live orders and reconcile totals in TallyPrime.
- Confirm refund Credit Note behavior with a controlled example.
- Approve a small product batch before expanding catalog work.
- Enable inventory only after every participating pair has a verified baseline.
Changing a critical identity or mapping should pause dependent automation until readiness is re-established.
Give daily exceptions an owner
A successful launch still needs a short operating routine. Someone should review Agent heartbeat, waiting work, failed commands, uncertain writes, product review rows, stale baselines, and inventory conflicts.
The owner does not need to watch every successful sync. They need a clear path for exceptions:
- fix the source data or mapping before retrying a safe failure;
- check TallyPrime before resolving an uncertain voucher write;
- choose a source of truth for an inventory conflict; and
- share command IDs and redacted diagnostics with support.
Start with the requirements guide, complete the setup checklist, and use the go-live guide for the final transition.