> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://bulkflow.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to Create an "Update" feed to Change Existing Records

# 1. Overview
Learn how to create an **'Update' Feed** in BulkFlow to modify existing records in your store — such as products, customers, blog posts, pages, or more — without creating duplicates. Instead of overwriting all data, you only update the fields you include in your file.

# 2. Requirements
Before creating an 'Update' feed, make sure you have:
* A BulkFlow account connected to your store.
* A file that includes at least one unique identifier for the entity you're updating (e.g., SKU or Handle for Products, Email for Customers).
* Access rights to create and manage feeds.

# 3. How to Create an 'Update' Feed
### **Step 1: Choose the Update Feed Type**
* From the BulkFlow Dashboard, click directly on the **Update** button.
* **Select Entity:** Choose what you want to update (e.g., Products, Collections, Customers, Orders, Pages, Blogs, Menus, Discounts, Companies, Metaobjects).
* **Select Connection Type:** Choose how you'll provide your data — upload file, Google Sheet, file URL, FTP/SFTP, or API.
✅ **Required**: Your file must include at least one unique identifier (varies by entity, e.g., SKU for Products, Email for Customers).
![](https://storage.crisp.chat/users/helpdesk/website/-/d/7/5/a/d75a04e726ca2800/image_rypf9i.png =1000x404)

### **Step 2: Prepare Your File**
Your file should:
* Be in .CSV, .XLSX format
* Contain **only the fields you want to update**
* Include **at least one ID column** for matching:
| **Entity** | **Required Identifier(s)** |
| Products | SKU, Handle, ID, Product ID, Barcode |
| Customers | Email, Customer ID, Phone |
| Orders | Order ID, Order Name/Number |
| Pages | Handle, Page ID |
| Blogs | Handle, Blog ID |
| Collections | Handle, Collection ID |
| Companies | Company Name |

NOTE: You don't need to include all columns — only the fields you want to update.

### **Step 3: Configure Field Mapping**
BulkFlow will try to match columns in your file with your store's fields.
* **Auto-mapping** is applied for default fields and correctly named metafields.
* **AI-powered field mapping** is also available to help match your fields more precisely.
* You can **manually adjust mappings** for custom fields or metafields.
To auto-detect metafields, name your column:
* Metafield: namespace.key (for Products, Customers, etc.)
* Variant Metafield: namespace.key (for Product Variants)

### **Step 4: Run a Demo, Then Process Your Update Feed**
* Click **Demo Import** to run the feed on a small sample of your data and preview the result before committing to anything.
* Once you're satisfied with the preview, click **Full Import** to process the entire feed — or enable **automation** if you'd like the feed to run regularly (daily, hourly, etc.)
* Check **Logs** to see:
    * Which records were successfully updated
    * Any rows with errors or missing identifiers

# 4. Tips
* Always test with a small file before mass updates — use **Demo Import**.
* Avoid removing required identifier columns mid-update.
* Use the correct format for metafield columns.
* BulkFlow does not delete existing media unless you explicitly overwrite them.

# 5. FAQs
1. **What's the difference between Update and Import feeds?**
Update modifies existing records using an identifier to match them, while Import creates new records.
2. **Will BulkFlow create duplicate records if I run an Update feed?**
No. Update feeds match records using the identifier you provide (e.g., SKU, Email) and only update existing records — they don't create new ones.
3. **Do I need to include every column in my file?**
No. Only include the columns you want to update. Fields you leave out won't be changed.
4. **What happens if a row has an invalid or missing identifier?**
That row will fail and be flagged in the Logs, so you can review and fix it.