Summary

iPaaS.com Locations can be transferred from Syspro warehouses through Manual Sync. Each transfer creates a new iPaaS.com Location or updates an existing one, carrying the warehouse code and its description. This is the reference data the inventory collections depend on, so warehouses must be transferred before stock quantities will land correctly.

ID Format

Manual Sync ID Format

Enter the Syspro warehouse code on the iPaaS.com Manual Sync page.

Example: MAIN

External ID Format

After a successful transfer, iPaaS.com saves the Syspro warehouse code as the external ID on a dedicated external-ID record, which routes subsequent updates to the same Location.

The warehouse code also carries operational significance beyond identification. The product and variant inventory collections resolve which Location a stock row belongs to by matching the Syspro warehouse code against the Location Name. That match is exact and case-sensitive.

Deleted Record Support

Outbound delete is not supported for this entity. The integration does not implement a delete operation for locations, delete mappings are not included in the default templates, and removing a warehouse in Syspro will not propagate to iPaaS.com.

Mapping Collection Status

Status: Enabled. The collection carries no mapping filter, so every Syspro warehouse routed to it is processed.

Trigger Events: None. No Syspro database trigger raises location events, so there is no automatic transfer path for this collection. Locations are transferred by Manual Sync only.

Duplicate or Conflicting Mappings

None. No other mapping collection in this integration writes to or from iPaaS.com Locations.

This entity does not support collision handling, so there are no selectable collision methods on this collection. Duplicate Locations are prevented by the external-ID link.

Supported Child Collections

None. This collection has no child collections — location addresses, relationships and location groups are not transferred.

System Caveats

Syspro Caveats

The warehouse code is the matching key. The value written to the Location Name must remain the Syspro warehouse code exactly as Syspro holds it. Re-mapping Name to the warehouse description will break location resolution for every inventory row.
Warehouse descriptions are free text. They are carried for readability only and play no part in matching.

iPaaS.com Caveats

Locations must exist before inventory transfers. The inventory collections perform an exact, case-sensitive match on the Location Name. A warehouse that has not been transferred, or whose Location name differs in any way from the Syspro code, causes inventory transfers for that warehouse to fail.
New warehouses need transferring before their stock. A warehouse added in Syspro after initial setup must be transferred through this collection before inventory for it will succeed.

Integration-Specific Caveats

Renaming a warehouse breaks inventory matching. Because inventory resolves locations by name, changing a warehouse code in Syspro without updating the corresponding iPaaS.com Location name causes subsequent inventory transfers for that warehouse to fail until the two are realigned.

Setup Requirements

Syspro Configuration

The Syspro REST API must be installed and reachable, and the subscription's API URL and credentials configured. Refer to the Syspro Installation Instructions for the full procedure.

iPaaS.com Configuration

No subscriber-facing setup is required beyond an authenticated subscription. Because there is no automatic trigger for this entity, plan to transfer warehouses by Manual Sync during implementation and whenever a warehouse is added or renamed.

Integration Flow

A subscriber initiates a Manual Sync using the Syspro warehouse code.
The integration retrieves the warehouse record from Syspro.
iPaaS.com looks for an existing external-ID record matching the warehouse code. If found, the transfer updates the linked Location; otherwise a new Location is created.
The warehouse code is written to the Location Name and the description to Description.
The external-ID record is saved so subsequent transfers route to the same Location.
Once the Location exists, inventory rows for that warehouse can resolve their location and transfer successfully.

Mappings

Add/Update Syspro Location TO iPaaS.com

iPaaS.com data type: Location

This collection captures the Syspro warehouse into iPaaS.com as a Location. It carries no mapping filter, so every warehouse routed to it is processed.

Mapping Type	Source Field (Syspro)	Destination Field (iPaaS.com)	Description
Field	`Warehouse`	Name	Required. The Syspro warehouse code. iPaaS.com rejects a Location with no name. The inventory collections match on this value exactly and case-sensitively, so it must remain the warehouse code rather than a friendlier label.
Field	`Description`	Description	Recommended. The Syspro warehouse description, carried for readability. Not used for matching, so it can be safely edited or re-mapped.

Error Handling

Errors raised by this collection are catalogued in the Syspro Error Messages article. The failure mode specific to this collection is a warehouse with no code, which iPaaS.com rejects because the Location name is required.

The more common symptom subscribers encounter is not an error on this collection at all, but a downstream inventory failure caused by a missing or mismatched Location. When inventory transfers fail to resolve a location, check that the warehouse has been transferred here and that its Location name matches the Syspro warehouse code exactly.

Testing & Validation

Test Scenarios

Transfer a Syspro warehouse by Manual Sync and verify a Location appears in iPaaS.com with the warehouse code as its name.
Change the warehouse description in Syspro, re-transfer, and verify the Location description updates without creating a duplicate.
Transfer a product with inventory in that warehouse and confirm the inventory row resolves to the correct Location.
Attempt an inventory transfer for a warehouse that has not been transferred, and confirm it fails with a location-resolution error.
Transfer the same warehouse twice and confirm the second transfer updates the existing Location rather than creating a second one.

Validation Checklist

Every Syspro warehouse in use has a corresponding iPaaS.com Location.
Each Location name matches its Syspro warehouse code exactly, including case.
Inventory rows resolve to the expected Location.
Repeat transfers update rather than duplicate.

Additional Notes

Location addresses are out of scope. Warehouse addresses are not captured.
Location groups and relationships are out of scope. Hierarchical location structures are not captured.
No automatic transfer path exists for this entity. For most subscribers this is not a practical constraint, since warehouses are few and change rarely — but it does mean a newly added warehouse will not appear in iPaaS.com until someone transfers it.
Bulk initialization is not supported. Subscribers or their MiSP can use bulk sync using Postman where the number of warehouses makes Manual Sync impractical.

Syspro to iPaaS.com Location Mapping Documentation