TL;DR: Shopify still has no bulk gift card import. A merchant moving to Shopify with thousands of outstanding gift cards has to recreate each one by hand in the admin, and the bulk-discount apps that look like a shortcut generate discount codes, not reloadable balances. Across 196 merchant threads in PainHunt scoring 10+/15, the gap is specific and unglamorous: import a CSV of existing 16-digit codes with customer, email and remaining balance, and verify what actually landed.
The evidence
PainHunt holds 196 posts on e-commerce operations pain scoring 10 or higher out of 15, average score 11.6/15, average commercial-intent score 7.4/10, and 188 of them are from the last six months. The distribution is lopsided in a way worth stating plainly: 161 of the 196 come from Discourse — the merchant and developer community forums where store owners go when the admin can't do something. AppStore reviews (9), Reddit (9) and a small Medium and WeWorkRemotely tail make up the rest.
Two operational gaps recur inside that corpus, and both are about doing the same thing to many records at once.
Gift cards, one at a time. Merchants describe Shopify's admin as having no bulk import for gift cards — you create them individually. That is fine for issuing a few, and unworkable for a migration. The concrete version that comes up: 2,500-plus existing gift card codes on an old website, each a 16-digit alphanumeric string tied to a customer name, email and a specific remaining value, with no CSV path to bring them into Shopify. Merchants also note that the existing bulk discount apps do not carry a reloadable balance — they generate discount codes, which is a different object.
Bulk catalog changes that fail silently. The developer-side of the corpus describes productVariantsBulkUpdate being scoped to a single product, forcing thousands of separate API calls for multi-product updates. Worse, a single bad variant ID fails the whole batch, there is no built-in retry for just the failed records, and no post-write verification to confirm which changes actually reached the catalog. Validation happens during the mutation instead of before it, so failures are discovered the expensive way.
The through-line is the same: Shopify handles single-record operations well and leaves bulk operations to merchants and app developers to stitch together.
Why now
Store migrations are routine. Merchants move onto and between platforms constantly, and each move turns outstanding gift card balances into a data-portability problem nobody owns. This is not a one-time spike; it is a steady, recurring event across the merchant base.
Gift cards became balances, not coupons. As gift cards moved from one-time discount codes to reloadable, customer-linked balances, the migration problem got harder — you are moving money and identity, not a string.
Bulk operations moved to less technical operators. Store owners with 50–500+ SKUs now run bulk updates themselves, closer to the business and further from the API's failure modes. When a batch fails halfway with no verification tool, they have no clean way to find out what stuck.
The wedge
The broad build is "a better Shopify admin." The threads point somewhere much narrower.
- A gift-card migration tool that respects the object. CSV import of existing 16-digit codes with customer, email and remaining value, importing reloadable balances rather than discount codes. The value is not the upload button; it is correctly preserving a spendable, customer-linked liability during a move.
- Bulk operations with pre-validation and post-write verification. Validate variant IDs and data integrity before submitting, retry only the failed records, and show a diff between what was submitted and what the catalog now holds. The product is answering "did it actually work" without a manual audit.
- A narrow, high-intent buyer. These are merchants mid-migration or mid-bulk-update — a sharp, time-boxed need with a clear cost of getting it wrong, which is a better place to charge than a vague "efficiency" pitch.
Risks and honest caveats
- Shopify can ship this. Native bulk gift card import is a plausible platform feature, and a cross-product bulk variant mutation has been requested for years. The defensible ground is the migration and verification workflow around the API, not a thin wrapper over one endpoint.
- You are handling money and PII. Gift card balances are liabilities and the CSV carries customer emails. The trust and correctness bar is higher than a typical catalog utility, and a mistake is a customer-facing one.
- API limits shape the product. Rate limits and single-product mutation scope are constraints you inherit; the honest version of the pitch is "we make the batch survivable," not "we make it instant."
- The buyer is episodic. A merchant migrates rarely. Price against the event and its risk, or pair the migration tool with the recurring bulk-operations verification so there is a reason to stay.
How to validate this further
Read the underlying merchant threads in the Pain Point Browser, then pressure-test which wedge matches your access to Shopify merchants with the Idea Validator. Related reading: e-commerce overselling and order integrity and Shopify catalog operations automation.