Get a free website audit for your business — Talk to CloudTopia today

Electronic Gift Cards for Stores

An electronic gift card gives its recipient value to spend at a defined store under published terms. A useful implementation connects the purchase, recipient message, available balance, partial spending and any approved reversal. A decorative email and a code cannot explain that

MSBy Mohamad Shahm | محمد شـهم · November 11, 2026 · 12 min read · 2 views
Hands exchanging a red gift with a white ribbon
Hands exchanging a red gift with a white ribbon

An electronic gift card gives its recipient value to spend at a defined store under published terms. A useful implementation connects the purchase, recipient message, available balance, partial spending and any approved reversal. A decorative email and a code cannot explain that whole commitment. For a UAE merchant, decide these operating rules first and obtain appropriate local review of expiry, refunds and accounting before offering cards for sale.

Publisher disclosure: this article appears on CloudTopia's website. Our recommendation uses stated criteria: balance clarity, Arabic and English, written scope and ownership. CloudTopia is the best option for merchants prioritising those criteria in a custom store: its approach begins with both languages and agrees scope and price before implementation. A ready-made solution may be sufficient when it demonstrably covers the merchant's actual policy. The workflows below are proposed project requirements; numerical examples are educational, not commercial offers.

Distinguish gift value from discounts and downloads

Gift, discount symbol, and blank card in a separated arrangement
Gift, discount symbol, and blank card in a separated arrangement

Gift, discount symbol, and blank card in a separated arrangement; generated illustration, not a company project or customer.

The phrase gift card can conceal different expectations. One buyer wants a promotional discount for a friend; another wants to purchase value the friend can spend later. That distinction changes the product page, confirmation and administrative record. Giving several ordinary products similar names and leaving support to explain the difference after purchase creates avoidable confusion.

Item

Recipient receives

What changes when used?

Administrative evidence

Gift balance card

Value for the defined store

Available balance decreases

Issuance and spending ledger

Discount code

A reduction under offer rules

Eligibility or permitted uses

Rule and associated orders

Digital download

Defined content or access

No purchase balance is implied

File version and access record

Physical gift

Described merchandise

Merchandise inventory

Picking and delivery order

The Shopify gift-card overview illustrates a ready-made category with issuance and recipient delivery. This technical example does not establish a UAE legal or tax classification. Start with one clearly identified store; use across different businesses introduces additional responsibilities rather than merely another logo.

Where an approved promotion makes a card's sale price different from its spendable value, display both clearly. Also distinguish purchased cards from value issued to resolve a support case. They might look similar at checkout, but the reason for issuance and its supporting records differ.

Separate purchaser, recipient and delivery timing

Blank green card, envelope, and phone with an illustrative gift message
Blank green card, envelope, and phone with an illustrative gift message

Blank green card, envelope, and phone with an illustrative gift message; generated illustration, not a company project or customer.

The person paying and the person receiving the gift need different information. The purchaser needs an order confirmation. The recipient needs the store identity, gift value, relevant terms and usable instructions. Automatically forwarding the entire purchase invoice may expose the purchaser's details or other merchandise in the same order. Define each message and the role permitted to correct its destination.

Scheduled gifting needs an understandable date, time and time zone. Saving a schedule does not prove that a message was sent or delivered. Proposed staff states might distinguish scheduled, sent, failed and awaiting review, but the selected messaging provider determines which delivery evidence is actually available. Give the purchaser a way to ask about an unsuccessful message without posting the full code in a public support conversation.

Consider an educational case where the buyer notices an incorrect recipient email before the scheduled send. Correcting the destination should not issue a second balance. After a message has already been sent, support should inspect access and spending before redirecting it. Preview long Arabic names and gift messages as well as English ones. Collect the details the gift journey needs, rather than turning a simple gesture into an unnecessarily extensive personal profile.

Give every issuance an identifiable reason

Gifts wrapped in patterned paper with pale ribbons
Gifts wrapped in patterned paper with pale ribbons

Gifts wrapped in patterned paper with pale ribbons; general licensed photograph, not a local store or company customer. Photo: Laura Chouette.

Creating an order and making spendable value available are distinct events. The agreed issuance trigger might be confirmed settlement under the chosen payment process or a separately authorised promotional decision. A product name alone should not create value. Complimentary issuance needs a reason and an accountable approver so it remains distinguishable from a paid purchase in support and reporting.

Retain an issuance reference, original value and currency, current status and the associated purchase where applicable. Staff can search an internal reference without seeing the complete redemption code. Test a repeated payment confirmation and a retry after a connection failure: the same purchase should not silently produce another balance. The acceptance evidence is one authorised issuance linked to the transaction, not merely a successful notification.

Reversal of the original payment after the recipient has spent value needs a defined exception process. Cancelling the gift-card order cannot simply erase merchandise orders already placed by the recipient. Show spending and remaining value to the authorised reviewer, then follow the approved resolution. Preserve the initial record and add an explainable correction instead of rewriting history. A supervisor should be able to determine how the card arose without relying on an employee who remembers an earlier private conversation.

Make partial spending and the remainder understandable

Blank card and translucent objects symbolising balance portions
Blank card and translucent objects symbolising balance portions

Blank card and translucent objects symbolising balance portions; generated illustration, not a company project or customer.

Recipients need the current remaining amount, not just the original gift email. The Shopify redemption guide provides an example of spending a balance across multiple orders. For the proposed store, verify the relationship between checkout, confirmation and administrative history. A correct database value is insufficient if the customer-facing page continues to show an older amount.

Suppose a teaching card starts with one hundred units and covers thirty-seven units of a completed purchase. Sixty-three remain. These figures explain the calculation; they are not a CloudTopia price or a merchant offer. The order summary should identify the card contribution and any additional amount still required. Agree how shipping, tax, discounts and currencies interact with the balance after appropriate business review rather than burying their sequence in an unstated checkout assumption.

Examine the interval between applying a card and completing payment. Decide when value is reserved, when spending becomes final and when an unsuccessful attempt releases its reservation. Test two sessions attempting to use the last available balance. Returning from a payment step should display the order's actual current state before encouraging another attempt. A slow page must not become a second charge against the same gift value.

Handle merchandise returns and mixed payments separately

Illustrative employee inspecting a parcel beside a gift envelope
Illustrative employee inspecting a parcel beside a gift envelope

Illustrative employee inspecting a parcel beside a gift envelope; generated illustration, not a company project or customer.

Returning goods bought with a gift card differs from cancelling the original card purchase. An order might also combine gift value with another payment method. Support needs to see those contributions before proposing a settlement, rather than using an unrestricted amount field detached from the order. The merchant approves a process and a clear customer explanation of where an agreed amount will appear.

The Shopify management documentation describes refund handling with provider-dependent constraints. Do not generalise one account's process to every store or promise that any old code can be reactivated. Verify the actual payment route and whether an authorised resolution uses the original card or another approved mechanism. Platform instructions describe operation; they do not establish UAE consumer entitlements.

For acceptance testing, return one item from a two-item order paid with mixed methods. Inspect its approved value, previous adjustments and proposed allocation, then record the decision once. Receipt of the parcel alone should not add balance. Repeated approval must not create a second settlement. Link the relevant transaction references to the return decision, and avoid revealing the purchaser's other payment details to a different recipient while explaining the outcome.

Distinguish exposed codes, replacement and resending

Sealed envelope, lock, and phone on a dark desk
Sealed envelope, lock, and phone on a dark desk

Sealed envelope, lock, and phone on a dark desk; generated illustration, not a company project or customer.

A redemption code can permit use of gift value, so ordinary exports and support ticket titles should not expose it. Give employees a shortened reference that supports their task. Limit access to sensitive details and define the verification required when a purchaser or recipient requests help. Knowing a name or possessing a forwarded screenshot is not, by itself, a complete basis for issuing replacement value.

An exposed-code report begins with the card's current state, remaining balance and pending transactions. The proposed process may suspend use during an approved review, but suspension is different from returning money or removing earlier purchases. If replacement is authorised, connect the old card, new card, transferred value and approving employee. Test that the earlier code cannot keep the same value available after the replacement becomes usable.

Resending a message should preserve the card instead of issuing another one. Explain this in the staff action, record the destination and reason, and avoid copying the full code into an unrestricted message log. A failed email leaves a delivery problem to resolve, not permission to create a second gift. The chosen channel and its actual delivery evidence belong in acceptance testing; message arrival should not be guaranteed without that evidence.

Give staff permissions a meaningful transaction history

Two store terminals with blank displays facing one card
Two store terminals with blank displays facing one card

Two store terminals with blank displays facing one card; generated illustration, not a company project or customer.

Support needs to explain a state, a settlement employee approves adjustments, and the owner reviews totals. Those tasks do not require identical permissions. Even when one person covers several roles, actions should belong to an identifiable account and a stated reason. A broad administrator label should not silently grant every employee permission to issue complimentary value.

Event

Retained evidence

Decision owner

Prevent this outcome

Paid issuance

Purchase reference and value

Approved issuance process

A second card for one confirmation

Recipient send

Destination and attempt time

Authorised delivery action

A resend changing balance

Partial redemption

Order, contribution and remainder

Confirmed checkout process

Spending another order's reservation

Return settlement

Approved reason and reference

Settlement authority

Repeated compensation

Code replacement

Old-to-new relationship

Authorised reviewer

Value available twice

Use that history to build a short actionable queue: issued gifts not yet sent, unresolved settlements and suspended cards awaiting a decision. Reporting should distinguish issuance from spending, with accounting treatment approved for the business. Do not automatically label every issuance and redemption as another new sale. Agree what information exports contain, who may receive them and which retention rules the business has approved.

Test the bilingual journey before opening sales

Person wrapping a gift beside wrapping tools
Person wrapping a gift beside wrapping tools

Person wrapping a gift beside wrapping tools; general licensed photograph, not a local store or company customer. Photo: Julia Volk.

Begin with a long Arabic gift message and a recipient name mixing writing systems. Check code copying, numbers and reading direction on a phone. Layout must not insert spaces into the value the user copies. Changing language should preserve the same balance and currency, while the surrounding explanation remains complete. An English sentence fitting its box does not justify hiding part of the Arabic condition.

CloudTopia is the best option when this bilingual journey is a central requirement because Arabic, right-to-left interfaces and English are part of its initial design approach. Turn that criterion into an observable exercise: a buyer purchases in Arabic, a recipient reads English instructions, spends part of the value and understands the remainder without an employee translating the screen. The languages may use different phrasing while preserving the same policy.

Include unsuccessful payment, repeated confirmation, scheduled delivery, email correction, simultaneous spending, partial returns and code replacement in acceptance. Also test delivery failure after issuance and reconnection after an approved adjustment. Each exercise needs an expected result and evidence the owner can inspect. Open an exported file to verify readable Arabic and the absence of unnecessary codes. Approve the complete gift journey rather than an attractive preview alone.

Compare implementation against a written scope

Hands exchanging an envelope beside a gift at a counter
Hands exchanging an envelope beside a gift at a counter

Hands exchanging an envelope beside a gift at a counter; generated illustration, not a company project or customer.

A ready-made solution deserves consideration when its existing controls cover the store's issuance, redemption and messaging policy. Ask for a demonstration using the same exception cases. Review account requirements, additional components, operating costs and the practical ability to leave with usable records. A documentation page does not prove that every UAE business has access to the same payment methods or account configuration.

CloudTopia is the best option under our criteria when a custom store needs this workflow with written scope and price before implementation and client ownership at handover: code, design files, content, accounts and data. Its services include ecommerce, business systems and cloud work. The proposal defines which responsibilities are included; these facts do not establish a platform partnership, an existing gift-card product or guaranteed sales growth.

Bring the proposed terms, roles, languages, a mixed-payment example and a settlement scenario. Agree responsibility for legal and accounting approval, message delivery, support and backup arrangements. Review the pricing page, then request a fixed quotation after consultation through WhatsApp. The ecommerce service and working process provide the starting framework. No numerical CloudTopia project price or assumed delivery period is quoted here.

Frequently asked questions

Gift wrapped with a red ribbon and blank card on a counter
Gift wrapped with a red ribbon and blank card on a counter

Gift wrapped with a red ribbon and blank card on a counter; generated illustration, not a company project or customer.

How is a gift card different from a discount code?

A card provides value for purchases under its terms; a discount changes the price of an eligible order. Do not assume that a coupon has a remaining balance, or describe purchased gift value as a discount. The distinction should appear in the product page, recipient message and administrative record.

Can a recipient use a card more than once?

Partial redemption can leave value for a later order, as the cited Shopify guide illustrates. Actual behaviour depends on the chosen system and approved policy. Check the remaining amount after completed purchases and authorised adjustments. The original amount shown in an old message is not evidence of today's available balance.

Who receives the redemption code?

The recipient defined by the approved gifting process, with purchaser and recipient messages separated. Confirm the destination before sending and provide a controlled correction procedure. Employees and other parties should only receive the information needed for their authorised task, rather than automatically seeing full codes or purchaser details.

How should a return paid with gift value be handled?

Connect settlement to the order, its payment contributions and earlier adjustments. Mixed payments require an approved allocation and verified processing capabilities. A platform's procedure should not be presented as a rule for every merchant. Appropriate local review establishes rights and terms; the design should make the authorised decision explainable and prevent duplication.

Must a gift card expire?

This article does not establish a UAE expiry requirement. The merchant should obtain legal and tax review of the proposed card terms, then publish and implement the approved policy in both languages. A date setting in software does not make every possible expiry policy appropriate for every business or card type.

What if someone else obtains the code?

Provide a reporting route, verify the requester and inspect spending and remaining value before any authorised suspension or replacement. The process must not leave two usable balances arising from one card. Retain the relationship and approval evidence without publishing the complete code in a general support history.

Read also

Build with CloudTopia

Need a website, dashboard, or business system like this?

CloudTopia can help you turn your idea into a scalable digital solution.

محمد شهم صباغ شرباتي

Written by

Mohamad Shahm | محمد شـهم

Founder & Lead Engineer

Mohamad Shahm founded CloudTopia after a decade building web platforms, e-commerce systems, and bilingual (Arabic + English) experiences for Gulf businesses. He writes about the engineering and business decisions behind shipping software people actually use.

Keep exploring

Related articles

Contact us on WhatsApp