Selling Gift Cards Online: What to Set Up First

What selling gift cards online commits you to

A gift card is a stored-value promise. The moment one sells, three things need to be true at once: the customer can check and spend the balance, your team can look a card up when something goes wrong, and your books can show how much value is still outstanding.

The failure pattern is almost always the same. The cards sell fine, and then the operator discovers that the balance lives in a spreadsheet, the support team cannot see it, and nobody can say what is still owed at the end of the month. Retrofitting those three things after a launch costs more than building them first, which is why the order below matters.

What has to exist before the first card is sold

Six things need to be working before a gift card appears on sale. Each is cheap to configure at the start and awkward to add once cards are in customers hands.

• A product per denomination, or a variable-amount product with a minimum, so the card exists as a catalog item you can merchandise, discount and report on like any other product.
• A unique code per card, generated when payment clears rather than printed in advance, holding its own balance.
• A redemption path inside the checkout you already run, so a card is a payment method as well as a product. If you also sell in person, the same balance has to be spendable at the counter.
• A balance lookup your support team can use without exposing the full code - a code pasted into a support thread is a code somebody else can spend.
• A void or refund route for a card issued twice or to the wrong buyer, with a record of who made the change and why.
• A report that separates issued, redeemed and outstanding value by period, because a single total hides all three.

Decide the rules before anything is printed

Most gift card disputes are rule decisions made late rather than software faults. Settle these in writing before you configure the product.

• Expiry. Some jurisdictions restrict expiry dates on gift cards or regulate how long a balance must stay redeemable, so confirm the rule where you sell before setting a period. Where expiry is allowed, it belongs in the product description as well as the terms.
• Partial redemption. Can a customer spend part of the balance and keep the rest? In practice almost always yes, and that answer decides whether a code needs a running balance or only a used flag.
• Buying a card with a card. Usually no. Allow it and you have created a loop that moves value between codes with no sale underneath.
• Discounts and sale items. Say whether a card applies to already-discounted products, because the answer changes the margin on a promotion.
• Combining with other payment. Whether a card can cover part of a basket with the rest on a card determines the checkout flow your customers meet.
• Discontinued products. What happens to a balance when the thing it was bought for stops existing - a cancelled event, or a subscription that ends.

Fraud is the failure mode that costs the most

A gift card is a bearer instrument: whoever holds the code holds the money. That makes it one of the most attacked parts of a storefront, and the controls are worth stating plainly.

• Issue codes at payment, and never pre-print a batch of live codes.
• Generate codes that are not sequential and cannot be guessed from a neighbouring card.
• Apply velocity limits per card, per customer and per address, and flag an unusually large single gift card purchase on an unverified payment method.
• Attribute every manual balance adjustment to a person, with a reason recorded.
• Reconcile outstanding balance against settlement totals, so a missing or duplicated code shows up as a number rather than as a suspicion weeks later.

The reporting an operator actually needs

Four numbers turn a gift card program from a gut feeling into a line you can run. Take them at a fixed point in each period so they stay comparable.

• Outstanding balance at the close of the period - the liability figure, and the first thing an accountant will ask for.
• Redemption rate by campaign and channel, which tells you whether the card behaved as a gift or as a discount in disguise.
• Average days from issue to redemption, which predicts when the cash converts into revenue.
• Value issued and not redeemed in the period, the part that may eventually be written down rather than earned.

How gift cards fit a ShopDango storefront

On a ShopDango storefront gift cards are a product type rather than a bolt-on. Card products sell at any denomination, codes are generated on fulfilment, the balance decrements during checkout, and the outstanding liability stays visible to the operator instead of living in a separate vendor dashboard. Expiry rules are configurable per product where your regulations allow them, and support can look a card up by balance, merchant and issue date.

The practical benefit is the boring one: the storefront, the payment method and the liability figure sit in the same system, so there is no monthly reconciliation between a gift card provider and your own order history.