Summary
Adobe Commerce/Magento 2 sales orders are transferred into iPaaS.com as Transaction records. The order header is the parent record, and nine child collections write the order's lines, payments, tax, billing address, and shipping address onto that same Transaction as part of the same transfer. The transfer is unidirectional: orders move from Adobe Commerce/Magento 2 into iPaaS.com, and this family does not write orders back to Magento.
A single mapping definition handles both new orders and subsequent updates to orders already transferred.
ID Format
Manual Sync ID Format
Enter the Adobe Commerce/Magento 2 order record identifier — the internal numeric entity identifier of the order, for example 1234.
This is not the order number shown on the storefront and in the Magento admin order grid (for example 000000123); it is the underlying record identifier for that order. Entering the storefront order number will not resolve an order.
External ID Format
After a successful transfer, iPaaS.com stores the Adobe Commerce/Magento 2 order record identifier as the external ID on a dedicated external-ID record that links the Magento order to the iPaaS.com Transaction. That external-ID record is the primary mechanism routing later transfers of the same order to the existing Transaction for an Update rather than creating a duplicate.
The Magento order number is separately written into the Transaction's TransactionNumber field, which serves both as the human-readable reference and as a fallback match when no external-ID record yet exists.
Deleted Record Support
Outbound delete is not supported for orders. Deleting or removing an order in Adobe Commerce/Magento 2 does not remove the corresponding Transaction from iPaaS.com, and delete mappings are not included in the default templates for this family.
Cancelling an order in Magento is a status change rather than a deletion. A cancelled order continues to transfer, and its status arrives through the status translation described under Lookup Translations below.
Custom Field Support
Several destination fields in this family are iPaaS.com custom fields rather than standard Transaction fields. They must exist in the subscriber's iPaaS.com environment before the mappings that populate them will land:
SellingUnit on the Transaction Line, carrying the order line's unit of measure.
Giftcard Number, Giftcard Message, and Giftcard Shippedto Recipient on the Transaction Line, carrying gift-card detail from gift-voucher lines.
Giftcard Number and AuthCode on the Transaction Payment, carrying the redeemed card and its authorization reference.
Each of these is optional or informational. A missing custom field leaves the value unrecorded; it does not fail the order transfer.
Mapping Collection Status
Status: Enabled. This collection ships enabled and processes every Adobe Commerce/Magento 2 order that passes its mapping filter.
Trigger Events: Order created and order updated in Adobe Commerce/Magento 2, plus Manual Sync on demand.
Adobe Commerce/Magento 2 has no native webhook capability, so the event notifications that drive automatic transfers depend on a third-party webhook extension being installed and configured in the Magento store. Until both that extension and the subscription's Inbound Data Flows entry for Magento orders are in place, no orders arrive automatically. Manual Sync is always available regardless.
Duplicate or Conflicting Mappings
Two other parent collections read the same Adobe Commerce/Magento 2 orders and are separated from this one only by the order-number suffix in their filters:
Add Adobe Commerce/Magento 2 Deposit Ticket TO iPaaS.com processes the orders whose order number ends in -D.
Add/Update Adobe Commerce/Magento 2 Gift Card Ticket TO iPaaS.com processes the orders whose order number ends in -GC.
Because all three families operate over the same underlying Magento orders, the suffix conditions in the three filters are what prevent one order from being processed twice into conflicting iPaaS.com Transactions. Subscribers or their MiSP should review all three filters together before enabling or modifying any of them. Loosening the suffix conditions on any one collection can cause the same Magento order to be written by more than one collection.
Duplicate matching
This integration implements no selectable collision-handling methods, and the behavior is not configurable on this collection. Two mechanisms decide whether an incoming order produces an Add or an Update:
Primary match — the external-ID record. Once an order has synced successfully, iPaaS.com maintains a record linking the Magento order to the iPaaS.com Transaction, and later transfers of that order route to the linked Transaction for an Update.
Fallback match — TransactionNumber. When no external-ID record yet exists, typically on first sync or after the external-ID record has been cleared, iPaaS.com looks for an existing Transaction whose TransactionNumber matches the incoming Magento order number and links to it rather than creating a duplicate.
If neither mechanism matches, a new Transaction and a new external-ID record are created.
Unmapped field overwrite risk
Because the fallback match depends on TransactionNumber carrying the Magento order number, remapping that field to a different source removes the auto-link for any pre-existing Transactions and makes duplicates possible on first sync.
When an order is re-transferred, the mapped values in this family are written again over the existing Transaction. Values a subscriber has edited directly in iPaaS.com on a mapped field will be replaced by the Magento value on the next transfer. Subscribers or their MiSP should validate this behavior in a staging environment before relying on manual edits to any field this family maps.
The fields at risk are every field this family maps — on the Transaction header SystemId, TransactionNumber, Type, Status, EmailAddress, DiscountAmount, TaxAmount, ShippingAmount, Subtotal, Total, TotalQty and TransactionCreatedDateTime — together with the line, payment, tax and address values written by the nine child collections.
The mitigation is a DestinationValue. Where an iPaaS.com field must hold a specific value that the source order does not supply, set a DestinationValue on that mapping so the integration writes the value chosen there instead of taking it from the source. Values that must be maintained only in iPaaS.com should be kept on fields these collections do not map.
Supported Child Collections
The parent collection is Add/Update Adobe Commerce/Magento 2 Order TO iPaaS.com. It is the parent of nine child collections, each of which writes its records onto the Transaction created or updated by the parent, and none of which transfers independently of it:
Add/Update Adobe Commerce/Magento 2 Order Line TO iPaaS.com: the order's ordinary product lines.
Add/Update Adobe Commerce/Magento 2 Order Line Gift Card TO iPaaS.com: the order's gift card lines.
Add/Update Adobe Commerce/Magento 2 Order Payment TO iPaaS.com: payments for every tender other than gift card.
Add/Update Adobe Commerce/Magento 2 Order Payment Gift Card TO iPaaS.com: gift card tender payments.
Add/Update Adobe Commerce/Magento 2 Order Tax TO iPaaS.com: the order's single consolidated tax record.
Add/Update Adobe Commerce/Magento 2 Order Bill Address TO iPaaS.com: the order's billing address.
Add/Update Adobe Commerce/Magento 2 Order Ship Address Flat Rate Fixed TO iPaaS.com: shipping address for Flat Rate - Fixed orders.
Add/Update Adobe Commerce/Magento 2 Order Ship Address Free Shipping TO iPaaS.com: shipping address for Free Shipping - Free orders.
Add Adobe Commerce/Magento 2 Order Ship Address Unmapped TO iPaaS.com: shipping address for every other shipping description.
The three shipping address variants are mutually exclusive by design — their filters partition orders by shipping description so that exactly one of them applies to any given order. Subscribers or their MiSP who add a new shipping method in Magento should confirm which variant it falls into, and adjust the filters if the new method needs its own handling rather than the catch-all.
System Caveats
Adobe Commerce/Magento 2 Caveats
Order statuses beyond the shipped set are not translated. The Status mapping ships with rows for Magento's standard pending, processing, complete, canceled, and completing statuses. Magento stores commonly define custom order statuses. A Magento status with no matching row is simply not translated — no value is sent for Status and no error is raised.
Webhook capability requires a third-party extension. Adobe Commerce/Magento 2 does not provide webhooks natively. The extension that supplies them must be installed and configured in the Magento store before automatic transfers can occur.
Custom fraud-review statuses are not excluded by default. The shipped filter excludes only Magento's built-in suspected fraud and fraud statuses. Stores using a fraud-screening extension that sets its own status values should extend the filter accordingly.
Gift-card lines are matched on one product type. Different third-party Magento gift card extensions expose different product type codes. The shipped line collections are configured for the giftvoucher code; a store running an extension that uses a different code, such as amgiftcard, must update the filters and the line Type formula on both the ordinary and the gift-card line collections. Left unchanged, those lines transfer as ordinary product lines, typed as Product and carrying no gift card reference, and no error is raised. The full list of values to change is in the Known Limitations article.
Order retrieval volume is subject to Magento's API limits. Larger stores and large historical catch-up runs can encounter Adobe Commerce/Magento 2 request-array and page-size limits. Subscribers or their MiSP should stagger large manual catch-up runs rather than issuing them concurrently.
iPaaS.com Caveats
A customer identity must be resolvable. Every iPaaS.com Transaction must be tied to a customer. This family satisfies that through the order's email address. If that mapping is removed and no customer or company reference is supplied in its place, the destination rejects the record and the failure is reported under Dashboard / Integration Monitoring / Error Logs.
Line SKUs must resolve for product lines. A Transaction Line whose Type is Product must carry a SKU that matches an existing iPaaS.com product or variant. A line whose SKU cannot be matched cannot be written. This constraint does not apply to gift-card lines.
Gift-card lines and payments require a resolvable gift card. A Transaction Line whose Type is Gift Card must supply a gift card reference, and a gift-card payment must supply one too. The gift card must already exist in iPaaS.com for the lookup to resolve.
Payment methods must be configured. The translated payment method value must match a Payment Method configured in the subscriber's iPaaS.com environment, or the payment cannot be written.
The transaction type bucket is fixed. The Type field is set to Order so that Magento orders land in the order bucket downstream.
Integration-Specific Caveats
Only one tax record per order is transferred. This is a design decision in the order family, and it applies regardless of how many tax rates Magento applied to the order. Subscribers whose reporting depends on a per-jurisdiction tax breakdown should be aware that the breakdown does not reach iPaaS.com through this transfer.
There is no historical back-fill. Orders placed before the integration was installed reach iPaaS.com only through Manual Sync.
Gift-card line pricing is calculated differently from product-line pricing. The standard product line divides the line discount across the ordered quantity to derive a net unit price; the gift-card line subtracts the whole line discount from the line price directly. On a multiple-quantity gift-card line, review the resulting unit price before relying on it downstream.
Setup Requirements
Adobe Commerce/Magento 2 Configuration
Install and configure the third-party webhook extension in the Magento store, and subscribe it to the order events.
Confirm the shipping descriptions the store produces, so the three shipping-address variants route orders correctly.
Confirm the product type the store's gift card products use.
iPaaS.com Configuration
Configure the Adobe Commerce/Magento 2 connection settings on the subscription, including the Magento API URL and the credentials or integration token the integration will use.
Review the M2 Transaction Status To iPaaS Lookup Translation and add a row for every custom order status the store uses.
Review the M2 Transaction Payment Method To iPaaS Lookup Translation and confirm every iPaaS.com value on the right matches a Payment Method configured in the environment.
Create the iPaaS.com custom fields listed under Custom Field Support above.
Review the mapping filters on this collection and on the deposit ticket and gift card ticket parent collections together, confirming that the three families remain mutually exclusive.
Enable the inbound flow for Adobe Commerce/Magento 2 orders on the subscription's Inbound Data Flows page.
Full step-by-step setup instructions are in the Adobe Commerce/Magento 2 Installation Instructions article, and the webhook extension setup is covered in Configure Mageplaza Webhooks for iPaaS.com.
Integration Flow
The order is retrieved from Adobe Commerce/Magento 2 by its order record identifier, including its line items, payment information, and addresses.
The order's prerequisites are resolved. See Prerequisite Handling below.
The order is evaluated against the parent collection's mapping filter. Orders that do not pass the filter are skipped without error.
The parent collection's mappings populate the iPaaS.com Transaction header.
Each child collection is evaluated against the order's related records, and the qualifying lines, payments, tax record, and addresses are written onto the same Transaction. A child collection whose filter matches nothing simply contributes no records.
iPaaS.com decides between an Add and an Update for the Transaction, using the external-ID record first and TransactionNumber as the fallback.
Because the header and its children are written as one sequence, a subscriber troubleshooting a partially populated Transaction should check the child collections' filters before concluding the header transfer failed.
Prerequisite Handling
Before the order itself is written, the integration resolves the records the order depends on, so subscribers do not need to pre-sync them. The steps run in this order, with these conditions:
A brief pause before processing. Some Magento stores do not assign the customer to an order until shortly after the order is placed, so the integration waits before reading the order.
Deposit and gift card tickets are skipped entirely. If the order number ends in -D or -GC, no prerequisites are processed — they were already handled by the originating order that raised the ticket.
Customer. This step runs only when the order carries a Magento customer id, so guest orders skip it. If that customer is already linked to an iPaaS.com Customer, nothing further happens. Otherwise the integration retrieves the customer from Magento and transfers it into iPaaS.com. It then searches iPaaS.com for a customer matching the order's email address and, if one is found, creates the link between the two records. A failed customer prerequisite blocks the order transfer.
Gift cards sold. Each gift-card line on the order triggers a gift card transfer into iPaaS.com before the order completes. A line whose gift card record cannot be retrieved is skipped without error; a line whose gift card record exists but carries no gift card code fails the transfer.
Mappings
Add/Update Adobe Commerce/Magento 2 Order TO iPaaS.com (Parent)
iPaaS.com data type: Transaction
Mapping Filter
!IncrementId.EndsWith("-D") && !IncrementId.EndsWith("-GC") && !(Status == "suspected_fraud") && !(Status == "fraud")This collection processes ordinary Adobe Commerce/Magento 2 sales orders and excludes four categories of record. Orders whose order number ends in -D are excluded because that suffix identifies a deposit ticket, which is a separate record raised by the integration and handled by its own collection. Orders whose order number ends in -GC are excluded for the same reason, as gift card tickets. Orders whose Magento status is suspected_fraud or fraud are excluded so that orders Magento has flagged as suspect do not reach downstream fulfillment or financial systems. Orders that do not pass are skipped silently — no error is written to the Error Logs.
The -D and -GC suffixes are values the integration itself appends when it raises a deposit or gift card ticket from an originating order. They are not a store naming convention, and subscribers do not need to configure anything in Magento to produce them.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| SystemId | Required. Resolves the current subscription's system identifier so the order is attributed to this Magento subscription. Do not change or remove this mapping. |
Field | IncrementId | TransactionNumber | Required. The Magento order number, for example 000000123. Also the fallback duplicate-detection key. Do not remap it to a different source in the current release. |
Static |
| Type | Required. Fixed so Magento orders land in the order bucket downstream. |
Lookup Translation | Lookup Translation: M2 Transaction Status To iPaaS | Status | Required. Translates the Magento order status into an iPaaS.com transaction status. An unmatched status sends no value and raises no error. |
Field | CustomerEmail | EmailAddress | Recommended. Ties the Transaction to a customer. Removing it without supplying a customer or company reference instead causes the transfer to be rejected. |
Field | DiscountAmount | DiscountAmount | Recommended. Order-level discount total. |
Field | TaxAmount | TaxAmount | Recommended. Order-level tax total. |
Field | ShippingAmount | ShippingAmount | Recommended. Order-level shipping total. |
Field | Subtotal | Subtotal | Recommended. Sum of line items before tax, shipping, and discounts. |
Field | GrandTotal | Total | Recommended. Strongly advised so the Transaction reflects the amount the customer was actually charged. |
Field | TotalQtyOrdered | TotalQty | Recommended. Total quantity of items ordered. |
Dynamic Formula |
| TransactionCreatedDateTime | Optional. Records when the transfer ran, not when the order was placed in Magento. Replace with a mapping to the order's created date if the original order date is needed. |
The five recommended financial fields do not individually cause a transfer to fail if omitted, but omitting any of them leaves the Transaction's financial picture incomplete for downstream consumers.
Add/Update Adobe Commerce/Magento 2 Order Line TO iPaaS.com (Child)
iPaaS.com data type: Transaction Line
Mapping Filter
IsEmpty(ParentItemId) && ProductType != "giftvoucher"
This collection writes the order's ordinary product lines. A line passes only when it is a top-level line — IsEmpty(ParentItemId) excludes the duplicate child lines that configurable and bundle products generate in Magento, so a configurable product contributes one line rather than two — and only when its product type is not a gift voucher. Gift-voucher lines are transferred by the gift card line collection instead. Lines that do not pass are skipped without error.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Type | Required. Resolves to Product for every line this collection processes, because the filter already excludes gift vouchers. Allowed values are Product and Gift Card. |
Static |
| Status | Required. New order lines are staged as Pending so downstream processing advances them from a consistent starting point. |
Dynamic Formula |
| Sku | Required. Takes the order line SKU, replaces forward slashes with hyphens, and strips any unit suffix so the base catalog SKU is sent. Must match an existing product or variant. Also the line match key on re-sync. Do not remap it. |
Field | Description | Description | Recommended. Human-readable item name on the line. |
Field | QtyOrdered | Qty | Recommended. Also feeds the per-unit price calculation on this line, so mapping it is strongly advised. |
Dynamic Formula |
| UnitPrice | Recommended. Net price per unit after the per-unit share of the line discount. Because the calculation divides by ordered quantity, ensure the quantity source is present and greater than zero. |
Field | RowTotal | ExtendedPrice | Recommended. Extended line amount before line-level tax. |
Field | DiscountAmount | DiscountAmount | Recommended. The same line discount used to derive the net unit price. |
Field | TaxAmount | EstimatedTaxAmount | Recommended. Line-level tax amount. |
Field | SellUnit | SellingUnit (custom field) | Optional. The line's unit of measure, for downstream systems that use it. |
Field | OriginalPrice | OriginalUnitPrice | Optional. Pre-discount unit price, for comparison against the net unit price. |
Field | DiscountPercent | DiscountPercent | Optional. Line-level discount percentage. |
Field | TaxPercent | TaxPercent | Optional. Line-level tax rate, for downstream tax reporting. |
Field | Weight | Weight | Optional. Item weight, for downstream systems that compute shipping or handling from line weight. |
Add/Update Adobe Commerce/Magento 2 Order Line Gift Card TO iPaaS.com (Child)
iPaaS.com data type: Transaction Line
Mapping Filter
ProductType == "giftvoucher"
This collection writes the order's gift card lines. A line passes only when its Magento product type is a gift voucher; every other line is transferred by the standard Order Line collection. Lines that do not pass are skipped without error.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| LineInfo | Required for gift-card lines. Resolves the order line's gift card number to the matching iPaaS.com gift card and records its identifier under a GiftCardId entry. A line whose gift card number cannot be resolved fails to transfer. |
Dynamic Formula |
| Type | Required. Resolves to Gift Card for every line this collection processes. This is what makes the gift card reference required. |
Static |
| Status | Required. New order lines are staged as Pending. |
Dynamic Formula |
| Sku | Required. Labels the gift-card line. Because the line's type is Gift Card, the SKU is not required to match a catalog product. Also the line match key on re-sync. Do not remap it. |
Field | giftcardnumber | Giftcard Number (custom field) | Recommended. The human-readable gift card code. This is the value the gift card lookup above resolves. |
Field | Description | Description | Recommended. Human-readable gift-card item name on the line. |
Field | QtyOrdered | Qty | Recommended. Ordered quantity. |
Dynamic Formula |
| UnitPrice | Recommended. Net price after discount. Unlike the standard product line, this subtracts the whole line discount rather than dividing it across quantity — review the result on multiple-quantity gift-card lines. |
Field | RowTotal | ExtendedPrice | Recommended. Extended line amount before line-level tax. |
Field | DiscountAmount | DiscountAmount | Recommended. Line-level discount amount. |
Field | giftcardcustommessage | Giftcard Message (custom field) | Optional. The personalized message a shopper entered at checkout. |
Field | giftcardshippedtorecipient | Giftcard Shippedto Recipient (custom field) | Optional. The intended recipient of the gift card. |
Field | OriginalPrice | OriginalUnitPrice | Optional. Pre-discount unit price. |
Field | DiscountPercent | DiscountPercent | Optional. Line-level discount percentage. |
Field | TaxPercent | TaxPercent | Optional. Line-level tax rate. |
Field | Weight | Weight | Optional. Item weight. |
Gift cards must be synced into iPaaS.com before the orders that sell or redeem them. The gift card prerequisite described above handles this automatically for gift-card lines on the same order.
Add/Update Adobe Commerce/Magento 2 Order Payment TO iPaaS.com (Child)
iPaaS.com data type: Transaction Payment
Mapping Filter
Method!="giftcard"
This collection writes the order's payments for every tender other than gift card. A payment passes only when its Magento method code is not giftcard; gift-card tenders are handled by the sibling gift card payment collection. Payments that do not pass are skipped without error.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Lookup Translation | Lookup Translation: M2 Transaction Payment Method To iPaaS | Method | Required. The translated value must match a Payment Method configured in iPaaS.com, or the payment cannot be written. |
Dynamic Formula |
| Amount | Recommended. Uses the amount ordered while the order is pending and the amount paid afterwards, subtracting gift cards sold on the order so gift-card sales are not double-counted. Resolves to zero when the underlying amounts are empty. |
Dynamic Formula |
| Status | Recommended. Set to Complete when any amount has been paid, otherwise Authorized. |
Field | Method | Description | Optional. Preserves the raw Magento method code, for example authorizenet or checkmo, alongside the translated value. |
Add/Update Adobe Commerce/Magento 2 Order Payment Gift Card TO iPaaS.com (Child)
iPaaS.com data type: Transaction Payment
Mapping Filter
Method=="giftcard"
This collection writes the order's gift card tender payments. A payment passes only when its Magento method code is giftcard; every other tender is handled by the sibling Order Payment collection. Payments that do not pass are skipped without error. If a store labels its gift-card tender with a different code, this filter and the payment method translation both need a matching row added.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| MethodInfo | Required for gift-card payments. Resolves the payment's gift card number to the matching iPaaS.com gift card and records its identifier under a GiftCardId entry, tying the payment to the correct card. The gift card must already exist in iPaaS.com. |
Lookup Translation | Lookup Translation: M2 Transaction Payment Method To iPaaS | Method | Required. The giftcard row is the one that applies here. Confirm its iPaaS.com value matches a Payment Method configured in the environment. |
Static |
| Status | Recommended. Gift-card tenders are treated as already collected, so this collection always records the payment as Complete. |
Dynamic Formula |
| Amount | Recommended. Same calculation as the standard payment collection. |
Field | giftcardnumber | Giftcard Number (custom field) | Optional. Records which gift card was used. This is the value the gift card lookup above resolves, so keep the source populated. |
Field | authcode | AuthCode (custom field) | Optional. Preserves the gift-card authorization reference. |
Field | Method | Description | Optional. Preserves the raw Magento method code, typically giftcard. |
Where a lookup does not resolve, review the transfer under Dashboard / Integration Monitoring / Error Logs.
Add/Update Adobe Commerce/Magento 2 Order Tax TO iPaaS.com (Child)
iPaaS.com data type: Transaction Tax
This collection runs against every order the parent collection transfers, and writes a single consolidated tax record.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Authority | Recommended. The name of the taxing authority, taken from the title of the order's first applied tax. When the order carries no applied-tax detail the mapping falls back to Avalara. This fallback is a built-in default rather than an example to swap out; adjust it only if the store consistently reports a different default authority. |
Dynamic Formula |
| Amount | Recommended. The whole order's tax rather than a breakdown by jurisdiction or line. Maps a zero amount when the order carries no tax. |
Only a single tax record is transferred per order by design. Neither field is required by iPaaS.com, so the transfer will not fail if either is omitted.
Add/Update Adobe Commerce/Magento 2 Order Bill Address TO iPaaS.com (Child)
iPaaS.com data type: Transaction Address
Mapping Filter
AddressType == "billing"
This collection writes the order's billing address. Only the address flagged as billing on the Magento order passes; shipping addresses are handled by the three shipping-address variants.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryBilling | Required by design. Marks the transferred address as the order's primary billing address. This is a designed constant, not an environment-specific value — leave it as true. |
Dynamic Formula |
| Address1 | Recommended. Magento stores the street as a multi-line list; this takes the first line, or an empty string when the street is empty. |
Dynamic Formula |
| Address2 | Recommended. The second street line, typically a suite, unit, or apartment. Expected to be blank for single-line addresses. |
Dynamic Formula |
| Address3 | Recommended. The third street line. Expected to be blank for most addresses. |
Field | City | City | Recommended. Billing address city. |
Field | RegionCode | Region | Recommended. The short state or province code rather than the full region name. |
Field | CountryId | Country | Recommended. Normally the two-letter country code, for example US. |
Field | PostCode | PostalCode | Recommended. Billing address postal code. |
Field | FirstName | FirstName | Recommended. Billing contact's first name. |
Field | LastName | LastName | Recommended. Billing contact's last name. |
Field | Company | Company | Recommended. Billing address company name. Expected to be blank for individual consumers. |
Add/Update Adobe Commerce/Magento 2 Order Ship Address Flat Rate Fixed TO iPaaS.com (Child)
iPaaS.com data type: Transaction Address
Mapping Filter
AddressType == "shipping" && Parent.ShippingDescription=="Flat Rate - Fixed"
This collection writes the shipping address for orders shipped using the Flat Rate - Fixed shipping description. It is one of three shipping-address variants; each order's shipping address is routed to exactly one of them based on the order's shipping description, so the address lands with the correct static shipping method for that shipping tier.
Placeholder value — replace during implementation: the shipping description Flat Rate - Fixed in this filter is an example Adobe Commerce/Magento 2 value. Subscribers or their MiSP should replace it with the exact shipping-description text their own store produces for the shipping method this variant is meant to capture, so the right orders are routed here rather than falling through to the catch-all variant.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryShipping | Required by design. Marks the transferred address as the order's primary shipping address. |
Static |
| ShippingMethod | Recommended. Placeholder value — replace during implementation: an example carrier value. Replace it with the shipping method that corresponds to the store's Flat Rate - Fixed shipping tier. |
Dynamic Formula |
| Address1 | Recommended. First street line from Magento's multi-line street list. |
Dynamic Formula |
| Address2 | Recommended. Second street line. |
Dynamic Formula |
| Address3 | Recommended. Third street line. |
Field | City | City | Recommended. Shipping address city. |
Field | RegionCode | Region | Recommended. The short state or province code. |
Field | CountryId | Country | Recommended. Normally the two-letter country code. |
Field | PostCode | PostalCode | Recommended. Shipping address postal code. |
Field | FirstName | FirstName | Recommended. Shipping contact's first name. |
Field | LastName | LastName | Recommended. Shipping contact's last name. |
Field | Company | Company | Recommended. Shipping address company name. |
Add/Update Adobe Commerce/Magento 2 Order Ship Address Free Shipping TO iPaaS.com (Child)
iPaaS.com data type: Transaction Address
Mapping Filter
AddressType == "shipping" && Parent.ShippingDescription=="Free Shipping - Free"
This collection writes the shipping address for orders shipped using the Free Shipping - Free shipping description.
Placeholder value — replace during implementation: the shipping description Free Shipping - Free in this filter is an example Adobe Commerce/Magento 2 value. Replace it with the exact shipping-description text the store produces for its free-shipping tier.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryShipping | Required by design. Marks the transferred address as the order's primary shipping address. |
Static |
| ShippingMethod | Recommended. Placeholder value — replace during implementation: an example carrier value. Replace it with the shipping method that corresponds to the store's free-shipping tier. |
Dynamic Formula |
| Address1 | Recommended. First street line from Magento's multi-line street list. |
Dynamic Formula |
| Address2 | Recommended. Second street line. |
Dynamic Formula |
| Address3 | Recommended. Third street line. |
Field | City | City | Recommended. Shipping address city. |
Field | RegionCode | Region | Recommended. The short state or province code. |
Field | CountryId | Country | Recommended. Normally the two-letter country code. |
Field | PostCode | PostalCode | Recommended. Shipping address postal code. |
Field | FirstName | FirstName | Recommended. Shipping contact's first name. |
Field | LastName | LastName | Recommended. Shipping contact's last name. |
Field | Company | Company | Recommended. Shipping address company name. |
Add Adobe Commerce/Magento 2 Order Ship Address Unmapped TO iPaaS.com (Child)
iPaaS.com data type: Transaction Address
Mapping Filter
AddressType == "shipping" && !(Parent.ShippingDescription == "Flat Rate - Fixed") && !(Parent.ShippingDescription == "Free Shipping - Free")
This collection is the catch-all of the three shipping-address variants. It writes the shipping address for any order whose shipping description is neither Flat Rate - Fixed nor Free Shipping - Free, so no order's shipping address is left untransferred when its shipping method has no dedicated variant.
Subscribers or their MiSP who add more specific shipping tiers should add or adjust the sibling variants accordingly, so those orders are captured by a dedicated variant rather than falling through here and receiving this variant's static shipping method.
Mapping Type | Source Field (Adobe Commerce/Magento 2) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryShipping | Required by design. Marks the transferred address as the order's primary shipping address. |
Static |
| ShippingMethod | Recommended. Placeholder value — replace during implementation: an example carrier value. Replace it with the shipping method that should apply to orders whose shipping description is not handled by a more specific variant. |
Dynamic Formula |
| Address1 | Recommended. First street line from Magento's multi-line street list. |
Dynamic Formula |
| Address2 | Recommended. Second street line. |
Dynamic Formula |
| Address3 | Recommended. Third street line. |
Field | City | City | Recommended. Shipping address city. |
Field | RegionCode | Region | Recommended. The short state or province code. |
Field | CountryId | Country | Recommended. Normally the two-letter country code. |
Field | PostCode | PostalCode | Recommended. Shipping address postal code. |
Field | FirstName | FirstName | Recommended. Shipping contact's first name. |
Field | LastName | LastName | Recommended. Shipping contact's last name. |
Field | Company | Company | Recommended. Shipping address company name. |
Lookup Translations
M2 Transaction Status To iPaaS
Used by the parent collection's Status mapping.
Source Value | Destination Value | Notes |
pending | Pending | |
processing | Pending | |
complete | Complete | |
canceled | Cancelled | |
completing | Complete |
A Magento status with no row here is not translated, no value is sent for Status, and no error is raised. Because no error is raised, the condition is not visible in the Error Logs and is only detected by reviewing transferred Transactions or by auditing this translation against the store's configured statuses. Add a row for every custom status the store uses.
Allowed iPaaS.com Status values: Pending, Complete, Cancelled, Shipped, Backorder, Refunded, Partially Refunded, Partially Shipped, Awaiting Pickup, Awaiting Payment, On Hold, Processing, Returned, Draft.
M2 Transaction Payment Method To iPaaS
Used by the Method mapping on both payment collections.
Source Value | Destination Value | Notes |
authnetcim | CASH | |
authorizenet | CASH | |
braintree | CASH | |
checkmo | CASH | |
paypal_express | CASH | |
purchaseorder | CASH | |
giftcard | GC | Applies to the gift card payment collection only. |
Adobe Commerce/Magento 2 stores can enable additional or custom payment methods, and only the methods listed here are translated by default. Add a row for any payment method the store uses that is not already listed, and confirm that each iPaaS.com value on the right matches a Payment Method configured in the environment. A payment whose method code is missing from this translation will not be matched.
Error Handling
The full catalog of messages this integration produces, with causes and resolutions, is in the Adobe Commerce/Magento 2 Error Messages article. The messages most often seen on this transfer are:
Error message: No Giftcard assigned to line item marked as gift card. The message also names the order number and the line item. An order line is marked as a gift card in Magento but the gift card record carries no gift card code. Resolution: confirm the gift card was issued correctly in Magento for that line, then re-sync the order.
A customer prerequisite failure: the order's customer could not be created in or linked to iPaaS.com. The order transfer is blocked. Resolution: check the Customer mapping collection and confirm the customer's email address is present and unique, then re-sync the order.
A gift card reference that cannot be resolved: a gift-card line or gift-card payment names a gift card that does not exist in iPaaS.com. Resolution: sync the gift card into iPaaS.com, then re-sync the order.
A payment method that is not configured: the translated payment method does not correspond to a Payment Method configured in iPaaS.com. Resolution: add the missing row to the payment method translation, or configure the Payment Method in iPaaS.com.
A line SKU that does not resolve: a product line names a SKU with no matching iPaaS.com product or variant. Resolution: sync the product into iPaaS.com, then re-sync the order.
Errors are reported under Dashboard / Integration Monitoring / Error Logs.
Testing & Validation
Test Scenarios
Place an order in Adobe Commerce/Magento 2 and confirm a Transaction appears in iPaaS.com with the correct transaction number, status, email address, and financial totals.
Update the order in Magento and confirm the same Transaction is updated rather than a duplicate being created.
Manually sync an order using its Magento order record identifier and confirm it resolves. Confirm that entering the storefront order number instead does not resolve an order.
Place an order with a customer who does not yet exist in iPaaS.com and confirm the customer is transferred automatically as a prerequisite before the order lands.
Place an order containing a gift card product and confirm the gift card line transfers with its gift card reference, and that the gift card itself is transferred as a prerequisite.
Place an order paid partly or wholly by gift card and confirm the payment routes to the gift card payment collection while other tenders route to the standard payment collection.
Place orders using each of the store's shipping methods and confirm each shipping address routes to the expected variant, including the catch-all.
Place an order with a Magento status that has no row in the status translation and confirm the Transaction arrives with no status set, so the gap is visible before go-live.
Place an order whose number ends in -D or -GC and confirm it is skipped by this collection and handled by the deposit ticket or gift card ticket family instead.
Place an order and set its Magento status to a fraud status, then confirm it is excluded.
Validation Checklist
Every custom field listed under Custom Field Support exists in the iPaaS.com environment.
The status translation has a row for every order status the store uses.
The payment method translation has a row for every payment method the store uses, and every destination value matches a configured Payment Method.
The three shipping-address filters together cover every shipping method the store offers.
The shipping-method static values have been replaced with the store's real carrier values.
The parent filters on the order, deposit ticket, and gift card ticket families remain mutually exclusive.
Additional Notes
TransactionCreatedDateTime records the date and time the transfer ran rather than the date the order was placed in Magento. Subscribers who need the original Magento order date should replace that mapping with one that reads the order's created date.
Automatic transfers depend on webhook delivery from the third-party Magento extension. Delivery delays or an extension outage on the Magento side delay arrival in iPaaS.com, and Manual Sync is the recommended recovery path for orders placed during such a window.
This family does not transfer shipment tracking numbers or order comments, and does not create or match the customer record itself beyond the prerequisite described above.
Validate dynamic formulas and filter changes in a staging environment before enabling automatic transfers in production.