Import Complex Rules Tool for BigCommerce
🔧 Quick Info: Import Rules lets you create, update, or delete complex product rules in BigCommerce from a CSV or Excel spreadsheet. Products are matched by SKU, while existing rules are identified by Rule ID.
What It Does
Import Rules updates the complex rules attached to your BigCommerce products from a spreadsheet. Complex rules are also commonly called product rules or SKU rules.
BigCommerce uses these rules to change a product’s price, weight, purchasing status, and other behavior based on the options, modifiers, or variants selected by a shopper.
For example, a rule could add $5 to the price and 2 pounds to the weight when a shopper selects Size: Large and Color: Red.
You upload a CSV or Excel file, map its columns to the available rule fields, and the tool applies the changes to the matching products.
Each spreadsheet row can perform one of the following actions:
- Create a new rule by leaving Rule ID blank.
- Update an existing rule by including its Rule ID.
- Delete an existing rule by including its Rule ID and marking the row for deletion.
How Rows Are Matched: The product is found using its SKU. Existing rules are found using the Rule ID. New rules use the modifier conditions or variant SKUs listed in the row.
The import runs as a background job, so you can close the page after starting it. You can choose to receive an email when the process is complete.
If any rows cannot be processed, the tool creates an error file showing the affected rows and the reason each one failed.
When Should You Use This?
- You want to create or change price adjustments across many products.
- You need to update weight adjustments in bulk.
- You want to enable, disable, or stop multiple rules at once.
- You need to disable purchasing for specific option or variant combinations.
- You want to add a message explaining why a particular combination cannot be purchased.
- You need to delete a group of existing product rules.
- You prefer editing rules in a spreadsheet instead of updating products individually in BigCommerce.
- You exported your existing rules, edited the file, and want to import the changes back into your store.
A common workflow is to first use Export Rules, edit the exported spreadsheet, and then use Import Rules to apply the changes.
Before You Get Started
- Make sure the products you want to update already exist in BigCommerce.
- Prepare a CSV or Excel spreadsheet.
- The first row of the file must contain the column names or headers.
- Include a SKU column so each row can be matched to the correct product.
- Include Rule ID when updating or deleting an existing rule.
- Make sure modifier names and modifier values already exist on the product.
- Make sure any variant SKUs used in rule conditions already exist on the product.
- Confirm that you are working with the correct connected BigCommerce store.
Existing Products and Options Required: Import Rules does not create products, modifiers, option values, or variants. Those items must already exist in BigCommerce before a rule can reference them.
How to Use It
1 Open the Tool
Open the Import Rules tool from your BigCommerce tools dashboard.
2 Review the File Requirements
On the Upload Rules step, review the on-screen instructions. The first row of your file must contain the column names.
Your file should include the columns relevant to the rules you are changing, such as SKU, Rule ID, Price Adjuster, and Weight Adjuster fields.
3 Upload the Rules File
Upload your CSV or Excel file. The tool reads the first row to identify the available columns.
4 Match the Columns
After the file is uploaded, the column-matching section appears. Match each spreadsheet column to the corresponding rule field.
At minimum, map the product SKU column to SKU.
Map Rule ID when updating or deleting existing rules, and map the appropriate modifier, variant SKU, adjustment, or status fields for the changes you want to make.
5 Configure Email Delivery
Continue to the Email Delivery step. Choose whether you want an email notification when the import is complete, then confirm the email address.
6 Start the Import
Start the import. A confirmation appears to let you know the process has begun.
The import runs as a background job, so you can close the page while it processes.
7 Review the Results
When the import is complete, check your email if you enabled email delivery.
If any rows could not be processed, download the error file, review the reported problems, correct the affected rows, and import them again.
Creating, Updating, and Deleting Rules
| Action | Rule ID | Delete Value | Result |
|---|---|---|---|
| Create | Blank | No or blank | Creates a new rule using the conditions and adjustments in the row. |
| Update | Existing Rule ID | No or blank | Updates the matching existing rule. |
| Delete | Existing Rule ID | Yes | Deletes the matching rule from the product. |
Deleting a Rule: A deletion row must include the existing Rule ID and a true or yes value in the Delete field. Without the Rule ID, the tool cannot determine which rule to remove.
How Rule Conditions Work
A rule is defined by the combination of modifier conditions and/or variant SKUs listed in the row.
The spreadsheet provides numbered condition slots from 1 through 20. In each numbered slot, use one of the following:
- A Modifier Name and its matching Modifier Value.
- A variant SKU.
One Condition Type Per Slot: Do not enter both a Modifier Name and a variant SKU in the same numbered slot. Use either a Modifier Name and Modifier Value pair or a variant SKU.
Modifier Conditions
A modifier-based condition uses a matching name and value, such as:
| Modifier Name | Modifier Value |
|---|---|
| Size | Large |
| Color | Red |
If you enter a Modifier Name, you must also enter its matching Modifier Value in the same numbered slot.
Variant SKU Conditions
A variant-based condition uses an existing variant SKU instead of a modifier name and value pair. The variant SKU must already belong to the product identified by the main SKU column.
Minimum Conditions for New Rules
When creating a new rule, include at least two valid conditions in total. These can be:
- Two Modifier Name and Modifier Value pairs.
- Two variant SKUs.
- One modifier pair and one variant SKU.
This minimum does not apply in the same way when updating an existing rule by Rule ID.
Price and Weight Adjustments
A new rule normally needs at least one price adjustment or weight adjustment.
| Adjustment | Fields Used |
|---|---|
| Price | Price Adjuster Adjuster and Price Adjuster Adjuster Value |
| Weight | Weight Adjuster Adjuster and Weight Adjuster Adjuster Value |
An adjustment may not be necessary when the rule is being used only to control Enabled, Stop, or Purchasing Disabled behavior, or when you are updating an existing rule by Rule ID.
File and Field Reference
The first row of your file must contain headers. After uploading the spreadsheet, map your columns to the fields below. Only include the fields relevant to the rules you are creating or changing.
| Column | Required? | Notes |
|---|---|---|
| SKU | Yes | The product SKU. Used to find the product where the rule belongs. |
| Rule ID | No | Include this value to update or delete an existing rule. Leave blank to create a new rule. |
| Sort Order | No | A numeric value controlling the order in which rules apply. |
| Enabled | No | Controls whether the rule is active. Accepts values such as y, yes, true, or 1 for yes, and n, no, false, or 0 for no. |
| Stop | No | A yes or no value indicating whether the rule is a stop rule. |
| Delete | No | Set to yes to delete the rule. An existing Rule ID is required. |
| Purchasing Disabled | No | A yes or no value controlling whether the matching combination can be purchased. |
| Purchasing Disabled Message | No | The message shown to shoppers when purchasing is disabled. |
| Price Adjuster Adjuster | No | Controls how BigCommerce applies the price adjustment, such as a supported relative or fixed adjustment. |
| Price Adjuster Adjuster Value | No | The numeric value of the price adjustment. |
| Weight Adjuster Adjuster | No | Controls how BigCommerce applies the weight adjustment. |
| Weight Adjuster Adjuster Value | No | The numeric value of the weight adjustment. |
| Modifier Name 1-20 | No | The option or modifier name used as a rule condition, such as Size. It must already exist on the product. |
| Modifier Value 1-20 | Required when its Modifier Name is used | The option value paired with the matching Modifier Name, such as Large. It must already exist on the product. |
| SKU 1-20 | No | An existing variant SKU used as a rule condition instead of a Modifier Name and Modifier Value pair. |
Troubleshooting and FAQ
A row says the product SKU was not found
The SKU in that row does not match an existing product in your store. Confirm that the SKU is correct, check for extra spaces or typing errors, and import the affected row again.
A modifier or variant SKU was not found
The Modifier Name, Modifier Value, or variant SKU must already exist on the product in BigCommerce. Create or correct the option, value, or variant first, then import the rule again.
A modifier name or value is missing
Modifier Name and Modifier Value must be provided together in the same numbered slot. If one is filled in, the matching field must also be filled in.
Also confirm that you did not enter both a Modifier Name and a variant SKU in the same numbered slot.
My rule was not deleted
The row must include the existing Rule ID and the Delete field must be set to a recognized yes or true value. Without the Rule ID, the tool cannot identify the rule to remove.
The error says I need at least two conditions
New rules require at least two valid conditions. Add two modifier pairs, two variant SKUs, or a combination of one modifier pair and one variant SKU.
If you intended to update an existing rule instead, include its Rule ID.
The tool cannot read my columns
Make sure the first row contains the column names and that the necessary SKU, Rule ID, Price Adjuster, Weight Adjuster, and condition columns are present. Correct the header row and upload the file again.
Where do the results go?
Successful changes are written directly to your BigCommerce store. If email delivery was enabled, you’ll receive a notification when the background import is complete.
Any rows that could not be processed are included in a downloadable error file.