Price and stock updates from the supplier’s file, with every change shown first.

Yes, if it is an Excel, OpenDocument or CSV file. You map its columns once, when you set up the configuration: a new one picks the columns whose names match a field and uses your SKU column as the record ID. A list can be as plain as SKU, price, sale price and stock, because a product that exists keeps its name and everything else the list does not set. Prices are read as the file writes them, with a decimal comma or a decimal point and with or without a currency symbol. A number that could mean two things, such as 1,299, is not guessed at: you say how the file writes numbers, or the row is refused with the reason.

The file stops before any row is read. The page says “This file doesn’t match the configuration”, lists the missing columns with the fields that use them, and nothing is processed. Rename the column back in your spreadsheet, or choose “Update mapping for this file” to point the field at the new name: the file is then checked again without a new upload. A column the supplier adds is harmless and is listed as not used. A column that disappeared since the last file always asks for a tick before publishing, even when everything required is there.

The review of the next list shows it. For every price, sale and stock quantity the list sets, it reads the shop, and a product whose value there differs from the list is shown as “On the site now” against “This file”. By default publishing puts the file’s value back, because the shop is meant to end up as the list says. For a field you can choose to compare only with the last list instead, so that a number changed on the shop stays until the list’s own number changes.

Not for a clean list. A configuration can publish a file on its own when nothing needs a person, and whoever uploaded the file is emailed that it was published. A list with a row that has an error, a price that moves too far, or the first list after any change waits for review, and that person is emailed that it needs them. A person still uploads each list: nothing is fetched or scheduled.

Only the products a list actually changes count. A record write is one item created or updated on your shop. Checking, previews, products that already match, skipped items, rows with errors, failed attempts and retries are free, so a list in which most products are unchanged uses a write only for each one that changed. The button “Publish N changes” tells you exactly what a run will use before you press it, and what each plan includes is on the pricing page.