Contents
Summary
When a BigCommerce order sells one or more gift certificates, the integration clones the order into a separate gift-card ticket — an order ID ending in -GC — and transfers it to iPaaS.com as its own Transaction. Splitting the gift-card sale onto its own ticket keeps the value of the gift card consistent across channels when the ticket is sent downstream to an ERP or accounting system. The ticket header — buyer, totals, quantity, status, and dates — is mapped onto the Transaction, and the ticket's related data is transferred through child collections: gift-card lines, billing address, tax, and payments (one collection per payment type). New and changed tickets are both handled by the single Add/Update parent collection, which runs 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 for the gift-card order — the numeric identifier BigCommerce assigns to the order. Example: 1234. The ticket is created internally from that order with a -GC suffix appended to the ID.
External ID Format
After a successful transfer, iPaaS.com records the ticket ID (the order ID with the -GC suffix) 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 ticket to an update rather than creating a duplicate. The ticket 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.
Deleted Record Support
Outbound delete of a gift-card ticket is not supported. This family creates and updates gift-card ticket Transactions only; no ticket-delete mapping collection ships in the default template, and archiving or removing the originating order in BigCommerce does not delete the linked ticket Transaction in iPaaS.com.
Custom Field Support
BigCommerce custom fields are not used by the gift-card ticket family. One iPaaS.com custom field on the Transaction Line is used by this family out of the box to carry the selling unit parsed from the line SKU:
Module | Custom Field |
Transaction Line | SellingUnit |
Mapping Collection Status
Status: Enabled. The Add/Update parent collection is enabled by default. Its filter accepts only gift-card ticket clones — orders that sell one or more gift certificates and whose ID ends in -GC. Review the filter 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 -GC ticket is derived from the order during preprocessing; there is no separate webhook for the ticket itself. Until the order events 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/Update BigCommerce Gift Card Ticket TO iPaaS.com: handles the -GC gift-card-ticket clones (this family).
Add BigCommerce Order TO iPaaS.com and Update BigCommerce Order TO iPaaS.com: handle the main order (order IDs without a -D or -GC suffix).
Add/Update BigCommerce Deposit Ticket TO iPaaS.com: handles the -D deposit-ticket clones.
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 gift-card ticket family does not use iPaaS.com collision handling — records are routed to create or update 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 gift-card ticket Transaction and transferred as part of the ticket. The single Add/Update parent (Add/Update BigCommerce Gift Card Ticket TO iPaaS.com) drives the full set on both creation and change:
Add/Update BigCommerce Gift Card Ticket Gift Card Line TO iPaaS.com: the ticket's gift-card line items.
Add/Update BigCommerce Gift Card Ticket Billing Address TO iPaaS.com: the ticket billing address.
Add/Update BigCommerce Gift Card Ticket Tax TO iPaaS.com: the ticket tax detail (zeroed, as gift cards are not taxable in BigCommerce).
Gift Card Ticket payment collections (Credit Card / Apple Pay, PayPal, Check, Test Payment Gateway) — the ticket's payments, one collection per payment type.
System Caveats
BigCommerce Caveats
Gift-card tickets are derived, not native. BigCommerce does not have a separate gift-card ticket entity; the ticket is a clone the integration derives from an order that sells gift certificates.
Special handling keeps gift-card value consistent. Gift-card tickets receive special handling so the value of the gift card stays consistent across channels. Splitting the gift-card sale onto its own ticket is what preserves that consistency when the ticket is sent downstream to an ERP or accounting system.
Gift cards are not taxable. BigCommerce does not tax gift-card sales, so the ticket's tax amounts are fixed at zero by design.
Different payment types need different mappings. The data BigCommerce returns differs by payment type, so ticket payments are split across gateway-specific child collections. If a ticket 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 ticket transfer does not complete.
Status translation. The ticket 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.
Full-replace updates. Ticket 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.
Review B2B and B2C mappings. Several of the ticket's mappings — particularly the buyer, email, and company resolutions — should be reviewed to confirm they are configured correctly for your B2B and/or B2C order flows before relying on them in production.
Integration-Specific Caveats
Buyer prerequisite. For standard orders the customer is resolved and transferred before the ticket; for B2B orders the company is used instead. A failed buyer prerequisite blocks the ticket transfer.
Originating-order prerequisite. The ticket links back to its originating order Transaction; that order is transferred by its own order collection. The link is resolved by dropping the -GC suffix from the ticket ID.
Payment-method prerequisite. When a ticket's payment gateway does not yet exist in iPaaS.com, it is created automatically during order preprocessing.
Gift-card prerequisite. The gift cards sold on the ticket 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 gift-card ticket is derived from the order during preprocessing, so it uses the same order webhooks — there is no separate gift-card-ticket webhook. 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 a gift-card order is transferred, the integration reads the full BigCommerce order behind the ticket, then dispatches the ticket header and each child to iPaaS.com in order:
The order is read and evaluated against the ticket filter. The ticket is processed only when the order sells one or more gift certificates and its ID ends in -GC; all other orders are skipped by this collection.
The buyer is resolved and transferred first: the customer for standard orders, or the company for B2B orders. Any payment gateway or gift card the ticket requires is also created during preprocessing.
The ticket links back to its originating order Transaction, resolved by dropping the -GC suffix from the ticket ID.
The header fields are mapped to the iPaaS.com Transaction, including the transaction number (the ticket ID), the gift-card sale totals and count, the translated status, and the order timestamps.
Child records are transferred and linked to the ticket Transaction — gift-card lines, billing address, tax (zeroed), and the payment records for the order's payment type.
On a successful first transfer, iPaaS.com saves the ticket ID as the external-ID link so later transfers of the same ticket route to an update.
Mappings
Each mapping collection is documented below with its live Mapping Filter, 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 Gift Card Ticket
iPaaS.com data type: Transaction
This single collection — Add/Update BigCommerce Gift Card Ticket TO iPaaS.com — maps the gift-card ticket header onto the iPaaS.com Transaction. It handles both new and changed tickets (the Add/Update action).
Mapping Filter
RequiresGiftCardTicket(Products_Data) && Id.EndsWith("-GC")Filter Description. The collection processes a record only when both conditions are true: the order requires a gift-card ticket — RequiresGiftCardTicket(Products_Data) is true, meaning the order sells one or more gift certificates — and the order Id ends in -GC, the suffix that identifies the gift-card ticket clone. Orders that do not sell gift certificates, and the original order records themselves, are skipped by this collection. No value in this filter is environment-specific, so no placeholder substitution is required.
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 ticket came from. |
Dynamic Formula |
| TransactionNumber | Required. Stores the ticket ID on the Transaction — the originating order ID with a -GC suffix appended. It gives the ID visibility and acts as a fallback match key: when no external-ID link yet exists for a ticket, iPaaS.com matches on this value to avoid creating a duplicate. |
Dynamic Formula |
| ParentId | Recommended. Links the gift-card ticket back to its originating order Transaction by dropping the -GC suffix from the ticket ID and resolving the linked iPaaS.com order record. |
Static |
| Type | Required. Fixed value — sets the Transaction type to Ticket. Every record created here is a gift-card ticket. |
Dynamic Formula | Dynamic Formula (customer resolution) | CustomerId | Recommended. Links the ticket 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. One of |
Dynamic Formula | Dynamic Formula (company resolution) | CompanyId | Recommended for B2B orders. Links the ticket 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 ticket 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 |
| Subtotal | Recommended. Totals the gift-card lines on the ticket. Because gift-card tickets contain only gift-card lines, that total is the ticket subtotal. |
Dynamic Formula |
| Total | Recommended. Totals the gift-card lines on the ticket. Because gift cards generally carry no tax or shipping, the subtotal is also the ticket total. |
Dynamic Formula |
| TotalQty | Recommended. Records the number of gift cards sold on this ticket. |
Field | order DateCreated | TransactionCreatedDateTime | Recommended. Preserves the original BigCommerce order creation date/time on the ticket. |
Field | order DateModified | TransactionUpdatedDateTime | Recommended. Preserves the BigCommerce order last-modified date/time on the ticket. |
Lookup Translation Tables
The Status mapping above uses the BC Transaction Status To iPaaS lookup translation, which maps each BigCommerce order status to an iPaaS.com Transaction status. These are subscriber-configurable defaults — review and customize them so each BigCommerce status maps to the Transaction status your workflow expects.
Source Value (BigCommerce) | Destination Value (iPaaS.com) |
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 this 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 Gift Card Ticket Gift Card Line
iPaaS.com data type: Transaction Line
This child collection captures the gift-card line items on the ticket and maps each 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 Filter
Type == "giftcertificate"
Filter Description. The collection processes a line only when its Type is giftcertificate — that is, a gift-card line. All other line types on the order are handled by their own line collections. No value in this filter is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| SellingUnit | Recommended. 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 | Dynamic Formula (gift-card number → line-info) | LineInfo | Recommended. Determines the gift-card number for this line and stores it in the line's line-info detail so the line can be tied to its gift card. |
Static |
| Type | Required. Fixed value — sets the line type to Gift Card. |
Static |
| Status | Required. Fixed value — sets the line status to Complete. |
Dynamic Formula |
| Sku | Recommended. Sets the line SKU, parsed from the line's SKU string — it identifies the gift-card 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 where it applies. Maps the line's total tax to the estimated tax amount; gift-card lines are generally not taxable. |
Field | order line Weight | Weight | Recommended where it applies. Maps the item weight to the line. |
BigCommerce Gift Card Ticket Billing Address
iPaaS.com data type: Transaction Address
This child collection captures the ticket billing address and maps it onto a Transaction Address, flagged as the primary billing address.
Mapping Filter
SourceTypeName == "ParentOnly"
Filter Description. The collection processes the address only when SourceTypeName is ParentOnly — the single billing address carried on the ticket header, rather than a per-line or per-shipment source. This ensures exactly one primary billing address is created for the ticket. No value in this filter is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryBilling | Required. Fixed value — flags this address as the ticket's primary billing address. |
Dynamic Formula |
| Address1 | Recommended. Maps the first billing street line from the parent order's billing address. |
Dynamic Formula |
| Address2 | Recommended where it applies. 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 where it applies. Maps the billing company name. |
BigCommerce Gift Card Ticket Tax
iPaaS.com data type: Transaction Tax
This child collection records the ticket's tax detail. Because gift cards are not taxable in BigCommerce, the amounts are fixed at zero; the collection maps the tax authority name and sets a zero amount, original amount, and tax percent.
Mapping Filter
!(Class == "Shipping")
Filter Description. The collection processes a tax line only when its Class is not Shipping — shipping-class tax is excluded from the ticket's Transaction Tax records. All non-shipping tax lines pass through. No value in this filter is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | order tax Name | Authority | Recommended. Maps the tax authority name to the Transaction Tax record. |
Static |
| Amount | Recommended. Fixed value — sets the tax amount to 0. Gift-card tickets are not taxable in BigCommerce, so they carry no tax by design. |
Static |
| OriginalAmount | Recommended. Fixed value — sets the original tax amount to 0, for the same reason as |
Static |
| TaxPercent | Recommended. Fixed value — sets the tax percent to 0, for the same reason as |
BigCommerce Gift Card Ticket Payment - Credit Card / Apple Pay
iPaaS.com data type: Transaction Payment
This child collection covers credit card and Apple Pay payments (and captures for those) on the ticket. It is an Add-only collection — it creates the payment record and does not update an existing payment.
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) || (Event == "purchase" && Method == "credit_card") && Status == "ok" )
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); or a purchase event whose Method is credit_card with Status ok. 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 as the total of the gift cards sold on the ticket. |
Dynamic Formula |
| Status | Required. Sets the payment status to Captured for a capture or purchase event, and Authorized otherwise. |
BigCommerce Gift Card Ticket Payment - PayPal
iPaaS.com data type: Transaction Payment
This child collection covers PayPal payments on the ticket (the Add/Update action).
Mapping Filter
SourceTypeName == "ParentOnly" && Parent.PaymentMethod.StartsWith("PayPal")Filter Description. The collection processes the payment only when SourceTypeName is ParentOnly (once per ticket, from the order header) and the order's PaymentMethod starts with PayPal. Non-PayPal orders, and per-line payment sources, are skipped. No value in this filter 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 total of the gift cards sold on the ticket. |
Dynamic Formula |
| Status | Required. Sets the status to Captured when the order's PayPal payment status is captured, and Authorized otherwise. |
BigCommerce Gift Card Ticket Payment - Check
iPaaS.com data type: Transaction Payment
This child collection covers offline check payments on the ticket. It is an Add-only collection — it creates the payment record and does not update an existing payment.
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 in this filter 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. 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 as the total of the gift cards sold on the 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 Gift Card Ticket Payment - Test Payment Gateway
iPaaS.com data type: Transaction Payment
This child collection covers BigCommerce's test payment gateway and test payment provider, typically used in non-production stores. It is an Add-only collection — it creates the payment record and does not update an existing payment. Review whether it should be enabled for a production subscription.
Mapping Filter
Parent.PaymentMethod == "Test Payment Gateway" || Parent.PaymentMethod == "Test Payment Provider"
Filter Description. The collection processes the payment only when the order's PaymentMethod is either Test Payment Gateway or Test Payment Provider. Payments by any other method are handled by their own payment collections. No value in this filter 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; these payments do not map to a specific card brand or wallet. |
Dynamic Formula |
| Description | Recommended. Passes the order's BigCommerce payment method name through as the payment description. |
Dynamic Formula |
| Amount | Required. Calculates the payment amount net of gift-card sales: the product sold total plus tax and shipping, minus redeemed gift-card amounts and the order discount. Gift-card sales are recorded on the separate gift-card ticket, so their amount is deducted here. |
Static |
| Status | Required. Fixed value — sets the payment status to Captured for test-gateway payments. |
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 ticket's customer or company cannot be created or linked in iPaaS.com, the ticket transfer does not complete. Confirm the buyer record can be resolved before re-running the transfer.
Testing & Validation
Test Scenarios
Create a new gift-card ticket. Place a completed BigCommerce order that sells one or more gift certificates, and verify the -GC ticket transfers to iPaaS.com as a Transaction of type Ticket with the correct transaction number, buyer, gift-card totals and count, gift-card lines, billing address, zeroed tax, and payment.
Update an existing ticket. Change a gift-card order that has already transferred (for example, change status) and verify the linked ticket Transaction is updated — not duplicated — and its transaction number is preserved.
Filter selection. Confirm that an order with no gift-certificate lines is not turned into a gift-card ticket, and that only orders whose ID ends in -GC are processed by this collection.
ID format. From the Manual Sync page, transfer a gift-card order by its numeric BigCommerce order ID and confirm the transfer succeeds and the external-ID link (the ID with the -GC suffix) is saved.
Payment-type coverage. Place gift-card orders paid by credit card, Apple Pay, PayPal, check, and the test gateway, and verify each is captured by the matching payment collection with the expected method, amount, and status.
Parent link. Verify the ticket's
ParentIdresolves to the originating order Transaction, and that the originating order transferred through its own order collection.Guest order. Place a guest gift-card order (no customer) and confirm the email falls back correctly — after replacing the placeholder guest email with your own value.
Validation Checklist
The ticket Transaction's type is Ticket and its transaction number equals the order ID with the -GC suffix.
The ticket's
ParentIdlinks to the originating order Transaction.The buyer is linked as a Customer (standard order) or Company (B2B order).
The gift-card totals — Subtotal, Total, and TotalQty — match the gift cards sold on the order.
Gift-card lines carry the correct type (Gift Card), status (Complete), SKU, quantity, unit price (after discount), and extended price.
The billing address is flagged as primary and carries the correct contact and address fields.
The tax record's Amount, OriginalAmount, and TaxPercent are all zero.
The payment is captured by the correct payment collection with the expected method, amount, and status.
The order status maps to the intended Transaction status through the status lookup translation.
The placeholder guest email has been replaced before enabling the collection.
Additional Notes
Not needed without gift-card sales. If your business does not sell or transact in gift cards in BigCommerce, this collection and its children have nothing to process and can be removed. Tickets can likewise be removed if your destination system does not use tickets.
The non-gift-card portion of the order is handled by the main Order collections, not this family.
Deposit tickets (the -D order clones) are handled by their own collections.
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.