---
title: "How to Import Global WooCommerce Attributes and Terms from CSV"
url: "https://wpimportexport.com/how-to-import-woocommerce-global-attributes-terms-csv/"
description: "Import global WooCommerce attributes and terms from CSV, including slugs and descriptions. Includes sample files, admin steps, and AI-agent prompts."
type: post
published: 2026-10-27T10:11:24+00:00
modified: 2026-11-14T10:35:45+00:00
categories: ["Import Guides", "WooCommerce"]
tags: ["AI Agents", "CSV import", "Product Attributes", "WooCommerce"]
docs_topics: ["WooCommerce"]
---

# How to Import Global WooCommerce Attributes and Terms from CSV

Suppliers often send the list of materials, sizes or finishes before the products themselves. Those values can go into WooCommerce first, as global attributes. Choose **WooCommerce Attributes** in Import Export by RockStarLab, upload a file with one attribute per row, map the slug, label, settings and terms, and run the import. The attributes then appear under **Products → Attributes**, ready for every product.

Building the attribute library first, with term slugs and descriptions, keeps the values consistent when you import or edit the products later.

Below are the CSV structure, the admin workflow, updates of existing terms and the same task through a connected AI agent. The example creates **Fabric** with Cotton and Linen, plus **Fit** with Regular, Relaxed, and Slim.

## Global attributes, terms, and product attributes: what are you importing?

A global attribute is a reusable product characteristic, such as Fabric. Its terms are the available values: Cotton, Linen, and Canvas. A product can then use some of those terms. These are separate pieces of the catalog, and choosing the right import type prevents a lot of confusion.

| Item | Example | Where it belongs |
| --- | --- | --- |
| Global attribute | Fabric, with slug fabric | Products → Attributes |
| Attribute term | Cotton, with slug cotton | Configure terms for Fabric |
| Attribute assigned to a product | A shirt uses Cotton and Linen | The product’s Attributes settings |
| Variation | A purchasable Cotton / Small shirt with its own SKU | The variable product’s Variations settings |
| Custom product attribute | A product-specific engraving instruction | That individual product, rather than the shared attribute library |

**This import creates or updates the global attribute library.** It does not assign Fabric to every product, turn product-specific attributes into global ones, or generate purchasable variations. For catalog rows, follow [the WooCommerce product import tutorial](https://wpimportexport.com/how-to-import-woocommerce-products-from-csv-or-excel/). For variation combinations, SKUs, prices, and stock, use [the variable product CSV tutorial](https://wpimportexport.com/how-to-import-woocommerce-variable-products-from-csv/).

WooCommerce also explains the distinction between global and individual product attributes in its [product taxonomy documentation](https://woocommerce.com/document/managing-product-taxonomies/).

## Before you start

You need WooCommerce, Import Export by RockStarLab, and its **PRO WooCommerce import functionality** active on the destination. Sign in with an account that can manage imports and WooCommerce attributes. The AI method additionally requires an authenticated MCP connection with permission to run the relevant abilities.

Open **Products → Attributes** before preparing your file. Check whether your intended attributes already exist and note their slugs. For example, a Fabric label might already use `material` as its slug. Use the existing slug when your intention is to update that attribute; a matching display label alone is not a reliable identifier.

Keep a current backup before changing an established catalog. Start with a small file so you can review labels, terms, and sorting before importing the rest of a supplier’s vocabulary.

## Download the sample WooCommerce attributes CSV

[Download the global attributes sample CSV](https://wpimportexport.com/wp-content/uploads/2026/10/woocommerce-global-attributes-sample.csv). It contains two attribute rows and six columns. Fabric uses structured JSON so each term has an explicit slug and description. Fit uses a simple comma-separated list.

| Slug | Label | Type | Sort order | Archives | Terms |
| --- | --- | --- | --- | --- | --- |
| fabric | Fabric | select | name | 0 | Cotton, Linen; JSON includes descriptions |
| fit | Fit | select | name | 0 | Regular, Relaxed, Slim |

Use **one row per global attribute**. Put all the terms belonging to that attribute in its `attribute_terms` cell. You do not need a separate row for every term or a product SKU column.

### CSV columns and their meanings

| Column | Example | Purpose |
| --- | --- | --- |
| `attribute_name` | `fabric` | Required unique attribute slug. This is the matching identifier, despite the word name in the column header. |
| `attribute_label` | `Fabric` | Readable label used in WooCommerce. |
| `attribute_type` | `select` | Attribute type. Use select for the standard reusable values in this guide. |
| `attribute_orderby` | `name` | Default sorting: menu_order, name, name_num, or id. |
| `attribute_public` | `0` | Attribute archives: 0 disables them; 1 enables them. |
| `attribute_terms` | JSON array or comma-separated names | The attribute’s values, optionally with slugs and descriptions. |

Use a short lowercase slug such as `fabric`, without the internal `pa_` taxonomy prefix. WooCommerce uses `pa_fabric` internally; the attribute-name column should contain `fabric`. Keep slugs stable on later imports.

For sorting, `name` means alphabetical names, `name_num` means numeric names, `menu_order` selects custom ordering, and `id` uses term IDs. Selecting custom ordering does not make this CSV an explicit per-term ordering file. Use WooCommerce’s term-order controls when you need a particular manual sequence.

Include all six columns when updating an attribute. In particular, carry forward its label, type, sort order, and archive setting. Do not assume that leaving those settings unmapped means they will be preserved: the importer can use defaults for omitted values.

### Simple term names

For values that need no custom slugs or descriptions, enter this in one `attribute_terms` cell:

```
Regular, Relaxed, Slim
```

When saved as CSV, that cell must remain a single field. Because it contains commas, a correctly written CSV encloses it in double quotes:

```
attribute_name,attribute_label,attribute_type,attribute_orderby,attribute_public,attribute_terms
fit,Fit,select,name,0,"Regular, Relaxed, Slim"
```

A spreadsheet’s CSV export normally handles the outer quoting for you. In the import preview, the three names should appear together in the terms column, not as extra columns. Use JSON instead if a term name itself contains a comma.

### Term names, slugs, and descriptions in JSON

For Fabric, put the following JSON array in a single cell:

```
[
  {"name":"Cotton","slug":"cotton","description":"Soft everyday fabric."},
  {"name":"Linen","slug":"linen","description":"Lightweight woven fabric."}
]
```

Each object describes one term. The `name` is its readable label; `slug` provides a stable identifier; `description` becomes the term description in WooCommerce. Explicit slugs are especially useful when you want to revise a term’s label or description later.

JSON quotation marks are part of the cell value. A CSV writer escapes them when it saves the file, so the raw CSV contains doubled quotes. Do not remove those doubled quotes from the downloaded sample. Edit the cell in your spreadsheet or use a proper CSV editor, then check the preview before importing.

## Import global WooCommerce attributes through the admin

### 1. Choose WooCommerce Attributes

Open **Import Export by RockStarLab → Import**. Choose **WooCommerce Attributes** as the content type, then continue to the upload step. This tells the plugin that each row defines an attribute and its terms.

Choose this content type even though WooCommerce represents attribute terms as taxonomies internally. The dedicated importer also creates the global attribute definition. For ordinary categories, tags, or other registered taxonomies, use [the WordPress taxonomy import guide](https://wpimportexport.com/how-to-export-import-wordpress-categories-tags-custom-taxonomies/).

### 2. Upload the CSV and inspect the preview

Select your CSV file and continue to **Preview**. The sample should show **2 rows and 6 columns**. Confirm that the first row is Fabric, the second is Fit, and the JSON remains entirely inside `attribute_terms`.

![CSV preview showing Fabric and Fit as two attribute rows with six columns](https://wpimportexport.com/wp-content/uploads/2026/10/attributes-01-preview.webp)

_Keep each terms list or JSON array inside its single attribute_terms cell._

If the entire header appears in one column, check the delimiter used when the CSV was saved. If terms spill into extra columns, check CSV quoting. Resolve either issue here rather than trying to compensate with field mapping.

### 3. Map the six columns

Click **Auto Map**. With the sample headers, the screen reports six mapped fields. Review the assignments, particularly the difference between the slug and the label.

![Auto Map assigns all six CSV columns to WooCommerce attribute fields](https://wpimportexport.com/wp-content/uploads/2026/10/attributes-02-mapping.webp)

_Check the slug and label mappings separately before continuing._

`attribute_name` belongs in **Attribute Name / Slug**, while `attribute_label` belongs in **Attribute Label**. Map the remaining columns to type, order by, archives, and attribute terms. If your supplier uses different header names, map those columns manually to the same destinations.

Leave **Attribute ID** unmapped for this workflow. Imported attributes are identified by their slugs, and an ID from another store is not a portable identifier. You also do not need to supply the number of terms; the terms themselves are in the JSON or list.

### 4. Review the import options

Use **Attribute Name / Slug** to check for existing items. Choose **Update** when a match is found and **Create** when no match is found. This is the create-or-update workflow used throughout the tutorial.

![WooCommerce attribute import options matching by slug and updating existing items](https://wpimportexport.com/wp-content/uploads/2026/10/attributes-03-options.webp)

_Match by attribute slug, update matches, and create new attributes._

The sample uses a batch size of **1**, so each batch processes one attribute row. A row can contain several terms; batch size is not a limit on how many values an attribute may have. Larger files should be sized for your server and the amount of data inside each row.

There is no URL change in this sample, so leave **Replace links** disabled. Recheck the incoming slugs before proceeding, especially when updating an existing catalog.

### 5. Start the import

Click **Start Import** and wait for the completion screen. With Fabric and Fit absent from the destination, the sample creates two attributes.

![Completed attribute import reporting two created attributes and zero failures](https://wpimportexport.com/wp-content/uploads/2026/10/attributes-04-completed.webp)

_The completion counters count attribute rows, not individual terms._

The success and created counters refer to **attribute rows**. Two successful rows here contain five terms in total. To inspect the values, open the corresponding attributes in WooCommerce rather than reading the row count as a term count.

### 6. Check the attributes and their terms

Open **Products → Attributes**. Fabric and Fit should appear with their intended slugs and sort settings. The Terms column lists Cotton and Linen for Fabric, and Regular, Relaxed, and Slim for Fit.

![WooCommerce Products Attributes page containing imported Fabric and Fit](https://wpimportexport.com/wp-content/uploads/2026/10/attributes-05-global-list.webp)

_The global attribute list shows the imported labels, slugs, sorting, and terms._

Click **Configure terms** for Fabric. Confirm the term names, slugs, and descriptions. A count of zero is normal before products use those values; importing the attribute library does not assign terms to products.

![Fabric terms Cotton and Linen with imported slugs and descriptions](https://wpimportexport.com/wp-content/uploads/2026/10/attributes-06-terms.webp)

_Configure terms displays the names, slugs, and descriptions saved from JSON._

Once the library is ready, select the relevant global attribute in a product’s Attributes settings and choose the terms that apply. If you are building variable products, their attribute selections and variation records need their own setup. Keep that work separate from creating the shared vocabulary.

## Update existing attribute terms without duplicating them

Use the same attribute slug to target the same global attribute. Within it, keep the term slugs stable to update existing terms. The readable labels and descriptions can change while those identifiers stay the same.

[Download the Fabric update CSV](https://wpimportexport.com/wp-content/uploads/2026/10/woocommerce-global-attributes-update.csv). It contains one attribute row with the same settings as before and this terms value:

```
[
  {"name":"Cotton","slug":"cotton","description":"Soft breathable fabric for everyday clothing."},
  {"name":"Canvas","slug":"canvas","description":"Durable woven fabric for bags and outerwear."}
]
```

With existing-attribute and term updates enabled, Cotton receives the new description and Canvas is added. Linen remains available even though it is not in the update file. **Omitting a term does not delete it.** This import is suitable for additions and updates; it is not a replacement list that removes every value absent from the CSV.

The same principle applies to other global attributes. A Fabric-only file does not need to repeat Fit, Color, or Size. Include the complete settings for the attribute row you are updating, and include the term properties you intend to save.

A changed slug can identify a new term rather than rename the old one. To revise a display name, keep its existing slug in the JSON and change the name property. Review term relationships before deliberately replacing slugs used by an established catalog.

## Import WooCommerce attributes with an AI agent

A connected agent can upload the CSV, inspect the parsed rows, map fields, start the attribute import, and monitor the job. First follow [the WordPress Abilities API and AI-agent setup guide](https://wpimportexport.com/how-to-use-the-wordpress-abilities-api-with-ai-agents-exports-imports-content-sync-and-backups/). Use the prompts below with your own connected store and attached CSV.

The agent should discover the abilities and read their current input schemas. The attribute import uses `rsl-ie-pro/import-start` with `import_type: woo_attribute`. File upload and job status use the `rsl-ie` abilities. The exact upload and job IDs must come from tool responses.

### Prompt 1: Check the CSV and prepare the mapping

```
Inspect the attached WooCommerce global attributes CSV for my connected store.
Discover the available abilities and read the upload and PRO import schemas.
Upload and preview the CSV, but do not start an import yet.

Confirm one row per attribute and these six columns:
attribute_name, attribute_label, attribute_type, attribute_orderby,
attribute_public, attribute_terms.

Check that attribute_name contains the slug without pa_, and that each
attribute_terms cell is a valid JSON array or a comma-separated list.
Show the parsed rows and the proposed mapping. Flag conflicting slugs,
missing settings, or malformed values before proceeding.
```

### Prompt 2: Run the reviewed import

```
Import the reviewed CSV into the connected store using the uploaded file ID.
Use rsl-ie-pro/import-start with import_type woo_attribute.
Map all six columns to their matching target fields.
Set has_header true, update_existing true, update_terms true,
skip_existing_terms false, and batch_size 1. The delimiter is a comma.

Use a unique request_id for this operation and reuse that same request_id
if retrying the identical start request. Poll rsl-ie/job-get until the job
finishes, then report processed, successful, failed, and skipped rows.
Do not import products, change product assignments, or create variations.
Finally inspect Products → Attributes and Configure terms in the browser
if browser access is available; otherwise give me those verification steps.
```

Behind this workflow, `rsl-ie/upload-create`, `rsl-ie/upload-chunk`, and `rsl-ie/upload-complete` prepare the file. The completed upload returns its parsed preview. The import-start response returns a job ID; `rsl-ie/job-get` reports progress. A pending response means the job has been queued, not that it has finished.

### Prompt 3: Add Canvas and update Cotton

```
Use the attached Fabric update CSV for the existing fabric attribute.
Preview it first and confirm the existing slug and intended settings.
Update Cotton's description by matching slug cotton, and add Canvas
with slug canvas. Keep Linen and all unrelated attributes.

Run the PRO woo_attribute import with update_existing true,
update_terms true, and skip_existing_terms false. Preserve the file's
explicit label, type, sort order, and archive setting.
After completion, verify in the browser that Fabric contains Canvas,
Cotton, and Linen, and that Cotton shows the revised description.
Report any failed rows. Do not change products or variations.
```

![Fabric terms after the AI import showing Canvas, updated Cotton, and retained Linen](https://wpimportexport.com/wp-content/uploads/2026/10/attributes-07-updated-terms.webp)

_The update adds Canvas, changes Cotton’s description, and retains Linen._

The destination term list is the clearest final check: Canvas is present, Cotton has the revised description, and Linen is still there. If the agent cannot access a browser, open this screen yourself before moving on to product assignments.

## Common attribute import problems and how to resolve them

| What you see | What to check |
| --- | --- |
| The CSV appears as one column | Check the delimiter and header row. Save a correctly delimited CSV and preview it again. |
| Term names become extra columns | The comma-containing terms cell needs proper CSV quoting. Use the sample or a CSV export tool. |
| A second attribute appears instead of an update | Compare attribute_name with the existing WooCommerce slug, not just its label. |
| Terms have names but no intended descriptions | Use JSON objects containing description, and confirm the entire array is mapped to attribute_terms. |
| Sort order or archive settings change | Include the intended attribute_orderby and attribute_public values in the update file and map them. |
| A value omitted from the file is still present | That is expected: missing terms are not deleted by this import. |
| The attribute exists but does not appear on a product | Assign it and its terms to that product, then check the product’s visibility settings. |
| No variations appear | Global terms are only the available values. Create or import the variable product and its variations separately. |
| Color or image swatches are missing | Swatch rendering and metadata depend on the swatch extension. This standard attribute file does not configure that extension. |
| The AI import is pending | Poll the existing job and inspect its status. Avoid starting several copies of the same import. |

## Frequently asked questions

### Can I bulk import global WooCommerce attributes from CSV?

Yes. Choose WooCommerce Attributes in Import Export by RockStarLab PRO, use one attribute per row, and map the slug, label, settings, and terms before importing.

### Is attribute_name the display name or the slug?

It is the unique attribute slug, such as fabric. Put the readable label, such as Fabric, in attribute_label. Do not add the internal pa_ prefix to the slug.

### How do I import attribute term descriptions?

Put a JSON array in attribute_terms. Each term object can include name, slug, and description. Keep that entire array in one CSV cell.

### Will importing global attributes assign them to my products?

No. This workflow creates or updates the global attribute library. Product assignments and variation records require a separate product edit or import.

### Can I update terms without creating duplicates?

Yes. Keep the same attribute slug and term slugs, and enable updates. Existing terms are matched by slug; new term slugs can create new values.

### Does leaving a term out of the CSV delete it?

No. Terms omitted from the incoming attribute row remain available. This workflow adds and updates values rather than deleting missing terms.

### Can I use a simple list instead of JSON?

Yes. A comma-separated list such as Regular, Relaxed, Slim works for basic term names. Use JSON when you need explicit slugs, descriptions, or names containing commas.

### Can an AI agent run the attribute import?

Yes. An authenticated agent with the required permissions can upload and preview the CSV, call the PRO import ability with woo_attribute, and poll the job. Check the resulting attributes and terms in the browser afterward.

For a complete store transfer involving products, customers, orders, and other store data, continue with [the WooCommerce store migration guide](https://wpimportexport.com/how-to-migrate-woocommerce-store-data-to-another-site/). You can also browse the [written tutorial library](https://wpimportexport.com/import-export-video-tutorials-for-wordpress/#written-guides) for related import, export, and synchronization workflows.
