Gift Card Processing in Acumatica stores a Customer ID with each sold gift card, along with the Order Number, Inventory ID, serial number, and amount details. The product guide does not document a separate recipient field or a rule that maps a card to a ship-to contact, store, location, or trading partner. If a gift is purchased for someone else, the documented Customer ID should be treated as the customer on the sale, not proof of who received the card.
The useful link is the card’s serial number. From the Gift Cards tab on Payment Methods, a user can open Gift Card History for that serial and review related activity. The guide also describes customer information arriving with gift cards created through the Biztech endpoint, although it does not specify the API’s customer-field mapping.
What Customer Information Follows a Gift Card Sale
A gift card can be sold as a non-stock item or as a serialized stock item on a standard Acumatica sales order. After the sale, the Gift Cards tab on Payment Methods lists Customer ID, Inventory ID, Gift Card Serial Number, Order Number, Gift Card Amount, Used Amount, and Remaining Amount. For a stock card, the sales order uses a selected lot or serial number; for a non-stock card, the number may be entered or generated according to Gift Card Preferences (BZ102000).
Those fields let staff trace a card back to the order and customer record captured by the sale. The guide does not define a recipient account, recipient email, or card-owner field. It also does not say that later redemption changes the original Customer ID. Keep purchase, delivery, and redemption identities separate in any business procedure until your implementation documents how each is recorded.
Gift Card Customer Tracking at a Glance
At sale, confirm the sales order is on the intended customer before the gift card is fulfilled.
Record or generate the card number. For a stock gift card, select the allocated serial number on the sales order line.
After sale, compare Customer ID and Order Number with the Gift Card Serial Number on the Payment Methods Gift Cards tab.
Open Gift Card History (BZ407099) from the serial number to review activity for that card.
If a card is created through the external API, verify the customer information displayed on Payment Methods, Gift Card Summary, and Gift Card History.
This is a review sequence for people using the documented screens. The manual does not describe a built-in duplicate-customer check or an automated recipient match.
Keep the Purchaser and Recipient Distinct
A buyer may purchase a card as a gift. In the documented workflow, the sales order has a customer and the resulting gift card record has a Customer ID. The guide never states that this ID changes to the person who receives the card. It gives no field where a recipient name, address, or email is captured for a gift card.
For downstream order accuracy, check the sale’s customer and order number against the card record before answering account questions. Use the serial number when asking about a specific card’s balance or history. If your business needs a separate recipient record or delivery instruction, define where that information will live and how staff will verify it. The Gift Card Processing guide cannot supply that mapping.
Check Customer Information on External Gift Cards
The guide says the Create Gift Card action in the Gift Card History endpoint can import gift card information from an external system through the Biztech API. After the request is processed, customer information, serial number, and amount appear on the Gift Cards tab of Payment Methods and on Gift Card Summary and Gift Card History.
The guide does not list the API request fields or explain how an external customer identifier is matched to an Acumatica Customer ID. It also gives no duplicate rule for two API requests with the same customer or serial number. For a new integration, test a small set of cards and compare the resulting Customer ID and serial number with the external source before increasing volume.
Avoid Duplicate and Misassigned Card Records
Gift Card Preferences controls how non-stock gift card numbers are generated. It offers numbering segments or random numbering. Stock cards use serial numbers generated during receipt and selected during allocation. These are number-generation methods, not documented customer-deduplication rules.
Use a concrete review: look up the card’s serial number, check the linked Order Number and Customer ID, and inspect Gift Card History before creating a second card for the same request. If a customer account was entered incorrectly on the source order or an external API request, the guide does not describe a reassignment or merge action for the card. Resolve the record with the implementation team rather than assuming an account edit will move the gift card history.
Where to Check Customer and Card Details
Sales Orders: review the customer and gift card line on the sale that created the card.
Payment Methods Gift Cards tab: compare Customer ID, Inventory ID, Gift Card Serial Number, Order Number, Gift Card Amount, Used Amount, and Remaining Amount.
Gift Card History: open the card by serial number to review related transactions.
Gift Card Summary: inspect the card details displayed after an external API creation.
The guide names no recipient, ship-to, store, location, or trading-partner field in those gift card views. Check such information in the original business process if your team records it elsewhere; do not present it as a built-in Gift Card Processing mapping.
Gift Card Customers and Recipients: Frequently Asked Questions
Does Customer ID identify the gift card recipient?
The guide does not say that. It stores Customer ID with the sold card and its Order Number, but defines no separate recipient field.
Can a gift card be linked to a ship-to address or store?
No such link is documented for the gift card record. A delivery or store requirement needs its own confirmed workflow.
How do I trace a card back to the original sale?
Use the Gift Card Serial Number and Order Number on the Payment Methods Gift Cards tab, then open Gift Card History for the serial.
Where does the customer appear for an API-created gift card?
The guide says customer information appears on Payment Methods, Gift Card Summary, and Gift Card History after the Create Gift Card API action is processed.
Does Gift Card Processing prevent duplicate customer accounts?
The documentation does not describe a customer-deduplication feature. Verify the customer record used by the source order or external request before creating cards at scale.
Can the customer on a sold gift card be changed later?
The guide gives no reassignment procedure. Confirm the correction path with your implementation team before changing a source order or customer record.
To review your gift card customer and recipient workflow, contact Biz-Tech Services at https://biz-techservices.com.
