Skip to main content

Acumatica to iPaaS.com Stock Item Mapping Documentation

How the Acumatica Stock Item integration captures product master data and per-warehouse inventory into iPaaS.com, including field mappings, ID format, and known limitations.

Summary

Acumatica Stock Item records can be transferred into iPaaS.com as Product records through API-based synchronization. The integration captures product master data — the inventory ID used as both SKU and Name, the item description, default price, sales unit of measure, dimension weight, item status, and the product tax category — so the iPaaS.com Product catalog stays aligned with the items maintained in Acumatica. Per-warehouse inventory (cost and quantities by location) is captured at the same time through a child collection. This is a one-directional capture into iPaaS.com: the integration reads from Acumatica and writes to iPaaS.com; it does not write product changes back into Acumatica through this collection.

ID Format

When manually transferring a Stock Item into iPaaS.com, supply the item's Acumatica inventory ID (the SKU) in the iPaaS.com input field on the Manual Sync page. The integration resolves that inventory ID to the underlying Stock Item record.

Each captured Stock Item is also identified in Acumatica by its record identifier, a system-generated value (for example, a430022e-26dc-e811-b816-00155d408001).

Child ID Format

Each warehouse-detail child is identified by the item inventory ID and the warehouse ID joined together (for example, ABC123|EQUIPHOUSE). This composite keeps exactly one inventory record per item per warehouse, so repeated transfers update the same per-warehouse record rather than creating duplicates.

External ID Format

After a successful transfer, the iPaaS.com Product is linked back to Acumatica by the Acumatica Stock Item record identifier. This external link is what allows later updates to resolve to the same iPaaS.com Product rather than creating a duplicate.

Custom Field Support

The Acumatica Product Tax Category is captured into a custom field on the iPaaS.com Product. The corresponding custom field must be configured in iPaaS.com for the value to be retained. Beyond this captured tax category, this collection does not map additional subscriber-defined custom fields.

Mapping Collection Status

  • Status: Enabled

  • Trigger Events: Create, Update of Stock Items in Acumatica (captured on the polling cadence or by Manual Sync)

Supported Child Collections

  • Parent Collection: Add/Update Acumatica Stock Item TO iPaaS.com

  • Child Collection: Add/Update Acumatica Stock Item Warehouse Detail TO iPaaS.com — captures warehouse-level inventory (cost, quantity on hand, available quantity, and location) for each warehouse associated with the Stock Item. This child runs as part of the parent Stock Item transfer and cannot be invoked on its own.

System Caveats

Acumatica Caveats

  • Stock Items must be accessible through the Acumatica web services endpoint, with warehouse detail expansion permitted, so that per-warehouse inventory can be captured by the child collection.

  • Acumatica enforces length and format constraints on fields such as the item description and inventory ID. Values that exceed Acumatica's limits will not be present in a form the integration can capture cleanly.

  • A warehouse record must be retrievable for each warehouse referenced on the item. A warehouse that cannot be read will not produce a captured detail record.

iPaaS.com Caveats

  • A unique SKU is required per Product. Two Acumatica Stock Items that resolve to the same SKU would update the same iPaaS.com Product.

  • The product tax category is captured into a custom field on the iPaaS.com Product. That custom field must be configured for the value to be retained.

  • Acumatica warehouse names must resolve to configured iPaaS.com locations for the warehouse detail to capture correctly.

Integration-Specific Caveats

  • Fixed product classification: Every captured product is assigned Type = Physical and Tracking Method = Product. These values are set by the integration and are not read from Acumatica.

  • Inventory ID reuse: The Acumatica inventory ID populates both the iPaaS.com SKU and the Name. A product whose inventory ID is empty cannot be reliably matched or displayed; subscribers should confirm inventory IDs are populated in Acumatica.

  • Duplicate handling: Repeated transfers of the same item update the existing iPaaS.com Product that shares the same SKU rather than creating a new one.

  • Warehouse location translation: Warehouse-level detail is mapped to iPaaS.com locations through a name-to-location translation handled by the child collection. The Acumatica warehouse name must resolve to a configured iPaaS.com location.

  • Dynamic formula field references use the Acumatica field names exactly as they appear on the Stock Item record and are case-sensitive.

Setup Requirements

Acumatica Configuration

  • The Acumatica Stock Item web services endpoint must be enabled, with warehouse detail expansion permitted.

  • Tax categories should be configured on the items in Acumatica so the value is available to capture.

iPaaS.com Configuration

  • The iPaaS.com Product mapping collection must be active.

  • A custom field for the Acumatica product tax category must be configured in iPaaS.com if the tax category value is to be retained.

  • iPaaS.com locations must be configured so that Acumatica warehouse names resolve to locations for the warehouse detail child collection.

  • Polling must be enabled and configured for Stock Items so that changed items are captured on a recurring cadence. Without polling enabled, items are captured only by Manual Sync.

Authentication & Security

Both systems are accessed over secure API connections. The Acumatica connection is authorized through OAuth 2.0 against the Acumatica instance, and every request carries the company identifier so the integration reads from the correct Acumatica company.

Integration Flow

  1. A Stock Item is created or updated in Acumatica.

  2. The integration captures the change on its polling cadence, or a subscriber runs a Manual Sync by supplying the item's inventory ID. Polling must be enabled for recurring capture; until then, capture happens only through Manual Sync.

  3. The integration retrieves the item from Acumatica by its inventory ID and expands its warehouse details.

  4. An iPaaS.com Product record is built from the mapped fields. If a Product with the same SKU already exists, the existing record is updated; otherwise a new Product is created.

  5. For each warehouse associated with the item, the warehouse-detail child collection captures cost, on-hand quantity, available quantity, and the resolved iPaaS.com location.

  6. The captured Product is linked back to Acumatica by the Acumatica record identifier so later updates resolve to the same iPaaS.com Product.

Mappings

Add/Update Acumatica Stock Item TO iPaaS.com (Parent)

This collection does not have a mapping filter applied. Every Stock Item that the integration polls or that is manually transferred is processed without additional filtering conditions. Subscribers who want to capture only a subset of items can add a mapping filter to restrict which Stock Items are processed.

Mapping Type

Source Field (Acumatica)

Destination Field (iPaaS.com)

Description

Dynamic Formula

InventoryID.Value

SKU

Required. Captures the Acumatica inventory ID as the iPaaS.com Product SKU. The SKU is the key that links the captured product to its iPaaS.com Product record and to its warehouse-detail children; a Product with a matching SKU is updated rather than duplicated. Validate in a staging environment that every Stock Item produces a unique, non-empty inventory ID.

Dynamic Formula

InventoryID.Value

Name

Recommended. Captures the Acumatica inventory ID as the product display name. The same inventory ID also populates SKU.

Dynamic Formula

Description.Value

Description

Recommended. Captures the Acumatica item description. Acumatica enforces a length constraint on the description; values are captured as stored in Acumatica.

Dynamic Formula

DefaultPrice.Value

Default Price

Recommended. Captures the item's default price set in Acumatica. Validate in staging that the captured value is in the expected currency and format.

Dynamic Formula

ItemStatus.Value

Status

Recommended. Captures the Acumatica item status (for example, active or inactive). The captured value reflects Acumatica's status vocabulary.

Dynamic Formula

SalesUOM?.Value

Unit

Recommended. Captures the sales unit of measure (for example, each, box, or kilogram). Read only when a sales unit of measure is present.

Dynamic Formula

DimensionWeight?.Value

Weight

Recommended. Captures the item's dimension weight for downstream use such as shipping. Read only when a dimension weight is present; items without a weight leave this field empty.

Dynamic Formula

TaxCategory?.Value

Acumatica Product Tax Category

Recommended. Captures the item's tax category into a custom field for downstream tax handling. Read only when a tax category is present. The corresponding custom field must be configured in iPaaS.com for the value to be retained.

Static

"Physical"

Type

Required static value. Sets the product type to Physical for every captured item. Applied by the integration; not read from Acumatica. Should not be changed.

Static

"Product"

Tracking Method

Required static value. Sets the tracking method to Product for every captured item. Applied by the integration; not read from Acumatica. Should not be changed.

Add/Update Acumatica Stock Item Warehouse Detail TO iPaaS.com (Child Collection)

This child collection runs as part of the parent Stock Item transfer and is never invoked on its own. It does not have a mapping filter applied; every warehouse on the parent Stock Item is processed. Dynamic formula references use the Acumatica field names exactly as they appear, including the Parent. prefix for values read from the parent Stock Item, and are case-sensitive.

Mapping Type

Source Field (Acumatica)

Destination Field (iPaaS.com)

Description

Dynamic Formula

await ConvertAcumaticaAttributNameToIpaasLocationId(WarehouseID.Value);

Location

Recommended. Translates the Acumatica warehouse name into the matching iPaaS.com location. This is the key that ties the captured cost and quantities to a specific location. The warehouse name must resolve to a configured iPaaS.com location; a name that does not resolve leaves the location unset for that warehouse, and an error appears in the Dashboard.

Dynamic Formula

QtyOnHand.Value

QtyOnHand

Recommended. Captures the on-hand inventory count for the item at the warehouse. This is the basis for the captured availability and should be validated against Acumatica during setup.

Dynamic Formula

QtyOnHand.Value

QtyAvailable

Recommended. Captures available quantity from the same Acumatica on-hand quantity as QtyOnHand. The integration does not subtract allocations or reservations to derive a separate available figure. Validate in staging if your availability logic must distinguish on-hand from available.

Dynamic Formula

Parent.LastCost?.Value

Cost

Recommended. Captures the most recent cost recorded for the item, read from the parent Stock Item. This is the parent item's last cost rather than a warehouse-specific cost. Read only when a last cost is present.

Error Handling

Errors raised during a Stock Item transfer appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs. The most common conditions are:

  • Warehouse name does not resolve to an iPaaS.com location: An Acumatica warehouse name on the item has no matching iPaaS.com location, so the warehouse detail for that location is not captured. Resolution: maintain the location translation so every warehouse used by captured items resolves to a configured iPaaS.com location.

  • Empty or non-unique inventory ID: A Stock Item whose inventory ID is empty cannot be reliably matched or displayed, and two items resolving to the same SKU update the same iPaaS.com Product. Resolution: confirm every Stock Item has a unique, non-empty inventory ID in Acumatica.

  • Acumatica temporarily unavailable: If the Acumatica web services endpoint is unavailable during a transfer, the capture fails and the item is re-captured on the next poll or Manual Sync. Resolution: confirm Acumatica is reachable, then allow the next poll or re-run the Manual Sync.

For shared error message wording and resolutions across the integration, see the Acumatica Error Messages article.

Testing & Validation

Test Scenarios

  1. Create a new Stock Item in Acumatica and verify it syncs to iPaaS.com as a Product with the inventory ID populating both SKU and Name.

  2. Update the description or default price on an existing Stock Item and verify the change propagates on the next transfer.

  3. Run a Manual Sync for a single item by supplying its inventory ID and confirm the Product is created or updated.

  4. Transfer an item that has warehouse details across more than one warehouse and confirm a per-warehouse inventory record is captured for each resolved location.

  5. Transfer an item that references a warehouse name with no configured iPaaS.com location and confirm the missing-location error appears in the Dashboard.

Validation Checklist

  • Inventory ID is populated and unique on every captured item

  • SKU and Name both reflect the inventory ID

  • Default price is a valid numeric value in the expected format

  • Type resolves to Physical and Tracking Method to Product

  • Each warehouse on the item resolves to a configured iPaaS.com location

  • QtyOnHand and QtyAvailable reflect the Acumatica on-hand quantity

Additional Notes

  • Warehouse detail capture is important for accurate downstream availability. Without per-location quantities, iPaaS.com may not hold a correct count of products in stock, which can affect order processing and customer-facing availability.

  • QtyAvailable is populated from the same Acumatica on-hand quantity as QtyOnHand. The integration does not derive a separate available figure by subtracting allocations or reservations. Subscribers whose availability logic must distinguish the two should validate this behavior in a staging environment before relying on it in production.

  • Capture is one-directional. Changes made to a Product in iPaaS.com are not written back to the Acumatica Stock Item through this collection.

Did this answer your question?