iPaaS.com to Shopify Customer Mapping Documentation
This documentation covers writing iPaaS.com Customers to Shopify (transfer FROM iPaaS.com). The Add/Update Shopify Customer FROM iPaaS.com collection creates new Shopify customers and updates existing ones, deciding between create and update by resolving the saved external id (the Shopify customer id) for the iPaaS.com Customer. It is the parent of the Customer Address and Customer Company child collections, which write the customer's address and B2B company relationship to Shopify. Customer deletion FROM iPaaS.com is handled by Delete Shopify Customer FROM iPaaS.com. The reverse direction (importing Shopify customers into iPaaS.com) is documented in Shopify to iPaaS.com Customer Mapping Documentation.
ID Format
Manual Sync ID: the iPaaS.com Customer id (for example, 10), entered on the iPaaS.com Manual Sync page.
External ID saved after sync: the Shopify customer id is recorded as the external-id link, so later updates edit the same Shopify customer rather than creating a duplicate.
Deleted Record Support
Customer deletion is supported in this direction. The Delete Shopify Customer FROM iPaaS.com collection propagates an iPaaS.com customer deletion to Shopify, removing the Shopify customer matched by the saved external id. Deletion runs only when the iPaaS.com Customer Delete outbound trigger is subscribed. (Earlier documentation stated that records removed from iPaaS.com are not deleted in Shopify; that is no longer accurate — a dedicated delete collection now propagates the deletion.)
Mapping Collection Status
Status: Enabled. The parent and Address child carry no mapping filter; the Customer Company child carries a filter that skips the relationship until the related Shopify company is linked.
Trigger Events: iPaaS.com Customer Create, Update, and Delete outbound triggers.
Duplicate or Conflicting Mappings
The opposite-direction Shopify to iPaaS.com Customer collections import customers from Shopify. In this direction, the single Add/Update collection handles both create and update, so there is no overlap between separate collections.
Supported Child Collections
Parent Collection: Add/Update Shopify Customer FROM iPaaS.com.
Add/Update Shopify Customer Address FROM iPaaS.com — writes the customer's address to Shopify, resolving the Shopify address id from the external id and normalizing the region via the StateAbbreviation function.
Add/Update Shopify Customer Company FROM iPaaS.com — attaches the Shopify customer to the corresponding Shopify B2B company, resolving the Shopify company id from the iPaaS.com relationship.
System Caveats
Shopify Caveats
Write access required. The Shopify connection must include the
write_customersOAuth scope; without it the transfer fails with an authorization error.Email uniqueness. Shopify rejects customer creation if the email already exists; the prerequisite handling links to the existing customer by email instead of duplicating.
Province code format. Shopify expects a valid province/state abbreviation; the StateAbbreviation function normalizes the iPaaS.com Region, but an unrecognized value is passed through unchanged and may be rejected.
B2B required for company relationships. The Customer Company child applies only to stores with Shopify B2B enabled — available on the Basic, Grow, Advanced, and Plus plans as of April 2026 (no longer Plus-only; advanced B2B features remain Plus-only).
iPaaS.com Caveats
EmailAddress required. A customer without an email cannot be created in Shopify.
External-id link required. The Shopify customer id is saved as the external id so updates edit the same Shopify customer.
Setup Requirements
iPaaS.com Configuration
Enable the Customer collections and subscribe to the iPaaS.com Customer Create, Update, and (if deletion is desired) Delete outbound triggers in the subscription configuration's Outbound Data Flows section. No automatic transfers occur until those subscriptions are enabled. Customers can also be sent on demand from the Manual Sync page using the iPaaS.com Customer id. The sample customer-metafield mapping (custom.test_custom_field) is a placeholder — point it at the Shopify metafield you actually write to, or remove it.
Shopify Configuration
The Shopify connection must be authorized with the write_customers OAuth scope.
Integration Flow
An iPaaS.com Customer Create, Update, or Delete trigger fires (or a Manual Sync is run).
Prerequisite handling. If the iPaaS.com Customer is not yet linked to Shopify, the integration looks up a Shopify customer by email and links it. For each company relationship, if the related Company is not yet linked to Shopify, the integration transfers that Company to Shopify first as a prerequisite. A failed prerequisite company transfer fails the customer.
The Id mapping resolves the Shopify customer id; an existing customer is updated, otherwise a new one is created and its id is saved as the external id.
Customer fields are written; iPaaS.com customer categories are converted to Shopify tags.
The child Address collection writes the customer's address.
The child Company collection attaches the customer to the Shopify B2B company, provided the company is linked (its filter skips the relationship otherwise — the prerequisite cascade establishes the link).
Mappings
Add/Update Shopify Customer FROM iPaaS.com (Parent)
Mapping Type | Source (iPaaS.com) | Destination (Shopify) | Description |
Dynamic Formula |
| Id | Resolves the Shopify customer id; null = create new. |
Field | EmailAddress | Required; unique in Shopify. | |
Field | FirstName | Firstname | |
Field | LastName | Lastname | |
Field | Comment | Note | |
Dynamic Formula |
| Tags | iPaaS.com categories → Shopify tags; sent only when non-empty. |
Field | ShopifyCustomerType (custom) | custom.test_custom_field | Placeholder — replace |
Add/Update Shopify Customer Address FROM iPaaS.com (Child)
Mapping Type | Source (iPaaS.com) | Destination (Shopify) | Description |
Dynamic Formula |
| Id | Resolves the Shopify address id; null = create new. |
Field | FirstName | FirstName | |
Field | LastName | LastName | |
Field | Company | Company | Free-text address field. |
Field | Address1 | Address1 | |
Field | Address2 | Address2 | |
Field | City | City | |
Field | Country | Country | |
Field | PostalCode | Zip | |
Field | PhoneNumber | Phone | |
Dynamic Formula |
| ProvinceCode | Normalizes Region to a province/state abbreviation; unrecognized input passes through unchanged. |
Add/Update Shopify Customer Company FROM iPaaS.com (Child)
Mapping Type | Source (iPaaS.com) | Destination (Shopify) | Description |
Dynamic Formula |
| CompanyId | Resolves the Shopify company id; filter skips the relationship if the company is not yet linked. |
Error Handling
Unauthorized access — ensure the Shopify connection includes the
write_customersscope.Duplicate email — Shopify rejects creation if the email exists; the prerequisite email lookup links to the existing customer instead.
Invalid province/postal code — Shopify rejects an address whose province code or postal code does not match the country; validate or rely on the StateAbbreviation normalization.
Prerequisite company failure — if the related Company cannot be transferred to Shopify, the customer transfer fails; resolve the company error and retry.
Testing & Validation
Add a new iPaaS.com customer and confirm a Shopify customer is created and the Shopify customer id is saved as the external id.
Update an existing customer and confirm the same Shopify customer is updated (matched by external id), not duplicated.
Confirm iPaaS.com customer categories appear as Shopify tags.
Confirm the address child writes with the correct ProvinceCode transformation.
For a B2B customer whose company is not yet in Shopify, confirm the company is auto-transferred as a prerequisite and the relationship then attaches.
Delete an iPaaS.com customer and confirm the Shopify customer is removed.
Additional Notes
Align address-sync logic with your business rules (overwrite default vs. append).
If the email changes in iPaaS.com, confirm whether a new Shopify customer should be created or the existing one updated, since email is the de-duplication key.
You do not need to pre-sync companies — the parent customer's prerequisite handling transfers the related Company to Shopify automatically.
