ImportKit
Why ImportKit
Custom data imports, without the guesswork
Five problems come up again and again when merchants bulk-import metafields. Here's each one, and what we do instead.
From the Shopify community
What merchants are dealing with
You need a high level of technical expertise to operate. By the time you fix the files you may as well have made the changes manually.App Store review · 2025
Wrong or made-up types? Simply not imported. No notice, no error — just… nothing.Shopify Community
The risky part is noticing if unrelated fields or existing metafields changed during the same pass.Shopify Community · 2025
Bulk CSV import of product metafields failed to populate values, even though the CSV had the correct columns.Shopify Community · 2024
Shopify doesn't have a way to bulk import metafields. They tell you to buy an app.Shopify Community
The import created an issue with existing images on the active store. I thought I was doing this in a test store.Shopify Community · 2024
Paraphrased from public discussions. Every quote links to its source.
Fixed by design
Five ways imports go wrong. Five things we changed.
-
Problem 01
Silent failures
A file uploads, something goes missing, and there's no row number and no explanation of what it didn't like.
ImportKit Every row gets a verdict before anything is written — with the row number and a specific message. Typos get a “did you mean?”.
-
Problem 02
Rigid file formats
Exact column names, specific prefixes, strict headers. If your export came from somewhere else, you're renaming columns first.
ImportKit Any column names. Map what you have to what Shopify needs from a dropdown. Extra columns are ignored, not stored.
-
Problem 03
Accidental overwrites
Hard to spot, impossible to undo. The usual advice is “test on 5–10 products first” — good advice that shouldn't be necessary.
ImportKit Only mapped columns are touched, and the check shows the current value before you replace it. Skip is the default.
-
Problem 04
Subscriptions for occasional work
$20–$200 a month is fair if you import constantly. Less so for setting up one store's custom data.
ImportKit One-time packs from $1.99. Credits never expire, and only rows that actually wrote something are charged.
-
Problem 05
Broken references
A definition pointing at a metaobject that doesn't exist yet. A value referencing a product that wasn't uploaded first.
ImportKit References resolve at check time and report per row — no product found matching “merino-crewneck”, with the row.
Side by side
For custom data specifically
Only the features that matter for metafields, metaobjects and articles.
| Feature | ImportKit | Full-store tools | Shopify native |
|---|---|---|---|
| Metafield definitions & values | ✓ | ✓ | — |
| Metaobject definitions & entries | ✓ | ✓ | — |
| Blog articles with metafields | ✓ | ✓ | — |
| Free row-by-row check first | ✓ | Varies | — |
| Any column names | ✓ | Fixed headers | Fixed headers |
| Duplicate detection + conflict modes | ✓ | ✓ | — |
| Cancel and resume mid-import | ✓ | Varies | — |
| Per-row results + failures CSV | ✓ | Varies | — |
| No subscription | ✓ Per row | $20–200/mo | Free |
| Products, orders, customers | Coming soon | ✓ | Products only |
| Scheduled imports | Coming soon | ✓ | — |
“Full-store tools” describes the category, not one product. Check any product's own docs for specifics.
Before you install
Is it the right fit?
Built for this
- Setting up custom data on a new store
- Filling in fields across a catalogue from a sheet
- Copying a data model from dev to production
- Agencies repeating the same setup per client
- Migrating a blog, metafields included
- Occasional imports where a subscription doesn't pay off
On the roadmap
- Products, customers & orders Coming soon
- Customer & order metafields Coming soon
- Scheduled & automatic imports Coming soon
- Export Planned
Worth knowing
Three deliberate trade-offs
There's no undo
ImportKit never deletes anything, which also means it can't reverse itself. That's the trade: an app that can bulk-delete from a spreadsheet is far more dangerous than one that only adds and updates. The free pre-import check carries that weight instead — read every row's verdict before anything is written, ideally on a development store first.
It can't read your customers or orders
Those permissions aren't requested, so that data is unreachable by design rather than by policy. Rows targeting it report the exact missing permission and the rest of the file still imports. Support for those owner types is on the roadmap.
Nothing is silently truncated
Some importers quietly shorten an over-long value to fit Shopify's limits. ImportKit doesn't — a value is written as you gave it or reported as a problem. Storing 255 of your 300 characters without telling you is the worse outcome, because you'd never know to look. Shopify's limits →
See what it would do, before it does it
Install free, upload your CSV, read the verdict on every row. Buy your first credit only once you agree with what it says.
Free to install · Credits from $1.99 · Test charges on development stores