How to Set Up a Supplier Feed in Shopify and Keep It Accurate
If you run a Shopify store or manage one for a client, your product, stock and price data often comes from suppliers as CSV files, spreadsheets or XML feeds. Importing a supplier feed into Shopify once is the easy part. The harder work comes afterward, because suppliers change their files and each new supplier adds another source that may update the same products.
This guide shows how to set up a supplier feed so it stays accurate. Decisions about field mapping, updates and feed ownership matter more than the app you use, so make them before your first or second import runs. Here, “feed” means data coming into Shopify from a supplier, not product feeds that Shopify sends to Google or marketplaces.
How to Set Up a Supplier Feed in Shopify
A reliable feed comes from three decisions made in order. First, confirm how each supplier delivers its data. Next, map and test its fields against Shopify. Finally, decide how ongoing updates and removals will be handled.
1. Confirm Delivery, Access and Update Frequency
Suppliers usually deliver product data in one of these forms:
- CSV file: a plain-text table where each row is a product and each column is a field.
- Spreadsheet: often one file per supplier, sent when the catalog or stock changes.
- XML feed: a structured data file that the supplier emails or publishes at a URL, typically meant for keeping your store in step with the supplier’s inventory.
Before you build anything, collect the same basic details from every supplier and keep them in one place:
- Delivery method: whether the supplier emails a file or publishes it at a URL you retrieve. This determines whether someone has to handle each file or a scheduled process can collect it.
- Access credentials: whether the file or URL requires a login, password or other credentials. Record who holds them so the workflow doesn’t stop when one person is unavailable.
- Update frequency: how often the supplier refreshes its data, for example daily or weekly. You will use this to set your own sync schedule.
2. Map Supplier Fields to Shopify Fields
Suppliers build their files around their own systems, not your store, so column names, layout and level of detail vary from one supplier to the next. A supplier file seldom fits Shopify as it arrives. Field mapping solves this by deciding which supplier column fills which Shopify product field, and every supplier needs its own mapping, even when two suppliers send similar data.
Often mapping is simple renaming: a supplier column is matched to the Shopify field that holds the same information, and many import tools handle this well. Your business may also need custom rules, such as combining columns, changing values or handling suppliers differently. Most import tools cannot apply complex transformation logic like this, so merchants usually bring the supplier data into their own spreadsheet in Excel or Google Sheets, apply the rules there and import the prepared file.
Whichever approach you choose, run small sample files through the full import process before using real supplier data. Mapping mistakes then appear on a handful of test products instead of across your live catalog.
3. Plan for Ongoing Updates and Discontinued Products
After the first import, the recurring job is applying each supplier’s changes to products already in your store. Price, stock and product detail changes are expected, so your mapping and schedule should handle them on every run.
Discontinued products need separate planning. Many import processes update the products they find without removing the ones that are missing, so a product won’t necessarily disappear from your store just because it left the supplier’s file. Check how your chosen method behaves and build a deliberate removal process.
A practical approach is to tag products that are missing from the latest feed. You can use that tag to trigger an automation, or collect the flagged products in a saved search or collection where staff can review them and remove them individually or in bulk.
Running Multiple Supplier Feeds Without Conflicts
A second supplier adds a new risk: two feeds can try to update the same product. When both suppliers carry an item with the same barcode or SKU and nothing decides which feed is in charge, whichever import ran last wins. That import can overwrite prices, images, descriptions, stock counts and variants, including manual edits your team made in Shopify.
The practices below are recommended workflow rules, not behavior every import app applies automatically. Check whether your setup supports each one, or plan how you will enforce it yourself.
Assign Feed Ownership Before the Second Feed Runs
Feed ownership means each product has one authoritative supplier, and only that supplier’s feed may update it. A second feed can then no longer change products it doesn’t own. If only one supplier carries a product, that supplier owns it by default, but products that appear in both feeds need an explicit choice.
Make that choice before the second import runs. Once a second feed has run without ownership rules, overlapping products may already carry its prices, images or stock counts, and fixing that afterward is harder than preventing it.
Set Pricing Rules and Sync Schedules per Supplier
Suppliers sit in different market positions, so one flat markup rarely fits them all. It leaves margin unused on some products and prices you above what the market will accept on others. Give each supplier its own pricing rules; with ownership in place, only the owning supplier’s cost and markup determine a product’s sell price.
Each supplier connection should also have its own sync schedule matching that supplier’s update frequency. A supplier with a live API might sync hourly, while one that sends a weekly CSV only needs a weekly run. Stagger the schedules so different suppliers’ imports don’t run at the same time.
Use Drafts and Separate Inventory Locations as Safeguards
Import new products from each supplier as drafts. Draft products aren’t visible to customers, so you can review the data before anything reaches your storefront.
Also give each supplier its own Shopify inventory location. Stock counts stay separate, so one supplier’s sync can’t change another supplier’s numbers or the stock you hold in your own warehouse.
Common Supplier Feed Problems and What They Mean
Most supplier feed problems don’t produce clear error messages. They show up as data that looks wrong, and the pattern of symptoms usually points to the cause.
Data Changing After Every Sync
When you add a second supplier without deciding who owns shared products, the warning signs tend to follow a recognizable order. Prices change though nobody edited them, improved product images revert to the manufacturer’s stock photos, stock counts stop matching what you can ship, and finally extra, missing or duplicated variants appear on the same product.
Because none of these symptoms triggers an import error, you usually find out through customer complaints or repeated manual corrections. If you fix the same products after every sync, treat it as an ownership problem rather than a one-off mistake, and assign one authoritative supplier to each shared product.
This error means the supplier’s server refused access, so the cause is usually missing or invalid credentials, not the file format. The URL and format can both be correct and still produce it when the feed requires authentication, so changing your mapping or file settings won’t help. Ask the supplier for valid credentials and enter them where you connect the feed URL.
Conclusion
A supplier feed in Shopify stays accurate when you design the workflow before imports scale up, rather than leaving the decisions to whatever import tool you use. With clear mapping, a plan for updates and removals, and defined ownership when feeds overlap, you can add suppliers without losing control of your catalog. We hope this guide helps you set up a supplier feed you can rely on from the first import onward.
