Contents
Summary
A BigCommerce order is transferred to iPaaS.com as a Transaction record. The order header — buyer, totals, tax, shipping, discount, dates, and status — is mapped onto the Transaction, and the order's related data is transferred through child collections: line items, billing and shipping addresses, tax, payments (one collection per payment type), order-level and per-line discounts, and customer and staff notes. New orders are created by the Add collection and later changes are applied by the Update collection; both run automatically when the BigCommerce order webhooks are enabled, or on demand from the iPaaS.com Manual Sync page.
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the BigCommerce order ID — the numeric identifier BigCommerce assigns to the order. Example: 1234.
External ID Format
After a successful transfer, iPaaS.com records the BigCommerce order ID as the external ID on a dedicated external-ID record. That external-ID record is the primary match that routes a later transfer of the same order to an update rather than creating a duplicate. The order ID is also written into the Transaction's transaction-number field, which gives the ID visibility on the Transaction and serves as a fallback match key when no external-ID record yet exists. Whether an incoming order is created or updated is determined by whether it is already linked by an external ID, not by which webhook event fired.
Remapping the transaction-number field to a different source is supported, but it disables that fallback auto-link for any Transactions that existed before the change.
Deleted Record Support
Outbound delete of an order is not supported. This family creates and updates Transactions only; no order-delete mapping collection ships in the default template, and archiving or removing an order in BigCommerce does not delete the linked Transaction in iPaaS.com. Refunds are handled separately — see Add BigCommerce Refund TO iPaaS.com — and are not a delete of the original order.
Custom Field Support
BigCommerce custom fields are supported on the Order and Order Product modules. To use a BigCommerce custom field in a mapping, first add it as a custom field in the BigCommerce subscription (Subscription Management → Subscriptions → BigCommerce → Custom Fields), then map it to the corresponding iPaaS.com field on the relevant collection. For Order Product custom fields — including product modifiers that arrive on line items — the custom-field module is BC Order Product, and the custom-field name must match the modifier's display name in BigCommerce. Products must be created with the modifiers for line-item modifier capture to work; see the BigCommerce Products article for how modifiers are configured.
Two iPaaS.com custom fields on the Transaction Line are used by this family out of the box:
Module | Custom Field |
Transaction Line | Original SKU |
Transaction Line | SellingUnit |
Mapping Collection Status
Status: Enabled. Both the Add and Update parent collections are enabled by default. Each has a filter that accepts completed, non-refund orders and rejects incomplete, pending, ticket, refund, and quote records (the Update filter additionally rejects Clover-payment orders). Review the filters against your business rules before enabling automatic transfers.
Trigger Events: Automatic transfers run when BigCommerce sends an order webhook to iPaaS.com. Enable the BigCommerce order events (order created, updated, and status-updated) under the Inbound Data Flows section of the subscription configuration. The external webhooks are
store/order/createdandstore/order/updated. Until these are enabled, no automatic transfers occur; Manual Sync is available at any time.
Duplicate or Conflicting Mappings
Several collections operate on the same BigCommerce order data. Review their filters and Add/Update settings before enabling, and decide which collection is the source of truth for each order state:
Add BigCommerce Order TO iPaaS.com: creates the Transaction for a new order.
Update BigCommerce Order TO iPaaS.com: applies later changes to an existing order.
Add/Update BigCommerce Deposit Ticket TO iPaaS.com: handles the -D deposit-ticket order clones.
Add/Update BigCommerce Gift Card Ticket TO iPaaS.com: handles the -GC gift-card-ticket order clones.
Add BigCommerce Refund TO iPaaS.com: handles refunds.
The Add and Update order collections move the same orders in the same direction (BigCommerce → iPaaS.com); the Add collection creates the Transaction and the Update collection refreshes it. Their filters are coordinated so a given order state is handled by exactly one of them.
Important: Enabling overlapping collections without coordinated filters can create duplicate or conflicting Transactions. Confirm each collection's filter selects a distinct set of orders.
Collision Handling
This Order family does not use iPaaS.com collision handling — records are routed to the Add or Update collection by external-ID presence (with a fallback match on the existing Transaction's number), not by a collision-recovery step. See ID Format for how the external-ID link and transaction-number fallback prevent duplicates.
Supported Child Collections
Each child below is linked to the parent order Transaction and transferred as part of the order. The Add parent (Add BigCommerce Order TO iPaaS.com) drives the full set on order creation; the Update parent (Update BigCommerce Order TO iPaaS.com) refreshes the payment and note children on order changes, while line items, addresses, tax, and discounts continue to flow through the line, address, tax, and discount collections.
BigCommerce Order Line TO iPaaS.com: the order's line items. Its own child, BigCommerce Order Line Per Item Discount TO iPaaS.com, captures per-line discounts.
BigCommerce Order Billing Address TO iPaaS.com and BigCommerce Order Shipping Address TO iPaaS.com — the order billing and shipping addresses.
BigCommerce Order Tax TO iPaaS.com: the order tax detail.
BigCommerce Order Payment TO iPaaS.com (Credit Card / Apple Pay, PayPal, Gift Card, Check, Test Payment Gateway) — the order's payments, one collection per payment type. The Update parent refreshes the Credit Card / Apple Pay, PayPal, Test Payment Gateway, and Check payments.
BigCommerce Order Customer Note TO iPaaS.com and BigCommerce Order Staff Note TO iPaaS.com — customer-entered and staff-entered order notes (both Add and Update variants).
BigCommerce Transaction Discount TO iPaaS.com and BigCommerce Automatic Header Promo Discount TO iPaaS.com — order-header-level coupon and automatic-promotion discounts.
System Caveats
BigCommerce Caveats
Order status drives eligibility. Orders in Incomplete, Pending, or Manual Verification Required status are not transferred until they reach an eligible status.
Ticket clones are separate. Orders whose ID ends in -D (deposit tickets) or -GC (gift-card tickets) are handled by their own collections, not by the order collections.
Clover payments excluded on update. Orders paid with Clover Payment are not processed by the Update collection.
Different payment types need different mappings. The data BigCommerce returns differs by payment type, so order payments are split across gateway-specific child collections. If an order uses a payment type not covered by the supplied payment collections, an additional payment sub-collection may be needed — review with your implementation team before relying on it in production.
Rate limiting. When BigCommerce rate-limits requests, the transfer is automatically rescheduled to resume after the limit window resets — no subscriber action is required.
iPaaS.com Caveats
Buyer link. The order's customer or company is transferred as a prerequisite; if that record cannot be created or linked in iPaaS.com, the order transfer does not complete.
Status translation. The order status is applied through a lookup translation. Review and customize the translation values so BigCommerce order statuses map to the iPaaS.com Transaction statuses your workflow expects.
Existing record required on update. The Update collection updates a Transaction that already exists in iPaaS.com. An order that has never transferred through the Add collection has no Transaction to update.
Full-replace updates. Order updates write the full record; fields left unmapped can be overwritten on each transfer. Map every field you want preserved, or use a destination-value approach for fields you do not source from BigCommerce. This behavior is accurate at the time this documentation was written.
Order notes are visible in iPaaS.com. Customer and staff notes captured from the order are readable by anyone with iPaaS.com access. Ensure notes are configured for the right level of access in downstream systems, and be aware of this visibility before mapping notes that contain sensitive content.
Integration-Specific Caveats
Buyer prerequisite. For standard orders the customer is resolved and transferred before the order; for B2B orders the company is used instead. Guest orders (no customer) are handled without a buyer prerequisite. A failed buyer prerequisite blocks the order transfer.
Payment-method prerequisite. When an order's payment gateway does not yet exist in iPaaS.com, it is created automatically during order preprocessing.
Gift-card prerequisite. When an order contains gift-certificate line items, the corresponding gift cards are created automatically during order preprocessing. This can be turned off with the Disable Gift Card Auto-Creation During Order To iPaaS Preprocessing subscription setting.
Setup Requirements
Before automatic transfers will run, configure the BigCommerce order webhooks (store/order/created, store/order/updated) and enable the corresponding order events under Inbound Data Flows in the subscription configuration. The store-level API account access token and store hash used for the connection are configured in the subscription settings. For the full webhook and credential walkthrough, see the BigCommerce Installation Instructions and the BigCommerce Connections and Settings article; this document does not duplicate those steps.
Integration Flow
When an order is transferred, the integration retrieves the full BigCommerce order and its related records, then dispatches the header and each child to iPaaS.com in order:
The order header is read and evaluated against the collection filter. Ineligible orders (incomplete, pending, ticket clones, refunds, quote-originated orders, and — on update — Clover-payment orders) are skipped.
Where needed, the buyer is resolved and transferred first: the customer for standard orders, or the company for B2B orders. Guest orders are handled without a buyer prerequisite. Any payment gateway or gift card the order requires is also created during preprocessing.
The header fields are mapped to the iPaaS.com Transaction. On Add, the transaction number is set from the BigCommerce order ID; on Update, the existing Transaction is matched by external ID (or the transaction-number fallback) and its transaction number is preserved.
Child records are transferred and linked to the Transaction — line items (and their per-line discounts), billing and shipping addresses, tax, payments, order-level discounts, and customer and staff notes.
On a successful first transfer, iPaaS.com saves the BigCommerce order ID as the external-ID link so later transfers of the same order route to the Update collection.
Mappings
Each mapping collection is documented below with its live Mapping Filter (where the collection has one), the iPaaS.com data type it targets, and its field-mapping table. In the tables, Dynamic Formula source values are shown inline in backticks; Static values are quoted. The Description column carries the required/recommended classification and behavior for each field.
Add / Update BigCommerce Order
iPaaS.com data type: Transaction
These two collections — Add BigCommerce Order TO iPaaS.com and Update BigCommerce Order TO iPaaS.com — map the same order header onto the iPaaS.com Transaction. They are presented together because their field mappings are nearly identical. The deltas are:
Transaction number. On Add, the transaction number is set from the BigCommerce order Id (a Field mapping). On Update, it is preserved from the existing iPaaS.com record (
DestinationValue.TransactionNumber) so the identifier stays stable across updates.Creation timestamp. The Add collection maps
TransactionCreatedDateTimefrom the order's DateCreated; the Update collection does not remap the creation date (it maps only the last-modified date).Filter. The Update filter additionally excludes orders paid with Clover Payment.
Mapping Filter (Add BigCommerce Order TO iPaaS.com)
!(Status == "Incomplete") && !(Status == "Pending") && !(Status == "Manual Verification Required") && !Id.EndsWith("-D") && !Id.EndsWith("-GC") && !IsRefund && string.IsNullOrEmpty(QUOTE_QuoteNumber)Filter Description. The Add collection processes an order only when all of these are true: the order Status is not Incomplete, Pending, or Manual Verification Required; the order Id does not end in -D or -GC (the deposit-ticket and gift-card-ticket clones, handled by their own collections); the order is not a refund (IsRefund is false); and the order has no quote number (QUOTE_QuoteNumber is empty — quote-originated orders are handled by the B2B Quote collections). Orders that fail any condition are skipped by this collection. No value in this filter is environment-specific, so no placeholder substitution is required.
Mapping Filter (Update BigCommerce Order TO iPaaS.com)
!(PaymentMethod == "Clover Payment") && !(Status == "Incomplete") && !(Status == "Pending") && !(Status == "Manual Verification Required") && !Id.EndsWith("-D") && !Id.EndsWith("-GC") && !IsRefund && string.IsNullOrEmpty(QUOTE_QuoteNumber)Filter Description. The Update filter applies the same rules as the Add filter and adds one more: the order's PaymentMethod must not be Clover Payment. Clover-payment orders are excluded from the update flow. All other branches match the Add filter above, and no value here is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| SystemId | Required. Sets the source system for the Transaction to the BigCommerce system this subscription is connected to — the Transaction must record which system the order came from. |
Field / Dynamic Formula | order Id (Add) / | TransactionNumber | Required. On Add, stores the BigCommerce order ID on the Transaction — it gives the ID visibility and acts as a fallback match key before an external-ID link exists. On Update, preserves the existing Transaction's number so the update targets the correct record. |
Static |
| Type | Required. Fixed value — sets the Transaction type to Order. Every record in this collection is an order. |
Dynamic Formula | Dynamic Formula (customer resolution) | CustomerId | Recommended. Links the Transaction to the buyer's iPaaS.com Customer for standard (non-B2B) orders. For B2B orders this is left unset and the company is used instead. The buyer is transferred as a prerequisite. One of |
Dynamic Formula | Dynamic Formula (company resolution) | CompanyId | Recommended for B2B orders. Links the Transaction to the buyer's iPaaS.com Company for B2B orders; left unset for standard orders (which use |
Dynamic Formula | Dynamic Formula (email resolution) | EmailAddress | Recommended. Sets the order email — the company email for B2B orders, otherwise the billing-address email, falling back to a guest email when the order has no customer. See the placeholder note below the table. |
Lookup Translation | Lookup Translation: BigCommerce Order Status → Transaction Status | Status | Recommended. Translates the BigCommerce order status into the iPaaS.com Transaction status. Review and customize the translation values so each BigCommerce status maps to the Transaction status your workflow expects. |
Dynamic Formula | Dynamic Formula (order discount + coupons, excluding shipping coupons) | DiscountAmount | Recommended. Calculates the order's total discount: the order discount amount plus every coupon discount, excluding shipping-type coupons (which are not counted as order discounts). |
Field | order TotalTax | TaxAmount | Recommended. Maps the order's total tax to the Transaction. |
Field | order ShippingCostExTax | ShippingAmount | Recommended. Maps the order's shipping cost (excluding tax) to the Transaction. |
Field | order SubtotalExTax | Subtotal | Recommended. Maps the order subtotal (excluding tax) to the Transaction. |
Field | order TotalIncTax | Total | Recommended. Maps the order grand total (including tax) to the Transaction. |
Field | order ItemsTotal | TotalQty | Recommended. Maps the total item quantity on the order to the Transaction. |
Field | order DateCreated | TransactionCreatedDateTime | Recommended (Add only). Preserves the original BigCommerce order creation date/time. The Update collection does not remap this field. |
Field | order DateModified | TransactionUpdatedDateTime | Recommended. Preserves the BigCommerce order last-modified date/time. |
Lookup Translation Tables
The Status field above is populated through the BC Transaction Status To iPaaS lookup translation. The configured Source → Destination value pairs are:
Source Value (BigCommerce) | Destination Value (iPaaS.com) | Notes |
Cancelled | Cancelled | |
Completed | Complete | |
Awaiting Payment | Pending | |
Awaiting Shipment | Pending | |
Partially Shipped | Pending | |
Awaiting Fulfillment | Pending | |
Awaiting Pickup | Pending | |
Shipped | Shipped | |
Refunded | Refunded | |
Partially Refunded | Partially Refunded |
Placeholder value — replace during implementation: the guest fallback email Guest@theredrookqa.com used by the EmailAddress formula is an example test-domain address. Replace it with the email your business wants to record on guest orders before enabling either collection.
The buyer-resolution, company-resolution, and email-resolution formulas are configurable dynamic formulas maintained on the mapping. Their behavior is summarized in the Description column above; the full expression bodies are recoverable from a live iPaaS.com subscription export.
BigCommerce Order Line TO iPaaS.com
iPaaS.com data type: Transaction Line
This collection has no mapping filter — every line on the order is transferred. It maps each order line's item, quantities, prices, discount, tax, and weight onto a Transaction Line. Because BigCommerce does not expose a unit price or an after-discount extended price directly, both are calculated from the line total, applied discounts, and quantity.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| SellingUnit | Optional. Derives the selling unit from the line's SKU by parsing the unit component out of the SKU string. When the SKU does not encode a unit, no selling unit is set. |
Dynamic Formula |
| Original SKU | Recommended. Records the original ordered SKU, parsed from the line's SKU string — it preserves the item identifier as it appeared on the order. |
Dynamic Formula | Dynamic Formula (gift-card number lookup) | LineInfo | Optional. For gift-certificate lines, retrieves the gift card number and records it in the line-info dictionary so the line can be linked to its gift card. Left unset for non-gift-certificate lines. |
Lookup Translation | Lookup Translation: BigCommerce Line Type → Transaction Line Type | Type | Required. Translates the BigCommerce order-line type into the iPaaS.com Transaction Line type. Review and customize the translation values so each line type maps as your workflow expects. |
Static |
| Status | Required. Fixed value — sets the line status to Pending for every line. Subscribers who track line-level fulfillment status separately should confirm this default in staging. |
Dynamic Formula |
| Sku | Recommended. Sets the line SKU, parsed from the line's SKU string — it identifies the item on the line. |
Field | order line Name | Description | Recommended. Maps the item name to the line description. |
Field | order line Quantity | Qty | Recommended. Maps the ordered quantity to the line. |
Field | order line QuantityShipped | QtyShipped | Recommended. Maps the shipped quantity to the line. |
Dynamic Formula |
| UnitPrice | Recommended. Calculates the per-item price after discounts (BigCommerce does not provide a unit price directly): the post-discount line total divided by the quantity, or 0 when the quantity is zero. |
Dynamic Formula |
| ExtendedPrice | Recommended. Calculates the after-discount extended price (BigCommerce does not expose it directly): the line total excluding tax minus the sum of applied discounts. |
Field | order line BasePrice | OriginalUnitPrice | Recommended. Maps the item's base (pre-discount) price to the line. |
Dynamic Formula |
| DiscountAmount | Recommended. Sums every discount applied to this line and records the total as the line discount amount. |
Field | order line TotalTax | EstimatedTaxAmount | Recommended. Maps the line's total tax to the estimated tax amount. |
Field | order line Weight | Weight | Recommended. Maps the item weight to the line. |
Lookup Translation Tables
The Type field above is populated through the BC Transaction Line Type To iPaaS lookup translation. The configured Source → Destination value pairs are:
Source Value (BigCommerce) | Destination Value (iPaaS.com) | Notes |
digital | Product | |
giftcertificate | Gift Card | |
physical | Product |
BigCommerce Order Line Per Item Discount TO iPaaS.com
iPaaS.com data type: Transaction Line Discount
This collection is a child of BigCommerce Order Line TO iPaaS.com — it captures discounts applied to individual line items.
Mapping Filter
Target == "product"
Filter Description. The collection processes an applied discount only when its Target is product — that is, discounts that target the line-item product. Discounts targeting anything else (for example, shipping or the order header) are skipped here and handled by the order-level discount collections.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | line discount Code | CouponCode | Recommended. Maps the coupon code to the line discount. Automatic (non-coupon) promotions carry no coupon code, so this may be empty for automatic-promotion discounts. |
Static |
| DiscountMethod | Required. Fixed value — sets the discount method to Line, identifying this as a per-line discount. |
Field | line discount Amount | DiscountAmount | Required. Maps the per-line discount amount to the line discount record. |
BigCommerce Order Billing Address TO iPaaS.com
iPaaS.com data type: Transaction Address
Mapping Filter
SourceTypeName == "ParentOnly"
Filter Description. The collection processes the address only when SourceTypeName is ParentOnly — that is, once per order, from the order header's billing address rather than from a per-line or per-shipment source. This ensures exactly one primary billing address is created for the order.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryBilling | Required. Fixed value — flags this address as the order's primary billing address. |
Dynamic Formula |
| Address1 | Recommended. Maps the first billing street line from the order's billing address. |
Dynamic Formula |
| Address2 | Optional. Maps the second billing street line; set only when a second line is present. |
Dynamic Formula |
| City | Recommended. Maps the billing city. |
Dynamic Formula |
| Region | Recommended. Maps the billing state or region. |
Dynamic Formula |
| Country | Recommended. Maps the billing country. |
Dynamic Formula |
| PostalCode | Recommended. Maps the billing postal code. |
Dynamic Formula |
| FirstName | Recommended. Maps the billing contact's first name. |
Dynamic Formula |
| LastName | Recommended. Maps the billing contact's last name. |
Dynamic Formula |
| Company | Recommended when the buyer is a company. Maps the billing company name. |
BigCommerce Order Shipping Address TO iPaaS.com
iPaaS.com data type: Transaction Address
Mapping Filter
SourceTypeName == "OrderShippingAddress"
Filter Description. The collection processes the address only when SourceTypeName is OrderShippingAddress — the order's shipping-address source. This keeps the shipping address distinct from the billing address (which is created by the billing-address collection) so each order gets one primary shipping address.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryShipping | Required. Fixed value — flags this address as the order's primary shipping address. |
Field | shipping address Street1 | Address1 | Recommended. Maps the first shipping street line. |
Field | shipping address Street2 | Address2 | Optional. Maps the second shipping street line; set only when a second line is present. |
Field | shipping address City | City | Recommended. Maps the shipping city. |
Field | shipping address State | Region | Recommended. Maps the shipping state or region. |
Field | shipping address Country | Country | Recommended. Maps the shipping country. |
Field | shipping address Zip | PostalCode | Recommended. Maps the shipping postal code. |
Lookup Translation | Lookup Translation: BigCommerce Shipping Method → iPaaS.com Shipping Method | ShippingMethod | Recommended. Translates the BigCommerce shipping method into the iPaaS.com shipping method. Review and customize the translation values. |
Field | shipping address ShippingMethod | ShippingMethodDescription | Recommended. Records the original BigCommerce shipping-method label as the description, preserving the raw value alongside the translated |
Field | shipping address FirstName | FirstName | Recommended. Maps the recipient's first name. |
Field | shipping address LastName | LastName | Recommended. Maps the recipient's last name. |
Field | shipping address Company | Company | Recommended when the delivery is to a company. Maps the recipient company name. |
Lookup Translation Tables
The ShippingMethod field above is populated through the BC Shipping Method To iPaaS lookup translation.
Placeholder value — replace during implementation: the pairs below are example UPS mappings from the development store. Replace them with your store's actual shipping-method names and the values your destination system expects before go-live.
Source Value (BigCommerce) | Destination Value (iPaaS.com) | Notes |
UPS (UPS Ground) | UPS GROUND | example |
None | UPS GROUND | example |
UPS (UPS 3 Day Select) | UPS GROUND | example |
UPS (UPS 2nd Day Air) | UPS BLUE | example |
UPS (UPS Next Day Air) | UPS RED | example |
Flat Rate | UPS GROUND | example |
BigCommerce Order Tax TO iPaaS.com
iPaaS.com data type: Transaction Tax
Mapping Filter
!(Class == "Shipping")
Filter Description. The collection processes a tax line only when its Class is not Shipping — shipping tax is excluded from the order's Transaction Tax records. All non-shipping tax lines pass through.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | order tax Name | Authority | Recommended. Maps the tax name to the taxing authority on the Transaction Tax record. |
Field | order tax LineAmount | Amount | Recommended. Maps the tax line amount to the Transaction Tax record. |
Field | order tax LineAmount | OriginalAmount | Recommended. Records the original tax line amount, sourced from the same value as |
Field | order tax Rate | TaxPercent | Recommended. Maps the tax rate to the Transaction Tax record. |
BigCommerce Order Payment - Credit Card / Apple Pay TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers credit card and Apple Pay payments (and captures for those). The same field mappings apply to its Update variant, Update BigCommerce Order Payment Credit Card / Apple Pay TO iPaaS.com, which refreshes these payments on an order update; both use the filter below.
Mapping Filter
!(Parent.PaymentMethod == "PayPal") && !(Parent.PaymentMethod == "Test Payment Gateway") && !(Parent.PaymentMethod == "Test Payment Provider") && ( Event == "capture" || (Event == "authorization" && CreditCardAuthIsCaptured(GatewayTransactionId, Parent.Transactions_Data) == false && Status == "ok") || (Event == "purchase" && Method == "credit_card" && Status == "ok") || (Method == "custom") )
Filter Description. The collection processes a payment only when the order's payment method is not PayPal, Test Payment Gateway, or Test Payment Provider (those are handled by their own collections), and the payment event qualifies as one of: a capture event; an authorization event that has not already been captured (CreditCardAuthIsCaptured(...) == false) and whose Status is ok; a purchase event whose Method is credit_card and Status is ok; or a custom method. Payments that do not meet one of these event conditions are skipped so an authorization already represented by a later capture is not double-counted. No value in this filter is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Method | Required. Resolves the payment method, examining the order's payment data and related transactions. Outputs one of CreditCard-Visa, CreditCard-Discover, CreditCard-MasterCard, CreditCard-AmericanExpress, CreditCard, ApplePay, PayPal, GiftCard, or Other. Credit card payments include the card brand when it can be determined, otherwise a generic CreditCard. Apple Pay is recognized only when BigCommerce labels the method exactly Apple Pay (and Apple Pay carries no card brand); anything unmatched becomes Other. |
Dynamic Formula |
| Description | Recommended. Passes the resolved payment method through as the payment description, preserving any detail beyond the standard method mapping. |
Dynamic Formula |
| Amount | Required. Records the payment amount, subtracting any gift-card sale amount on the order because gift-card sales are recorded on a separate transaction. |
Dynamic Formula |
| Status | Required. Sets the payment status from the event: Authorized for an authorization, Captured for a capture or purchase, Other otherwise. |
BigCommerce Order Payment - PayPal TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers PayPal payments. The same field mappings apply to its Update variant, Update BigCommerce Order Payment Paypal TO iPaaS.com; both use the filter below.
Mapping Filter
SourceTypeName == "ParentOnly" && Parent.PaymentMethod.StartsWith("PayPal")Filter Description. The collection processes the payment only when SourceTypeName is ParentOnly (once per order, from the order header) and the order's PaymentMethod starts with PayPal. Non-PayPal orders, and per-line payment sources, are skipped. No value here is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Method | Required. Runs the standard payment-method resolution, which for this collection always outputs PayPal because the filter restricts it to PayPal orders. |
Dynamic Formula |
| Description | Recommended. Passes the order's BigCommerce payment method name through as the payment description. |
Dynamic Formula |
| Amount | Required. Records the payment amount as the order total including tax, subtracting any gift-card sale amount (recorded separately). Uses 0 when no order total is available. |
Dynamic Formula |
| Status | Required. Sets the status to Captured when the order's PayPal payment status is captured, and Authorized otherwise. |
BigCommerce Order Payment - Gift Card TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers gift-card (gift-certificate) payments. It has no Update variant; gift-card payments are captured on the Add flow.
Mapping Filter
Method == "gift_certificate"
Filter Description. The collection processes a payment only when its Method is gift_certificate. All other payment methods are skipped and handled by the card, PayPal, check, or test-gateway collections.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula | Dynamic Formula (gift-card number → detail collection) | MethodInfo | Recommended. Stores the gift-card number used for the payment in the payment's detail collection. Because the number cannot be mapped directly to a detail field, the integration builds the detail value automatically. |
Dynamic Formula |
| Method | Required. Resolves the payment method; for a gift-certificate payment it outputs GiftCard (the full set of possible outputs is the same as the card collection above). |
Dynamic Formula |
| Description | Recommended. Passes the resolved method through as the payment description. |
Field | payment Amount | Amount | Required. Records the amount paid with the gift card. |
Field | payment Status | Status | Required. Records the payment status from BigCommerce. |
BigCommerce Order Payment - Check TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers offline check payments. The same field mappings apply to its Update variant, Update BigCommerce Order Payment Check TO iPaaS.com; both use the filter below.
Mapping Filter
Parent.PaymentMethod == "Check"&& Gateway == "cheque" && Method == "offline" && Status == "ok"
Filter Description. The collection processes a payment only when all four are true: the order's PaymentMethod is Check, the Gateway is cheque, the Method is offline, and the Status is ok. Any payment that is not an approved offline check is skipped. No value here is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula | Dynamic Formula (match existing Check payment method, else Check) | Method | Required (Add) / Recommended (Update). Looks up an existing iPaaS.com payment method matching Check and uses it if found; otherwise records the method as Check. Confirm the check payment method your workflow expects exists in iPaaS.com so the intended method is matched. |
Static |
| Description | Recommended. Sets the payment description to Website Check, a readable label identifying the payment as an online check. Subscribers may customize this label. |
Dynamic Formula |
| Amount | Required. Records the payment amount, subtracting any gift-card sale amount on the order (recorded on a separate ticket). |
Static |
| Status | Required. Fixed value — sets the payment status to Authorized. An offline check is recorded before funds clear, so it is captured as Authorized. |
BigCommerce Order Payment - Test Payment Gateway TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers test-gateway payments. The same field mappings apply to its Update variant, Update BigCommerce Order Payment Test Payment Gateway TO iPaaS.com; both use the filter below.
Mapping Filter
!(Parent.PaymentMethod == "PayPal") && SourceTypeName == "ParentOnly" && (Parent.PaymentMethod == "Test Payment Gateway" || Parent.PaymentMethod == "Test Payment Provider")
Filter Description. The collection processes the payment only when the order's PaymentMethod is not PayPal, SourceTypeName is ParentOnly (once per order, from the order header), and the order's PaymentMethod is either Test Payment Gateway or Test Payment Provider. All other payments are skipped. No value here is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| Method | Required. Fixed value — sets the payment method to Other for test-gateway payments (a generic default; the transfer succeeds with it). Subscribers who need a more specific method may replace it and validate in staging. |
Dynamic Formula |
| Description | Recommended. Passes the order's BigCommerce payment method name through as the payment description. |
Dynamic Formula |
| Amount | Required. Records the payment amount as the order total including tax, subtracting any gift-card sale amount (recorded separately). Uses 0 when no order total is available. |
Static |
| Status | Required. Fixed value — sets the payment status to Captured for test-gateway payments. |
BigCommerce Order Customer Note TO iPaaS.com
iPaaS.com data type: Transaction Note
This collection captures the shopper's checkout comment as a customer note. The same field mappings apply to its Update variant, Update BigCommerce Order Customer Note TO iPaaS.com; both use the filter below.
Mapping Filter
!(Parent.CustomerMessage == null) && !(Parent.CustomerMessage == "")
Filter Description. The collection processes the order only when the order's CustomerMessage is present (not null and not empty). Orders without a customer message produce no customer note.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| SequenceNumber | Recommended. Fixed value — sets the note's position within the order's notes to 2, ordering the customer note relative to other notes. |
Static |
| Type | Required. Fixed value — sets the note type to Customer Note. |
Dynamic Formula |
| Text | Recommended. Sets the note text from the order's customer message — the comment the shopper entered at checkout. This is the note's content. |
Dynamic Formula |
| NoteCreatedDateTime | Recommended. Sets the note's creation date/time from the order's creation date so the note carries a meaningful timestamp. |
Static |
| IsPublic | Recommended. Marks the note as public — customer notes are public by design in this collection, so downstream consumers can see the shopper's message. |
BigCommerce Order Staff Note TO iPaaS.com
iPaaS.com data type: Transaction Note
This collection captures the order's staff note as a private, internal note. The same field mappings apply to its Update variant, Update BigCommerce Order Staff Note TO iPaaS.com; both use the filter below.
Mapping Filter
!(Parent.StaffNotes == null) && !(Parent.StaffNotes == "")
Filter Description. The collection processes the order only when the order's StaffNotes value is present (not null and not empty). Orders without a staff note produce no staff note.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| SequenceNumber | Required. Fixed value — sets the note's sequence number to 1. BigCommerce holds a single staff note per order, so it is always recorded first. |
Static |
| Type | Required. Fixed value — sets the note type to Private. Staff notes are internal and are not shown to the buyer. |
Dynamic Formula |
| Text | Required. Sets the note text to the order's staff note — this is the note content. |
Dynamic Formula |
| NoteCreatedDateTime | Recommended. Sets the note's creation date/time to the order's creation date; BigCommerce does not record a separate timestamp for the staff note. |
Static |
| IsPublic | Required. Fixed value — marks the note as not public. Staff notes are internal and not exposed to the buyer. |
BigCommerce Transaction Discount TO iPaaS.com
iPaaS.com data type: Transaction Discount
This collection records order-header-level coupon discounts on the Transaction.
Mapping Filter
if (SourceTypeName != "ParentOnly" ) { return ContainsHeaderCouponDiscount(Parent.Products_Data, Convert.ToInt32(Type), Convert.ToString(Code));} else { return false;}Filter Description. For a per-item source (SourceTypeName is not ParentOnly), the collection uses ContainsHeaderCouponDiscount(...) to determine whether the coupon (identified by its Type and Code) was applied to the order header, and processes the record only when it was. When the source is the parent header itself (SourceTypeName == "ParentOnly"), the filter returns false — header coupon discounts are detected from the line items, not from the header source. Records that do not correspond to a header-applied coupon are skipped. No value in this filter is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | coupon Code | CouponCode | Recommended. Stores the BigCommerce coupon code on the Transaction Discount — it identifies which coupon produced the discount. |
Static |
| DiscountMethod | Required. Fixed value — sets the discount method to Header, marking this as an order-level discount rather than a per-line discount. This is a genuine classification value, not an environment-specific placeholder. |
Field | coupon Discount | DiscountAmount | Recommended. Maps the monetary value of the coupon discount to the Transaction Discount. |
BigCommerce Automatic Header Promo Discount TO iPaaS.com
iPaaS.com data type: Transaction Discount
This collection records order-header-level automatic promotion discounts — promotions that apply without a coupon code.
Mapping Filter
if (SourceTypeName == "ParentOnly" ) { return ContainsHeaderPromoDiscounts(Parent.Products_Data);} else { return false;}Filter Description. Automatic header promo discounts do not register as header coupons, so this parent-only mapping uses ContainsHeaderPromoDiscounts(...) to check the order's line items for an automatic promotion. When the source is the parent header (SourceTypeName == "ParentOnly") and a header promo discount is present, the record is processed; otherwise it returns false and is skipped. No value in this filter is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| DiscountMethod | Required. Fixed value — sets the discount method to Header, identifying this as an order-header-level discount. |
Dynamic Formula |
| DiscountAmount | Required. Sums the automatic (non-coupon) promotion discount applied to the order's line items and records the total as the discount amount. |
Error Handling
The BigCommerce integration reports errors through the standard iPaaS.com error path. For the catalog of order-related error messages and how to resolve them, see the BigCommerce Integration - Error Messages article rather than duplicating it here. Two behaviors specific to this family are worth noting:
Rate limiting. When BigCommerce rate-limits requests, the transfer is automatically rescheduled to resume after the limit window resets — no subscriber action is required.
Buyer prerequisite failure. If the order's customer or company cannot be created or linked in iPaaS.com, the order transfer does not complete. Confirm the buyer record can be resolved before re-running the transfer.
Testing & Validation
Test Scenarios
Create a new order. Place a completed, non-refund order in BigCommerce (with at least one line item, a billing and shipping address, tax, and a payment) and verify it transfers to iPaaS.com as a Transaction with the correct transaction number, buyer, totals, lines, addresses, tax, payment, and any discounts.
Update an existing order. Change an order that has already transferred (for example, add a staff note or change status) and verify the linked Transaction is updated — not duplicated — and that its transaction number is preserved.
Filter rejection. Confirm that an Incomplete, Pending, or Manual Verification Required order, a -D or -GC ticket clone, a refund, and a quote-originated order are each skipped by the order collections. On update, also confirm a Clover Payment order is skipped.
ID format. From the Manual Sync page, transfer an order by its numeric BigCommerce order ID and confirm the transfer succeeds and the external-ID link is saved.
Payment-type coverage. Place orders paid by credit card, Apple Pay, PayPal, gift card, check, and the test gateway, and verify each is captured by the matching payment collection with the expected method, amount, and status.
Discounts. Place an order with a header coupon, an automatic promotion, and a per-line discount, and verify each is recorded on the correct discount collection.
Guest order. Place a guest order (no customer) and confirm the email falls back correctly — after replacing the placeholder guest email with your own value.
Validation Checklist
The Transaction's transaction number equals the BigCommerce order ID (Add), or is preserved from the existing record (Update).
The buyer is linked as a Customer (standard order) or Company (B2B order).
Order totals — Total, Subtotal, TaxAmount, ShippingAmount, DiscountAmount, TotalQty — match the BigCommerce order.
Line items carry the correct SKU, quantity, unit price (after discount), extended price, tax, and weight.
Billing and shipping addresses are flagged as primary and carry the correct contact and address fields.
The order status maps to the intended Transaction status through the status lookup translation.
The placeholder guest email has been replaced before enabling the collections.
Customer and staff notes appear with the correct public/private visibility, and their visibility is acceptable for downstream systems.
Additional Notes
B2B quotes are handled by the B2B Quote collections, not the order collections.
Deposit tickets and gift-card tickets (the -D and -GC order clones) are handled by their own collections.
Refunds are handled by the Refund collections. iPaaS.com pulls in the shipping and billing addresses used for a refund; if you need to ensure those do not change, review with your implementation team.
Full details of the read and write endpoints this integration uses are in the BigCommerce API Endpoints article.
For the full list of integration-wide constraints, see the BigCommerce Integration Known Limitations article.