Summary
An Acumatica StockItem can be transferred to iPaaS Product through API-based synchronization. iPaaS automatically syncs product master data, such as SKU, descriptions, pricing, units of measure, weight, and warehouse-level details, ensuring consistency between systems.
Mapping Collection Status
Status: Enabled
Trigger Events: Create, Update of Stock Items in Acumatica
Id Format
When manually transferring a stock item from Acumatica to iPaaS, the correct Inventory ID (SKU) must be entered into iPaaS.
Supported Child Collections
Parent Collection: Stock Item
Child Collection: Stock Item Warehouse Detail
System Caveats
Acumatica Caveats
Product Type must be explicitly mapped.
Field constraints apply on Name and Description length.
iPaaS.com Caveats
Requires unique SKU per product.
All custom field IDs must be correctly configured.
Integration-Specific Caveats
The system handles duplicate records by updating existing products with the same SKU instead of creating new ones.
Error handling ensures all required fields are validated.
Setup Requirements
Acumatica Configuration
Stock Item endpoint must be enabled.
Warehouse detail expansion must be allowed.
iPaaS.com Configuration
Product mapping collection must be active.
Warehouse location ID translation logic must be enabled.
Authentication & Security
OAuth 2.0 / API Key: Required for both Acumatica and iPaaS.com endpoints.
Integration Flow
The product synchronization process between Acumatica and iPaaS follows a clear sequence of steps:
Product Creation/Update: The process begins when a product is either created or updated in Acumatica.
API Push: The product data is then automatically pushed to iPaaS via the API.
Warehouse Detail Sync: The warehouse detail child collection is synchronized, providing specific location and quantity information.
iPaaS Record Update: Finally, the product record in iPaaS is created or updated with the synchronized data from Acumatica.
Mappings
Stock Item (Parent)
Mapping Type | Source Field (Acumatica) | Destination Field (iPaaS.com) | Description |
Static | Physical | Type | Product type, always set to Physical. |
Static | Product | Tracking Method | Tracking Method always set to Product. |
Dynamic Formula |
| Acumatica Product Tax Category | Retrieves the Category value |
Dynamic Formula |
| SKU | Retrieves Inventory Id |
Dynamic Formula |
| Description | Retrieves the Description |
Dynamic Formula |
| Default Price | Retrieves Default Price |
Dynamic Formula |
| Name | Retrieves Inventory Id |
Dynamic Formula |
| Status | Retrieves Item Status |
Dynamic Formula |
| Unit Price | Retrieves SalesUOM |
Dynamic Formula | Acumatica Sales Order Tracking Number From iPaaS (Standalone) | Weight | Retrieves Dimension Weight |
Stock Item WareHouse Detail (Child Collection)
Mapping Type | Source Field (Acumatica) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Cost | Retrieves the Category value |
Dynamic Formula |
| QtyAvailable | Retrieves Inventory Id |
Dynamic Formula |
| QtyOnHand | Retrieves the Description |
Dynamic Formula |
| Location | Retrieves Default Price |
Error Handling
Collection: Sales Order (Parent)
Invalid Customer ID
Description: The provided
CustomerIddoesn't exist in Acumatica.Resolution: Ensure an external ID mapping exists or provide a valid email for the fallback lookup.
Unsupported Financial Terms
Description: The specified term isn't configured in Acumatica (CS2065PL).
Resolution: Configure the appropriate credit terms in Acumatica before syncing.
Collection: Product (Parent)
Missing SKU
Description: SKU required but not provided.
Resolution: Ensure SKU maps correctly when transferring the product to iPaaS.
Invalid Price Format
Description:
DefaultPricemust be a decimal.Resolution: Format values correctly in Acumatica before sync.
Duplicate SKU
Description: iPaaS requires unique SKUs.
Resolution: Apply uniqueness validation or append identifiers.
Invalid WarehouseID
Description: Warehouse not mapped in iPaaS.
Resolution: Maintain warehouse ID translation logic.
Testing & Validation
Test Scenarios
Valid Product → Syncs successfully.
Missing SKU → Error logged, no sync.
SKU > 30 characters → Truncated/rejected.
Invalid WarehouseID → Mapping error on LocationId.
Validation Checklist
SKU populated
Price valid decimal
Type = Physical
Warehouse location mapping successful
Validation Rules
Warehouse Name must not be null.
Warehouse Name must be unique.
Warehouse Name must not exceed 50 characters.
Additional Notes
Warehouse detail mapping is crucial for maintaining accurate inventory availability. Without this information, iPaaS may not have a correct count of the products in stock, which can lead to errors in sales order processing and customer communication.