Integrate iPaaS.com with Zoho Commerce to enable seamless data synchronization for product categories, products, product variants and inventory levels sent out to the store, and for sales orders — with their line items, billing and shipping addresses, taxes, payments and header discounts — captured back into iPaaS.com.

This article is the ongoing reference for a Zoho Commerce subscription: what each setting does, where its value comes from, and how the connection is authorized and maintained. If you are setting a subscription up for the first time, follow the Zoho Commerce Installation Instructions article and use this article afterwards for reference, credential rotation and environment changes.

Complete the following in Zoho Commerce before configuring the subscription in iPaaS.com.

Subscribers cannot supply the additional OAuth 2.0 configuration on the iPaaS.com side themselves. Subscribers or their MiSP (Managed Integration Service Provider) should plan for the MiSP or implementation partner to complete that part of the setup.

Each value below is entered on the Zoho Commerce Subscription Settings page in iPaaS.com.

Open Subscriptions, select the Zoho Commerce subscription, and enter the values on the Subscription Settings page. Field labels are displayed in uppercase on the page.

Organization_Id is optional on the page and required in practice. Nothing in iPaaS.com or Zoho Commerce warns you when it is missing — transfers simply fail to produce records. If a newly configured subscription moves no data at all, this is the first field to check.

The throttling and concurrency values are pre-populated when the subscription is created and can differ between subscriptions. See Throttling below before changing any of them.

Zoho Commerce uses OAuth 2.0. iPaaS.com drives the authorization code exchange on your behalf and stores the resulting tokens against the subscription — you never construct a token request yourself, and no API key or password is involved.

Step 1 — register the OAuth client in Zoho. In the Zoho API Console at https://api-console.zoho.com, select Add Client, choose Server-based Applications, and create the client with the iPaaS.com production redirect URI https://portal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/app. Zoho issues a Client ID and Client Secret on the client's Client Secret tab.

Step 2 — enter the credentials in iPaaS.com. On the Zoho Commerce Subscription Settings page, enter API Url, Client_Id, Client_Secret and Organization_Id, then click Apply.

Step 3 — authorize the connection. Click the Authenticate icon in the toolbar at the top of the Subscription Settings page.

A Zoho authorization window opens listing the permissions iPaaS.com is requesting for your store. Review them, tick I allow iPaas to access the above data from my Zoho account, then click Accept. The Accept button stays disabled until that box is ticked.

Step 4 — confirm the tokens were stored. Close the confirmation window, return to iPaaS.com, and refresh the Subscription Settings page. When authorization succeeded, an AccessToken and a RefreshToken value appear in the stored-settings area below the credential fields. If they are empty, the authorization did not complete — re-check Client_Id, Client_Secret and the redirect URI on the Zoho client, then repeat step 3.

How the tokens are maintained. iPaaS.com stores the access token with its expiry and the refresh token alongside it. When the stored access token expires, the integration exchanges the refresh token for a new one automatically the next time it needs to call the store; the refresh token itself does not expire on a schedule. Two consequences are worth knowing:

The subscription's connection test does not verify your credentials. At the time this documentation was written, the connection check reports success without contacting Zoho Commerce, so a green result does not prove the credentials, the Organization ID or the API address are correct. Confirm the connection by transferring a real record instead — see the Post-Installation Verification section of the Zoho Commerce Installation Instructions article. Errors from a genuine transfer attempt are reported under Dashboard / Integration Monitoring / Error Logs.

Currently, initialization is not supported for Zoho Commerce in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.

There is no bulk first-load of an existing catalog or order history. To move a large existing data set, use the bulk sync using Postman pattern, which drives the same per-record transfers the integration already supports.

Throttling limits how quickly the subscription calls Zoho Commerce, so a large transfer does not overwhelm the store API or trigger rate-limit rejections. The same controls exist in the opposite direction for calls made to iPaaS.com.

While the throttling fields are required, the values are pre-populated by the integration settings and do not normally need to be changed. Reduce API Throttle Limit or increase API Throttle Seconds if you begin seeing rate-limit errors under Dashboard / Integration Monitoring / Error Logs; Concurrent Connections controls how much work the subscription runs at once and should only be changed on advice from iPaaS.com Support at support@ipaas.com or your MiSP.

Zoho does not publish a call quota for the Zoho Commerce store API, and a store may still refuse calls made too quickly, so there is no target figure to tune towards. Stagger large catalog or inventory runs rather than sending everything at once, and validate throughput in a staging environment before relying on it in production.

For field-by-field guidance on these controls, refer to Subscription Configuration – Edit.