Summary
iPaaS.com gift cards write out to BigCommerce. Outbound transfers create new BigCommerce gift cards and write later balance, status, and expiry changes to existing cards from iPaaS.com Gift Cards. Transfers run automatically from subscribed iPaaS.com triggers or on demand from the iPaaS.com Manual Sync page. These flows let iPaaS.com merchants accept gift cards in an omnichannel fashion, so a balance issued in iPaaS.com becomes spendable in BigCommerce.
Capturing BigCommerce gift cards and their issuance activity into iPaaS.com is covered by the companion BigCommerce to iPaaS.com Gift Card Mapping Documentation.
Contents
Data Types and Direction
This article documents the following mapping collections and the iPaaS.com data type each one operates on. Every collection here transfers iPaaS.com to BigCommerce.
Collection | iPaaS.com data type | Direction |
Add BigCommerce Gift Card FROM iPaaS.com | Gift Card | iPaaS.com to BigCommerce |
Update BigCommerce Gift Card Updates FROM iPaaS.com | Gift Card | iPaaS.com to BigCommerce |
Gift cards are matched on their code (ID) only — there is no additional pre-processing to reconcile them.
ID Format
Manual Sync ID Format
Gift Card: enter the iPaaS.com Gift Card ID — the numeric identifier iPaaS.com assigns to the gift-card record. Example: 4501.
External ID Format
After a successful transfer, iPaaS.com records the BigCommerce gift-card identifier as the external ID on the iPaaS.com Gift Card. The Update BigCommerce Gift Card Updates FROM iPaaS.com collection resolves this external-ID link to find the correct BigCommerce card; if the link is missing, the card must first be created by the Add collection. The external-ID record is the primary match that routes later transfers of the same card to an update rather than creating a duplicate.
Deleted Record Support
Outbound gift-card delete is supported. iPaaS.com can call BigCommerce to remove a linked gift card when the card is deleted in iPaaS.com. Confirm the delete behavior against your business rules in a staging environment before relying on it in production.
Custom Field Support
BigCommerce does not expose custom fields for the gift-card data type, and no iPaaS.com custom fields are created by default for gift cards. No custom-field configuration is required to run these collections.
Mapping Collection Status
All collections in this article ship Enabled. Trigger events:
Gift Card: iPaaS.com gift card created and gift card updated triggers.
Neither collection has a mapping filter, so every gift card selected by the subscribed outbound trigger or by Manual Sync is processed. Automatic transfers do not run until the corresponding triggers are subscribed — see Setup Requirements.
Duplicate or Conflicting Mappings
The two outbound collections operate on the same underlying BigCommerce gift card. Review their Add/Update settings before enabling them so each card is handled once.
Add vs. Update. Add BigCommerce Gift Card FROM iPaaS.com creates a new card in BigCommerce; Update BigCommerce Gift Card Updates FROM iPaaS.com writes later balance, status, and expiry changes to an existing card. The external-ID link decides which one applies: a card with no link is created by the Add collection, and a card with an existing link is routed to the Update collection. Configure both so a new card is created once and subsequent changes are routed to the update collection.
Gift cards do not use email-based collision handling; the outbound collections match on the gift-card code through the external-ID link.
Supported Child Collections
The outbound Gift Card collections (Add and Update) are leaf collections with no children of their own.
System Caveats
BigCommerce Caveats
Matched by code. Gift cards are matched on their code (ID) only, with no additional pre-processing to reconcile them.
Purchasing name and email required. BigCommerce requires a purchasing customer name and email on every gift card. When the iPaaS.com source has neither, the mappings supply a default so the write does not fail. Review the defaults against your business needs.
Card must already exist (update). The Update collection updates an existing BigCommerce gift card; it does not create one. A card that has not been created by the Add collection cannot be updated.
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
Status translation. The Status mapping uses a lookup translation. Review and customize the translation values so each iPaaS.com gift-card status maps to the BigCommerce status you expect.
Optional links resolve when present. The originating customer and originating order links are populated only when those records are already linked in iPaaS.com; otherwise they are left unset and the gift card still transfers.
Recipient tracking for purchase-for-another. These collections support the scenario where one person purchases a gift card for someone else. The purchasing customer is tracked through the purchasing name and email and the linked originating customer; the recipient is tracked through the recipient name and email. Both sides of the gift are carried through the transfer.
External-ID link required (update). The Update collection resolves the BigCommerce card from the external-ID link saved on the initial Add transfer; if that link is missing, the update cannot locate the card.
Integration-Specific Caveats
Full-replace writes. Each outbound transfer writes the full gift-card record to BigCommerce; fields left unmapped can be overwritten on each transfer. Map every field you want preserved, or use a DestinationValue approach for fields you do not source from iPaaS.com.
Setup Requirements
Automatic transfers do not run until the corresponding triggers are subscribed. Enable the iPaaS.com gift-card triggers (gift card created and gift card updated) under Outbound Data Flows in the subscription configuration.
Integration Flow
Gift card:
An iPaaS.com gift card created or updated trigger fires, or a gift card is manually synced by its iPaaS.com Gift Card ID.
The integration resolves the originating customer and originating order links from their iPaaS.com external-ID records so the BigCommerce card carries those associations when they exist.
A card with no external-ID link is created in BigCommerce by the Add collection; a card that is already linked is updated by the Update collection, which resolves the BigCommerce card from the external-ID link.
Mappings
Each collection below lists its Mapping Filter (when the collection has one), the iPaaS.com data type it operates on, and its field mapping table. Source and destination field names are shown as they appear in each system.
Add BigCommerce Gift Card FROM iPaaS.com
iPaaS.com data type: Gift Card
Writes a new iPaaS.com Gift Card to BigCommerce in a single create operation, mapping the code, starting amount, balance, status, expiry date, the purchasing customer, the recipient, and links to the originating order and customer. This collection handles new cards; later changes are handled by Update BigCommerce Gift Card Updates FROM iPaaS.com. This collection has no mapping filter, so every gift card selected by the subscribed outbound trigger is processed.
Mapping Type | Source Field (iPaaS.com Gift Card) | Destination Field (BigCommerce) | Description |
Field |
| Code | Required. Sets the BigCommerce gift-card code from the iPaaS.com gift-card number; the code identifies the card in BigCommerce. |
Dynamic Formula |
| Amount | Required by BigCommerce. Sets the card's starting balance. Uses the iPaaS.com original amount when one exists, and otherwise falls back to the current balance. |
Lookup |
| Status | Recommended. Translates the iPaaS.com gift-card status into the BigCommerce gift-card status. Review and customize the translation values so each iPaaS.com status maps to the BigCommerce status you expect. |
Field |
| Balance | Recommended. Sets the current spendable balance on the BigCommerce gift card. |
Field with Default |
| ToName | Recommended. Sets the recipient's name. When the iPaaS.com receiving-customer name is empty, the default |
Dynamic Formula |
| OrderId | Recommended. Links the gift card to its originating order when the card was created on a linked order; when no linked order exists, it is left unset. |
Field with Default |
| ToEmail | Recommended. Sets the recipient's email. When the iPaaS.com receiving-customer email is empty, the default address is used. |
Dynamic Formula |
| FromName | Required by BigCommerce. Sets the purchasing customer's name. BigCommerce requires a name, so when none is present the value |
Dynamic Formula |
| FromEmail | Required by BigCommerce. Sets the purchasing customer's email. BigCommerce requires an email, so when none is present a default address is used. |
Dynamic Formula |
| CustomerId | Recommended. Links the gift card to an existing BigCommerce customer when the iPaaS.com customer is linked; otherwise it is left unset. |
Field |
| ExpiryDate | Recommended. Sets the gift card's expiry date on the BigCommerce card. |
Placeholder value — replace during implementation: the default recipient email guest@theredrook.com (ToEmail) and the purchaser-email fallback support@theredrook.com (FromEmail) are example addresses used when the source has no recipient or purchaser email. Replace each with the email your business wants to record before enabling this collection.
Status Lookup Translation
The Status mapping uses the BC Gift Card Status From iPaaS lookup translation. Review and customize the translation values so each iPaaS.com gift-card status maps to the BigCommerce status you expect.
Source Value (iPaaS.com) | Destination Value (BigCommerce) | Notes |
Active | active | |
Void | disabled | |
Expired | expired | |
Pending | pending |
Update BigCommerce Gift Card Updates FROM iPaaS.com
iPaaS.com data type: Gift Card
Writes later changes to an existing BigCommerce gift card from iPaaS.com in a single update operation, keeping the card's balance and status in step with the iPaaS.com Gift Card. It resolves the BigCommerce card from the external-ID link saved on the initial Add transfer, so the write updates the correct existing card rather than creating a new one. This collection handles changes to existing cards; new cards are created by Add BigCommerce Gift Card FROM iPaaS.com. This collection has no mapping filter, so every gift-card change selected by the subscribed outbound trigger is processed.
Mapping Type | Source Field (iPaaS.com Gift Card) | Destination Field (BigCommerce) | Description |
Field |
| Code | Required. Sets the BigCommerce gift-card code from the iPaaS.com gift-card number; the code identifies the card in BigCommerce. |
Dynamic Formula |
| Amount | Required by BigCommerce. Sets the card's starting balance. Uses the iPaaS.com original amount when one exists, and otherwise falls back to the current balance. |
Lookup |
| Status | Recommended. Translates the iPaaS.com gift-card status into the BigCommerce gift-card status. Review and customize the translation values so each iPaaS.com status maps to the BigCommerce status you expect. |
Field |
| Balance | Recommended. Sets the current spendable balance on the BigCommerce gift card. This is the value most commonly changed after issue. |
Field |
| ExpiryDate | Recommended. Sets the gift card's expiry date on the BigCommerce card. |
Status Lookup Translation
The Status mapping uses the same BC Gift Card Status From iPaaS lookup translation as the Add collection. Review and customize the translation values so each iPaaS.com gift-card status maps to the BigCommerce status you expect.
Source Value (iPaaS.com) | Destination Value (BigCommerce) | Notes |
Active | active | |
Void | disabled | |
Expired | expired | |
Pending | pending |
Testing and Validation
Test Scenarios
Gift card create. Manually sync an iPaaS.com Gift Card by its Gift Card ID and confirm a new gift card is created in BigCommerce with the mapped code, amount, balance, status, expiry, purchaser, and recipient; confirm the purchaser and recipient defaults are applied when the source values are empty.
Gift card update. Change the balance or status on an already-transferred iPaaS.com Gift Card, sync it, and confirm the existing BigCommerce card is updated (not duplicated) via its external-ID link.
Missing external link. Attempt an update on a gift card that has never been created in BigCommerce and confirm the update cannot locate a card; create it with the Add collection first.
Status translation. Confirm each iPaaS.com gift-card status resolves to the intended BigCommerce status, adjusting the lookup translation values as needed.
Delete. Delete a gift card in iPaaS.com and confirm the delete behaves as your business rules expect on the linked BigCommerce card.
Validation Checklist
The status lookup translation has been reviewed so each status maps to the intended value.
The purchaser-email fallback, recipient-email default, and purchaser-name fallback have been reviewed and replaced with business-appropriate values before enabling outbound transfers.
The Add and Update collections' Add/Update settings are set so a new card is created once and subsequent changes route to the update collection.
Delete behavior has been confirmed against your business rules in a staging environment.
Additional Notes
Matching. Gift cards are matched on their code (ID) only, with no additional pre-processing to reconcile them.
Full-replace writes. Outbound transfers write the full gift-card record on each run; map every field you want preserved, or use a DestinationValue approach for fields not sourced from iPaaS.com.
Purchase-for-another. The outbound flow records the purchasing customer and the recipient separately, so a gift card bought by one person for another carries both sets of details.
Inbound direction. Capturing BigCommerce gift cards and their issuance activity into iPaaS.com is documented separately in the companion BigCommerce to iPaaS.com Gift Card Mapping Documentation.