ApiMate vs Matrixify

Matrixify (formerly Excelify) is the import and export tool that serious Shopify migrations run on. The flow is file-first: export products, variants, metafields, orders, customers, collections, pages, blog posts or metaobjects as an Excel or CSV workbook, edit it, import it back. The same flow moves a catalog from WooCommerce, Magento, BigCommerce or Lightspeed into Shopify, and merges two Shopify stores.

The export is the part people underrate. One sheet per resource, every column Shopify exposes, including metafields and inventory per location, and the column names match the import format. The usual safe pattern is export, filter in the spreadsheet, delete the rows you are not touching, change the column you are, re-import with "update only", which refuses to create anything.

Jobs can be scheduled and repeated, with FTP and SFTP for supplier feeds. The import ceiling is 20 GB, far past where other apps stop. Rollback is a re-import of a prior export rather than an undo button. The App Store listing, as of the May 2026 check, shows 4.9 with over twelve hundred reviews and the Built for Shopify badge.

ApiMate is a chat that reads and writes your store. The request is a sentence with conditions: "every product from Cedar & Pine that has no weight: set the weight metafield to 0.4 kg, and list the ones where the vendor is empty". ApiMate reads the catalog, resolves the target set and the rule, and shows a preview: one row per product or variant, current value, new value, the reason it is in scope. Nothing writes until you approve.

After approval the job runs, is stored in history with the values it replaced, and can be reverted with one instruction. Reads need no approval and produce a report. Writes always go through the preview.

ApiMate also takes an uploaded sheet as the source of values: "load the dimensions from this sheet by SKU" is a job with a per-row preview and a list of SKUs that did not match. For a small sheet that is convenient. For a large one, Matrixify is faster, and this page says so.

A job that sits right on the line: a supplier sends a sheet with 1,800 SKUs and new cost prices. The store needs the price set to cost times 2.2, rounded to .99, but only where the new price is higher than the current one; where it is lower, keep the current price and flag the row.

In Matrixify: export variants, add the supplier sheet as a second tab, VLOOKUP the cost by SKU, formula the new price, a second formula for the flag, filter to the rows where the new price is higher, delete the rest, keep the Variant SKU and Variant Price columns, import with update only. Check the import log. To revert, re-import the original export.

In ApiMate: upload the sheet and send the sentence below. The preview shows every variant with the cost, the current price, the new price, and the flag on the rows kept at the current price. Approve. Revert by name later.

Both work. The spreadsheet route is faster for someone fluent in VLOOKUP, and its output is a file you can keep. The chat route is faster for someone who is not, and its output is a history entry with the saved values. The condition ("only where higher") is the part that tips it: it is a formula and a filter in the file, and a clause in the sentence.

Matrixify wins whenever the values already exist as a file and the job is to get them into Shopify accurately. Nothing about a sentence improves that job.

ApiMate wins when the change is a rule rather than a set of values, when there is a question to answer first, when the text has to be written per row, or when the preview and the revert should live in the tool rather than in a file you have to keep.

This is the section where the two tools are most different, because the file model has no preview step separate from the file, and no undo separate from a prior export. Both are workable. Both require discipline the tool does not enforce.

Matrixify is priced by tier: Free with feature and volume limits, Basic at $20 a month, Big at $50, Enterprise at $200. The tiers gate file size and features like scheduling and FTP. A migration usually needs one month of a high tier and then a downgrade; a store that runs supplier feeds stays on the tier that fits the feed. You pay for capacity, not usage: a quiet month costs the same as a busy one.

ApiMate has a free plan and paid plans by usage. The free plan runs audits and small jobs on any catalog size; the estimate for each job is shown as a range before it runs, and a job cannot spend past the balance. Paid plans add larger jobs and longer history. A month with no jobs costs nothing on the free plan.

For a store that does one migration and then daily catalog work, the pattern most people land on is Matrixify for the migration month and ApiMate for the daily work. For a store that runs feeds, Matrixify stays. Neither replaces the other's job, so "which is cheaper" is really "which jobs do you have".

Matrixify is built for scale in the file sense: 20 GB imports, tens of thousands of rows, scheduled and resumable. For a catalog that size, the file is the right container, and the checks happen in the spreadsheet before import.

ApiMate has no per-product cap, and a large catalog changes the estimate, not the eligibility. A rule applied to a large catalog produces a long preview; the scope line is the number to read first, and the rows are paginated below. Long jobs report per batch and can be revoked partway, with the written rows revertable as a set. Reads scale the same way: an audit of a large catalog is a longer report.

The split at scale is the same as at small scale: values in a file go through the file tool; rules and questions go through the sentence. What changes is that the cost of getting either wrong is larger, so the preview and the export-before-import matter more.

Matrixify exports and imports metafields as columns, one per definition, typed by the definition. For loading a supplier's weights and dimensions into metafields on thousands of variants, it is the fastest route: map the columns, import.

ApiMate edits metafields from a sentence or a small sheet, with a per-row preview that shows the typed value and the unit, proposes missing definitions before the write, and lists unmatched rows as skipped. Structural edits, deleting an option or renaming variants across products, are where the sentence is safer than the file: a CSV round trip that removes an option column collides on re-import, and ApiMate previews the delete by variant and refuses to leave a product with none.

The split: values from a large sheet, Matrixify. Values by rule, structural edits, or anything preceded by a question, ApiMate.

Most stores past a few thousand products end up with both. Matrixify owns the file jobs: migration, supplier catalog, scheduled feed, backup workbook. ApiMate owns the sentences: the request from the founder, the cleanup after the import, the question that turns into a fix.

The cleanup after the import is the most common handoff. A supplier catalog goes in through Matrixify with the supplier's structure, and the next day the sentences start: remove the "Ships From" option, rename the variants, strip the supplier text from descriptions, write alt text. Those are per-product structural and text jobs, and they are the ones a file round trip does worst.

The test is not "which is better". It is "which of my jobs are files and which are sentences". Take the last five bulk changes and sort them.

Matrixify has no rule engine. The file carries values, and the rule lives in your spreadsheet. It has no per-row preview separate from the file and no undo separate from a prior export. Structural edits through a CSV round trip are the place merchants get hurt.

ApiMate is not a file tool. It refuses migrations and large supplier imports and points at Matrixify. It does not schedule feeds. Small sheets are fine; large ones are the wrong proportion.

Neither creates barcodes, brand names or product photos. Those come from the supplier.