Shopify GST accounting features, shown by workflow.

Shopify's checkout has no native GSTIN field -- Ledgeree reads it from a checkout note attribute, an order or company metafield, or Shopify's native B2B/Wholesale company (Shopify Plus), configurable per shop.

Customer names vary and typo across orders ("Acme Pvt Ltd" vs "ACME Private Limited") -- the one reliable identifier is the GSTIN, so party-ledger lookup is always keyed on it, checked before ever creating a new ledger.

The first order from a new B2B customer creates their dedicated ledger (name + GSTIN + state) on the fly -- idempotent, so a hundred repeat orders from the same customer never create a hundred ledgers.

B2B orders are excluded from the standard state-day gateway/website aggregate entirely and post against the customer's own ledger, preserving the GSTIN-linked party treatment needed for review.

Unlike the B2C daily aggregate, every B2B fulfillment gets its own voucher -- so a tax-credit invoice always maps to exactly one real shipment, never a blended multi-order total.

B2B sales and returns post to dedicated ledgers, kept separate from ordinary retail Sales/Sales Return -- your B2C and B2B revenue never mix in one account.

If auto-ledger-creation is switched off, a captured GSTIN is simply ignored and the order falls back to plain B2C -- a deliberate escape hatch, not a silent failure.

Any order shipping outside India is treated as an export -- no manual flagging per order.

Every line item is posted at 0% GST regardless of its normal domestic rate -- but only once a valid LUT (Letter of Undertaking) number is configured; without one, the export order is blocked (not silently posted at the wrong rate).

A LUT is filed per financial year and goes stale every April 1st. Ledgeree records which FY your LUT covers, blocks an export order whose FY doesn't match, and nudges you every January-March to file the next year's LUT before the current one expires.

Like B2B, export orders are never folded into a daily aggregate -- a Shipping Bill (customs) is issued per physical shipment, so one voucher always maps to exactly one shipping bill, never several blended together.

Kept out of your domestic Sales accounts entirely, same principle as B2B.

A Shipping Bill doesn't exist until customs actually clears the shipment, days after the order syncs -- so Ledgeree lets you record the Shipping Bill number, date, and port code against the already-posted voucher once you have them, for your Rule 46 compliance records.

When a customer is charged in a foreign currency, that currency and total are recorded alongside the INR figures your books actually need (already correctly converted by Shopify's own payment processing) -- so you have both figures on file without a manual note.

Don't want export orders synced at all? A single toggle excludes them from sync entirely, with no blocking errors generated for orders you've chosen to handle yourself.

If an order is returned before its shipment's daily aggregate has even posted, it's excluded before ever reaching your books -- no Sales entry, no credit note, no cleanup needed.

Posted as a separate return-date aggregate -- gross sales and returns stay visible on separate lines instead of being silently netted against the original entry.

Returns never reverse into the Sales account directly -- always their own ledger, so a glance at Sales alone never overstates true net revenue.

If your Tally instance is running in demo/educational mode, a voucher write is refused outright -- so a licensing gap gets caught immediately, not discovered later as vouchers that silently never actually saved.

A small local relay agent talks to your Tally Prime installation directly over your own network -- your ledger and voucher data reaches Tally without needing to pass through a third-party server that also has to read your books.

At 80% of your plan's shipment cap you get a warning; at 100%, new fulfillments are still captured and cached -- never dropped -- while sync pauses until you upgrade, then flushes through automatically in order.

A failed push retries automatically; if it keeps failing, sync pauses and the real ERP error message is logged -- not just "something went wrong."

A dedicated view compares Shopify's own totals against what actually posted in Tally/Zoho, to catch sync drift -- separate from payment/settlement reconciliation, which is out of scope.

Tally has no cloud API of its own -- the relay agent bridges your local Tally installation to Ledgeree's sync engine.

Zoho's own REST API is called directly -- GST itself is computed by Zoho from each line's tax percentage, so the same canonical order model drives both adapters without duplicating tax logic.

Place-of-supply splits, B2B GSTIN handling, export zero-rating, and return handling are identical regardless of which ERP you connect -- the adapter changes, the correctness doesn't.