This section of the subscription configuration defines which mapping collections will be sent to iPaaS from that subscription.

This section of the subscription configuration defines which mapping collections will be sent from iPaaS to that subscription.

The data model for a merchant’s list of transactions when a customer purchases products from them.

A single product may have multiple options such as size or color. These are referred to as variants in iPaaS.com but they may be referred to differently in other systems. Each option on the variant is referred to as a variant option.

The section in the subscriber experience where you can create, update and delete users and roles.

An account that is tied to a person who has access to pieces of the iPaaS platform. They may be one or more types of users (i.e. MiSP, Subscriber or Integration Partner) and have a role assigned to them.

In each system, each record contains a piece of data that is unique (typically an ID number, but can be an email address or any other piece of unique information). This is used to ensure that data in that system or in others is looking at that specific record when

This is the next evolution of the omnichannel experience. When commerce is truly unified, shoppers can interact with a brand across channels seamlessly. For instance, they can buy online and pickup in store, as well as buy online and return in store. Store gift cards work seamlessly online and at

Within iPaaS a subscriber can leverage the iPaaS.com translation functionality or can write code (C#) that allows for incoming or outgoing data to be modified. For instance, if data from an e-commerce platform comes in as first name and last name in 2 fields and their CRM stores it in

The amount of data that is transferred via the API between iPaaS and an external subscription.