An online retailer receives a spreadsheet from a supplier containing hundreds or thousands of products. Creating every listing manually, copying its description, uploading pictures and entering prices or specifications would take considerable time. When the supplier changes its price list the following week, much of that work must be repeated. Product imports offer a way to make this process manageable and scale the catalogue.
However, importing products is not simply a matter of uploading a file. The data needs preparation, reliable matching rules, testing and a plan for ongoing maintenance. Even a perfectly valid spreadsheet can produce duplicates or overwrite carefully edited product pages if the integration is configured incorrectly.
1. Where product data comes from
Suppliers may provide CSV, Excel, XML or JSON files, API access or an inventory management system. A spreadsheet may be sufficient for a one-time transfer. Recurring updates require a stable, authorised data source whose refresh frequency and meaning are understood by the retailer.
If a supplier does not provide a file, start by requesting an official product feed. Where permission has been granted, a dedicated data collection tool may also be developed. Before collecting and publishing product information, agree on the rights to use photographs, descriptions and technical documents, as well as any restrictions on automated access. Being able to open a page does not automatically grant permission to copy its content.
An estimate should be based on representative source data. Two spreadsheets with the same number of rows can involve very different amounts of work. One might contain clearly labelled attributes and accurate image URLs, whereas another embeds dimensions in descriptions, combines multiple currencies and requires additional processing before the data can be imported.
2. Why SKUs matter more than product names
An SKU, or stock keeping unit, identifies a specific product. The name may change when it is edited or translated, but the stable identifier should remain consistent. This allows the import process to match a record from a new file to the corresponding listing in the shop.
Suppose a supplier renames a lamp from Nord 10 to Nord 10 White. An import matching products solely by title could create a duplicate listing. If the SKU stays the same and the importer is configured to match against it, the existing product can be updated instead. Different colour variations should have their own identifiers whenever they are accounted for separately.
Multiple suppliers may use identical item codes for completely different products. Before combining their feeds, check for collisions. One solution is to use a supplier identifier together with the original product code as the unique import key. Preserve the manufacturer's reference separately so that staff can check the corresponding technical documentation whenever a customer has a question.
Import quality depends on source preparation, not just product count. 3. Categories, attributes and product variations
Categories help customers navigate the catalogue, while attributes allow them to filter and compare products. Create a logical structure before importing, such as Furniture, Chairs and Office Chairs. Colour, material and maximum load should usually be separate attributes if they are needed for search and filters, rather than being embedded in a generic description.
A variable product brings related options together on one product page, where the customer selects a size, colour or another option. Individual purchasable variations can have their own SKUs, prices and stock quantities. If the supplier's file contains only a general product description, without clear links between the actual variants and their stock, that structure needs to be established first.
Imagine a clothing retailer selling one T-shirt in three colours and four sizes. There is no need to create twelve unrelated product pages if the products can be organised as one variable product. Only combinations actually available should be included. A black XL shirt being unavailable should not automatically make every other size and colour unavailable too.
4. Images, documents and descriptions
Product image imports require valid files or accessible image URLs. The WooCommerce CSV importer supports image URLs in its documented format. Before loading the entire catalogue, verify that those links actually return images, rather than a login page, expired download or an error response.
A large catalogue with several images per listing can require substantial hosting storage. Optimise images to a suitable resolution and inspect the quality after compression. When the same gallery is used by multiple variations, consider how media can be reused instead of repeatedly creating unnecessary copies. Image rights and credits also need to be addressed during the planning stage.
Technical PDFs, size charts and instructions may be more valuable than marketing descriptions for specialist products. Decide which documents may be published and how updated versions will be handled. Descriptions should be useful for the intended customer, rather than merely reproducing supplier content that might be incomplete or unsuitable for retail visitors.
5. Cleaning and preparing the spreadsheet
Check encoding, separators, column names, number formats, units of measurement, currencies, missing fields and duplicate records. Prices need to be interpreted as numeric values under agreed rules. A weight expressed in grams cannot simply be written unchanged to a field configured to use kilograms.
The shop structure does not have to mirror the supplier's spreadsheet. Mapping rules can assign a supplier group to a store category, turn brand names into attributes and standardise values such as white, White and WHITE. This prevents filters from displaying multiple versions of the same colour or material simply because the source uses inconsistent wording.
Distinguish missing values from genuine zero values. An empty stock field may indicate that information has not been supplied, whereas zero usually means that an item is out of stock. Handling these situations identically without an explicit rule can accidentally change the availability of thousands of products.
6. Built-in importer or dedicated integration
WooCommerce offers a built-in product CSV import and export tool. It is a practical option for standard product fields and one-off transfers when the data can be prepared in the required format. Start by manually creating a few representative listings, exporting them and using the export as a template for the supplier data.
More complex XML feeds, recurring files from several suppliers or custom processing rules may require an additional plugin such as WP All Import or a dedicated integration. The decision depends on the data structure, update frequency and required flexibility. Additional extensions and maintenance can involve costs, so include them in the project estimate.
At CianBay Studio, our work has included the Casecomponents.com.ua catalogue with around 650 items and preparing structured product data for Penn-Elcom items. In these situations, importing the basic description and images is only part of the job. Specifications also need to be organised so buyers can find compatible components. Our data import service covers this kind of project.
7. Test before importing the full catalogue
Avoid beginning with the entire feed. Select a representative sample containing a simple product, a variable product, a discounted item, an out-of-stock item and a product with multiple photographs. A staging copy of the site allows these cases to be tested without affecting real customer orders.
After importing, inspect the result outside of the administration panel. Visit the catalogue, check categories, search, attributes, filters, variations and displayed prices, then test adding products to the basket. Repeat the import with the same file and then with changed values. The item count should not increase because of duplicates during a normal update.
Each stage is checked before a full catalogue import. A large import can be split into manageable batches. This makes errors easier to investigate, limits server load and simplifies checks. Appropriate batch sizes depend on available hosting resources, media volume and the processing required. Test them rather than assuming the same configuration will work on every hosting plan.
8. Automating updates to prices and stock
After the initial import, determine which fields need recurring updates. These typically include prices, quantities, availability and sometimes new products. Manually improved descriptions, SEO titles and original photography may remain under the retailer's control and should not automatically be overwritten.
Suppose a supplier provides a new spreadsheet each morning. The shop can run an import on a schedule and apply a defined pricing formula. Where several currencies are involved, agree on exchange-rate sources, rounding, taxes and minimum price rules. Unexpectedly large changes should be reviewed before being published, particularly if a supplier has accidentally changed a column format.
A product missing from the source is not always a discontinued product. The source might be temporarily incomplete. A safer approach may be to mark the affected items unavailable after verification, rather than deleting their URLs and important catalogue information. An unavailable data source should trigger an alert, not automatically set every product to zero stock.
9. Monitoring, backups and ongoing maintenance
Every recurring import should have useful execution logs. Staff need to know when the last successful run occurred, how many items were created or updated, what errors occurred and where the information came from. An unexpected drop in file size or a change to its schema should prompt investigation before the shop is changed on a large scale.
Create a backup of the database and files before major imports. On a live store, restoring an old database without further planning can destroy recently created orders. The recovery procedure should account for which product information needs restoring and how to retain transactions created after the backup.
Assign responsibility for catalogue integrity: checking stock discrepancies, correcting category mappings, approving unusual price changes and responding to data failures. Automation reduces repetitive tasks but does not remove the need for supervision. This is especially important when the store combines product data from several independent suppliers.
For example, one supplier may provide exact warehouse quantities and another may simply indicate whether an item can be ordered. These are not necessarily equivalent. The storefront might distinguish ready-to-ship inventory from items with a lead time requiring confirmation. Document the meaning of each status and the source of each field so that a new supplier or maintenance provider can work with the existing integration reliably.
10. What determines the cost of a product import?
Product count is only one consideration. A clean CSV containing a thousand standard products may be easier to process than a spreadsheet with a hundred variable products, diverse technical attributes and inconsistent data formats. Preparation, mapping, media, testing, update frequency and custom integration requirements all influence the cost.
For a simple one-off transfer, the standard WooCommerce tools may suffice. For more complex projects, separate the initial import from scheduled synchronisation. This makes it possible to verify the catalogue before enabling recurring updates. Future changes to the supplier's file structure may require separate adjustment of the integration.
It is equally important to plan the storefront itself. Effective filters, SKU search, mobile presentation and clear navigation are necessary regardless of how the products were entered. We develop WooCommerce stores and product catalogue websites with those requirements in mind. Our comparison of catalogues and online stores explains which format might suit the business.
Multilingual stores need an additional plan for translating descriptions, categories and attributes and linking their language versions. The stock and price of the same physical product need to remain consistent, but not every text field should be copied into translated listings. Test this arrangement with a few representative items before importing hundreds of records. A successful project should include documentation for future updates, so the next price list does not require a complete redevelopment of the integration.
Frequently asked questions
Can I import products from Excel?
Yes. For the built-in WooCommerce importer, the spreadsheet is generally prepared as a CSV file. Additional import solutions may support other formats. Preserve product identifiers as text when required, especially when they have leading zeros, and verify the column mapping.
Can I automatically update only stock and prices?
Yes, if the data source has reliable product identifiers and the importer is configured to modify only the required fields. Test repeated updates and establish rules for missing and zero values before enabling scheduled synchronisation.
Do I need to download all product images again every time?
Not necessarily. When images have not changed, configure the import to update only the intended data. This can reduce server load and the risk of unnecessary duplicate media files.
How to scale a WooCommerce catalogue without manual data entry
A well-designed product import turns a catalogue into a manageable business process rather than a collection of repetitive manual tasks. Stable identifiers, clean data, realistic tests and controlled updates make it possible to expand the product range safely. In 2027, this is a practical foundation for businesses looking to scale sales through a store they own.
Sources and documentation
- WooCommerce: product CSV importer and exporter
- WooCommerce: migrating products
- WP All Import: CSV and XML product imports
- WP All Import: unique identifiers
Originally published at CianBay Studio.
Disclosure: This article was prepared with AI assistance.
