Does data flow in both directions between Zoho Books and BigCommerce?

No. Orders flow from BigCommerce into Zoho Books. BigCommerce is an order source only and has no accounting features like GL accounts or purchase orders, so there is nothing to push back to BigCommerce. Invoices, payments, and credit memos are managed in Zoho Books only.

How does ml-connector handle Zoho Books regional URLs and token refresh?

Zoho Books token responses include the region (api_domain), which ml-connector uses to route all subsequent API calls to the correct regional endpoint (US, EU, India, etc.). Access tokens expire after 1 hour, so ml-connector refreshes the token proactively at 55 minutes to avoid expired-token errors mid-flow.

What happens if a BigCommerce webhook fails or is retried?

BigCommerce automatically retries webhooks over 48 hours if the destination does not return HTTP 200 or 201. ml-connector validates the webhook signature, fetches the full order from the BigCommerce API, and posts to Zoho Books. If the post fails, ml-connector logs the error in its audit trail and the webhook can be manually replayed, or the next webhook for that order can trigger a retry of the earlier step.

Zoho BooksBigCommerce

Zoho Books and BigCommerce integration

Zoho Books handles your accounting and invoicing. BigCommerce powers your online store. Connecting them keeps your orders and accounts in sync. When a customer places an order in BigCommerce, that order flows into Zoho Books as an invoice and the customer becomes a contact, ready for payment tracking and financial reporting. ml-connector bridges the very different authentication schemes and moves the data reliably on a schedule you set.

How Zoho Books works

Zoho Books is a cloud accounting platform that exposes invoices, bills, purchase orders, vendor payments, customer payments, items, chart of accounts, journals, and expenses through REST APIs. Authentication uses OAuth2 with a user-delegated refresh token, no machine-to-machine client credentials. The API is regional (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia), each with its own base URL resolved from the token response. Zoho Books supports both outgoing webhooks (for invoices, bills, purchase orders, contacts, and payments) and polling via offset-based pagination, with a 100 requests per minute rate limit and daily limits ranging from 1,000 to 10,000 per organization.

How BigCommerce works

BigCommerce is an e-commerce platform that exposes orders, customers, products, variants, and refunds through REST APIs. Authentication is a simple static API key delivered as an X-Auth-Token header, with no expiry or rotation. BigCommerce delivers order and customer events via webhooks that post to a registered HTTPS endpoint, with automatic retry over 48 hours and auto-deactivation if delivery success drops below 90 percent. The API has a 30-second rate limit window that varies by plan (150 to 450 requests per window). BigCommerce has no accounting GL accounts, vendors, or purchase orders, so it is purely an order source.

What moves between them

Orders flow from BigCommerce into Zoho Books. When a customer places an order in BigCommerce, ml-connector receives the webhook, fetches the full order details via the BigCommerce REST API, and posts it into Zoho Books as an invoice tied to the customer contact. Customer records from BigCommerce flow into Zoho Books as contacts so orders reference valid customer data. Payments, refunds, and order cancellations flow the same direction. No data flows back from Zoho Books to BigCommerce, since BigCommerce is order-only.

How ml-connector handles it

ml-connector stores the Zoho Books refresh token encrypted and refreshes the access token proactively before expiry (at 55 minutes). It stores the BigCommerce API key encrypted and presents it on every call. Zoho Books requires an organization_id query parameter on every call; ml-connector resolves this once after authentication and caches it. When a BigCommerce webhook arrives, ml-connector validates the HMAC-SHA256 signature against the BigCommerce secret, fetches the full order payload from the BigCommerce REST API, then maps the order to a Zoho Books invoice. Order line items map to Zoho Books items; if an item does not exist, ml-connector can create it. The customer maps to a Zoho Books contact, created if not found. Because Zoho Books is regional, ml-connector routes all calls to the correct region (resolved at authentication time). BigCommerce webhooks can fail and are retried automatically by BigCommerce itself, but ml-connector tracks the order in its audit log and can replay the invoice creation if needed. Zoho Books enforces a 100 requests per minute rate limit; if that limit is hit, ml-connector backs off and retries. Refunds are handled as credit memos in Zoho Books, tied back to the original invoice.

A real-world example

A mid-sized SMB sells products online through BigCommerce and manages invoicing and accounting in Zoho Books. Before the integration, the accounting team extracted order data from BigCommerce daily and manually entered invoices into Zoho Books, matching customers by name and reconciling line items by hand. This created duplicate-entry risk and month-end reconciliation was slow. With BigCommerce and Zoho Books connected, each order posts as an invoice automatically within seconds of the customer placing it, the customer is created in Zoho Books on first order, and refunds and order cancellations update the accounting records without re-work. Month-end close is faster because the revenue has already been recorded.

What you can do

Post BigCommerce orders into Zoho Books as invoices, with line items mapped to Zoho Books items.
Create and update customer contacts in Zoho Books from BigCommerce customer records.
Handle order refunds as credit memos in Zoho Books, tied to the original invoice.
Route all calls to the correct Zoho Books regional endpoint and refresh OAuth2 tokens before expiry.
Validate BigCommerce webhook signatures and audit every order, with replay capability if posting fails.

Questions

Does data flow in both directions between Zoho Books and BigCommerce?: No. Orders flow from BigCommerce into Zoho Books. BigCommerce is an order source only and has no accounting features like GL accounts or purchase orders, so there is nothing to push back to BigCommerce. Invoices, payments, and credit memos are managed in Zoho Books only.
How does ml-connector handle Zoho Books regional URLs and token refresh?: Zoho Books token responses include the region (api_domain), which ml-connector uses to route all subsequent API calls to the correct regional endpoint (US, EU, India, etc.). Access tokens expire after 1 hour, so ml-connector refreshes the token proactively at 55 minutes to avoid expired-token errors mid-flow.
What happens if a BigCommerce webhook fails or is retried?: BigCommerce automatically retries webhooks over 48 hours if the destination does not return HTTP 200 or 201. ml-connector validates the webhook signature, fetches the full order from the BigCommerce API, and posts to Zoho Books. If the post fails, ml-connector logs the error in its audit trail and the webhook can be manually replayed, or the next webhook for that order can trigger a retry of the earlier step.

Connect Zoho Books and BigCommerce

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started