How does ml-connector handle Zoho Books regional endpoints?

ml-connector resolves the organization ID and region from the OAuth2 token response, then routes all subsequent API calls to the correct regional base URL (US, EU, India, Australia, Japan, Canada, China, or Saudi Arabia). This eliminates the need for manual region configuration per customer. If the region changes, the connector detects it at the next token refresh.

What format do outbound invoices use when they leave Zoho Books?

Outbound invoices are wrapped in SPS Commerce's RSX 7.7.7 JSON envelope format before being posted to SPS, which then routes them to the correct retail trading partner in their required EDI format (X12, EDIFACT, or raw JSON). ml-connector handles the envelope transformation; you don't manually convert formats.

Does the integration require manual trading partner setup in SPS Commerce?

Yes. Trading partner IDs (retailer identifiers like Walmart or Amazon) must be provisioned during onboarding with SPS Commerce and are not discoverable via the API. Once provisioned, ml-connector polls for inbound orders and routes outbound invoices to the correct partner based on the purchase order source. SPS Commerce typically requires 4 to 8 weeks of testing and certification per new retail partner.

Zoho BooksSPS Commerce

Zoho Books and SPS Commerce integration

Zoho Books handles your accounting and purchase orders. SPS Commerce connects you to major retail trading partners like Walmart, Target, and Amazon through an EDI network. Connecting the two keeps your supply chain and accounting ledgers aligned. New purchase orders from retail partners flow into Zoho Books without manual entry, and your invoices route to trading partners in the format they require. ml-connector bridges the OAuth2 and regional complexity on the Zoho side, handles the RSX JSON envelope format on the SPS side, and keeps data moving on a schedule you control.

How Zoho Books works

Zoho Books exposes contacts, invoices, bills, purchase orders, vendor payments, customer payments, items, chart of accounts, journals, and expenses through a REST API with region-specific base URLs (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia). Authentication uses OAuth2 Authorization Code flow with user-delegated refresh tokens valid for one hour; the organization ID must be included as a query parameter on every call. Webhook push and polling are both supported, with offset-based pagination for list endpoints and a maximum of 100 requests per minute across all plans.

How SPS Commerce works

SPS Commerce exposes purchase orders, PO acknowledgments, invoices, advance ship notices, inventory advice, POS data, warehouse transactions, and functional acknowledgments as EDI documents wrapped in RSX 7.7.7 JSON envelope format. It authenticates with OAuth2 client credentials against a dedicated token endpoint, and documents are accessed via REST. Polling is the primary integration pattern at five to fifteen minute intervals; the webhook framework is still under development. Trading partner IDs are provisioned during onboarding and are not discoverable via API.

What moves between them

Purchase orders flow from SPS Commerce into Zoho Books as soon as they arrive from retail partners. Zoho Books invoices flow outbound to SPS Commerce on creation or update, wrapped in the RSX envelope format for delivery to the correct trading partner. Order acknowledgments and inventory data move on a polling schedule tied to your supply chain cadence, typically every 5 to 15 minutes.

How ml-connector handles it

ml-connector manages two distinct authentication flows: Zoho Books OAuth2 with proactive token refresh at 55 minutes, and SPS Commerce OAuth2 client credentials with per-request bearer token presentation. Because Zoho Books lives in customer-specific regions, ml-connector resolves the organization ID after authentication and routes all subsequent calls to the correct regional base URL (US, EU, India, etc) embedded in the token response. On the SPS side, ml-connector wraps outbound documents in the RSX 7.7.7 JSON envelope before POST, and unwraps inbound documents from the envelope on receipt. Polling hits SPS at your configured interval; inbound orders are validated against existing items in Zoho Books before creation. Rate limits are respected with exponential backoff: Zoho Books returns HTTP 429 at 100 requests per minute per organization, and SPS Commerce returns 429 with undocumented per-endpoint limits (exponential backoff with jitter handles both). Every document carries its source order or invoice number for deduplication on the ml-connector side.

A real-world example

A mid-sized CPG supplier manufactures packaged goods and ships to major retailers including Walmart and Target. Before the integration, purchase orders arrived via EDI file drop on SFTP, were manually entered into Zoho Books for inventory and cost tracking, and invoices were generated in Zoho Books but had to be reformatted and reuploaded to SPS for delivery to trading partners in the correct EDI format. With SPS Commerce and Zoho Books connected, inbound orders auto-populate in Zoho Books at 10-minute intervals, and invoice creation triggers an immediate push to SPS in RSX format. The supply chain and accounting teams see the same PO data in real time, month-end close includes orders that retailers have already received, and manual file handling is eliminated.

What you can do

Pull purchase orders from retail trading partners via SPS Commerce and create them in Zoho Books on a configurable schedule, without manual entry.
Push Zoho Books invoices to SPS Commerce wrapped in RSX JSON envelope format for delivery to the correct retail partner.
Resolve Zoho Books organization ID and region after OAuth2 authentication, routing all calls to the correct regional endpoint.
Handle OAuth2 refresh cycles for both Zoho Books user-delegated tokens and SPS Commerce client credentials, with proactive expiry management.
Deduplicate purchase orders and invoices by document number, with exponential backoff retry on rate limit responses from both systems.

Questions

How does ml-connector handle Zoho Books regional endpoints?: ml-connector resolves the organization ID and region from the OAuth2 token response, then routes all subsequent API calls to the correct regional base URL (US, EU, India, Australia, Japan, Canada, China, or Saudi Arabia). This eliminates the need for manual region configuration per customer. If the region changes, the connector detects it at the next token refresh.
What format do outbound invoices use when they leave Zoho Books?: Outbound invoices are wrapped in SPS Commerce's RSX 7.7.7 JSON envelope format before being posted to SPS, which then routes them to the correct retail trading partner in their required EDI format (X12, EDIFACT, or raw JSON). ml-connector handles the envelope transformation; you don't manually convert formats.
Does the integration require manual trading partner setup in SPS Commerce?: Yes. Trading partner IDs (retailer identifiers like Walmart or Amazon) must be provisioned during onboarding with SPS Commerce and are not discoverable via the API. Once provisioned, ml-connector polls for inbound orders and routes outbound invoices to the correct partner based on the purchase order source. SPS Commerce typically requires 4 to 8 weeks of testing and certification per new retail partner.

Connect Zoho Books and SPS Commerce

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

Get started