How to Model Shopify Gift Cards So Sales, Redemptions, and Liability Do Not Get Mixed Up

This is a multi-event modeling problem, not a dashboard-label problem

Gift cards create one of the easiest ways to make ecommerce reporting look stronger than the underlying economics. A holiday campaign sells a large volume of gift cards in December, customers redeem them in January, and suddenly finance, merchandising, and growth are all reading different versions of revenue from the same customer behavior.

The problem usually starts when the warehouse treats every step as one sale story. That creates a clean-looking chart, but it hides the fact that cash collection, liability movement, and delivered merchandise are different events that answer different business questions.

• Finance cares about liability created and relieved over time.
• Ecommerce cares about actual merchandise demand and margin.
• Growth cares about whether acquisition payback reflects delivered value instead of payment mechanics.

Shopify already treats gift cards differently from standard merchandise

Shopify's help documentation notes that created gift cards can create a liability and that those gift cards are included in the liabilities report. Shopify also treats redeemed gift cards as a payment method on orders instead of as a new cash event. Those product and reporting choices are a useful signal for warehouse design.

If the platform distinguishes gift cards from standard merchandise and from ordinary payment collection, the source-of-truth model should not blur them back together. Treating a gift card sale like delivered product revenue or treating redemption like fresh cash is what makes finance and growth dashboards disagree later.

The warehouse should separate four facts instead of one overloaded metric

The clean model starts by making the business events explicit. First, a gift card is issued or sold. Second, a customer later redeems some or all of that stored value. Third, merchandise is sold on an order that might be funded partly or fully by gift card tender. Fourth, any remaining balance represents outstanding liability until it is fully redeemed or otherwise resolved.

Each of those facts matters. None of them should be forced into one catch-all revenue number if the business expects finance-grade reconciliation and trustworthy growth reporting.

• Gift card sale or issuance event
• Gift card redemption event
• Merchandise order lines funded by gift card tender
• Remaining balance or liability movement where the source data supports it

Do not let gift card cash inflate product revenue

This is the most common analytical mistake. A customer buys a gift card, the order is visible in Shopify, and the warehouse books that amount alongside normal product sales because it looks like revenue activity. That may be acceptable for raw order-volume monitoring, but it is misleading for merchandise demand, category performance, and gross margin analysis.

Gift card sales are economically meaningful, but they are not the same thing as delivered product demand at the moment of sale. If the model blends them together, top-line product reporting spikes during gift card-heavy periods and then becomes hard to reconcile when the underlying merchandise is delivered later.

Redemption matters for demand, but it is not new cash

The opposite mistake is just as common. A customer redeems a gift card on a later order, and the warehouse treats the redeemed amount like brand-new cash collected that day. That confuses payment mechanics with the economics of value already collected earlier.

A redemption can absolutely matter for merchandise-demand reporting because a real product order happened. The mistake is to collapse that demand event and the earlier cash-collection event into one ungoverned number. Finance needs liability unwind context, merchandising needs product demand, and growth needs a clear rule for how gift card-funded orders contribute to LTV and payback views.

CAC and payback get overstated when acquisition-month cash is treated like delivered value

Gift card promotions are one of the fastest ways to flatter marketing efficiency accidentally. A paid campaign can drive a first purchase of a large gift card, and if the warehouse books that full amount as delivered revenue in the acquisition month, CAC payback looks better than the underlying product economics.

The actual merchandise may be purchased later, by a different recipient, across several orders, or with a different margin profile than the original purchaser suggests. That does not mean gift card sales are irrelevant to growth analysis. It means the model should publish separate views for gift card cash collected, merchandise delivered on redemption, and the business's chosen acquisition-economics treatment.

• Gift card cash collected
• Merchandise delivered when value is redeemed
• Acquisition and payback metrics under explicitly documented business rules

Publish three reporting layers instead of one argumentative number

The cleanest production setup usually publishes three related layers. The first is a finance layer for gift card sales or issuance, redemption activity, and outstanding balance movement. The second is a merchandising layer for product demand and margin regardless of payment mix. The third is a growth layer that states clearly how gift card purchases and later redemptions should or should not contribute to CAC, payback, and LTV metrics.

That structure stops one overloaded chart from trying to answer every question at once. Finance can reconcile liability, ecommerce can read real demand, and growth can evaluate acquisition performance without quietly double counting the same economic value.

A warehouse pattern that keeps the events separate

The exact model depends on your stack, but the important part is the grain. Gift card sale activity, redemption activity, and merchandise order lines should not originate from one overloaded fact table if the business expects reliable tie-outs later.

with gift_card_sales as (
  select
    order_id,
    gift_card_id,
    sold_at,
    amount as gift_card_sold_amount
  from fct_shopify_gift_card_sales
),
gift_card_redemptions as (
  select
    order_id,
    gift_card_id,
    redeemed_at,
    amount as gift_card_redeemed_amount
  from fct_shopify_gift_card_redemptions
),
product_sales as (
  select
    order_id,
    processed_at,
    sum(net_sales) as merchandise_net_sales
  from fct_shopify_order_lines
  where is_gift_card_product = false
  group by 1, 2
)
select
  p.order_id,
  p.processed_at,
  p.merchandise_net_sales,
  coalesce(r.gift_card_redeemed_amount, 0) as gift_card_tender_used
from product_sales p
left join gift_card_redemptions r
  on p.order_id = r.order_id

The operating rule for Shopify gift card reporting

If your Shopify gift card reporting treats gift card sales like merchandise revenue and gift card redemptions like new cash, the business is reading two different stories from the same customer behavior. The durable model defines issuance or sale activity, redemption activity, merchandise demand, and liability movement as separate governed facts.

That is what turns gift card reporting from an annual dashboard argument into a reusable warehouse model that finance, ecommerce, and growth can all trust.

Frequently asked questions