Sort the results and pass the file to the Converter

The case: the scraping of Atelier Démo's sweaters read some products, a few of them without a price. You want to sort them, then prepare a file for a WooCommerce shop.

Read the Results screen

The results open with View results on the end screen, or with Results on the row of a job that ran to the end in Jobs; a stopped job offers Resume there instead. Results, in the left bar, lists the latest jobs that have products as long as you have opened none; after that, it reopens the last results you opened.

The table gives, for each product, its price, a reason when it is not accepted, and its status in words. Clicking the name opens its details: fields read, variants, and View source to the original page. The filters above count the products: All, Accepted, To review, Excluded. The most common reasons:

• Incomplete data (name or price missing).: the product is to review.
• Manifestly invalid data (no name and no identifier).: the product is excluded and goes into no CSV.

Decide on the products to review

1. Click the To review filter. The screen becomes Products to review.
2. For each product, click Accept or Exclude.

Each decision rewrites the job's CSV files, and Decision saved. confirms it. An accepted product moves to the main CSV; accepting does not fill in a missing price, the cell stays empty. An excluded product is in no CSV any more. These buttons only exist in this filter: a product already accepted cannot be excluded from the screen.

Open and find the files

The Scraper saves the files itself, at the end of the job and after each decision: there is nothing for you to save. They are kept in the Data folder, shown in Settings, Files & browser card:

• csv\<id>.csv: the accepted products, one row per product and one image each, comma-separated, UTF-8 encoded. Open CSV opens it with the program Windows uses for .csv files.
• csv\<id>-to-verify.csv: the products still to review, if any.
• jobs\<id>\products.json: every product of the job, whatever its status, with all its images, the crossed-out price and the reference when the site gives them. A manifest.json file next to it says what the job contains and whether every product page was read; the CSV has its own, ending in .manifest.json.
• reports\<id>.txt: the report, which Report opens.

The id is the name of the CSV file, shown below the buttons of the end screen. To keep a copy elsewhere, copy the file from Windows File Explorer.

Pass the file to the Converter

1. In Eloshon Converter, pick Eloshon Scraper as the source and WooCommerce as the destination.
2. Drop the job's file: the CSV, or products.json.
3. Follow the Converter's steps up to the export: Products: Shopify to WooCommerce.

Which file to choose: the CSV only holds the accepted products, with a single image each, without a crossed-out price or a reference. products.json keeps all the images, the crossed-out price and the reference, and it is the file the Converter recommends. It also holds the products to review or excluded: the Converter writes those with a name as unpublished products, and leaves out those without one.

The Converter also reads a weight written the way it is on the label (“4x90g”), cleans up the SEO title and description, and tells you before the import what you should check: Eloshon Scraper files: weight, SEO, dimensions.

The Converter writes the import file; the import itself happens in your shop, according to its official help. For another platform: Products: WooCommerce to Shopify, Products: Shopify to Wix, Products: Shopify to BigCommerce. All of the Converter's help: Eloshon Converter help.

Check

Once everything is decided, the To review filter shows Nothing to review., and the -to-verify.csv file is no longer in the csv folder. The main CSV then has one row per accepted product.