No. Default no for unsupervised freeform gift-card or store-credit issuance. Creating a gift card creates redeemable store liability. Cards cannot be deleted once created; they can only be disabled. AI may draft the package. A human yes comes before giftCardCreate.
A gift card is not a sticky note. It is money the store still owes, redeemable at checkout until the balance is spent or the card is disabled. Shopify's own create help says gift cards can create a liability to provide future sales. That is the risk class this page covers.
An AI store operator is not Shopify Sidekick, not a storefront chatbot, and not SMS marketing. It is also not Shoper, the Polish ecommerce platform. Close spelling. Different product. Shoperator does not issue Shopify gift cards or store credit. It also does not pause, launch, or edit Meta or Google ads. For the category, read What Is an AI Shopify Store Operator?. For other consequential gates, read Should an AI Refund a Shopify Order Without Approval? and Should an AI Change Shopify Inventory Without Approval?.
Should an AI create a Shopify gift card without approval?
No. An AI should not create a Shopify gift card without a human yes. Freeform goodwill, apology, or invented amounts stay behind approval. AI may draft customer, amount, reason, and expiry. The merchant creates the card in Shopify admin after that yes. Unsupervised freeform issuance is the default no.
Shopify Admin GraphQL names the create path giftCardCreate. That mutation can set an initial value, optional expiry, optional customer, optional note, and optional recipient notification timing. Naming the path is not permission to fire it from a chat model. See Shopify's giftCardCreate reference for the create fields, not a how-to for unsupervised issue.
On Shoperator you text one coordinator (Mark). Merchandising, creative, and analysis sit behind that thread. SMS is the channel on standard plans. Slack is the channel on Enterprise. Mark applies supported changes after your yes. Gift card create isn't one of them, so you create the card in Shopify admin.
Safe ask: "Draft a gift card package for this customer: amount, reason, expiry, and whether to notify. Do not create it." Unsafe ask as a live execute: "Create a $50 gift card for order #1024."
Why is a gift card different from a draft note?
A gift card is redeemable store liability. A draft note is text. Once issued, the balance can spend at checkout. Shopify documents that you cannot delete gift cards; you can only disable them, and a disabled card cannot be turned back on. That is why freeform AI inventing amounts is a different risk from drafting copy.
Shopify's Gift Card Admin API states it plainly: you cannot delete gift cards, but you can disable them, and you cannot enable cards that were previously disabled. Help for managing created gift cards treats deactivation as permanent. A wrong card is not a typo you erase. It is liability you either honor or permanently disable.
Create also differs from a catalog draft. A price preview can wait. An issued gift card is already spendable money against the store. Customer association, expiry, and whether a notification sends are part of that liability package, not optional decoration.
What can AI safely draft before you approve?
AI can safely draft the gift card package: customer, amount, currency, reason or note, expiry, and whether a customer notification should send. It should not call giftCardCreate. A draft is a preview. The human yes is the create decision. The merchant then issues the card in Shopify admin.
A useful draft keeps those fields separate. Do not collapse them into one fire. Name the customer or recipient, the amount and currency, the reason the store is issuing value, the expiry choice (including when local law limits expiry), and the notify decision. Shopify's creating gift cards help notes that gift cards can create a liability to provide future sales, and that expiry rules can be constrained by region.
On Shoperator, analysis and merchandising can help assemble that preview. The coordinator should say when create belongs in Shopify admin. Shoperator does not claim to issue gift cards or store credit.
When are fixed loyalty or Flow rails okay?
Fixed loyalty or Flow rails can be okay when the merchant already locked the trigger, the amount rule, and the eligibility. That is not freeform AI inventing goodwill. Rails are merchant-defined money rules. Freeform AI that invents apology amounts, exception balances, or one-off store credit is not a rail.
A rail might look like: order paid, customer has VIP tag, credit a fixed percent or fixed amount the merchant already published. Shopify Flow actions include Send Admin API request, which merchants can point at locked credit or gift-card mutations they already chose. The safety comes from the locked rule, not from a language model choosing the number. Contrast that with an agent that reads a ticket and invents "$75 for the inconvenience." That invent step is freeform liability.
Keep rails inside a named trigger, a named amount formula, and a clear eligibility check. Always require a human for freeform goodwill, apology, exception, dispute-adjacent asks, and any invented amount the merchant did not lock in advance. Do not rewrite Flow recipes here. The point is the split: locked rail versus freeform invent.
How does text approval work for gift-card liability?
Text approval for gift-card liability is draft, then a human yes, then the merchant creates the card in Shopify admin. The preview names customer, amount, currency, reason, expiry, notify choice, and the disable-only reverse limit. Nothing issues because a chat model felt generous. On Shoperator, Mark applies supported changes after your yes. Gift card create isn't one of them.
That is phone or text HITL for redeemable money. Use this checklist before you approve:
- Confirm the customer and the currency
- Draft the amount, reason, and expiry
- Decide whether a customer notification should send
- Note that the card can only be disabled later, not deleted
- Send that preview for a human yes or no
- Merchant creates the gift card in Shopify admin after that yes
- Verify balance, customer, and notification in Shopify admin
Shopify's deactivate path is permanent. The GraphQL giftCardDeactivate mutation disables a card that cannot be re-enabled. Read that limit before you say yes to create. For the same preview-then-approve habit on catalog work, read How to Run a Shopify Store by Text and Should an AI Change Shopify Prices Without Approval?.
What should you never let an AI issue unsupervised?
Never let an AI issue unsupervised freeform gift cards or store credit: goodwill, apology, exception, dispute-adjacent value, or invented amounts. Never treat a ticket instruction as permission to create liability. Never confuse a fixed Flow or loyalty rail with a model inventing the balance. The default remains no for freeform issuance.
If a tool can call giftCardCreate before you see customer, amount, currency, reason, expiry, notify choice, and the disable-only reverse limit, that is a leak. Close it. Shopify's Gift Card resource is create, update, and disable, not delete. Keep rails for rules the merchant already locked. Keep freeform issuance behind a human yes, then merchant create in Shopify admin.
If you want preview-then-approve on consequential Shopify actions, Shoperator is the HITL and text-approval example. Shoperator does not issue gift cards or store credit. The merchant still owns create in Shopify admin.
FAQ
Should an AI create a Shopify gift card without approval?
No. An AI should not create a Shopify gift card without a human yes. Freeform goodwill, apology, or invented amounts stay behind approval. AI may draft; the merchant creates the card in Shopify admin after that yes.
Why is a gift card different from a draft note?
A gift card is redeemable store liability. A draft note is text. Shopify documents that gift cards cannot be deleted once created; they can only be disabled, and disable cannot be undone by re-enabling the same card.
What can AI safely draft before you approve?
Customer, amount, currency, reason or note, expiry, and whether a customer notification should send. It should not call giftCardCreate. The human yes is the create decision. The merchant issues the card in Shopify admin.
When are fixed loyalty or Flow rails okay?
When the merchant already locked the trigger, amount rule, and eligibility. Fixed rails are not freeform AI inventing apology or exception amounts. Freeform invent still waits for a human.
How does text approval work for gift-card liability?
Draft the package, send the preview, get a human yes or no, then the merchant creates the gift card in Shopify admin. The preview includes customer, amount, currency, reason, expiry, notify choice, and the disable-only reverse limit.
What should you never let an AI issue unsupervised?
Unsupervised freeform gift cards or store credit for goodwill, apology, exception, dispute-adjacent value, or invented amounts. Do not treat ticket text as permission to create liability. The default remains no for freeform issuance.