Zoho Books and Adobe Commerce integration

What moves between them

Order and invoice data flow from Adobe Commerce into Zoho Books. When an order is placed or invoiced in Adobe Commerce, ml-connector reads the order detail, invoice amounts, tax, and shipping charges, and creates a matching invoice in Zoho Books allocated to GL accounts for product revenue, tax payable, and shipping revenue. The sync runs on a schedule you define, typically tied to your daily or weekly order fulfillment cycle. Reference data such as customer contacts and product items are also synced to keep Zoho Books in sync with your storefront.

How ml-connector handles it

ml-connector stores both credential sets encrypted. For Zoho Books it routes all API calls to the correct regional endpoint based on the region field in your OAuth token, and refreshes the access token proactively before the 1-hour expiry. For Adobe Commerce it presents the OAuth credentials on each call and handles 401 responses by refreshing the bearer token. Order details from Adobe Commerce are transformed into Zoho Books invoice line items, with tax and shipping amounts mapped to configured GL accounts. Both systems enforce rate limits that trigger HTTP 429, so ml-connector backs off and retries with exponential jitter. Organization ID is resolved once per sync and cached. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A small-to-mid-sized online retailer runs Adobe Commerce for their Shopify alternative and Zoho Books for accounting. Before the integration, the finance team exported daily orders from Adobe Commerce and manually entered them into Zoho Books as invoices, a process that took 30 to 45 minutes and was error-prone when order totals did not match GL expectations. With Adobe Commerce and Zoho Books connected, each order syncs automatically as an invoice with tax and shipping correctly allocated to GL accounts. Revenue reconciliation at month-end is now instant, and the manual data entry step has been eliminated.

What you can do

• •Sync orders from Adobe Commerce as invoices into Zoho Books with correct line-item detail.
• •Map tax collected and shipping revenue to configured GL accounts so revenue is allocated correctly.
• •Authenticate both systems encrypted and route Zoho Books calls to the correct regional endpoint.
• •Transform Adobe Commerce order structure into Zoho Books invoice schema and handle currency conversion via Zoho exchange rates.
• •Run on a schedule tied to your order fulfillment cycle, with retries and a full audit trail on every record.

Questions

Which direction does data flow between Adobe Commerce and Zoho Books?

Orders and invoices flow from Adobe Commerce into Zoho Books. ml-connector reads order data from Adobe Commerce, transforms it into invoice format, and creates invoices in Zoho Books. GL accounts are not exposed in Adobe Commerce, so the connector applies GL mapping rules on the Zoho Books side to allocate revenue, tax, and shipping to the correct accounts.

How does the integration handle Zoho Books regional endpoints and OAuth expiry?

Zoho Books publishes region-specific API endpoints (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia). ml-connector extracts the region from your OAuth token response and routes all subsequent calls to the correct regional base URL. Access tokens expire after 1 hour, so ml-connector refreshes the token proactively before expiry to avoid failed calls.

How are tax and shipping amounts handled in the invoice mapping?

Adobe Commerce orders include tax and shipping amounts alongside product line items. ml-connector extracts these amounts and creates corresponding invoice line items in Zoho Books mapped to configured GL accounts for tax payable and shipping revenue. This ensures your GL revenue breakdown matches your actual order structure.