Shopify product exporter

What Shopify product exporter means for a Shopify store

A CSV of public products: titles, prices, compare-at prices, variants, SKUs, and images. What that includes, and what it leaves out.

Key takeaways

  • Read the checks, not only the headline.
  • Confirm anything you might change in the admin, the ad account, or both.
  • If the result cannot see cost, sessions, or repeat rate, it cannot answer those questions.

What you actually get

Shopify product exporter downloads the public catalog of a Shopify store as a CSV: titles, prices, compare-at prices, variants, SKUs, and images, as a shopper could see them.

Sort the sheet by price and you can see the price architecture: the hero price, how often compare-at is used, and how deep the variant list goes. Cost, draft products, and admin inventory are not in the file. The file is built for your download and is not stored.

The CSV is the catalog a shopper can already open, product by product. Unpublished and draft products stay out. Spot-check two prices against the live product page before you trust the sheet in a meeting.

What it leaves out

The CSV is the public catalog: titles, prices, compare-at prices, variants, SKUs, and images. Cost, admin inventory, and draft products stay out. The file is not stored.

The steps for a single pass are in how to run Shopify product exporter.

What a public catalog file contains

The exporter builds a CSV of the public catalog of a Shopify store. You point it at a storefront and you receive a file of what that storefront is willing to show: titles, prices, compare-at prices, variants, SKUs, and images. The file is a snapshot of published catalog data. It reads like a spreadsheet because a spreadsheet is a useful way to scan many products, and the contents are still the public catalog.

You are not downloading the merchant admin. Draft products stay unpublished, so they stay out of the file. Private cost stays in the admin, so it stays out of the file. Inventory quantities that a merchant sees in the back office stay there too. The CSV is the storefront written into columns. If a shopper could not see a product on the store, you should not expect the sheet to reveal it.

The download arrives for you to keep or to discard. The file is not stored for you after the fact. When the download finishes, the copy on your machine is the copy that exists. If you close it without saving, you run the export again later, and later may not match today. A public catalog moves when the merchant edits prices, variants, or photos. Your sheet does not follow those edits on its own.

Titles, prices, compare-at, variants, SKUs, and images

Title is the product name as published. You use it to recognize the item and to search the live store. A title in the sheet should be traceable to a page. If a title looks truncated or odd, you confirm it on the storefront before you quote it in a meeting. The sheet is a convenience. The page is the catalog the shopper sees.

Price is the public price, and compare-at is the public compare-at price when the storefront is showing one. You can read both as a pair the merchant chose to display. The pair is a pricing presentation. A compare-at above the price means the page is showing a comparison price. It does not carry a history of how many people bought at either number, and it does not explain the merchant motive.

Variants break the product into the options the store publishes, such as size or color, with the SKU printed when the store publishes a SKU. Images are the image addresses or files the export includes so you can see the public photography. A SKU in this sheet is a label from the catalog. An image is a picture from the catalog. Availability in a warehouse is a different fact, and it is not a column you should pretend to see.

Cost, drafts, and admin inventory stay out

Cost is missing because cost is not a storefront field. You may know your own cost in your own admin, and you still will not find another merchant cost in their public CSV. Any margin conversation that uses this sheet as if it contained cost is using a blank and calling it a number. Leave the cost column off your mental model of the file, or add an empty column of your own that you fill from your own quotes.

Drafts are missing because a draft is unpublished. A merchant can be building a product that shoppers cannot see. The exporter does not slip behind the publish switch. If your question is about secret upcoming products, this file will disappoint you, and the disappointment is correct. You study what is public. You let private work remain private.

Admin inventory is missing. A variant row can exist in the CSV while you remain ignorant of units on hand. You do not infer a stockout from a missing quantity, and you do not infer abundance from a present SKU. Some themes show an availability word to shoppers, and you can read that on the live page if it is there. The spreadsheet itself is not the inventory ledger.

A snapshot you hold, with no second copy kept

Because the file is not stored, your saving habit is part of using the tool. You choose a folder, you include the store domain and the date in the file name, and you treat that file as the snapshot. A teammate who needs it has to receive it from you. There is no shared bin to reopen next month and trust. Next month you either reuse the file you saved, with its date, or you export again and accept a new snapshot.

Prices can change after you download. The merchant can edit a variant, end a compare-at presentation, or replace an image. Your sheet will keep the old values until you replace the sheet. That is ordinary spreadsheet life, and it is why a later reader needs the download date in the file name. An undated CSV becomes an argument. A dated CSV becomes a source.

Say you export a store in the morning and the founder asks for it in the afternoon. You send the morning file and you name the morning. If they need the afternoon state of one important price, you open the live product page for that check. You do not assume the morning file mutated. The exporter gave you a snapshot and left the storage to you.

Two live prices before the sheet earns trust

The sheet becomes something you are willing to quote only after you spot-check two live prices. You pick two products you might actually mention, you open their current product pages, and you compare the page price with the sheet price. Two checks are the habit. They are a small sample of care, and they are the minimum bar written into the way you use this file. A sheet you have not checked is a download, and a download is allowed to be unverified.

You record the result of each check in words next to the file: matched, or differed. If either differs, you stop treating the sheet as a price authority until you understand the gap. Understanding can be as simple as noting that the live page has moved on since the snapshot. You do not average the two prices into a third number. You do not quietly pick the one that helps your argument.

Images, titles, and SKUs can be scanned more loosely, and prices still get the formal check because prices cause decisions. A wrong title is embarrassing. A wrong price copied into your own strategy is expensive. The exporter has shown you the public catalog in columns. Your two live checks are what stand between those columns and a decision.

Columns taken from the storefront a shopper can load

Every column traces back to the published Shopify storefront. A title is a title the theme can render. A price is a price the product page can show. A compare-at value is a comparison price the storefront is presenting, when it is presenting one. Variants and SKUs are the option structure the store has published. Images are the pictures attached to that public product. Reading the CSV is a faster way to scan those storefront facts, and it remains a scan of storefront facts.

Your own Shopify admin, if the store is yours, still holds a wider set of fields than this file. You can open a product in admin and see cost, inventory, and draft status when you have permission. The exporter did not fail by omitting them. It stayed on the public side. If the store is not yours, the public side is the only side you are invited to read. The CSV is that invitation written into rows.

Say you need a number that would only appear after login. You close the sheet and you open the correct door, which is your admin for your store and no door at all for a store you do not operate. The public file keeps its shape either way: titles, prices, compare-at, variants, SKUs, images, a download you must save yourself, and two live prices to check before the sheet is allowed to speak in a decision.

Shopify questions

Does Shopify product exporter need access to the Shopify admin?

No. Public tools read a URL anyone can open. Calculators use the numbers you type and do not connect to the store.

Can the result be wrong?

Yes. A public tool can read the wrong URL, miss an app that never loads, or match the wrong brand. A calculator repeats a cost you left out. The result is only as good as that input.