Orderful purchase orders (EDI 850) can be transferred to iPaaS.com as transactions, including their addresses and line items. The integration records the order header along with the Orderful EDI detail (sender and receiver identifiers, reference numbers, dates, and message status).
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the Orderful transaction ID. Example: 1009.
External ID Format
iPaaS.com saves the Orderful transaction ID as the external ID on a dedicated external-ID record (the primary match for later updates). The purchase order number is also stored in the transaction number field for visibility, where it serves as a fallback match key when no external-ID record yet exists.
Deleted Record Support
Outbound delete is not supported. Deletions are not propagated to Orderful, and delete mappings are not included in the default templates.
Custom Field Support
The Orderful EDI detail is captured into iPaaS.com custom fields (business number, sender/receiver identifiers, reference numbers, dates, and message status) as part of the standard mapping. No additional custom-field configuration is required.
Mapping Collection Status
Status: Enabled (filtered to purchase order documents)
Trigger Events: Retrieved by polling. Subscribers schedule the poll cadence or trigger an on-demand poll from Dashboard / Integration Monitoring / Events.
Duplicate or Conflicting Mappings
Add Orderful Purchase Order FROM iPaaS.com transfers purchase orders in the opposite direction.
Update Orderful Purchase Order Status TO iPaaS.com updates the status of an existing purchase order.
Review the filters and Add/Update settings of these collections before enabling them together, and decide which system is the source of truth for purchase order data.
Supported Child Collections
Add Orderful Purchase Order Address TO iPaaS.com — the billing and shipping addresses on the order.
Add Orderful Purchase Order Line TO iPaaS.com — the line items on the order.
System Caveats
Orderful Caveats
Orderful does not provide an email address in standard EDI fields, so a static placeholder email is used on the transaction (replace it if a real address is needed). Many Orderful EDI elements are carried as custom fields for reference.
iPaaS.com Caveats
Addresses and line items are recorded through the child collections; a complete order needs at least one of each. The transaction status is set from the Orderful status through a lookup translation.
Integration Flow
A purchase order (850) is retrieved from Orderful by polling (or on demand via Manual Sync).
The integration creates the iPaaS.com transaction with the order header and the Orderful EDI detail.
The order's addresses and line items are recorded through the child collections.
The Orderful transaction ID is saved as the external ID.
Mappings
Add Orderful Purchase Order TO iPaaS.com
Mapping Filter: Type.Name == "850_PURCHASE_ORDER" — only transactions whose type is an 850 purchase order are processed; transactions of any other type are skipped.
The order header, including the Orderful EDI identifiers, dates, reference numbers, totals, and status.
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Static | EmailAddress | Placeholder — Orderful does not provide an email in EDI; replace before go-live. | |
Field | BusinessNumber | Orderful BusinessNumber | The trading-partner relationship the order belongs to. |
Field | BeginningSegmentForPurchaseOrder_Date | Orderful Date | The date the purchase order was created. |
Field | Delivered_DateTimeReference_Date | Orderful Delivered DateTimeReference Date | The date corresponding to the delivered date/time qualifier. |
Field | Delivered_DateTimeReference_DateTimeQualifier | Orderful Delivered DateTimeReference DateTimeQualifier | Type of date given (DTM02); for example 002 means Delivery Requested. |
Field | href | Orderful href | The Orderful API address of the transaction message, for reference. |
Field | AcknowledgmentStatus | Orderful Message Acknowledgement Status | APPROVED or REJECTED. |
Field | DeliveryStatus | Orderful Message Delivery Status | DELIVERED or FAILED. |
Field | BeginningSegmentForPurchaseOrder_PurchaseOrderTypeCode | Orderful Purchase Order Code Type | Type of order; for example SA means Standalone. |
Field | BeginningSegmentForPurchaseOrder_PurchaseOrderNumber | Orderful Purchase Order Number | The purchase order number. |
Field | Receiver_IsaId | Orderful Receiver IsaId | The receiver's ISA interchange ID. |
Field | Receiver_IsaIdQualifier | Orderful Receiver IsaIdQualifier | The qualifier for the receiver's ISA interchange ID. |
Field | Receiver_Name | Orderful Receiver Name | The name of the party receiving the order. |
Field | ReferenceIdentificationQualifier | Orderful Reference ID Qualifier | Type of reference (REF01); for example DP means Department Number. |
Field | ReferenceIdentification | Orderful Reference Identification | The reference identification value. |
Field | Sender_IsaId | Orderful Sender isaID | The sender's ISA interchange ID. |
Field | Sender_IsaIdQualifier | Orderful Sender IsaIdQualifier | The qualifier for the sender's ISA interchange ID. |
Field | Sender_Name | Orderful Sender Name | The name of the party sending the order. |
Field | Shipped_DateTimeReference_Date | Orderful Shipped DateTimeReference Date | The date corresponding to the shipped date/time qualifier. |
Field | Shipped_DateTimeReference_DateTimeQualifier | Orderful Shipped DateTimeReference DateTimeQualifier | Type of date given (DTM02) for the shipped date reference. |
Field | Stream | Orderful Stream | The Orderful stream the transaction was received on, such as TEST or LIVE. |
Field | TransactionSetHeader_TransactionSetControlNumber | Orderful Transaction Set Control Number | A control number unique within the transaction set (length 4 to 9). |
Field | BeginningSegmentForPurchaseOrder_TransactionSetPurposeCode | Orderful Transaction Set Purpose Code | Purpose of the order; 00 means Original. |
Lookup | Lookup Translation: Orderful Transaction Status To iPaaS | Status | Converts the Orderful transaction status to the iPaaS.com transaction status. |
Dynamic Formula | Sum of line quantity times unit price | Subtotal | The order subtotal, computed across the line items. |
Dynamic Formula | iPaaS.com subscription | SystemId | The subscription that owns the transaction. |
Dynamic Formula | Sum of line quantity times unit price | Total | The order total, computed across the line items. |
Dynamic Formula | Sum of line quantity | TotalQty | The total quantity, computed across the line items. |
Field | BeginningSegmentForPurchaseOrder_PurchaseOrderNumber | TransactionNumber | The purchase order number, stored for visibility and fallback matching. The Orderful transaction ID is the external-ID link. |
Static | "Order" | Type | Sets the iPaaS.com transaction type to Order. |
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.
Add Orderful Purchase Order Address TO iPaaS.com
The billing and shipping addresses on the order. Each address links to the parent transaction by a composite external ID made of the entity identifier code and the parent transaction ID (for example, ST then 4).
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Field | AddressInformation | Address1 | The first line of the address. |
Field | CityName | City | The city of the address. |
Field | Name | FirstName | The party name on the address. |
Dynamic Formula | Entity identifier code | IsPrimaryBilling | Marks the billing address; derived from the entity identifier code (BT = Bill To). |
Dynamic Formula | Entity identifier code | IsPrimaryShipping | Marks the shipping address; derived from the entity identifier code (ST = Ship To). |
Field | EntityIdentifierCode | Orderful Entity Identifier Code | The address role; for example BT (Bill To), ST (Ship To), BY (Buying Party). |
Field | PostalCode | PostalCode | The postal code of the address. |
Field | StateOrProvinceCode | Region | The two-character state or province code. |
Add Orderful Purchase Order Line TO iPaaS.com
The line items on the order. Each line links to the parent transaction by a composite external ID made of the line number and the parent transaction ID (for example, 1 then 4).
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Field | Description | Description | A free-form product description. |
Dynamic Formula | Quantity times unit price | ExtendedPrice | The extended price for the line. |
Field | AssignedIdentification | Orderful Assigned Identification | The line number of the item. |
Field | ItemDescriptionTypeCode | Orderful Item Description Code Type | Type of item description (PID05); F means Free-Form. |
Field | ProductServiceID | Orderful Product Service ID | The product/service identifier per the qualifier (PO105). |
Field | ProductServiceID1 | Orderful Product Service ID 1 | The second product/service identifier value (PO107). |
Field | ProductServiceIDQualifier | Orderful Product Service ID Qualifier | Type of item reference (PO106); UP means Universal Product Code. |
Field | ProductServiceIDQualifier1 | Orderful Product Service ID Qualifier 1 | The second item reference qualifier (PO108); VN means Vendor's Item Number. |
Field | UnitOrBasisForMeasurementCode | Orderful Unit | The unit of measure for the quantity (PO103); CA means Case. |
Field | Quantity | Qty | The quantity ordered. |
Field | ProductServiceID | Sku | The product/service identifier used as the line SKU (PO105). |
Static | "Pending" | Status | Sets each line's status to Pending. |
Static | "Product" | Type | Sets each line's type to Product. |
Field | UnitPrice | UnitPrice | The price of the item for the unit of measure. |
Error Handling
See the Orderful Error Messages article for the full catalog. This inbound flow surfaces errors such as "The Transaction Type is not valid" (the returned transaction is empty or unsupported) — resolution: confirm the transaction type is supported and the transaction ID exists in Orderful.
Testing & Validation
Test Scenarios
Sync an Orderful purchase order by its transaction ID and verify the iPaaS.com transaction is created with its addresses and line items.
Update the order in Orderful and re-sync; verify the change propagates and the line items match by line number.
Confirm a non-purchase-order transaction is skipped by the filter.
Validation Checklist
The order header, addresses, and line items all transfer.
The purchase order number appears as the transaction number and the Orderful transaction ID is the external ID.
Line items and addresses match to existing children on re-sync rather than duplicating.
Related Documents