# 🔄 Import & Export Price List Rules
When managing large catalogs or tailoring numerous pricing schemes for many clients, manually creating each price list is often impractical. Our **Import / Export Price List** feature helps you **bulk upload, edit, or migrate** Price List rules effortlessly — saving hours and minimizing mistakes.
### 📤 Export Your Price List Rules
1. From the **Import / Export PL Rules** section in **Price list per customer** module, click the **Export** button (typically found at the bottom of the page).
2. Download a CSV file containing all your current price list rules.
3. Open the file to review or modify existing rules — it becomes your working template for bulk edits.
***
### 📥 Import New or Updated Rules
#### **Step 1: Download the Sample Template**
* From the **Import / Export PL Rules** section, click **Download Sample**.
* The template includes all required columns and guidelines to help you fill in correct values.
#### **Step 2: Fill Out the Template**
* **To create new rules**: Leave the **ID** column blank.
* **To update existing rules**: Include the matching **ID** in your worksheet.
* Be sure to follow formatting guidelines for each column.
* Input fields must adhere to the allowed values.
#### **Step 3: Import & Choose Overwrite Behavior**
* Upload your completed CSV in the same **Import / Export PL Rules** section.
* Choose whether to **Add (merge with existing rules)** or **Replace (overwrite all existing rules)**.
* **Add / Merge**: Adds your new entries alongside existing ones.
* **Replace**: Deletes all current rules and replaces them with the imported set.
* After upload, the app validates your file and applies new or updated rules. If there are errors, it will display messages pointing to invalid rows or fields.
* Once successful, your newly imported rules are live and active.
| **id** | Required for updating rule | Number | Used only when updating an existing rule. Leave blank for new entries. |
| ----------------------------------------------- | ------------------------------------------------------------------ | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **name** | Required | String | Rule name for internal identification. |
| **priority** | Required | Number | Value must be a positive integer from 0–99 (0 = highest priority). |
| **status** | Required | String | Must be either `enable` or `disable`. |
| **apply\_to** | Required | String | One of: `All`, `Logged-in customers`,`Not logged-in customers, Specific customers`, `Customer tags`, `Specific customers` |
| **customer\_emails** / **customer\_tags** | Required when apply\_to is `Specific customers` or `Customer tags` | String | List of customer emails or tags, separated by commas. |
| **exclude\_from** | Required | String | One of: `None`, `Specific customers`, `Customer tags`. |
| **exc\_customer\_emails / exc\_customer\_tags** | Required when exclusion applies | String | List of emails or tags to exclude, separated by commas. |
| **exc\_product\_type** | Required | String | One of: `None`, `Specific variants`. |
| **exc\_variant\_ids / exc\_sku / exc\_barcode** | Required when exclusion applies | String | List of variant IDs, SKUs, or barcodes separated by commas. |
| **start\_date** | Optional | Date | Format: `YYYY-MM-DD`. Defines when the rule becomes active. |
| **start time** | Optional | Time | Format: `HH:MM`. Works with the start date for precise timing. |
| **end date** | Optional | Date | Format: `YYYY-MM-DD`. Defines when the rule ends. |
| **end time** | Optional | Time | Format: `HH:MM`. Works with the end date for precise timing. |
| **apply\_at** | Required | String | One of: `Product level` or `Variant level`. |
| **product\_titles / sku / barcode** | Required (at least one field) when applying to specific products | String | List of product identifiers separated by commas. |
| **variant\_ids / sku / barcode** | Required (at least one field) when applying to specific variants | String | List of variant identifiers separated by commas. |
| **discount\_type** | Required | String | One of the following: – Apply a price to selected products
– Decrease a fixed amount of the original prices of selected products
– Decrease the original prices of selected products by a percentage
- Apply an increased fixed price to selected products
- Increase the original prices of selected products by a fixed amount
- Increase the original prices of selected products by a percentage
|
| **discount\_value** | Required | Number | Positive number defining the discount or fixed price value. |
***
#### ✅ Tips & Best Practices
* Always **export and back up** your current rules before importing.
* Use the **sample file template** — altering column headers can cause import failures.
* Only use the **Replace** option when you want to refresh your entire pricing structure.
* Double-check your product SKUs, variant IDs, and customer identifiers to ensure accuracy.
* Keep file size manageable (e.g., below 10 MB) to avoid upload issues.
{% hint style="info" %}
If you need further assistance, please feel free to reach us at [**support-sbc@bsscommerce.com**](mailto:support-sbc@bsscommerce.com) or [**Live Chat**](https://go.crisp.chat/chat/embed/?website_id=9f64b5a9-1a02-4190-93b8-8ef56b19f740).
{% endhint %}