Summary

This article explains how the Zuper integration writes location records from iPaaS.com to Zuper. The Add/Update Zuper Location FROM iPaaS.com mapping collection creates and updates product locations in Zuper from iPaaS.com location records. When a location is dispatched through this collection, the integration creates or updates the matching Zuper product location with its name, description, and type. Zuper uses product locations to track where product inventory is stored, so this collection is a prerequisite for transferring product inventory to the correct location.

The data flows in one direction only: the source is iPaaS.com and the destination is Zuper. The collection has no mapping filter, so every dispatched location record is processed.

ID Format

Manual Sync ID Format

Manual Sync ID Format : The iPaaS.com location identifier. Enter this value on the iPaaS.com Manual Sync page to send a specific location to Zuper. Example: 41.

External ID Format

External ID Format : After a successful transfer, iPaaS.com records the Zuper location_uid as the external ID on a dedicated external-ID record. This link routes later updates to the same Zuper product location. Example location_uid: f1e127f0-dd15-11ed-9b2c-c3a22815cf76.

Deleted Record Support

Deleted record support : Not supported. This collection creates and updates Zuper product locations only. Deleting a location in iPaaS.com does not delete the corresponding product location in Zuper.

Mapping Collection Status

Status : Enabled. This collection has no mapping filter, so all dispatched records are processed.

Trigger Events: Transfers to Zuper are driven by iPaaS.com outbound Add and Update triggers (subscribed under Outbound Data Flows), by initialization, and by Manual Sync. This collection does not use Zuper webhooks in this direction. The Location entity supports initialization, so all iPaaS.com locations can be transferred to Zuper in a single bulk initialization run from the subscription configuration.

Duplicate or Conflicting Mappings

This collection is the only one that operates on the Location entity. There are no conflicting collections to reconcile.

Collision Handling

Collision handling : Not used. Locations are matched by the saved external ID, and before an external-ID link exists, by the location identifier.

Zuper Caveats

Location type : Locations are created with the type SITE by default, which classifies the location as a physical site. Change the Type mapping if your Zuper account uses a different location type.

Product location purpose : Zuper product locations track where product inventory is stored. A location must exist in Zuper before product inventory can be assigned to it.

iPaaS.com Caveats

Record must exist first : The location record must exist in iPaaS.com before it can be dispatched to Zuper.

Name is required : A Zuper product location must have a name. The source location's Name must be populated for the transfer to succeed.

Setup Requirements

Outbound triggers : In the subscription configuration's Outbound Data Flows section, subscribe the relevant location Add and Update triggers. No automatic transfers occur until those outbound subscriptions are enabled.

Initialization : Initialization is available for this collection. Run it from the subscription configuration to transfer all existing iPaaS.com locations to Zuper in a single bulk operation.

Authentication : The integration authenticates to Zuper with an API key. See the Zuper Installation Instructions article for how to obtain and configure the API key.

Manual Sync : Available at any time from the iPaaS.com Manual Sync page. Enter the iPaaS.com location identifier for the record you want to send to Zuper.

Integration Flow

A location is created or updated in iPaaS.com, or a Manual Sync or initialization run is started.
iPaaS.com dispatches the location record to the Add/Update Zuper Location FROM iPaaS.com collection through the subscribed outbound triggers, initialization, or Manual Sync.
The integration checks for a saved external-ID link to determine whether the location already exists in Zuper.
On a new record, the integration creates the product location with a POST to the Zuper Product Location endpoint. On an update, it writes to the existing product location by its identifier.
On a successful create, iPaaS.com saves the returned Zuper location_uid as the external ID so later updates route to the same product location.

Mappings

Add/Update Zuper Location FROM iPaaS.com

This mapping collection creates and updates Zuper product locations from iPaaS.com location records, writing the location's name, description, and type.

Mapping Type	Source Field (iPaaS.com)	Destination Field (Zuper)	Description
Field	Name	LocationName (`location_name`)	Sets the name of the product location in Zuper. This is a required field: a Zuper product location must have a name.
Field	Description	LocationDescription (`location_description`)	Sets the description of the product location in Zuper. This is an optional field.
Static	Static value: "SITE"	Type (`location_type`)	Sets the location type in Zuper. It is set to a fixed value of "SITE", which classifies the location as a physical site. This is a default that subscribers can change: subscribers who use a different Zuper location type can change this value in the iPaaS.com mapping editor.

Error Handling

For the meaning of specific errors returned during a location transfer and how to resolve them, see the Zuper Error Messages article.

Testing & Validation

Test Scenarios

Create a new location in iPaaS.com with a populated Name and confirm that a matching product location is created in Zuper with the correct name and the SITE type.
Add a Description to the source location and confirm it appears on the Zuper product location.
Update the name or description of an existing, already-transferred location in iPaaS.com and confirm the same Zuper product location is updated rather than a duplicate being created.
Run an initialization and confirm that all existing iPaaS.com locations are transferred to Zuper in a single run.
Perform a Manual Sync using the iPaaS.com location identifier and confirm the location is sent to Zuper.

Validation Checklist

The Zuper product location name matches the iPaaS.com location Name.
The Zuper product location description matches the iPaaS.com location Description when one is provided.
The Zuper product location type is SITE, or the type you set if you changed the Type mapping.
The external ID (Zuper location_uid) is saved in iPaaS.com after a successful transfer.
A subsequent update to the same location updates the existing Zuper product location instead of creating a duplicate.

Additional Notes

This collection is the prerequisite for transferring product inventory to Zuper. The Add Zuper Product Inventory FROM iPaaS.com and Update Zuper Product Inventory FROM iPaaS.com collections resolve their target Zuper location from the link this collection saves, so a location must be transferred here before its inventory can be written.
The SITE value on the Type mapping is a default. Confirm it matches the location type your Zuper account uses before relying on it in production, and update the Type mapping if a different type is required.
Transfers to Zuper in this direction are driven by iPaaS.com outbound triggers, initialization, and Manual Sync, not by Zuper webhook events, at the time this documentation was written.

iPaaS.com to Zuper Location Mapping Documentation