Agent versions and compatibility
Understand why an online Agent can read successfully while writes remain blocked.
The current source requires Agent 0.5.0 or newer for the current write protocol. Shopify Sales Vouchers and Credit Notes require 0.5.1 or newer because they include verified delivery details. A heartbeat or successful discovery does not establish write readiness.
Current capability gates
| Capability | Version gate in the current application | Meaning |
|---|---|---|
| Product discovery support | 0.2.4+ | Includes corrected handling of Tally's reserved Primary group |
| Lease fencing | 0.2.3+ | Distinguishes successive command leases |
| Independent catalog snapshot proof | 0.2.6+ | Provides native-count and identity evidence for proof-gated scans |
| Current write protocol | 0.5.0+ | Required before an Agent may lease any write |
| GST voucher posting proof | 0.5.0+ | Adds the supported master and persisted line-level GST checks |
| Shopify delivery details | 0.5.1+ | Writes and verifies buyer/consignee delivery fields |
These are capability thresholds from the current code, not recommendations to install older versions or certification of a particular TallyPrime release. Other prerequisites still apply even when the version passes.
Older Agents during an upgrade
The cloud retains a limited compatibility path for structurally compatible read-only operations: company discovery, master discovery, Stock Item reads, stock reads, voucher reads, and health checks. It uses the older protocol envelope only for those allow-listed reads.
Older Agents cannot receive a new write through that path. Legacy discovery results also do not substitute for the current proof required to authorize lifecycle decisions. If discovery succeeds but write readiness asks for an update, complete the update instead of re-pairing or changing mappings to bypass the gate.
Upgrade checklist
- Pause automation and inspect any active or uncertain writes.
- Obtain the operator's approved Windows release.
- Follow Windows Agent operations for the configured update method. Automatic updates require explicit configuration.
- Restart as needed and confirm the version reported in Shopify Setup.
- Refresh masters and check the readiness messages again.
- Resume a controlled workflow and verify the result.
Private-pilot unsigned packages use a separate distribution path and do not have the production automatic-update configuration. Ask the operator for the matching approved package.
Version support versus TallyPrime proof
Passing the Agent version check does not prove support for every GST scenario, currency, catalog size, or TallyPrime release. Review Supported behavior and the release proof maintained by the app operator before enabling production workflows.