Guide
Shopify Supplier Sync: How to Automate a Product Feed
Last updated: November 18, 2026
A Shopify supplier sync brings product data from your supplier's feed into your store. Without one, your team has to download a CSV, fix its columns in Excel and upload it to Shopify after every feed change.
Skip a week and prices go stale. A renamed supplier column can also break the import while the old stock remains visible to customers.
If a wholesaler, brand or dropship partner gives you a CSV, Excel or XML feed, Pro and Scale let you schedule it without downloading a new file each day. Changed files can update prices and stock from the source. New products can be handled by a separate scheduled import.
This guide covers:
- What a supplier sync actually needs to do
- The four common ways merchants handle it and where each breaks
- The criteria for a good sync setup
- A step-by-step walkthrough of setting up automated supplier sync with Simple CSV on Pro or Scale, including matching, scheduling and monitoring
- Real-world scenarios with example schedules
- The tricky cases - authentication, discontinued products, file formats and limits - handled honestly
If your supplier's feed is a one-time import rather than an ongoing sync, the guide to importing products with CSV covers that scenario. This guide is for a feed that changes and needs to run again.
What "Sync" Actually Needs to Do
Before picking a tool, it helps to be clear about the four jobs a supplier sync handles. They're not the same job and they don't all need to run at the same time:
- New products appear in the feed. The supplier added 30 SKUs last night. You want them in your store with images, descriptions and prices.
- Existing prices change. A brand raised wholesale prices by 8% across the board. Every product you sell from them needs the new price reflected.
- Stock levels change. The supplier sold a batch to another retailer and is down to two units of a popular SKU. Your store should show "2 in stock" before someone orders ten.
- Products disappear from the feed. A SKU is discontinued. The supplier silently drops it. You probably don't want to keep selling it, but you also don't want it auto-deleted from your catalog without a check.
The first three jobs benefit from automation because they are frequent and predictable. The fourth is an architectural decision that needs a deliberate answer. The limitations section returns to it.
The Four Ways Merchants Handle Supplier Sync
There's no single right answer. The right choice depends on the supplier's feed format, the size of your catalog and how much engineering you want to own.
Manual download -> upload. Open the supplier's portal, download the CSV, save it, open Shopify, click Import. Works for the first few weeks, then becomes the chore that doesn't get done. One missed update can cost more in oversells than the entire automation would have cost.
Shopify's built-in CSV importer. It is free but cannot fetch from a URL, run on a schedule or map a supplier's columns to Shopify's columns. For a one-off catalog import it is fine. See the guide to importing products with CSV. For ongoing sync, it is the wrong tool.
Custom Shopify development. A developer wires the supplier's feed directly into Shopify's API. This can work well when the feed format is stable, but every supplier change creates more development work. It makes sense for very large stores with unusual requirements and costs too much for most daily price updates.
Full ERP, PIM or dropship platform. These platforms cover much more than a CSV import and often charge per SKU or order on top of a base fee. Many merchants need a small part of the feature set but pay for all of it.
A focused product-feed sync tool. Right answer when the feed is CSV, XLS, XLSX or XML, sits at a public URL and you want a scheduled setup without an enterprise stack. This is where Simple CSV fits on Pro or Scale.
If your supplier's feed is JSON, this article still covers the workflow, but you'll need a different tool for the actual sync. Inventory & Price Sync handles JSON feeds.
What You Need from a Supplier Sync Setup
Use these eight criteria to evaluate any supplier sync setup, including the one you'll build below:
- URL-based imports - no manual download step
- Scheduled execution at a known time
- Column mapping, so the supplier's headers don't have to match Shopify's
- Match by SKU, first barcode or product ID when Handle is not suitable
- Choice between create-only or update-only on a per-schedule basis
- Pre-flight preview before a run touches the live store
- Logs with row-level detail
- Backup integration before destructive runs
A URL import without scheduling still needs a manual run. For CSV or Excel files with a header row, a saved mapping follows non-blank header names without | or * when the supplier adds or reorders columns, or removes unmapped columns. Removing or renaming a mapped column holds the action. Files without a header row still rely on position. Row-level logs show exactly which SKU failed.
Setting Up Supplier Sync with Simple CSV
The walkthrough uses a wholesale supplier that publishes a product feed at an HTTPS URL and updates it once each night. The same setup works with CSV, XLS, XLSX and XML.
Step 1 - Get your supplier's feed URL
Ask the supplier for a feed URL. Most B2B portals offer one - sometimes called a "stock feed," "product feed," or "data export URL." It should be publicly accessible over HTTPS and return a CSV, XLS, XLSX or XML file when you open it in a browser.
If your team maintains the feed in a spreadsheet, you can also publish a Google Sheet as a CSV URL and use that as the scheduled source on Pro or Scale.
- HTTPS only. Simple CSV doesn't fetch from FTP or SFTP. If your supplier only offers FTP, ask whether they have an HTTPS option or set up a small mirror script that pulls the FTP file every morning and serves it from your own HTTPS endpoint. For larger setups this is a one-line cron job to a static file host.
- Authentication. If the URL requires a username and password, use basic auth in the URL itself:
https://username:password@example.com/feed.csv. API key headers, OAuth and signed URLs aren't supported - for those, the same mirror-script approach works. - Test the URL in a browser in private mode, so your saved credentials don't disguise a problem. If the file downloads cleanly there, Simple CSV can fetch it.
Save the URL - you'll paste it into the import step.
After you submit the URL, the validation screen says We are downloading your file. It shows a percentage when the supplier reports the total size, or the downloaded size so far when it does not. Once the download is complete, the bar disappears and the screen says We are validating your file in the background.
The steps below describe the normal flow when Quick setup does not appear or you choose Set it up myself.
Step 2 - Choose your import strategy

When you start a new import in Simple CSV, first choose to create new products or update existing ones.
- Inventory and price refresh. Update existing products only. This processes fewer fields and avoids re-creating products you've manually customized.
- Adding new products from the feed. Create new products. On Pro or Scale, run this on a separate schedule from the price and stock update.
The second choice on this screen - whether one row equals one product or whether the same product spans multiple rows - depends on whether the supplier's feed contains variants. Most B2B feeds use one row per SKU.
On Pro and Scale, a saved feed can include more than one action against the same URL. When you add Import new products, Simple CSV reuses another import mapping if one exists. Update inventory and Custom update reuse each other's mapping. If the feed has no matching action yet, Simple CSV fills in a fresh mapping from the file. Each action keeps its own mapping for later runs, so you do not have to map the columns each time. For CSV or Excel files with a header row, saved mappings follow non-blank header names without | or * when columns move.
Step 3 - Map your columns
The mapping screen shows Loading mapping fields… until the field list is ready. Save and continue stays in a loading state until then. Wait before continuing, especially with hundreds of columns or large XML feeds.
The example below uses a CSV source. XML record selection is explained after the header rules.

Suppliers rarely use Shopify's column names. A feed may contain headers such as OFFERID, NAME, PRICE_OLD and WEIGHT, sometimes in another language.
Simple CSV reads the supplier's headers and proposes a mapping. You confirm or change each field. Up to five examples per column show the actual data in the feed (scroll horizontally to see them all) so you can spot a wrong guess immediately - for instance a column labeled OFFERID that actually contains a 13-digit barcode rather than a Shopify product ID.
For CSV or Excel files with a header row, header names are case-sensitive, with spaces at the start or end ignored. Duplicate headers are numbered in order, so two Price columns become Price and Price#2. A file set to First row is not a header still uses column positions. Blank headers and headers containing | or * are positional too. If a mapped header is removed or renamed on a later run, Simple CSV holds the whole action before changing Shopify products. Safe name-based mappings continue when columns are added or reordered, or unmapped columns are removed.
Existing scheduled feeds move to header-based mappings over their next runs. Simple CSV first records the current columns, then upgrades fields that stayed in place. The import log says which fields were upgraded. If a mapped column moved during that check, its mapping stays positional and the log warns you to review it.
XML files use the same field-mapping screen. Field positions stay stable between downloads and new fields are added at the end. An optional field appearing in a different record does not move other fields. A mapped field disappearing from the whole file holds the action. When the XML records section offers more than one option, choose the part of the feed that contains the products you want to import, then select Use this record element. Changing it refreshes the preview and clears the current mapping. Our XML import guide explains the one-time import workflow and record-element step.
On every plan, AI Rewrite offers optional Brand voice and Protected terms settings for your whole store. Brand voice guides description prose, with the chosen tone taking priority. Protected terms stay exactly as written, with case-sensitive, whole-word matching. These settings do not turn rewriting on.
Keep original text cannot be combined with a target language. Choose another tone to translate. Same as source with Keep original text skips rewriting.
If AI Rewrite rewrites the first product’s title, description or product type, Preview offers Show original text. It switches all three fields to the source text for comparison. The import still publishes rewritten copy. Choose Show rewritten text to switch back. The button is hidden when none of these fields were rewritten.
When an Import or Update uses AI Rewrite, its status page lists the fields being rewritten, target language and tone. It confirms brand voice and protected terms when set, without showing your answers or terms. Reload the page after the run finishes to see “were rewritten” instead of “are being rewritten”. When rewriting starts, the activity log adds one Info line with the same summary. Individual product lines do not list rewritten fields. With AI Rewrite off, neither the section nor the summary line appears.
With AI Rewrite on, Full file dry run rewrites only the first 5 data rows. Remaining rows keep their source text. The whole file is still checked without changing Shopify. The status section and log summary explain this limit.
For a typical supplier feed, the fields that matter are:
- The match key, usually SKU
- Price and Compare-at price if the feed has both regular and sale prices
- Inventory quantity
- Title, description and images - usually only on the create side, since you may not want supplier title changes overwriting your edited Shopify titles
On update runs, map only the fields you actually want changed. If you've spent time rewriting the supplier's terrible default titles, don't map the title column on the daily update. The supplier's "Premium Quality 100% Pure Set 3-Pack" doesn't need to overwrite your "Outdoor Wood Care Set" every morning.
If a mapped column disappears or an older positional mapping shifts, Simple CSV holds the feed action before changing Shopify. Holds and their email are on every plan. Scheduling requires Pro or Scale. Files set to First row is not a header are not checked.
Read why an action is held and how to review its mapping.
Step 4 - Choose products
On Pro and Scale, including trials, use Choose products after Mapping to import or update only products matching conditions. For example, import only Philips from a 10,000-product supplier feed. Free continues with the whole file.
On Pro and Scale, conditions are saved with the mapping and reused on scheduled runs. Open Choose products with the filter icon before the play icon in the automation’s Actions row to edit them. A missing condition column stops the run. While conditions are set, out-of-feed cleanup is disabled.
Learn how to choose products with conditions.
Step 5 - Choose the location this import updates
Whenever a manual or scheduled import is processed, it updates inventory at one Shopify location that you pick during setup. Point a supplier's feed at a dedicated location such as Supplier stock, and Simple CSV only changes quantities there. Whatever you count and adjust by hand at Own stock stays untouched.
Each automation targets its own location. A wholesale feed can update Supplier stock every morning while a separate dropship feed updates Dropship warehouse on its own schedule, with neither run overwriting the other's numbers.
Step 6 - Choose how products are matched

For an update run, the most important decision is how Simple CSV figures out which row in the supplier's feed corresponds to which product in your store.
- SKU - the default and the right answer for most supplier feeds. Stable across renames and URL changes. Use this unless you have a specific reason not to.
- Barcode - useful when the supplier provides the same UPC, EAN or GTIN as the first barcode on each Shopify variant.
- Product ID - Shopify's internal numeric ID. It is rare in supplier feeds and almost never the right choice.
- Handle (URL) - the product's URL slug. Fragile because handles change when titles change. Avoid for supplier sync.
Simple CSV compares SKU, handle and the first barcode exactly after ignoring letter case and surrounding spaces. A supplier value of TEE-S-BLU cannot update TEE-S-BLU-CP. If a variant has several barcodes, Simple CSV checks only the first one. A secondary barcode in the feed does not match, so the row is skipped as not found. If an exact SKU or first barcode exists on more than one product, Simple CSV skips the row and records the number of matches in the import log instead of choosing a product.
If the feed itself repeats a SKU or first barcode, Simple CSV processes every row in file order. The last successful row for that identifier determines the final value. If an update matches by handle, only the first row for that handle is processed. Later rows with the same handle have no effect and do not add a warning or skipped row to the import log. This does not affect new-product imports that group variant rows under a shared handle.
If you previously created products with the retired supplier setup, use SKU when you move them to a normal XML update. The XML import creates new handles and does not reuse the old supplier handles, so matching by handle will not find those products.
Match by SKU or Shopify ID when you can. Use barcode matching only when the supplier value is the first barcode on each Shopify variant.
Step 7 - Translate or restyle text
After Choose products and before Preview, AI Rewrite appears on every plan for Import and Update. Choose a language, tone and mapped text fields for unique product copy in your brand’s voice. Select Skip this step to continue without rewriting. Only the first product is rewritten for the preview. Read how AI Rewrite works and check the result for errors.
Step 8 - Review the summary before running
Before any run touches your live store Simple CSV shows a pre-flight summary. A full preview of the data being changed is shown for imports of new products. For updates the summary tells you the row count, the source file or URL and the match key.
When you update existing products with Handle mapped, Summary shows “Create URL redirects when handles change” on every plan. When checked, Shopify creates the redirect from the old URL to the new one.
Read how to change product handles and set URL redirects.
On Summary, “Full file dry run” checks the whole file without changing Shopify. On Pro and Scale, “Run first 100 rows” makes real changes in Shopify. This limited run processes the first 100 data rows and includes complete products at the cutoff. It is separate from Free’s file limit.
If you choose “Import without checking SKU or barcode”, a later full import creates the products from the limited run again. Check your setting for existing products before continuing.
Read how to use a limited live run and return to the full file.
On Scale, run change history shows confirmed changes an import made in Shopify, with values before and after. It covers one-off imports, scheduled URL runs and AI Rewrite changes. History is kept for 90 days. It does not undo changes.
Read how to browse run change history.
On a new-product import, the Status row shows the status that Simple CSV will write. You can override the mapped or default status for all new products with Active, Draft or Unlisted. Unlisted products can be opened and bought through a direct link, but they stay out of Shopify-powered search, collections and recommendations. Existing products are never changed by this setting. If you save the import as a Pro or Scale automation, the saved override is used whenever the scheduled file is processed.
Read this screen. The number of rows tells you whether the feed is the size you expected - a feed that's suddenly 12 rows when it's normally 4,000 is a sign the supplier's export broke. The match key reminds you what's being used to find products.
The "Create backup now" link is worth using before any large update. Image changes in particular can't be reversed cleanly and a backup taken sixty seconds before a sync gives you a clean rollback path. Simple CSV integrates with the free backup app for this.
On Free, choose Start import or Start update for a one-time URL run. If the file is over the 100-row limit, the action is Try import (100 rows) or Start limited update.
On Pro or Scale, choose Save & Run now to save the reusable feed and mapping, then queue one run. It opens the run status page without asking for a schedule name or time. If this is an existing automation, its schedule times and Active or Paused state stay unchanged.
Choose Save & Schedule when you want to create or edit a recurring schedule.
Step 9 - Schedule the recurring sync

On Pro and Scale, Save & Schedule opens the schedule form. Enter a name and choose when the automation should run. The screenshot shows an existing automation being edited. Inventory location appears when editing an automation with mapped inventory. Simple CSV fetches the source at the scheduled time.
On Pro and Scale, the schedule form includes these settings:
- Name - anything that helps you recognize this run later, such as
Supplier A - daily stockorBrand X - weekly price - Day of week - every day or a specific weekday
- Import time - choose one time for new products in your store’s timezone. Updates keep their time checkboxes within your plan’s limit
- Inventory location - when editing an automation with mapped inventory, choose the location for future runs
- Status - the existing automation’s Active or Paused state
Choose how often each automation runs. On Pro and Scale, new-product imports run at most once per day. Updates can run every 6 hours on Pro or hourly on Scale. Pro supports up to 3 automations and Scale supports up to 7.
After a fully successful scheduled run, Simple CSV remembers which file that automation processed. If the next scheduled run has the same file and settings, it completes without touching Shopify. Import and update automations for the same feed each remember their own last successful file.
- Run before your shop's peak hours. If most of your traffic is 9 AM onward, schedule the sync for 4 AM. Fresh data is live before customers arrive and the sync doesn't compete with checkout traffic for API capacity.
- Run after the supplier's update. If the supplier publishes their daily feed at 2 AM their time, schedule yours for at least an hour after, accounting for timezone differences.
- Run separate schedules for create and update. Each schedule has one strategy, either create new products or update existing ones. For most suppliers this means two schedules. One processes new products and the other processes prices and stock when the file changes. Two narrower schedules are easier to debug than one combined run.
Change the inventory location
On Pro and Scale, open Simple CSV from Shopify Admin and edit the existing automation’s schedule. If it maps inventory, Inventory location lists your active Shopify locations with the saved location selected. Choose another location and select Update.
Each automation still updates one location. The new choice applies to future runs only. It does not transfer or clear stock at the previous location. Runs already queued or running keep their original location.
After you change the location, the next run processes the feed again even if the file itself is unchanged.
Automations without mapped inventory have no location selector. If Simple CSV cannot load your locations, it shows a warning and keeps the saved location.
Step 10 - Monitor
Once a Pro or Scale schedule is live, you check on it through two screens.
While Shopify runs a bulk operation, the status says Shopify is processing your products. This may take a few minutes… There is no increasing counter. With AI Rewrite, you also see Preparing your product text… and a rows rewritten count. Large files can take several hours. Once the import starts, you can close the page and check progress later. If a product cannot be rewritten safely after one automatic retry, it is not imported or updated. The import log names the row. The original text is never published in its place. Other products continue.
On Pro and Scale, changing the AI Rewrite language or tone, store-wide brand voice or protected terms makes the next scheduled run process the file again, even when the file itself is unchanged. Previously rewritten text can be reused when the text and rewrite settings still match.
The Recent imports list shows every manual run and every scheduled Pro or Scale run with its current status, including Completed, Running, Scheduled and Not completed. An unchanged scheduled run appears as Completed in this list.
The columns are File, Started, Status and View. Started shows when each import or update began, using your store's regional settings and timezone. If no start time was recorded, for example for a queued run, it shows "—".

Open any run for the row-level detail.

The summary at the top shows the number of rows processed, variants updated, failures and skipped variants. Below that, every row gets a Success, Warning or Error status with an explanation.
Open an unchanged scheduled run to see No changes in the file with every counter at zero. Its log says This file is the same as the one we last processed. We skipped this run because there is nothing new to import or update.
Select Run now on the automation when you need to process the same file again. The unchanged-file check never skips Run now, one-off manual imports or test runs that do not change Shopify. A mapping hold still blocks a feed action. After a failed or partial run, or one stopped because it reached a limit, the next scheduled run processes the file normally once any mapping hold is cleared.
Scale cleanup adds a success message only when it changes an out-of-feed product. If its inventory at this import's location is already 0, its Continue selling when out of stock setting is already off and its product status does not need to change, a repeat run has no cleanup message for that product. There is no separate message to confirm that cleanup ran with nothing to change. Warnings, errors, products that no longer exist in Shopify and explanations for products left active because they have stock at another location still appear.
When an exact SKU or first barcode belongs to several products, the log names the identifier, reports how many products matched and confirms that the row was skipped to avoid updating the wrong product.
Download the import log to review run messages. On Scale, run change history shows values before and after actual changes. That history is kept for 90 days and cannot be exported as CSV.
A mapping hold sends one email per hold. Open the feed and select Review mapping and resume. Other run failures are shown in-app. Check Recent imports weekly, especially in the first month. Read how to review a held action.
Real-World Scenarios
Three common supplier sync setups and how to configure each.
Daily inventory sync from a wholesale supplier
You sell ~3,000 SKUs from a wholesaler. They publish a daily stock feed at 2 AM. You want stock levels in your store to reflect their warehouse before your customers wake up.
- Strategy: Update existing only
- Match: SKU
- Mapped fields: SKU + inventory quantity and nothing else
- Pro or Scale schedule: Every day at 4 AM local time
Minimal mapping matters when you have already edited titles, descriptions and images in Shopify. The supplier's feed may contain all of them, but the daily run should not overwrite your work. Map only the SKU and stock fields for a predictable daily update.
Weekly price update from a brand
You sell a brand's products at retail. They update wholesale prices weekly, on Sundays. You want your retail prices and compare-at prices to reflect the new wholesale costs every Monday morning.
- Strategy: Update existing only
- Match: SKU
- Mapped fields: SKU, price and compare-at price
- Pro or Scale schedule: Every Monday at 6 AM
The compare-at price column handles sale rotations. When the brand puts a product on sale, the feed populates compare-at. When the sale ends, compare-at goes blank and your "was/now" UI clears automatically.
New product additions from a dropship supplier
A dropship supplier adds new products throughout the week. You want them in your store within 24 hours with images descriptions and starting prices. You also want to review them quickly before they go live to customers.
- Strategy: Create new products
- Existing products: Check existing products by SKU (skips variants whose SKUs already exist)
- Mapped fields: SKU, title, description, images, price, inventory quantity and vendor
- Pro or Scale schedule: Every day at 3 AM
- Set new products to Draft status then promote to Active after a quick review
On “How should we handle existing products?”, choose “Import without checking SKU or barcode”, “Check existing products by SKU” or “Check existing products by barcode”. The checking options skip individual variants whose identifiers already exist. For this daily feed, choose SKU checking when every variant has a reliable SKU.
When grouped rows contain an existing variant, Simple CSV adds the new variants to that product. If none exist, it creates a new product. Import never updates existing products or variants. Read how to group rows when adding variants.
Pair this Pro or Scale create schedule with a separate update schedule for the same supplier. One processes new products. The other processes prices and stock on existing products when the file changes, which makes a failed run easier to trace.
Advanced Pricing and Inventory Rules (Pro and Scale plans)
The Pro and Scale plans can adjust supplier stock and prices without editing the source feed. The rules below run when the scheduled file is processed. An unchanged file is skipped after a fully successful scheduled run.
Advanced inventory
The Advanced inventory page is available on Pro and Scale. Free can import and update inventory manually, but cannot apply these rules.
Map SKU to use the SKU fields. To write stock, map inventory or set a default inventory quantity and choose a Shopify location. The result replaces Available stock at that location.
Add text before or after the SKU
A prefix goes before each mapped SKU. For example, SUP- changes TEE-S-BLU to SUP-TEE-S-BLU. A suffix goes after it: -EU gives TEE-S-BLU-EU. You can use both together.
These settings work for imports and updates. Surrounding spaces are removed from the source SKU and the saved prefix or suffix. An empty SKU stays empty.

Low stock -> set to 0
For updates only, enter a cutoff in Set stock to 0 if it is below. A numeric quantity strictly below that number becomes 0. Quantities at or above it stay unchanged.
| Source quantity | Result with cutoff 5 |
|---|---|
| 4 | 0 |
| 5 | 5 |
| 6 | 6 |
The cutoff does not subtract 5 from every quantity. Leave it blank to turn it off. New-product imports ignore it, even if the form shows the field.
Set out of stock by value
Choose a source column under Field and enter the value that means out of stock under Value. For example, a hypothetical status column could use inactive.
The whole value must match, ignoring letter case. INACTIVE matches inactive, but temporarily inactive does not. Spaces in the source cell count: inactive does not match inactive. Spaces around the value you enter are removed when saved.
With a column selected, an empty Value matches an empty source cell. Leave Field at Select field to turn the rule off.
This rule works for imports and updates when the row has an inventory quantity from the file or a default. A matching row gets 0, unless fixed stock is set.
Same stock for all products
For updates, set a fixed stock quantity to replace the quantity for every processed row. Fixed stock 10 turns both source 2 and source 100 into 10. It also overrides the cutoff and out-of-stock-by-value rule. Fixed 0 sets stock to 0. Leave it blank to use the other rules.
Fixed stock is a replacement, not a maximum stock cap. Use it for updates: the new-product import form shows this field, but does not save it.
Saved rules and scheduled updates
A Pro or Scale scheduled update reuses its saved Advanced inventory settings when it processes the file. The current plan must still include Advanced inventory when the run starts. The cutoff remains update-only on scheduled runs.
After a fully successful scheduled run, an unchanged file with unchanged settings is skipped. Read the unchanged-file limits before relying on scheduled stock updates.
Advanced pricing
The Advanced pricing step changes product selling prices on Pro and Scale, including trials. Paid legacy plans also include these rules. Free can import and update prices manually within its row limit, without these rules. These settings change product prices, not your Simple CSV subscription.
Map Price to use the controls. If Price is not mapped, the form asks you to continue. There is no currency conversion setting here. Prepare prices in your Shopify store currency. A fixed change of 2 adds two units of that currency.
Fixed and percentage changes
Use one row for all prices. Fixed change adds or subtracts an amount. With no other rules, 10 plus 2 becomes 12.00, while -3 makes it 7.00. Percentage change applies next: 25 makes 10 become 12.50, and -20 makes it 8.00.
When both are set, a source price of 10, fixed change 2 and percentage change 30 gives (10 + 2) × 1.30 = 15.60. This is a markup, not a profit-margin calculation. Blank changes and 0 add nothing.
Different changes by price range
Select Add another price range to show Price up to. The app chooses one row using the selling price before any changes, rounded to two decimals. It checks limits from lowest to highest, regardless of row order. Each limit includes that exact price. Rows do not add together.
| Price up to | Fixed change | Percentage change | Example before → after |
|---|---|---|---|
10 | 2 | 10 | 10 → 13.20 |
20 | 0 | 20 | 15 → 18.00 |
| Blank | 0 | 5 | 30 → 31.50 |
These examples use No rounding and Keep as is. Leave the last limit blank to cover higher prices. Without that row, higher prices get no fixed or percentage change, but rounding and price endings still apply. Use each limit once and only one blank limit. Each range needs a fixed or percentage value. Enter 0 for an explicit no-change range. Use Remove to delete an extra row.
Round price, then set the price ending
The calculation rounds the source price, the fixed-change result and the percentage result to two decimal places. For example, 10.01 plus 5% becomes 10.51. The final price cannot be below 0.
Round price defaults to No rounding, which keeps two-decimal precision. Round up to the next whole number changes 23.75 to 24.00 and keeps 24.00 unchanged.
The options labeled Round up to nearest 1 through 9 choose the next whole-number part ending in that digit and keep the decimals. For example, nearest 5 changes 23.75 to 25.75, and 26.75 to 35.75. Nearest 10 changes 23.75 to 30.75. Nearest 90, 95, 99 and 100 work within hundreds: 123.75 becomes 190.75, 195.75, 199.75 or 200.75. An already matching whole-number part stays unchanged. These options do not round to multiples of the selected number.
Price ending runs last. Keep as is leaves the result alone. End with .90, .95, .99 or .00 replaces its decimals. From 23.75, these give 23.90, 23.95, 23.99 or 23.00. An ending can lower the price: 23.99 with .95 becomes 23.95.
A supplier price of 19 with a 25% markup, No rounding and a .99 ending becomes 23.99 instead of 23.75. If you also round up to the next whole number, it becomes 24.99.

Selling price, discounted price and compare-at price
These rules change only the selling price. They leave cost per item and compare-at price unchanged. A compare-at price is the higher original price used to show a discount.
When a mapped Discounted price is greater than 0, it becomes the selling price. The mapped regular Price becomes compare-at, replacing any separate Compare at price value. For example, Price 20 and Discounted price 15 with a 10% markup send selling price 16.50 and compare-at 20. The price range is chosen using 15, not 20.
A blank, zero or negative Discounted price is ignored. The regular Price and separate Compare at price are then used. A blank compare-at value is omitted, so an update leaves the existing compare-at value alone. Check that your final selling price still makes sense beside the unchanged compare-at price.
A missing, blank or invalid regular Price starts at 0 unless a positive Discounted price supplies the selling price. A mapped Price of 0 is also processed: adding 2 makes it 2.00. A blank mapped Price can therefore overwrite an existing price on an update. There is no default-price control in Advanced pricing. To leave selling prices alone on updates, leave both Price and Discounted price unmapped.
The form's example calculation uses the regular Price, so it can differ from the actual result when Discounted price is mapped. Check the resolved selling price before running a large file.
Imports, updates and saved schedules
The same price rules apply when creating new products and updating existing products. Updates calculate from the file's price, not the current Shopify price. Repeating a source price of 10 with a fixed change of 2 sends 12.00 again, not 14.00.
A Pro or Scale automation saves its own pricing settings and reuses them when it processes a scheduled file. The current plan must still include Advanced pricing when the run executes. Without access, the run applies no advanced price changes. An unchanged file with unchanged settings is skipped after a fully successful scheduled run. See the unchanged-file limits.
Why these rules matter for sync
Without these rules, every supplier feed needs preprocessing before or after import. Simple CSV applies the saved rules whenever a Pro or Scale scheduled file is processed. The markup stays in the app rather than in a copy of the supplier's feed.
Advanced rules and scheduled URL imports are part of the Pro and Scale plans. The Free plan still supports manual URL imports and column mapping. Automated supplier sync requires a paid plan.
Known Limitations
Unchanged scheduled files. After a fully successful scheduled run, Simple CSV skips the same file when the automation settings have not changed. That saves work, but it does not repair changes made in Shopify after the previous run. If sales reduce inventory or someone deletes a product, an unchanged supplier file will not restore it. Open the automation and select Run now to process the file again.
Changing the automation settings, schedule hours, mapping, feed URL or out-of-feed cleanup setting makes the next scheduled run process the file. Each automation remembers its own last successful file.
Variants missing from the feed. While Choose products conditions are set, out-of-feed cleanup is disabled. Free and Pro do not clean up missing feed items automatically. On those plans, use a manual diff between your Shopify catalog and the latest supplier feed to find discontinued products. On Scale, optional cleanup checks every previously managed variant. If the import updates inventory, a missing variant is set to 0 only at that import's Shopify location, even when sibling variants are still present. Quantities at every other location stay unchanged. Simple CSV turns off Continue selling when out of stock only when the variant has no stock at another active location.
Inventory is set to 0 before Simple CSV applies the configured product action. A product stays active when only some variants are missing or stock remains at another active location. When every tracked variant is missing and no stock remains elsewhere, cleanup leaves the product active, sets it to draft or unlists it according to your setting. Simple CSV does not delete it. If the import does not map inventory, it has no location to clean up. Simple CSV makes no inventory or Continue selling changes but still applies the configured product action when the whole product is missing.
While Choose products conditions are set, out-of-feed cleanup is disabled. Products outside your selection stay unchanged in Shopify.
If a variant reappears, the next import restores its feed quantity. Simple CSV does not restore Continue selling when out of stock if an earlier cleanup turned it off.
Cleanup uses the saved Shopify variant ID when one is available. For older tracked rows, it falls back to the mapped Shopify variant SKU or first barcode.
Authentication beyond basic auth. Basic auth in the URL works at https://user:pass@example.com/feed.csv. API key headers, OAuth tokens and signed URLs with expiring parameters do not. The standard workaround is a small middleware script. It authenticates to the supplier's API, downloads the feed and serves it from your own HTTPS endpoint with basic auth. A free Cloudflare Worker can do this in under fifty lines.
FTP and SFTP feeds. Not supported. Ask whether the supplier also offers HTTPS. If FTP is the only option, use a scheduled job to copy the file to a public HTTPS path each morning.
XML limits. Simple CSV rejects XML files with a DOCTYPE declaration and records larger than 10 MB. A file without a repeating element containing fields fails with No repeating XML record element containing fields could be detected. Invalid XML reports the parser error. The 200 MB download limit for URL sources still applies.
JSON feeds. Simple CSV does not accept JSON. Inventory & Price Sync handles JSON feeds.
Sub-hourly sync. A Pro or Scale schedule runs once at its chosen time. Multiple schedules per day are possible within the plan limits, but a real-time or sub-hourly sync from a single feed is not. On Pro and Scale, scheduled new-product imports run at most once per day. Updates can use several times within the plan limits. Flash sales and high-velocity inventory that need sub-hourly parity require another tool.
Mapping-hold emails. We send one email when an action enters a mapping hold. Other failed runs are shown in-app. Check Recent imports weekly.
Best Practices
Use these checks when setting up a Pro or Scale production schedule.
- Test with one row first. Before enabling a Pro or Scale schedule, manually run a one-row CSV to confirm the mapping and matching are correct. A row-level success on a single product is much cheaper than discovering a mapping bug across 3,000 products.
- Back up before the first large sync. A free backup app gives you a recovery path if a feed change causes the wrong updates.
- Match by SKU. It is predictable and the right default for almost every supplier feed.
- Schedule outside peak shop hours. Pro and Scale imports use API calls. Large imports can compete with other store activity if scheduled during a busy period.
- Check logs weekly, especially in the first month. Most issues surface in the first few weeks, including column renames, format changes and expired authentication. After a month of clean runs, monthly checks are usually enough.
- One schedule per concern. Within the Pro or Scale automation limit, a daily price refresh, a daily stock refresh and a daily new-product create are easier to debug as three schedules than one.