Guide

Review import history and resolve conflicts in bulk

Find what every past import did, open its row-by-row report, and settle a whole catalogue of held values in one action.

What your last import did

Every import you run is kept. On Settings → Import Data, each section lists its most recent runs underneath the upload card: the file, who ran it, when, and what it changed — how many rows applied, how many said nothing new, how many were rejected, and how many values were held for review.

Open a run to see its full report. The receipt names every row Skuvelo could not apply, with the reason and the line number in your own spreadsheet, so you can correct those rows and upload them again without re-uploading the file.

Nothing is deleted when you run another import. A weekly upload leaves a weekly trail.

Why a value is held instead of applied

Skuvelo keeps one item master across every channel you sell on, so two sources can disagree about the same field. Your field precedence rules (Settings → Field precedence) decide who wins each field. When the incoming value loses, it is not thrown away and it is not applied — it waits in Import conflicts with both values and where each came from.

A value you typed in yourself always outranks an automatic one, and only another person can replace it.

Clearing the queue in one action

Open Import conflicts from the Products screen, from an item, or from the link on Import Data. The queue holds every open conflict in your catalogue, not one item's.

Narrow it first. Filter by field ("just cost"), by where the incoming value came from ("just the spreadsheet"), or search a SKU or product name. The line under the filter tells you how many conflicts match.

Then tick the ones you want — or tick the header box to take the whole page — and choose one of three decisions:

  • Keep current leaves your values as they are and closes the conflicts.
  • Take incoming applies the waiting values.
  • Apply my precedence rule settles each one by your own field precedence rules as they stand today. A field someone typed in by hand stays as it is, because a rule never overrules a person.

When more conflicts match your filter than fit on one page, tick Apply to all N matching this filter before choosing, and the decision reaches every one of them.

Skuvelo reports back per row: how many took the incoming value, how many kept the current one, and how many somebody else had already settled while you were looking. Each decision is written to your activity log exactly as a one-item decision is, so the trail is the same either way.

A read-only role can read the queue and cannot resolve anything.

If the numbers do not look right

See Fixing a failed or partial spreadsheet import for what a partial import means and how to correct only the rows that failed.

Try the plan on your own stock.

Start a trial with your own sales and stock, or look around the live demo first.