Shopify to iPaaS.com Location Mapping Documentation

This mapping collection imports Shopify locations into iPaaS.com (transfer TO iPaaS.com — Add and Update). Each Shopify location is read and written to a matching iPaaS.com Location, linked by the Shopify location id saved as the external id, so subsequent transfers update the same record rather than creating a duplicate. It is the inbound counterpart to iPaaS.com to Shopify Location Mapping Documentation (FROM iPaaS.com), which creates and updates locations on the Shopify side.

ID Format

Manual Sync ID: the Shopify location id (for example, 10), entered on the iPaaS.com Manual Sync page.
External ID saved after sync: the Shopify location id is recorded as the external-id link, so later transfers update the same iPaaS.com Location.

Deleted Record Support

Shopify also publishes a Location Deleted (locations/delete) event, but deletion is not handled by this collection — a location deleted in Shopify is not removed from iPaaS.com automatically.

Mapping Collection Status

Status: Enabled (no mapping filter; every Shopify location sent through the collection is processed).
Trigger Events: Shopify Location Created (locations/create) and Location Updated (locations/update).

Duplicate or Conflicting Mappings

The outbound iPaaS.com to Shopify Location collection writes iPaaS.com Locations to Shopify (creating and updating the Shopify location and its address). Because this inbound collection maps only the Name, and the iPaaS.com API replaces the entire record on update, an inbound transfer through this collection overwrites every unmapped iPaaS.com Location field.

Unmapped Field Overwrite Risk. The iPaaS.com API uses PUT (full record replace) when updating Location records. Parent (parent_id), Type (type_id), Description, and the address fields are not mapped here, so any existing values in those fields are overwritten with empty/null each time this collection runs — unless preservation mappings are added. To retain a value, add a Dynamic Formula mapping that sources it from the existing record (for example, map DestinationValue.Description to the iPaaS.com Description). This matters most for locations created or maintained by the FROM-iPaaS collection.

Supported Child Collections

None — this is a standalone collection with no dependent child collections.

System Caveats

Shopify Caveats

Read access required. The Shopify connection must include the read_locations OAuth scope to import locations; without it the transfer fails with an authorization error.
Shopify is the source in this direction. This collection reads Shopify locations and does not modify Shopify. (Earlier integration versions treated Shopify locations as read-only and required the external-id link to be entered by hand; locations are now created and maintained on Shopify by the FROM-iPaaS collection, and this collection imports them back into iPaaS.com.)

iPaaS.com Caveats

External-id link drives inventory association. iPaaS.com relies on the saved Shopify location id to associate location inventory with the correct Shopify location; without the link, inventory cannot be tied to a location.
Minimal field coverage by default. Only the location Name is imported. The Shopify location record also exposes address (Address1/Address2, City, Province, Zip, Country), phone, and active status — map these if your business needs them in iPaaS.com, and add preservation mappings (see the overwrite warning) for iPaaS.com-side fields that must survive inbound updates.

Setup Requirements

iPaaS.com Configuration

Enable this mapping collection, and subscribe to the Shopify Location Created and Location Updated events in the subscription configuration's Inbound Data Flows section. No automatic transfers occur until those subscriptions are enabled. Locations can also be imported on demand from the Manual Sync page using the Shopify location id.

Shopify Configuration

The Shopify connection must be authorized with the read_locations OAuth scope. The Shopify-side webhook registration for the location events is covered in the Shopify Installation Instructions.

Integration Flow

A Shopify location is received via the location webhook, or retrieved via the Shopify Locations API on Manual Sync.
The integration matches the existing iPaaS.com Location by the saved external id (the Shopify location id), or creates a new one on first sync.
The location Name is written to the iPaaS.com Location, and the Shopify location id is saved as the external-id link.

Mappings

Add/Update Shopify Location TO iPaaS.com

Mapping Type	Source Field (Shopify)	Destination Field (iPaaS.com)	Description
Field	Name	Name	Required. The Shopify location name, imported to the iPaaS.com Location Name. Only field mapped by default — all other iPaaS.com Location fields are overwritten on update unless preserved (see Duplicate or Conflicting Mappings).

Error Handling

Unauthorized access — ensure the Shopify connection includes the read_locations scope.
Missing external id — iPaaS.com cannot link a location's inventory without the Shopify location id; sync the location to establish the link.

Testing & Validation

Sync a Shopify location and confirm it appears in iPaaS.com with the correct Name.
Confirm the Shopify location id is saved as the external id and a re-sync updates the same iPaaS.com Location rather than creating a duplicate.

Additional Notes

This direction reads Shopify and imports locations into iPaaS.com. Creating and updating locations on Shopify is handled by the FROM-iPaaS collection (see Related Documents).