How-to guide
Unblock the export when an error stops the Review step
At the Review step, the button to continue stays greyed out while a blocking problem is not fixed. Here is how to find it, fix it in the Converter or in your file, then export.
Checked against the software on November 1, 2026
Example: Atelier Démo converts 60 products from Shopify to WooCommerce. At the Review step, the red banner shows “Export is blocked: 2 blocking problem(s) to fix.”: one product has no name, and two mugs share the SKU TASSE-BLEU.
Why the export is blocked
The Converter only blocks what would prevent a product or a customer from being created in the new store. The rest (missing price, empty description, negative stock…) stays a warning or a piece of information: it does not prevent the export.
| Message shown | When | Target platform |
|---|---|---|
| Product has no title: it cannot be created. | A product has no name in your file. | All |
| Duplicate SKU “TASSE-BLEU”: the target may overwrite or reject this product. | Two products or variants carry the same SKU: the second one is flagged. | WooCommerce and BigCommerce. To Shopify and Wix, it is a warning. |
| Customer has no e-mail: it cannot be created. | A customer has no e-mail address. | All |
Find the problem
- At the Review step, click the Blocking tab above the table.
- In the Line column, note the row number: it is the row’s number in your file, as a spreadsheet shows it, the row of column names being row 1.
- If the number is followed by an asterisk, read the sentence under the table: “*: the product’s first row in your file; the problem may come from another of its rows, such as a variant.”
Fix it in the Converter
- On the problem’s row, click Fix.
- In the Fix the value window, type the value in the New value field: the product’s name, another SKU (for example TASSE-BLEU-2) or the customer’s e-mail.
- Click Save: the Converter runs the conversion and the review again.
- Repeat for each blocking problem, then click Continue.
The value is changed in memory; your original file is never touched. The Ignore button is not offered for a blocking problem: it only serves warnings and information.
Fix it in your file, or work around it
- Fix the product or the customer in your old store, export again, then drop the new file at the File step. This is the right way when many rows are concerned.
- For a duplicate SKU, choosing Shopify or Wix as the target no longer blocks the export: the problem becomes a warning. The file written will still hold two identical SKUs.
- A customer without an e-mail cannot be created: if you have no e-mail to give, remove that customer from your file before you drop it.
Known limit
The review at the Review step looks at your file with the corrections made through Fix. It does not yet take into account Edit the data, Edit the output file or the SKU generator: a name added by a transformation may therefore still be flagged. In that case, fix the value with Fix.
Check that it is solved
- The green banner shows “No blocking problems. Warnings do not prevent export.”
- The Continue button is available and leads to the Export step.
Other stops, outside the Review step
- Orders to Wix or BigCommerce: the refusal does not come when you drop the file. “Wix imports products only by CSV (no orders).” or “BigCommerce has no order CSV import.” appears later, at the latest when you click Export. Start again with Shopify or WooCommerce as the target.
- Orders with no line item read: “Order with no line items.” appears, at the latest in the The conversion stopped window when you click Export. An order without line items is never written; check that your file holds each order’s line items: one row per line item in a Shopify or BigCommerce export, the
item_namecolumn in a WooCommerce export. - A failure to write the file, for example a folder that already carries the file’s name: the The conversion stopped window shows “Unrecognized format.” today, followed by a technical detail. This message is wrong: your file was recognised. Change the folder, or change the File name field, then export again.