Frequently asked questions

Not for Zoho Books or Ledgeree Books: both run in the cloud. For Tally Prime you install a small Ledgeree Agent on the PC that runs Tally, because Tally has no cloud API.

Download it from the Tally Prime page at ledgeree.com/sync-shopify-to-tally, or from the link in the app's connect step. It is a small Windows program that runs on the PC where Tally Prime runs. If the download is blocked or you need help installing, email support@ledgeree.com.

Tally Prime with its local XML/HTTP interface enabled, running on a Windows machine the agent can reach. That covers a desktop install, and Tally on Cloud or AWS cloud access where the agent can run next to it. Multiple companies and financial-year rollovers are handled by company-name patterns.

Ledgeree reads the data centre of your organisation from Zoho during authorisation and uses the matching API address. If you are unsure whether your region or plan has the API access Ledgeree needs, write to us before connecting.

Yes. Choose Ledgeree Books to begin, or skip the connection step and finish it later from Settings.

Yes. The wizard uses the same screens as Settings, so nothing you chose is locked in.

Write to support@ledgeree.com first. Vouchers already posted stay where they are, and the start date needs to be set so the same fulfilments are not posted twice.

Posting follows fulfilment, not payment. Fulfilments are aggregated per day and posted at the daily start time you set in Settings > Sync schedule. B2B and export orders post per fulfilment instead of in the daily aggregate. Ledgeree does not promise instant sync.

Revenue is booked when goods ship. The order is picked up when it is fulfilled.

A refund after shipment posts as its own sales return (Tally) or credit note (Zoho) on its own date. It is never silently netted against the original sale, so gross sales and returns stay visible. Return shipping charges can post as a separate GST-inclusive line.

Historical backfill is capped at the last 60 days, which is Shopify's standard order-access window for apps. See Settings > Historical backfill for what is available in your store.

Every posting carries a stable identity. If your ERP already holds the document, Ledgeree records the existing result instead of posting again, and a retry never creates a duplicate.

Temporary problems (Tally offline, a rate limit, a network error) are retried automatically on the schedule you set. Problems that need your decision, such as a missing mapping, pause posting for the affected dates and show a banner with a Resume sync button. Capture continues during ordinary posting-error recovery. Plan-limit pauses have a separate timeline, explained under billing below.

Yes. Gateways and COD couriers can each get their own clearing ledger, mixed-payment orders are split across them, and gift-card sales and redemptions are accounted for as liabilities. Refunds reverse the clearing accounts that actually funded them.

No. It prepares accurate sales records, a running GST view and downloadable data for your accountant's GSTR-1 and GSTR-3B work. It does not generate or file complete returns.

No. Ledgeree covers the sales side: fulfilments, refunds and related adjustments.

No. It keeps gateway and courier receivables in separate clearing ledgers, which makes settlement review easier, but matching bank and payout statements is outside its scope.

No. It connects Shopify activity to the system you already use.

Every plan starts with 5 free days after installation. Billing runs through Shopify, so you approve a recurring charge in Shopify and can cancel from the Billing screen inside the app or by uninstalling.

Usage counts shipments fulfilled in the last 30 days. An order shipped in two fulfillments counts as two shipments. Historical recovery counts against its original fulfillment dates, so bringing older orders into your books does not inflate current-period usage.

You get a warning at 80% of your shipment allowance, and posting continues up to 120%, giving you 20% headroom. Above 120%, posting pauses. Choose a higher-capacity plan that covers your usage to resume; falling usage or a new billing cycle does not release this pause. New orders continue to be captured for the first 60 days of the pause.

Upgrade within the first 30 days of a plan-limit pause and there is no catch-up charge. After a completed 30-day paused period, a one-time catch-up charge may apply for up to the first two periods: the price of the plan that period required, allowing the 20% headroom, less the plan already paid for. The amount is quoted for your approval through Shopify before posting resumes. There are no per-shipment overage charges.

At 60 days of a plan-limit pause, new order capture stops. At 90 days, the subscription is scheduled for cancellation under the notification process. We send reminders to your configured contact email, with a Shopify store-email fallback. Upgrading promptly keeps your accounting moving; recovery after capture stops is limited to eligible Shopify history within 60 days.

When your subscription becomes cancelled, posting and capture stop. Store data is scheduled for deletion after 60 days, with reminders starting after 30 days. Resubscribing before deletion clears that countdown. Entries already posted to Tally or Zoho Books stay in your accounting system. See the privacy policy for the deletion process and retained erasure records.

It is priced at 50% of your base plan fee and gives per-SKU margin estimates from your own cost history. It is an operational estimate, not an accounting profit and loss statement.

No. Zoho access uses OAuth. The refresh credential is encrypted before it is stored, and you can revoke it from your Zoho account at any time.

No. The agent opens the connection from your PC outward. No public Tally port is required.

Posting stops immediately and session credentials are deleted. See the uninstall page for details, and the privacy policy for retention.

Use the privacy-request contact in the privacy policy, or write to support@ledgeree.com and we will route it.