Product import for WooCommerce stores.

We assess CSV, Excel and XML files, as well as documented supplier APIs. The built-in WooCommerce importer uses CSV; Excel data needs conversion, while XML or API sources may require a suitable plugin or custom integration. We choose the method after reviewing a sample rather than assuming every format can be loaded directly.

Yes, subject to the source data and the store's server capacity. A catalogue with many variations or large images takes more work than the same number of simple products. We test a sample, check resource limits and use suitable batches where needed. We estimate the duration after reviewing the actual catalogue and environment.

Yes, if the images are accessible and clearly linked to products. We check representative URLs, file formats and the order of the main image and gallery. Links requiring login or pointing to a preview page may need another approach. Image alt text is a separate field or task; the core WooCommerce CSV importer does not manage it.

Yes, where the source identifies parent products and their variations. Each variation needs suitable attributes and its own identifier, price and stock where applicable. We test products with several combinations to check selection, availability and basket behaviour. A flat list of colours without relationships may require preparation before it can become a working variable product.

Send the file as it is, preferably with a small representative sample. We will identify the changes needed: consistent column names, stable SKUs, category hierarchy or image references. Leading zeros, decimal separators and character encoding also matter. We explain what can be converted automatically and what needs a decision from your team before import.

Yes, if products can be matched reliably. We configure selected-field updates and exclude your own descriptions, images or other fields that should remain unchanged. The same rule applies to variation records. We also agree what empty values mean, so a missing price or stock quantity in the supplier file does not automatically overwrite valid store data.

We can assess scheduled imports from a suitable CSV, XML or API source. We agree the update interval, matching rules, field ownership and error handling. A scheduled feed is not necessarily real-time synchronisation: the delay depends on the supplier and the agreed frequency. Plugin licences, hosting requirements and ongoing monitoring are discussed before implementation.

Send your store address, a representative data sample, approximate product and variation counts, and the fields you want to create or update. Mention existing manual content and any supplier documentation. Tell us whether this is a one-off transfer or a repeating process. We then clarify the missing information and provide an estimate for the agreed scope.

We agree a stable matching key: a SKU, an existing product ID or a mapped source identifier. Before repeating an import, we test matching for products and variations. A product name alone is not a reliable key. We also define how to handle new records or changed identifiers, rather than deleting and recreating products as a default response.

Yes, where those fields are excluded from the agreed update mapping. Rank Math, ACF and other plugin fields require a separate compatibility check; they are not automatically part of the standard CSV structure. We inspect a small sample before launch and verify both updated and preserved fields. Supplier descriptions should not overwrite your own content without agreement.

We agree the policy before automation. A missing item may mean discontinued stock, an incomplete file or a feed failure. It should not automatically delete your catalogue after one unsuccessful run. We can assess rules for changing stock or status after agreed checks. Empty and partial feeds need separate handling from confirmed product unavailability.

Before a full run, we check backups and recovery arrangements, assess a test environment and agree timing. Afterwards, we compare created and updated record counts with the source, review the log and inspect representative products. Currency, tax classes and price calculations follow the agreed store rules. Any discrepancies are resolved before the process is approved for recurring updates.