OroCommerce Connections and Settings

Integrate iPaaS.com with OroCommerce to synchronize products, pricing, customers, customer categories, and orders between the two systems. This article is a reference for connecting the integration, the credentials and settings it uses, and how authentication works — useful during first setup and later when rotating credentials or onboarding new team members.

Prerequisites

Before configuring the subscription in iPaaS.com, create an OAuth application in your OroCommerce back-office so iPaaS.com can authenticate. You will need the resulting Client Id, Client Secret, and the Redirect Url.

Log in to the OroCommerce back-office (admin panel).
Go to System > User Management > OAuth Applications.
Click Create OAuth Application, select the organization, and click Continue.
Complete the form:
- Application Name: a descriptive name (for example, your iPaaS.com subscription name).
- Active: checked.
- Grant Type: Authorization Code (this integration uses the Authorization Code flow).
- Confidential Client: checked.
- Redirect URLs: the iPaaS.com callback URL for your environment (see the Redirect Url field below).
Click Save and Close. OroCommerce displays the Client Id and Client Secret.

Note: The Client Secret is shown only once, immediately after creation. Copy and store it securely before closing the dialog.

Note: OAuth applications can only be created after the OroCommerce instance has its OAuth encryption keys configured. If the back-office reports that OAuth authorization is unavailable, ask your OroCommerce administrator to complete the encryption key configuration first.

Configuration Details

You will enter the following values when you configure the subscription:

API Url — your OroCommerce instance API endpoint. This is unique to each OroCommerce instance. Example: https://yourdomain.oro-cloud.com
Admin Base Path — the root path to your OroCommerce admin interface, used to build API endpoint URLs. Example: /admin
Client Id — from the OroCommerce OAuth application created above.
Client Secret — from the OroCommerce OAuth application created above.
Redirect Url — the iPaaS.com OAuth callback URL. Staging example: https://stagingportal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/app; production uses the equivalent https://portal.ipaas.com/... URL.

Configure Subscription Settings

To reach the subscription settings in iPaaS.com:

Go to Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the OroCommerce integration tile, then click Subscribe.
Enter a unique subscription name and select a version. A naming pattern such as "OroCommerce – Release" works well.
Leave Create Default Mappings checked (recommended) to create the standard mappings automatically. Uncheck it only if you intend to build every mapping yourself.
Enter the integration settings described in the table below.
Click Apply to save.

After the subscription exists, you can return to these settings at any time by opening the subscription from the Subscriptions list.

Field	Description	Required	Example
API Url	Your OroCommerce instance API endpoint URL.	Yes	https://yourdomain.oro-cloud.com
Admin Base Path	Root path to the OroCommerce admin interface, used to build API endpoint URLs.	No	/admin
Client Id	OAuth client ID from your OroCommerce OAuth application.	Yes	(from OroCommerce)
Client Secret	OAuth client secret from your OroCommerce OAuth application. Shown once at creation.	Yes	(from OroCommerce)
Redirect Url	iPaaS.com OAuth callback URL for your environment.	Yes	https://stagingportal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/app
Auto Create Product	When Yes, products referenced by incoming pricing are created in OroCommerce if they do not already exist. When No, records that reference an unknown product fail.	No	False
Auto Create Customer Group	When Yes, customer groups referenced by incoming price-list assignments are created in OroCommerce if they do not exist. When No, records that reference an unknown customer group fail.	No	False
Default Pricing Custom Field Name	The entity field name of a boolean field on the OroCommerce Product Price module that flags whether a price record is the product's default price. Required for the integration to create or update default pricing.	No	(boolean Product Price field name)
Order Poll Days	How many days back the integration looks when polling OroCommerce for new and updated orders. Set this wide enough to cover the gap between polls so no order is missed. Example: 7 (default if left blank).	No	7

Authentication Methods

This integration authenticates with OroCommerce using OAuth 2.0 with the Authorization Code flow. iPaaS.com uses the Client ID, Client Secret, and Redirect URL you supplied to obtain an access token, and refreshes that token automatically as needed.

To generate the access token after entering your settings:

Open your OroCommerce Subscription Settings in iPaaS.com.
Click the Authentication icon.
Enter your OroCommerce login credentials.
Click Authorize when prompted.
Click Close Page on the confirmation screen.
Refresh the subscription. The access token value is now present in the subscription settings.

Initialization Support

Currently, initialization (a bulk import of existing data on first connect) is not supported for OroCommerce in iPaaS.com. All data synchronization is handled through the mappings, which transfer records as they are created or updated. Configure your mappings during setup and transfer existing records through the normal mapping flow.

Throttling

iPaaS.com limits how many requests the integration can make so that no single subscription overwhelms the system. These fields are pre-populated from the integration settings and can be tuned on the subscription:

API Throttle Limit — the maximum number of API requests allowed within the throttle window. A lower value (for example, 5) is useful during initial setup; a higher value (up to 500) suits ongoing and high-volume operations.
API Throttle Seconds — the length of the throttle window, in seconds, over which the limit is measured. Default: 60.
Concurrent Connections — the maximum number of simultaneous API connections the subscription will process. Default: 5 (range 1–10).
Concurrent Batch Executions — the maximum number of simultaneous batch transfers the integration will run at once. Default: 5 (range 1–10).

When a limit is reached, additional requests are queued or rejected until the window resets or an active connection finishes.

See Subscription Configuration – Edit for details on these throttle settings.