Summary
Locations are written from iPaaS.com into Adobe Commerce/Magento 2 as inventory sources under Multi Source Inventory. Each iPaaS.com Location becomes one Magento inventory source carrying the source code, name, description, an enabled flag, and an address.
These sources are what the inventory transfers write stock against. The source code created here is the value the inventory collections' source-code translation must point at, so this collection normally runs before any inventory transfer.
The address fields ship as fixed example values rather than being read from the iPaaS.com Location, and must be replaced during implementation. See Placeholder values below.
ID Format
Manual Sync ID Format
Enter the iPaaS.com Location record identifier — the internal numeric identifier of the location in iPaaS.com, for example 7734.
The location name is not accepted as a Manual Sync value.
External ID Format
After a successful transfer, iPaaS.com stores the Adobe Commerce/Magento 2 source code as the external ID on a record linking the iPaaS.com Location to the Magento inventory source. That record routes later transfers of the same location to the existing source for an update rather than creating a second one.
Deleted Record Support
Outbound delete is not supported for locations, and Magento does not support it either. An inventory source cannot be deleted in Adobe Commerce/Magento 2 once created — it can only be disabled in the Magento admin. A source created with the wrong code is permanent.
This makes the first transfer of each location unusually consequential: confirm the source codes are correct before running it.
Custom Field Support
This collection reads no custom fields. Every value comes from a standard field on the iPaaS.com Location or from a fixed value.
Mapping Collection Status
Status: Enabled. This collection ships enabled and processes every iPaaS.com Location record.
Trigger Events: Creation or update of a Location record in iPaaS.com, plus Manual Sync on demand.
Automatic outbound transfers are enabled on the subscription's Outbound Data Flows page. Until that flow is enabled, no locations are sent automatically. Manual Sync is always available regardless.
Duplicate or Conflicting Mappings
No other collection creates Magento inventory sources, so there is no competing collection to reconcile filters with. There is, however, a dependency in both directions:
Every inventory collection — the standalone product and variant inventory collections, and the inventory children beneath the product transfers — resolves a Magento source code through the M2 Product Inventory Source Code From iPaaS Lookup Translation. The source codes this collection creates are what that translation must point at.
The shipment track collections ship from a Magento inventory source, resolved either from a custom field or from a fallback source code.
Subscribers or their MiSP should transfer locations first, confirm the resulting source codes in the Magento admin, and only then configure the inventory source-code translation.
Duplicate matching
This integration implements no selectable collision-handling methods, and the behavior is not configurable on this collection. The external-ID record linking the iPaaS.com Location to its Magento source decides whether a transfer creates or updates.
Unmapped field overwrite risk
When a location is re-transferred, the fields this collection maps are written again over the existing Magento inventory source. The fields at risk are SourceCode, Name, Enabled, Description, CountryId, Region, City, Street and Postcode.
That includes the address fields. Because those ship as fixed values, an address corrected by hand in the Magento admin is replaced by the fixed value again on the next transfer — unless the mappings themselves are changed. This is the single most likely source of surprise on this collection.
The integration provides no guarantee that unmapped or blank fields are preserved on a source update. Subscribers or their MiSP should validate in a staging environment which fields are affected on their own store before relying on manual edits.
The mitigation is a DestinationValue. Where a Magento field must hold a specific value that the iPaaS.com Location does not supply — which is exactly the case for the address fields — set a DestinationValue on that mapping, or repoint the mapping at a custom field carrying the real value.
Supported Child Collections
None. This is a standalone collection with no parent and no children. It writes a single Magento inventory source per record and has no subordinate data to contribute.
System Caveats
Adobe Commerce/Magento 2 Caveats
Sources cannot be deleted, only disabled. A source created by mistake, or with the wrong code, is permanent. Confirm codes before the first transfer.
Source codes are case-sensitive throughout the integration. The code created here must match exactly what the inventory source-code translation later points at. A case mismatch causes the Magento inventory indexer to fail, and a failed inventory index can hide all products in the Magento admin until it is corrected and reindexed.
The address must be valid for Magento to accept the source. Magento validates the region against the country. A region value that is not a real region for the given country is rejected.
Multi Source Inventory must be available in the store. Inventory sources are a Multi Source Inventory feature.
iPaaS.com Caveats
The location name is used twice. It becomes both the Magento source code and the source's display name, so it must be acceptable as an identifier as well as a label.
The address is not read from the Location. Whatever address is held on the iPaaS.com Location record is ignored by this collection as shipped.
Integration-Specific Caveats
Every source arrives enabled. The enabled flag is a fixed value, so a source disabled by hand in Magento is re-enabled on the next transfer of that location.
The address values are placeholders and two of them are not valid values of their kind. See below.
Placeholder values
Five of this collection's nine mappings send fixed values rather than reading the iPaaS.com Location. Four of them form the source's address, and they must be replaced before the first production transfer.
Placeholder value — replace during implementation: the address fields ship as example values from the environment the template was built in:
CountryId ships as US. Replace it with the two-letter ISO country code for the source's real country.
Street ships as an example street address. Replace it with the source's real street.
City ships as an example city. Replace it with the source's real city.
Region ships with a city name in the region field. A city name is not a valid region, and Magento validates the region against the country, so this value is likely to be rejected. Replace it with the real state or province.
Postcode ships with a city name in the postcode field. Replace it with the source's real postal or ZIP code.
Because the values are fixed rather than mapped, every location transferred by this collection receives the same address. A store with more than one real location needs either per-location custom fields feeding these mappings, or separate mapping collections with distinct filters, each carrying its own address.
The Enabled flag is also a fixed value, but that one is a designed constant rather than a placeholder — leave it as true unless sources should arrive disabled.
Setup Requirements
Adobe Commerce/Magento 2 Configuration
Confirm Multi Source Inventory is available in the store.
Decide the exact source code for each location, including casing, before the first transfer — sources cannot be deleted afterwards.
iPaaS.com Configuration
Confirm each iPaaS.com Location's name is acceptable as a Magento source code as well as a display name.
Replace the four address placeholder values, or repoint those mappings at custom fields carrying the real address per location.
Where the store has more than one real location, arrange for per-location addresses rather than accepting the same fixed address on every source.
Transfer locations before configuring the inventory source-code translation, so the real source codes are known.
Enable the outbound flow for Adobe Commerce/Magento 2 locations on the subscription's Outbound Data Flows page.
Full step-by-step setup instructions are in the Adobe Commerce/Magento 2 Installation Instructions article.
Integration Flow
A Location record is created or updated in iPaaS.com, or a Manual Sync is run against one.
The location is processed by this collection. It carries no filter, so every location record is processed.
The location's name is written as both the Magento source code and the source's display name, and its description is carried across.
The enabled flag and the four address values are supplied as fixed values.
The inventory source is created or updated in Adobe Commerce/Magento 2, and iPaaS.com records the link between the two.
The resulting source code is then available for the inventory source-code translation the inventory collections use.
Mappings
Add/Update Adobe Commerce/Magento 2 Location FROM iPaaS.com
iPaaS.com data type: Location
This collection carries no mapping filter — every iPaaS.com Location record is processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Adobe Commerce/Magento 2) | Description |
Field | Name | SourceCode | Required. The Magento inventory source code, taken from the location name. This is the value the inventory source-code translation must later point at, and it is case-sensitive. It cannot be changed once the source exists. |
Field | Name | Name | Required. The source's display name in the Magento admin, taken from the same location name. |
Static |
| Enabled | Required by design. Each source arrives active and available for stock assignment. This is a designed constant rather than a placeholder; a source disabled by hand in Magento is re-enabled on the next transfer. |
Static |
| CountryId | Required. The source address country as a two-letter ISO code. Placeholder value — replace during implementation: replace with the source's real country code. |
Static |
| Region | Required. The source address region. Placeholder value — replace during implementation: the shipped value is a city name in the region field. Magento validates the region against the country, so this is likely to be rejected as delivered. Replace it with the real state or province. |
Static |
| City | Optional. The source address city. Placeholder value — replace during implementation: replace with the source's real city. |
Static |
| Street | Optional. The source address street line. Placeholder value — replace during implementation: replace with the source's real street. |
Static |
| Postcode | Optional. The source address postal or ZIP code. Placeholder value — replace during implementation: the shipped value is a city name in the postcode field. Replace it with the real postal code. |
Field | Description | Description | Optional. The source description shown alongside the source in the Magento admin. |
Error Handling
The full catalog of messages this integration produces, with causes and resolutions, is in the Adobe Commerce/Magento 2 Error Messages article. The conditions most often seen on this transfer are:
A source rejected for an invalid region. The region value is not a valid region for the country supplied. Resolution: replace the placeholder region with a real state or province for that country.
A source rejected for an invalid address. Another address field is not acceptable to Magento. Resolution: replace the remaining placeholder address values.
A duplicate source alongside an existing one. No external-ID link existed, so a new source was created rather than the existing one being reused. Resolution: because sources cannot be deleted, disable the unwanted one in the Magento admin.
A failed inventory index after a later inventory transfer. Caused by a source code whose casing does not match what the inventory translation points at. Resolution: correct the casing and reindex in Magento.
Errors are reported under Dashboard / Integration Monitoring / Error Logs.
Testing & Validation
Test Scenarios
Transfer a Location from iPaaS.com and confirm a Magento inventory source is created with the expected source code and name.
Manually sync using the iPaaS.com Location record identifier and confirm it resolves; confirm the location name does not.
Confirm the source arrives enabled.
Attempt a transfer with the shipped placeholder region in place and confirm whether Magento accepts or rejects it, so the behavior is known before go-live.
Replace all four address placeholders and confirm the source is created with the real address.
Transfer two different locations and confirm both receive the same fixed address, so the limitation is understood.
Update the location description in iPaaS.com and confirm the same Magento source is updated rather than a second one created.
Correct a source's address by hand in the Magento admin, re-transfer the location, and confirm the fixed value replaces it.
Confirm the resulting source code, exactly as cased in Magento, is what the inventory source-code translation points at.
Disable a source in the Magento admin, re-transfer, and confirm it is re-enabled.
Validation Checklist
Every source code is correct, including casing, before the first transfer — they cannot be deleted afterwards.
The four address placeholder values have been replaced, or the mappings repointed at per-location custom fields.
The region value is a real state or province for the country supplied.
Stores with more than one real location have per-location addresses rather than one shared fixed address.
The inventory source-code translation points at the source codes this collection actually created.
Additional Notes
This collection is a prerequisite for every inventory transfer in the integration. The source codes it creates are what the inventory source-code translation resolves to.
The permanence of Magento inventory sources makes the first transfer the important one. Confirm codes before running it.
Four of the nine mappings send fixed address values that are not read from iPaaS.com. Replacing them is a required implementation step, not an optional refinement.
Validate the address values in a staging environment before enabling automatic transfers in production.