Summary
Acumatica Warehouse records can be transferred into iPaaS.com through an API-based capture, where each warehouse becomes an iPaaS.com Location. The integration maps the Acumatica warehouse identifier to the Location Name and the warehouse description to the Location Description. This is a one-directional capture: data moves from Acumatica into iPaaS.com only; warehouse records are not written back to Acumatica through this collection.
Warehouse Locations underpin per-warehouse inventory: when Stock Item availability is captured by warehouse, each warehouse name must resolve to a Location that already exists in iPaaS.com. For that reason this collection is typically run before Product and inventory data is integrated.
ID Format
The external identifier for each Location is the Acumatica Warehouse ID — the warehouse's primary identifier in Acumatica (for example, EQUIPHOUSE). When capturing a single warehouse through Manual Sync, enter this Warehouse ID into the iPaaS.com input field on the sync page. To refresh the full set, run the Manual Sync without a specific identifier so all warehouses are read.
External ID Format
After a successful transfer, the iPaaS.com Location is linked back to Acumatica by the Acumatica Warehouse ID. This external link is what allows repeated transfers of the same warehouse to update the existing Location rather than create a duplicate.
Custom Field Support
Custom field mappings are not supported on this collection. Only the warehouse identifier and description are captured into the iPaaS.com Location.
Mapping Collection Status
Status: Enabled
Trigger Events: Manual Sync (capture on demand). There is no automatic warehouse trigger.
Supported Child Collections
None. This is a standalone parent collection with no parent and no child collections.
System Caveats
Acumatica Caveats
Warehouse identifier uniqueness: In multi-branch Acumatica configurations the warehouse identifier may need to be unique per branch. Subscribers running multi-branch setups should confirm their warehouse identifiers are distinct enough to resolve unambiguously to a single Location.
Warehouse must be exposed in the Acumatica API: The warehouse entity must be available through the Acumatica web services endpoint the integration uses. Warehouses that are not retrievable through the API cannot be captured.
iPaaS.com Caveats
Location identity is keyed on the warehouse identifier. Two Acumatica warehouses that resolve to the same identifier value would map to the same iPaaS.com Location. Keep warehouse identifiers distinct.
The warehouse identifier becomes the Location Name. A Location is most useful when it carries a meaningful name; subscribers should validate the behavior of empty or duplicate name values in a staging environment before relying on it in production.
Setup Requirements
Acumatica Configuration
The warehouse entity must be available through the Acumatica web services endpoint.
Each warehouse intended for capture should have a valid Warehouse ID in Acumatica.
iPaaS.com Configuration
The Acumatica connection must be configured and authorized so the integration can read warehouse records.
Authentication & Security
The Acumatica connection is authorized through OAuth 2.0 against the Acumatica instance, and every request carries the company identifier so the integration reads warehouses from the correct Acumatica company.
Initialization Support
This collection supports a bulk Initialization (bulk pull) in addition to single-record Manual Sync. A bulk initialization reads the full set of warehouses from Acumatica in one pass and is useful when the Location records need to be in place before related Product data is integrated — for example, when inventory availability is captured per warehouse. Bulk initialization is triggered from the Location area of the integration.
Bulk initialization is only needed by subscribers who integrate warehouses from Acumatica. Subscribers who do not use warehouse data do not need to run it.
Integration Flow
A subscriber runs a Manual Sync — for a single warehouse by entering its Warehouse ID, or for the full set by running the sync without a specific identifier — or runs a bulk Initialization to read all warehouses at once.
The integration reads each warehouse record from Acumatica.
The warehouse identifier is captured as the Location Name and the warehouse description as the Location Description.
If a Location already linked to that Warehouse ID exists, it is updated in place; otherwise a new Location is created.
The Acumatica Warehouse ID is stored as the external identifier so later transfers resolve to the same Location.
Because there is no automatic trigger, subscribers who need warehouse changes reflected in iPaaS.com should run the Manual Sync on the cadence appropriate to how often their warehouse list changes in Acumatica.
Mappings
Add/Update Acumatica Warehouse TO iPaaS.com
This collection does not have a mapping filter applied. All warehouse records read from Acumatica are processed without additional filtering conditions.
Mapping Type | Source Field (Acumatica) | Destination Field (iPaaS.com) | Description |
Field | Name | Name | Recommended. Captures the Acumatica warehouse identifier as the Location Name (for example, EQUIPHOUSE). This is the human-readable identifier and the value other collections reference when resolving a warehouse to a Location, and it is also used as the external link back to the Acumatica source. Validate the behavior of empty or duplicate name values in staging, since two warehouses resolving to the same value map to the same Location. |
Field | Description | Description | Optional. Captures the Acumatica warehouse description as the Location Description. Free-text context only; it does not affect how the Location is identified or referenced. If the warehouse has no description, the Location is captured without one. |
Error Handling
Errors raised during a Warehouse transfer appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs. The most common conditions are:
Acumatica temporarily unavailable: If Acumatica is unavailable during a transfer, the warehouse capture fails. Resolution: confirm Acumatica is reachable, then re-run the Manual Sync.
Duplicate or ambiguous warehouse identifier: Two warehouses that resolve to the same identifier map to the same Location, which can overwrite the intended record (most relevant in multi-branch setups). Resolution: confirm warehouse identifiers are distinct enough to resolve unambiguously to a single Location.
For shared error message wording and resolutions across the integration, see the Acumatica Error Messages article.
Testing & Validation
Test Scenarios
Run a Manual Sync for a single warehouse by entering its Warehouse ID and verify a Location is created in iPaaS.com with the matching Name.
Update the description on an existing warehouse in Acumatica, re-run the sync, and verify the Location Description updates in place rather than creating a duplicate.
Run a bulk Initialization and verify all warehouses are captured as Locations in a single pass.
In a multi-branch setup, verify each warehouse identifier resolves to a single distinct Location.
Validation Checklist
Location Name reflects the Acumatica Warehouse ID
Description is captured when present and omitted when absent
Repeated transfers update the existing Location rather than creating duplicates
Warehouse identifiers are distinct across branches
Additional Notes
Product-data dependency: This collection is typically run first so that warehouse Locations exist before Stock Item inventory is integrated. Per-warehouse availability captured by the Stock Item Warehouse Detail collection depends on each Acumatica warehouse name resolving to a configured iPaaS.com Location. If Locations are not in place first, warehouse detail for unresolved names will not capture.
This collection is only required for subscribers who integrate warehouses from Acumatica. Subscribers who do not use warehouse data do not need to run this collection or perform a bulk initialization.
Capture is one-directional. Warehouses flow from Acumatica into iPaaS.com only; there is no write-back path.