Should You Build or Buy Gift Cards with the Plus API?
Building gift-card issuance on the GiftCard GraphQL API wins for Shopify Plus stores that issue cards from warranty, service or loyalty rules. A custom app calling giftCardCreate costs $6,000 to $15,000 one-time (Deploi estimate, illustrative) and issues native cards with no per-card fee. Build on GraphQL, not the REST endpoint the plan page advertises: REST has been legacy since October 1, 2024. Buy Rise or Gift Card Hero when gifting UX is the product.
Your profile — see how the verdict shifts
- Confidence
- Medium — Shopify's changelog entry dated March 19, 2021 states that as of API version 2021-04 the GiftCard GraphQL APIs are available for custom and private apps installed on Shopify Plus stores, and that GiftCard REST access was extended to the same custom apps. Shopify's REST rate-limits page states that the REST Admin API is a legacy API as of October 1, 2024 and that all apps and integrations should be built with the GraphQL Admin API. The GraphQL reference lists giftCardCreate, giftCardUpdate, giftCardDeactivate and two notification mutations under the gift-card scopes, read 2026-09-05. Three gift-card apps with live listings and published prices were checked: Rise (4.7★, 757 reviews), Gift Card Hero (4.9★, 172 reviews) and GV (4.2★, 85 reviews). The category is healthy and cheap, which is why confidence is medium: the build wins on control and fit, not on subscription math.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · agency dev bench · a few hundred programmatic issuances a month from warranty, service-recovery and loyalty events
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Not on Shopify Plus | BUY | Custom apps below Plus can't reach the GiftCard API, so programmatic issuance means an app. Gift Card Hero lists API access on its PRO tier at $19.99/month (verified Sep 2026), which is the cleanest bought answer. |
| Plus · under 50 programmatic issuances a month | WAIT | Issuing from the admin takes a minute a card. Neither a build nor a subscription pays back at this volume; write the issuance SOP, log the reason codes in the card note, and revisit at a few hundred a month. |
| Plus · hundreds a month from warranty, service or loyalty rules | BUILD | One mutation, one trigger, native cards. A $6,000–$15,000 build (Deploi estimate, illustrative) keeps a vendor out of your compensation path and never lands you in a per-order pricing tier. |
| Plus · a consumer gifting program plus programmatic issuance | BUY | Scheduled delivery, recipient messaging and balance reminders are the app's real product, and the apps issue native Shopify cards anyway. Use the app's API or bulk tools rather than building beside it. |
What Gift Card REST API Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Retention & LTV | High | A compensation card issued the moment a warranty or service case closes turns a complaint into a return visit, with the value tied to your store rather than a refund to a card. |
| Operational efficiency | High | Issuance from a rule replaces admin clicks and a spreadsheet: the card, the reason code and the approver are recorded in one step, hundreds of times a month. |
| Revenue — indirect | Medium | Gift-card balances get spent above face value on average, so cards issued as loyalty rewards or compensation bring incremental baskets back to the store. |
| Data & insight | Medium | Reason codes on every card show which warranty, service or loyalty rules cost the most, which is a product-quality signal as much as a finance one. |
| Customer experience | Medium | The code arrives in your own branded email inside the customer's existing journey, rather than a generic notification from a vendor template. |
Spend ceiling: Size the spend to the issuance rules, not the card. One mutation is cheap; the policy work (amounts, expiry, approvers, reason codes) is where the value and the risk both sit, so budget the $6,000–$15,000 build (Deploi estimate, illustrative) around getting that right.
What buying enables (top apps)
- + Live this week: scheduled delivery, recipient messaging, balance reminders and bulk creation out of the box
- + Store credit and loyalty bundled with gift cards in one install on Rise
- + An API path to programmatic issuance for stores below Plus, where custom apps can't reach the GiftCard API
- + Vendor-maintained templates and POS tooling with no design decisions to make
What building additionally unlocks
- + Issuance from your own warranty, service and loyalty rules, with your amounts, expiry and reason codes on every card
- + No vendor in the compensation path and no per-order pricing tier to outgrow
- + An audit trail of trigger, approver and reason in your own records, ready for finance and for fraud review
- + Delivery through your ESP so the compensation message is part of the customer journey you already run
Find Your Verdict in 3 Questions
Is your store on Shopify Plus?
Yes: Go to question 2.
No: Your verdict: BUY — custom apps below Plus can't reach the GiftCard API; Gift Card Hero's PRO tier lists API access at $19.99/month (verified Sep 2026).
Do you issue more than about 50 cards a month from warranty, service or loyalty rules?
Yes: Go to question 3.
No: Your verdict: WAIT — issue from the admin, record the reason in the card note, and revisit when volume reaches a few hundred a month.
Is the consumer gifting experience (scheduled delivery, recipient messages, reminders) part of what you need?
Yes: Your verdict: BUY — the gifting UX is the app's real product, and the apps issue native cards anyway; use the app's API or bulk tools for your triggers.
No: Your verdict: BUILD — a custom app on giftCardCreate, $6,000–$15,000 (Deploi estimate, illustrative), built on GraphQL rather than the legacy REST endpoint.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | An app installs in a day; the custom app is 2–4 weeks including the Flow trigger and the customer notification (Deploi estimate, illustrative). | ||
| Recurring fees | Rise prices by monthly store orders at $19.99–$199.99/month across its listed tiers (verified Sep 2026), and the listed tiers stop at 2,000 orders; the build's recurring cost is one API version move a year. | ||
| Maintenance & upgrades | One mutation on a stable native object: upkeep is the annual GraphQL version bump, roughly $900–$3,000/yr (Deploi estimate, illustrative). | ||
| Switching & exit | Both paths create native Shopify gift cards, so balances survive either exit; leaving an app loses only its scheduling and reminder history. | ||
| Risk | |||
| Vendor risk | Three live vendors with 85 to 757 reviews is a healthy category, and still a third party sitting inside a customer-compensation flow. | ||
| Security & compliance surface | Gift cards are cash equivalents; an app holds a permanent gift-card write grant, while your custom app's scope, secrets and audit trail are yours to lock down. | ||
| Platform-deprecation exposure | The REST GiftCard endpoint the Plus plan page lists is legacy as of October 1, 2024; a GraphQL build carries only the routine version cycle, while a REST build carries a migration from day one. | ||
| Value | |||
| Fit to requirement | Apps issue cards on their triggers and templates; the build issues exactly when your warranty, service or loyalty rule fires, with your amounts, expiry and reason codes. | ||
| Time to market | Live this week with an app versus about a month for the custom app and its trigger. | ||
| Performance & scale | Neither path touches the storefront; a few hundred issuances a month sits far inside Plus's 1000 points/second GraphQL Admin API limit (verified Sep 2026). | ||
| Data ownership & AI-readiness | Native gift cards are your data on both paths; the build also keeps the issuance reason, trigger and approver in your own records instead of a vendor dashboard. | ||
| Focus & opportunity cost | Small enough scope that the opportunity-cost argument barely applies: one mutation behind one trigger is a first custom-app build, not a distraction. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Rise Gift Cards & Store Credit | Live — 4.7★, 757 reviews; Built for Shopify. Gift cards, store credit and loyalty in one app. Pricing tiers are set by monthly store orders and the listed tiers stop at 2,000 orders a month, so a mid-market store confirms pricing above that on the current listing. | Starter $19.99/month (100 monthly orders), Small-Business $59.99/month (400), Pro $199.99/month (2,000, includes bulk gift card creation); 7-day free trial (verified Sep 2026) | A full gift-card and store-credit program where bulk creation and loyalty matter more than your own triggers |
| Gift Card Hero • All‑in‑one | Live — 4.9★, 172 reviews; Built for Shopify. Advertises API access for developers on its PRO tier, which is the cleanest bought answer to programmatic issuance for stores below Plus. Confirm the API's scope on the current listing before designing around it. | Free to install at 2% of gift card value (min. $9.99/month, max. $49.99); PRO $19.99/month with API access; Shopify Plus tier $39.99/month (verified Sep 2026) | Programmatic issuance without Plus, or a percent-of-value entry price for a small program |
| GV: Gift Cards & Store Credit | Live — 4.2★, 85 reviews; Built for Shopify. A free plan for small and new stores and the lightest paid tier in the category. | Free plan; Premium $15/month (verified Sep 2026) | Basic gift-card and store-credit features at the lowest price in the category |
| Custom issuance app on the GiftCard GraphQL API | Build lane — A custom app installed on your Plus store with the gift-card write scope, calling giftCardCreate from a Flow action, a webhook or your help desk, then delivering the code through your ESP. Custom-app access to the GiftCard API is Plus-only; build on GraphQL, not the legacy REST endpoint. | $6,000–$15,000 one-time plus roughly $900–$3,000/yr upkeep (Deploi estimate, illustrative) | Plus stores issuing hundreds of cards a month from warranty, service-recovery or loyalty rules |
The Build Path
- Custom app + giftCardCreate: A custom app with the gift-card write scope, installed on your Plus store, exposes one operation: create a card of a given value for a given customer, with an expiry and a note recording the reason. The GraphQL mutation returns the card; your app stores the reason code, the trigger and the approver beside it.
- Trigger from Flow or your help desk: Plus stores can use tasks created by custom partner apps, so issuance shows up as a Flow action your CS lead drops into a workflow. Flow's Send HTTP Request action (Grow, Advanced and Plus; waits up to 30 seconds for a response) is the lighter alternative, and a help-desk macro or warranty form can call the same endpoint.
- Deliver through your ESP: Send the code with your own template from your ESP or transactional sender so the compensation message reads like your brand and lands inside the customer's existing journey. giftCardSendNotificationToCustomer covers the native email path when you'd rather not template it.
- Effort band
- $6,000–$15,000 build — Deploi estimate (illustrative); lands in the $10–25K contact-form band
- Typical timeline
- 2–4 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $900–$3,000/yr (Deploi estimate, illustrative), mostly the annual GraphQL API version move. There is no subscription line and no per-card fee.
- What you own — and what you take on
- You own: the issuance rules, amounts, expiry policy, reason codes and the audit trail of who issued what and why. You take on: a cash-equivalent write permission to lock down, and the yearly API version bump.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $1,500–$5,000 (setup and trigger integration) | $6,000–$15,000 |
| Years 1–3 (recurring) | $720–$7,200 | $2,700–$9,000 (maintenance) |
| 3-year total | ≈$2,200–$12,200 | ≈$8,700–$24,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: Gift Card Hero PRO at $19.99/month or Rise Starter to Pro at $19.99–$199.99/month (verified Sep 2026), plus integration of the app's API into your triggers; mid-market order volumes exceed Rise's listed 2,000-order tier, so the upper band is illustrative.
- † Build column: custom app, Flow action and ESP delivery; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Order-count pricing tiers: Rise's listed tiers stop at 2,000 monthly orders (verified Sep 2026), and a mid-market store sits above them from day one
- — Percent-of-value pricing on entry tiers charges you for the cards you issue as compensation, which is money you already gave away
- — The app's API becomes the integration surface your warranty and loyalty systems depend on, so a vendor change means rewriting those hooks
- — A gift-card app holds a permanent write grant on a cash equivalent; review who inside the vendor can issue cards
On the build path
- — Starting on the REST endpoint the Plus plan page advertises buys a migration: REST has been legacy since October 1, 2024
- — Reason codes and approver identity are the audit trail; skip them and you've built an untraceable cash printer
- — Expiry and balance policy still follow the gift-card laws of every state and province you sell into, app or no app
- — ~$900–$3,000/yr upkeep (Deploi estimate, illustrative)
What Merchants Say
Gift-card apps get flagged for pricing by store orders rather than by cards issued: a store that issues twenty compensation cards a month pays for the tier its total order count lands in.
Ops leads describe compensation cards issued by hand from the admin and reconciled from a spreadsheet, because nobody wanted another app sitting in the refund path.
If You Change Your Mind Later
If you bought and outgrow it
Native gift cards issued by an app stay redeemable after you uninstall it, because the balance lives on Shopify's gift-card object rather than in the vendor's database. What you lose is the scheduling, reminder and analytics history, and any triggers you wired to the vendor's API. Confirm export of issuance history at signup, not at exit.
If you built and want out
Nothing is stranded: the cards are native and the reason codes sit in your own records. If Shopify ships a first-party issuance action or an app fits better later, you switch the trigger and keep every balance. The exit cost rounds to zero, which is part of why a small build is defensible here.
When This Answer Changes
We're watching for:
- ▸ Shopify opening GiftCard API access to custom apps below Plus (custom-app access is Plus-only per the 2021-04 changelog, verified Sep 2026)
- ▸ A REST Admin API sunset date following the October 1, 2024 legacy designation, which would strand any issuance built on the REST endpoint
- ▸ Rise, Gift Card Hero or GV publishing tiers above 2,000 monthly orders, which would make the buy math legible for mid-market stores
Verdict change log:
- 2024-10-01Shopify designated the REST Admin API a legacy API and directed all apps and integrations to the GraphQL Admin API. The Plus plan page still lists GiftCard among its exclusive REST endpoints, but the GraphQL gift-card mutations carry the same Plus gate for custom apps, so any new issuance build belongs on GraphQL.
Common Questions
Is the Shopify GiftCard API only available on Shopify Plus?
The GiftCard API is Plus-only for custom apps. Shopify's changelog states that as of API version 2021-04 the GiftCard GraphQL APIs are available for custom and private apps on Shopify Plus stores (verified Sep 2026). REST access was extended to the same custom apps. Public App Store apps such as Rise or Gift Card Hero issue cards on any plan, which is the buy path below Plus.
Should a new gift-card integration use the REST or GraphQL API?
A new gift-card integration belongs on the GraphQL Admin API. Shopify's REST rate-limits page states that the REST Admin API is a legacy API as of October 1, 2024 (verified Sep 2026). The same page says all apps and integrations should be built with the GraphQL Admin API. The GraphQL reference lists giftCardCreate, giftCardUpdate, giftCardDeactivate and two notification mutations, which cover the full issuance lifecycle.
How much does it cost to build programmatic gift-card issuance on Plus?
A custom issuance app costs $6,000 to $15,000 one-time (Deploi estimate, illustrative), covering the custom app, a Flow action or help-desk trigger and delivery through your ESP. Upkeep runs roughly $900 to $3,000 a year (Deploi estimate, illustrative), mostly the annual API version move. An app such as Gift Card Hero PRO lists $19.99/month (verified Sep 2026), so the build wins on control rather than on price.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- List every event that should issue a card: warranty outcomes, service recovery, loyalty milestones, corporate orders
- Define the policy per event: amount, expiry, reason code, approver, and who can raise the amount
- Build the custom app on giftCardCreate with the gift-card write scope, on the current GraphQL version
- Expose it as a Flow action or an HTTP endpoint your help desk can call, then template the delivery email in your ESP
- Report monthly on cards issued by reason code and redemption rate; that report is the ROI number
If you're going with BUY
- Match your monthly order count to the app's pricing tier before you compare features; the tier is the price
- Confirm the app's API scope covers create, deactivate and notify, not just balance checks
- Verify the app issues native Shopify gift cards so balances survive a later vendor change
- Restrict who inside your team can issue cards through the app and review the log quarterly
- Diary a re-decision at your next Plus renewal, when the GraphQL build is a small line against the subscription
Official Docs & Sources
- GiftCard API available for Shopify Plus custom and private apps (changelog) — shopify.dev
- REST Admin API rate limits (carries the legacy notice) — shopify.dev
- GraphQL Admin API reference — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Store-Credit Operations on Shopify?
Store-credit operations belong on Shopify's native ledger: customize the workflow instead of renting a second wallet.
Should You Build or Buy a Gift Card Program on Shopify?
Gift cards are native on every Shopify plan: the honest first move is spending nothing and merchandising what you already own.
Build or Buy Corporate & Bulk Gifting on Shopify?
Corporate bulk gifting on Shopify favors a build once gifting is a real revenue line; the app category is thin, and draft orders plus the API cover it.
Build or Buy Personalized Video Gift Cards on Shopify?
Personalized and video gift cards on Shopify are a BUY: a niche app layers video messages and scheduled delivery onto native gift card codes.
Should You Build or Buy a Points Program on Shopify?
Buying a points program wins for Shopify brands under roughly $50M in revenue; the liability math and vendor ecosystems beat building.
Ready to issue gift cards from your own rules?
One mutation behind one trigger, built on the GraphQL API your Plus plan already includes. We scope the issuance rules, wire the Flow action and keep the REST endpoint out of it.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.