The status of an existing iPaaS.com purchase order transaction can be updated from Orderful. When Orderful reports a new status for a purchase order, this collection refreshes the transaction's status and its Orderful message acknowledgement and delivery status, while preserving all of the order's other values. This is an Update collection — it does not create new transactions.
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the Orderful transaction ID.
External ID Format
The update matches the existing iPaaS.com transaction by the Orderful transaction ID saved as the external ID. If no matching transaction exists, there is nothing to update.
Deleted Record Support
Not applicable — this collection only updates the status of an existing transaction.
Custom Field Support
The Orderful message acknowledgement and delivery status are recorded into iPaaS.com custom fields. No additional custom-field configuration is required.
Mapping Collection Status
Status: Enabled (filtered to purchase order documents)
Trigger Events: Retrieved by polling from Dashboard / Integration Monitoring / Events.
Duplicate or Conflicting Mappings
Add Orderful Purchase Order TO iPaaS.com brings in the original purchase order.
Add Orderful Purchase Order Acknowledgement TO iPaaS.com brings in the acknowledgement.
This collection updates existing transactions only. Review filters and Add/Update settings before enabling these together, and decide which system is the source of truth for purchase order status.
Supported Child Collections
None — this collection updates the transaction header only.
System Caveats
Orderful Caveats
The new status comes from Orderful and is converted to the iPaaS.com status through a lookup translation.
iPaaS.com Caveats
The transaction must already exist in iPaaS.com (matched by external ID) for the update to apply. All fields other than the status and message-status fields are re-supplied from the transaction's current values so they are not overwritten.
Integration Flow
A purchase order status change is retrieved from Orderful by polling (or on demand via Manual Sync).
The integration matches the existing iPaaS.com transaction by its external ID.
The transaction's status and Orderful message acknowledgement/delivery status are updated; all other fields are preserved.
Mappings
Update Orderful Purchase Order Status TO iPaaS.com
Mapping Filter: Type.Name == "850_PURCHASE_ORDER" — only purchase order transactions are processed; transactions of any other type are skipped.
The fields this collection updates, plus the preserve-existing-value mappings that protect the rest of the transaction.
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Lookup | Lookup Translation: Orderful Transaction Status To iPaaS | Status | The field this collection updates. Converts the Orderful transaction status to the iPaaS.com transaction status. |
Field | AcknowledgmentStatus | Orderful Message Acknowledgement Status | APPROVED or REJECTED. Updated on each status refresh. |
Field | DeliveryStatus | Orderful Message Delivery Status | DELIVERED or FAILED. Updated on each status refresh. |
Dynamic Formula | Existing value | CompanyId | Preserves the existing iPaaS.com company so the update does not overwrite it. |
Dynamic Formula | Existing value | CustomerId | Preserves the existing iPaaS.com customer so the update does not overwrite it. |
Dynamic Formula | Existing value | ParentId | Preserves the existing parent reference so the update does not overwrite it. |
Dynamic Formula | Existing value | TransactionNumber | Preserves the existing transaction number so the update does not overwrite it. |
Dynamic Formula | Existing value | Type | Preserves the existing transaction type so the update does not overwrite it. |
Dynamic Formula | Existing value | SystemId | Preserves the existing subscription that owns the transaction. |
Dynamic Formula | Existing value | TransactionCreatedDateTime | Preserves the existing transaction created date/time. |
Dynamic Formula | Existing value | EmailAddress | Preserves the existing email address. |
Dynamic Formula | Existing value | DiscountAmount | Preserves the existing discount amount. |
Dynamic Formula | Existing value | ShippingAmount | Preserves the existing shipping amount. |
Dynamic Formula | Existing value | TaxAmount | Preserves the existing tax amount. |
Dynamic Formula | Existing value | Subtotal | Preserves the existing subtotal. |
Dynamic Formula | Existing value | Total | Preserves the existing total. |
Dynamic Formula | Existing value | TotalQty | Preserves the existing total quantity. |
The Orderful Transaction Status To iPaaS lookup translation maps each Orderful transaction status to the corresponding iPaaS.com transaction status; the value pairs are maintained in that translation collection.
Error Handling
See the Orderful Error Messages article for the full catalog. If no matching transaction exists for the incoming status, there is nothing to update.
Testing & Validation
Test Scenarios
Bring in a purchase order, then process a status change from Orderful and verify only the status and message-status fields update on the existing transaction.
Confirm the order's other values (totals, customer, dates) are unchanged after the status update.
Process a status change for a purchase order that does not exist in iPaaS.com and confirm no new transaction is created.
Validation Checklist
The transaction status reflects the latest Orderful status.
The message acknowledgement and delivery status are recorded.
No other fields on the transaction are overwritten by the update.
Related Documents