Build a whole custom data model from a spreadsheet — definitions, values, metaobject entries and blog posts. ImportKit checks every row against your store first, writes them one at a time, and charges only for the rows that land.
Free to install · Credits from $1.99 · No subscription · Nothing is written until you approve the preview
Hero shot — the pre-import check
Step 3 of the wizard: verdict badges (“to create”, “to update”, “to skip”) with the row-by-row report underneath. This is the most persuasive screen in the app; lead with it.
ImportKit
assets/screenshots/hero-pre-import-check.png
What you can import
Shopify handles products and customers. ImportKit handles the custom data layer wrapped around them — the part you otherwise build by hand, one definition and one product at a time.
| Data type | One row is | What people use it for |
|---|---|---|
| Metafield definitions | one field definition | Standing up 30 product fields without 30 trips through the admin. Types, validations, pinning, storefront access — 13 owner types. |
| Metafield values | one value on one resource | Filling those fields in across a catalogue from a supplier sheet. Reference products by handle, variants by SKU, anything by ID. |
| Metaobject definitions | one content type, with all its fields | Creating an Author, Size chart, Store location or FAQ structure — every field packed into a single cell. |
| Metaobject entries | one entry | Loading 200 locations or 50 ingredients. Columns come from your own definition, so nothing is generic. |
| Blog articles | one article | Moving a blog off WordPress, with HTML bodies, tags, handles, dates and article metafields in the same row. |
Products, collections, customers, orders and themes. ImportKit is narrow on purpose — it never asks for customer or order permissions, so it cannot read that data at all. Use Shopify's own product import for the catalogue, then ImportKit for everything wrapped around it.
The question everyone asks
Nothing you didn't ask for. ImportKit recognises what already exists in your store, tells you before it runs, and does what you chose.
| Data type | Matched on |
|---|---|
| Metafield definitions | owner type + namespace + key |
| Metafield values | owner type + owner + namespace + key |
| Metaobject definitions | type |
| Metaobject entries | handle |
| Blog articles | nothing — every row is new |
Duplicate rows inside one file are caught too — the second is flagged as “duplicate of row 12” rather than colliding mid-import.
| Mode | Result | Cost |
|---|---|---|
| Skip Default | Left completely unchanged | Free |
| Update | Patched with this row's values | 1 credit |
| Fail | Reported as an error | Free |
Re-running an already-imported file on the default setting costs nothing and changes nothing. How conflicts work →
Set a column to Ignore and its contents never reach Shopify and are never stored. Fields absent from your file are left exactly as they are, so a partial spreadsheet makes a partial update — not a wipe. Blank cells are skipped rather than written, so gaps in an export can't clear existing values.
How it works
Nothing reaches your store until you press Start Import — and by then you already know what every row will do, and what it costs.
Built for the boring failures
Half a file imported. A handle that doesn't exist. Credits burned on rows that never landed. Most of ImportKit is the handling for those cases.
Rows that error, skip or conflict are refunded automatically. Credits are reserved just before each write and released the moment the outcome is known, so your balance never runs ahead of your store.
Cancel, run out of credits, or hit a server restart — the job stops cleanly and Retry picks up from the first unprocessed row. No duplicates, no paying twice for the same work.
Any column names, any order, extra columns welcome. Export from another store, a PIM, or a client's spreadsheet and map what you got to what you need — nothing has to be renamed first.
Every job keeps a per-row record: the Shopify ID for each success, the reason for each failure. Download just the problem rows, fix them in your spreadsheet, re-import that file alone.
Not “invalid input”. Instead: ownerType “PRODUCTS_VARIANT” is not valid — did you mean “PRODUCTVARIANT”?, with the row number attached and the credit refunded.
Those permissions aren't requested, so that data is unreadable by design. Rows targeting it are reported with the exact missing permission instead of failing quietly — and the rest of the file still imports.
Before you install
The right tool for the right job. See if ImportKit fits before you install.
For undo: the free pre-import check is the answer — read every row’s verdict before anything is written. Nothing is ever deleted.
The full list of what it deliberately won’t do, with the reasoning →
After the run
A finished job tells you how many rows succeeded, failed, were skipped, and exactly how many credits it cost. Open it and every row is there with its own verdict.
Job detail — per-row results
A finished job in Jobs → detail: the stat tiles (total, succeeded, failed, skipped, credits used) and a results table showing a success with its Shopify ID next to a failure with its message.
assets/screenshots/job-results.png
The problem we solve
These are the complaints that come up year after year in the Shopify community. Each one is something we deliberately built around.
The problem
A file uploads, something goes missing, and nothing tells you which row or what it objected to.
ImportKit Every row gets a verdict in the free check — with the row number and a message specific enough to act on.
The problem
Tools built for developers expect developer-shaped files: exact column names, strict headers, specific prefixes.
ImportKit Your column names don’t matter. Upload the file you already have and map it in a dropdown.
The problem
An unexpected overwrite is hard to spot and impossible to undo. The usual advice is to test on a handful of products first.
ImportKit Only mapped columns are touched, and the check shows the current value before you replace it.
The problem
Subscription pricing makes sense for constant use. Less so for setting up one store’s custom data.
ImportKit One-time packs from $1.99. Credits never expire, and only rows that wrote something are charged.
Pricing
No monthly fee, nothing to cancel, no expiry. One credit imports one row — and rows that don't import come back to your balance.
A typical custom data setup runs about 50 credits. Filling two fields across 400 products is 800. Full pricing, with worked examples →
FAQ
Not much. Download the template for the type you want and it arrives with a correct header row plus worked example rows, each showing a different case. Change the values, keep the headers, import it. The quick start does a real import in about five minutes.
No, and that's deliberate. ImportKit never deletes anything, which also means it can't reverse itself — undoing an import is manual work in the Shopify admin. An app that can bulk-delete from a spreadsheet is a far more dangerous thing to install. The free pre-import check is the trade we made instead: read every row's verdict before anything is written.
The check reports “N of M rows will be written”, and N is the credit cost exactly. It's free and re-runnable after every edit to your file, so you can get the number to where you want it before spending anything.
Up to 50 GB and 1,000,000 rows per import, streamed rather than loaded into memory. Need more? Ask us — higher limits and additional files can be arranged. The preview reads the whole file at once, so it caps at 50,000 rows; above that the import still works and conflict handling still applies per row, you just don't get the preview. All limits →
Rows go to Shopify one at a time, so thousands of rows take minutes rather than seconds. That's deliberate — Shopify's API throttles hard enough that parallel writes end up slower, and serial keeps every row's outcome unambiguous. The job runs on our servers, so you can close the tab.
Upload CSVs. Excel, Google Sheets and Numbers all export one in a couple of clicks — here's the route through each, including the encoding setting that matters.
The uploaded file is never written to disk — it's read as a stream. The values from the columns you mapped are kept with the job so failures can be reviewed and imports resumed, and ignored columns are never stored at all. ImportKit holds no customer personal data and can't read your customers or orders. Privacy policy →
Neither. Packs are one-time purchases through Shopify, and credits sit on your store's balance until you use them — including across an uninstall and reinstall.
Install it, upload your CSV, and read the verdict on every row. Buy your first credit only once you agree with what it says.
Free to install · Test charges on development stores, so a full rehearsal costs nothing