Summary
iPaaS.com Shipping Method entity can be transferred from Acumatica Enhancements Templates Latest Shipping Method entity through manual synchronization. iPaaS.com supports the synchronization of shipping method records from Acumatica using its API endpoint. Dynamic formulas are also applied to retrieve parent identifiers when applicable.
Mapping Collection Status
Status: Enabled
Trigger Events: Manual Sync, Update Event in Shopify
Id Format
When manually transferring data to iPaaS.com for a Shipping Method entity (e.g. ID 25), the correct ID must be entered into the iPaaS.com manual sync input field.
System Caveats
Acumatica Caveats
Some shipments may not contain a declared cost field.
iPaaS.com Caveats
Requires valid ParentId when linking shipments.
Setup Requirements
Acumatica Configuration
Sales Order endpoint must be enabled.
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
Acumatica Enhancements Templates Latest → iPaaS.com
Data is pushed using API calls.
Dynamic formula is used to derive parent transaction references.
Mappings
Mapping Filter
var parentId = await GetSpaceportIdAsync(TransactionID_, "Transaction", SpaceportSystemId);
if(parentId == null)
throw new exception("Transaction Tracking Number is not linked to any Transaction");
var getShipment = await FindShippingMethodFromName(Type);
if(getShipment == null)
throw new exception($"Shipping Method ({Type}) needs to be created manually in iPaaS first");
return true;
Description
This mapping filter checks if the transaction tracking number is linked to a transaction and ensures the shipping method exists in iPaaS; otherwise, it throws errors.
Mapping Type | Source (Acumatica) | Destination (iPaaS.com) | Description |
Dynamic Formula |
| ParentId | Returns the iPaaS transaction ID from Acumatica Transaction ID. If it exists; otherwise, it returns null. |
Field | Type | ShippingMethod |
|
Field | Description_Package_ | ShippingMethodDescription |
|
Field | TrackingNbr_Package | TrackingNumber |
|
Field | DeclaredValue_Package | Cost |
|
Error Handling
Collection: Sales Order Tracking Number
Invalid ParentId
Description: Returned null if no match is found.
Resolution: Ensure the transaction exists in the system.
Missing ShippingMethod
Description: The record will fail to sync without a shipping method value.
Resolution: Ensure the shipping method exists in the system. Collection: Sales Order Address
Missing Required Fields
Description:
FirstName,LastName,City, orCountryis null.Resolution: Validate all address fields in iPaaS before syncing.
Collection: Sales Order Address
Invalid Postal Code
Description: The
PostalCodeformat fails the regex check for numeric values.Resolution: Correct the postal code to a valid format.
Collection: Sales Order Line
Invalid SKU
Description: The SKU (
InventoryID) is not found in Acumatica.Resolution: Verify the product exists in Acumatica before the order sync.
Quantity Zero or Negative
Description:
OrderQtyis less than or equal to 0.Resolution: Provide a valid quantity greater than 0.
Collection: Sales Order Payment
Payment Method Not Found
Description: The payment method (e.g.,
ONLINE) is not configured in Acumatica.Resolution: Add the payment method in Acumatica or update the mapping.
Collection: Sales Order Tax
TaxID Not Found
Description: The
TaxIDlookup fails to find a matching ID in Acumatica.Resolution: Configure a matching TaxID in Acumatica.
Validation Rules & Testing
Test Scenarios
Valid Transaction: Shipping Method record is successfully created with ParentId linked.
Missing ParentId: Record sync should fail gracefully with proper error message.
Validation Checklist
ParentId retrieved successfully
ShippingMethod mapped correctly
TrackingNumber retained in iPaaS.com
DeclaredValue stored if present
Additional Notes
When syncing data, Parent Sales Order validation must pass before any child collections are synchronized.
Child collection errors such as an invalid line item, may prevent the entire order from being created, depending on Acumatica configuration.
To prevent frequent syncing errors, it is crucial that Financial Terms and Tax Zones are preconfigured in Acumatica.
Use external ID lookups whenever possible for the most reliable mapping across systems.