Build a 500-Plant WooCommerce Store with Novamira
Back to Blogs
WooCommerce
WordPress AI Automation

How to Build a 500-Plant WooCommerce Store in a Day from One Supplier CSV with Novamira

Skip manual product entry. Use one supplier CSV, Novamira, Claude, and WooCommerce's importer to prepare and check a 500-plant catalog.

Huzaifa Rizwan November 16, 2026 13 mins read
Build A 500 Plant WooCommerce Store With Novamira Scaled

Adding 500 products to WooCommerce means entering each product’s name, price, SKU, image, and category one by one. That takes time and increases the chance of mistakes.   

A duplicate SKU can disrupt inventory tracking, while an incorrect price or missing image can cause problems after launch. But your supplier’s CSV holds most of this data, so the challenge is mapping the data correctly and getting it into WooCommerce without entering every product by hand.   

That’s why this guide shows you how to build a 500-plant WooCommerce store from one supplier CSV with the Novamira WordPress plugin and Claude.ai. You’ll install and connect the plugin, clean the file, let Claude create the products, and check everything before launch. Claude creates the products. You don’t. 

Quick Answer

Build a 500-product WooCommerce plant store without manually adding each product. Use Novamira to connect Claude with WordPress, review your supplier CSV, prepare it for WooCommerce, and check the imported products. Import the CSV using WooCommerce’s built-in importer, then verify product details, prices, images, stock, and checkout on a staging site before launch.

What you need before starting   

Gather these items before you open WordPress. Each one saves you from stopping halfway through the build.

  • WordPress with WooCommerce installed and activated
  • The Novamira plugin ZIP
  • A Claude.ai account
  • The 500-product supplier CSV
  • A staging site, separate from your live store
  • A recent backup

Confirm the backup exists before you turn on Novamira’s site access.   

Step 1: Prepare Your WordPress and WooCommerce Step 1: Prepare Your WordPress and WooCommerce Site

  • Open your WordPress dashboard   
  • Go to Plugins > Add Plugin   
Image 471
  • Install and activate the WooCommerce plugin    
Image 472
  • Make sure the staging site is separate from the live store.  

The Novamira plugin can execute PHP, run WP-CLI commands, query the database, and modify files. It’s meant for development and staging sites, so don’t connect it to your live store. Use the WooCommerce security checklist to lock down the staging site.   

Take a fresh backup before you continue.

Step 2: Download and Install the Novamira Plugin   

To download and set up the Novamira plugin, follow these steps:   

Image 446
  • After the .zip file is downloaded, go to the WordPress dashboard     
  • Plugins > Add Plugin > Upload Plugin   
Image 449
  • Upload that .zip file and click on Install Now   
Image 448

Step 3: Enable AI Abilities and Connect Novamira to Claude.ai Using OAuth   

  • Once the plugin is successfully installed, open Novamira > Configuration and turn on AI abilities for the site.   
Image 450
  • Select Claude.ai from the client list. Novamira also supports Claude Code, Claude Desktop, ChatGPT, Cursor, VS Code, GitHub Copilot, and others.   
  • Select the OAuth option. The application password isn’t available for Claude.ai, since it requires OAuth.   
  • Click Add the connector to Claude.ai and then Novamira redirects to the MCP settings of Claude with the connector name and URL already filled in. Change the server name first if you want a different label.   
Image 452
  • Click Add, and your MCP is successfully added in Claude.   
Image 453
  • After clicking the Add button, a new tab appears with the URL of that MCP server and the Connect button. Click Connect. 
Image 451
  • Now Claude sends you back to WordPress to authorize the connection between Claude and WordPress.   
Image 455
  • In Claude, assign access to each group of tools. The read-only tools are Discover Abilities and Get Ability Info. Write/delete covers for Execute Ability, This is where the level of access is allowed, not write tools, and approval is needed.   
Image 454

Note:

If your host runs a firewall in front of WordPress, read the warning on this screen. Some hosts classify the OAuth request as bot traffic and block it before WordPress receives it.

Step 4: Test the Claude and WordPress Connection

Start a new Claude conversation and enable the Novamira connector for that chat.

Before asking Claude to work with products, check whether it can access the correct WordPress site.

Copy this prompt into Claude:

Prompt to Claude:

Connect to my WordPress staging site through Novamira. List the installed plugins and confirm whether WooCommerce is active. Also report the WordPress version. Only inspect the site. Do not install, update, delete, or modify anything.
Image 473

What Claude should return:

Claude should use the available Novamira tools to inspect your WordPress installation and return:

  • The installed plugins.
  • WooCommerce activation status.
  • WordPress version.
  • Existing WooCommerce product count.

Check that Claude identifies your staging site, not another WordPress installation.

Note:

Do not approve a tool request that proposes changing site files, database records, or plugin settings during this connection test.

Step 5: Upload and Review the 500-Plant Supplier CSV

Now prepare the supplier file for Claude.

Open Claude’s chat and upload the supplier CSV. Once the file appears in the conversation, send this prompt.

Prompt to Claude:

I have uploaded a supplier CSV containing 500 plant products for my WooCommerce store.   

Analyze the file and prepare an audit report. Do not modify the original CSV or import any products.

Check the following:

Total number of product records.
Missing or duplicate SKUs.
Missing product names.
Missing or incorrectly formatted regular prices.
Empty product descriptions.
Missing categories and tags.
Empty plant type, sunlight, and watering information.
Missing or incorrectly formatted image URLs.
Any other column inconsistencies that could cause a WooCommerce import problem.

Show the affected row numbers and explain the corrections needed. Do not invent missing product information or rewrite product descriptions. 
Image 456

What Claude should return:

Claude should provide an audit report with the number of records, detected issues, affected rows, and suggested corrections.

For example, it may identify duplicate SKUs, missing prices, empty descriptions, or image cells without URLs. The actual findings will depend on your supplier file.

Review the report before allowing Claude to prepare a replacement file.

Keep the original supplier CSV unchanged so you can refer back to it if something goes wrong.

Step 6: Map the Supplier Data to WooCommerce Fields

Once the CSV passes the initial review, prepare its columns for WooCommerce’s product importer.

Send this prompt to Claude in the same conversation:

Looking for a Ready-Made Solution?

Explore our WordPress, WooCommerce, and LMS plugins built to extend functionality without custom development.

Browse Our Products

Prompt to Claude:

Prepare a separate WooCommerce-compatible version of the attached supplier CSV.

Use WooCommerce's standard product CSV importer format.

Map the supplier information to the correct fields:

Product name
SKU
Regular price
Short description
Description
Categories
Tags
Product images
Stock status
Stock quantity
Product weight

Convert plant type, sunlight requirements, and watering requirements into properly formatted columns for WooCommerce product attributes.

Use the correct WooCommerce attribute column structure, including Attribute name, Attribute value(s), Attribute visibility, and Global attribute status.

Use the supported stock fields and value formats.

Do not invent missing product information, alter product prices, or generate fake image URLs. Preserve all valid supplier data.

Create a separate downloadable CSV file and provide a report of any fields that still need manual attention.   
Image 457

What Claude should return:

Claude should provide a separate WooCommerce-ready CSV file and a mapping report.

For stock information, WooCommerce uses fields such as “In stock?” and “Stock.”The importer accepts 1 or 0 for stock status and numeric values for stock quantity.

Plant attributes should follow the supported WooCommerce CSV structure. For example:

CSV columnExample value
Attribute 1 namePlant type
Attribute 1 value(s)Indoor
Attribute 1 visible1
Attribute 1 global0

Use additional numbered attribute columns for sunlight and watering requirements.

Check that Claude has preserved the original product information and has not filled missing details with guesses.

Step 7: Import the 500 Products as Drafts with Claude into WooCommerce

Stay on the same chat where Novamira is connected. Then send this prompt.

Prompt to Claude:   

Use Novamira on my WooCommerce staging site. Read the CSV I uploaded in this chat and create every product in it as a WooCommerce product.

Rules:
1. Save every product as a draft. Don't publish anything.
2. Import every field in the CSV. That includes product name, SKU, regular price, sale price, short description, description, categories, tags, images, stock status, stock quantity, weight, and any other column that has data.
3. Add plant type, sunlight, and watering as visible product attributes.
4. Create any category or tag that doesn't exist yet.
5. Download each image from its URL into the media library. Set the first image as the featured image and the rest as the gallery.
6. If a column doesn't match a WooCommerce field, tell me before you skip it.
7. Skip any SKU that already exists in the store.
8. Don't change prices, rewrite descriptions, or invent missing data. Leave empty cells empty.

Show me the PHP before you run it. After it finishes, report how many products were created, skipped, and failed, with the SKUs for any failures. Stop if anything fails.   
Image 474

What Claude should return:

Claude shows you the PHP code first. Read it before you approve. Look for anything that touches products you didn’t ask about, like deleting or updating existing records.   

After the run, Claude reports how many products it created, skipped, and failed, with the SKUs for any failures. The numbers should add up to 500 created, plus any rows you already knew would be skipped.   

Check the products before you trust the result.   

Go to Products > All Products in WordPress. Open three or four of the new drafts and confirm the name, price, images, categories, stock, and attributes match the CSV. If something’s wrong, tell Claude what’s wrong and ask it to fix the code. Then delete the bad drafts and run it again. 

Important Note:

Claude may not be able to read the CSV from the chat and create the products. If that happens, upload the CSV to your staging site’s media library through Media > Add New Media File. Open the file, copy its File URL, and paste it into the chat with this message:

Read the supplier CSV from this URL on my staging site instead: [paste File URL]. Then follow the same rules from my last prompt.

Step 8: Verify the Imported Products with Claude

Go to Products > All Products on your staging site and check the drafts.

  1. Confirm the Draft count matches the number Claude reported as created.
  2. Set Screen Options to 100 items per page and scan for gray image placeholders, blank prices, blank stock, and “Uncategorized.”
  3. Click View on Each Product to View the Product Page and Check Their Price, Images, Category, Stock, and Plant Attributes.   
  4. Fix small problems in the product editor. For repeated problems, ask Claude to fix only the affected SKUs.    

Once the drafts look right, send this prompt in the same Claude chat.   

Prompt to Claude:   

Use Novamira on my WooCommerce staging site. Publish every draft product created from the supplier CSV in this chat.

Only change the status from draft to published. Don't edit any other product data, and don't touch products that weren't created from this CSV.

Show me the PHP before you run it. After it finishes, report how many products were published and list any SKUs that failed.   
Image 475

What Claude should return:   

Claude shows the PHP first. Check that it only changes the product status. After the run, the published count should match your draft count. Refresh Products > All Products and confirm the draft count is zero.  

Step 9: Test the Store Before Launch

Open your staging store in a browser and review the product catalog on desktop and mobile.

Choose several plants from different categories and check:

  • Product names and descriptions.   
Image 468
  • Prices   
Image 465
  • Stock availability   
Image 466
  • Featured images and gallery images.   
Image 469
  • Category navigation.   
Image 467
  • Add-to-cart functionality, including cart totals and checkout fields.   
Image 470
  • Test order confirmation.

Use your payment gateway’s staging or test mode when available. Avoid unnecessary live transactions.

Fix any product information or checkout problems before moving the approved store changes to production.

You can also review these practices for optimizing your WooCommerce store before launch.

Common Problems and Fixes

ProblemFix
Duplicate SKUsFind and correct duplicate SKUs in the supplier CSV before importing (Step 5).
Incorrect field mappingReview the WooCommerce mapping screen and match each column to the correct field (Steps 6 and 7).
Missing product imagesCheck image URLs in the CSV and correct invalid or empty entries (Steps 5 and 6).
Wrong stock valuesUse the supported In stock? and Stock fields with valid values (Step 6).
Failed product importsCheck the import report, fix affected rows, and retry. Split the CSV if the server times out (Step 7).
Novamira connection errorsCheck OAuth authorization and review whether your hosting firewall blocks the connection (Steps 3 and 4).

Conclusion

A one-time build works well with Novamira and Claude. But if your supplier regularly updates prices, stock, images, or product details, repeating the process wastes time and creates inventory errors.   

WooNinjas’ WordPress integration services can connect your supplier’s system to WooCommerce through an API, webhook, or export file. Our team can build a custom integration that maps product data, automates updates, and handles import errors, with staging-site testing before launch.

Need to sync your supplier’s product data with WooCommerce automatically? Contact WooNinjas to discuss your supplier’s system and get a solution scoped around your store’s requirements.   

FAQs   

Can WooCommerce Import 500 Products from One CSV File?

Yes. Novamira lets Claude create them from one CSV. WooCommerce’s built-in importer also handles 500 in one file if your host allows it. Split the file if it times out.   

Does Novamira Support WooCommerce Product Management?

Yes. Novamira lets Claude run PHP on your site, and Claude uses it with WooCommerce’s product functions to create products. Test on staging first and approve each action.   

How Do You Import Plant Attributes from a Supplier CSV?

Add plant details as WooCommerce attribute columns. Use numbered fields for attribute names, values, visibility, and global status, then map them before importing.

How Can You Check Whether All 500 Products Were Created Correctly?

Check the drafts in Products > All Products. Compare a product export against the supplier CSV by SKU, then open sample product pages.   

Need Ongoing WordPress Maintenance & Support?

We handle updates, performance monitoring, security hardening, and technical fixes so your WordPress and WooCommerce site stays stable and secure.

View Maintenance Plans

Scroll to Top