Thousands of items. One run.
Select the products, choose the fields and see exactly what will change before you run it. Every run is logged as a job and can be rolled back in full.
Select the set. Choose the field.
Steps 1 & 2
| Item | Artikelnr | Skötselråd NO | Komplett | |
|---|---|---|---|---|
| Shell Tech Jacka | APP-221 | — | ||
| Softshell Vest Light | APP-330 | — | ||
| Fleece Halfzip Nord | APP-076 | — | ||
| Regnjacka Kust 3L | APP-402 | Vask 40° | ||
| Vinterparkas Bore | APP-511 | — | ||
| Arbetsjacka Vinter HD | WRK-512 | — |
The selection uses the same filters as the product list, so what you see in the list is what runs.
Before → after, row by row.
| Artikelnr | Field | Innan | Efter | Resultat |
|---|---|---|---|---|
| APP-221 | Skötselråd NO | — | Maskinvask 40°, ikke tørketrommel | Will change |
| APP-330 | Skötselråd NO | — | Maskinvask 40°, ikke tørketrommel | Will change |
| APP-076 | Skötselråd NO | — | Maskinvask 40°, ikke tørketrommel | Will change |
| APP-402 | Skötselråd NO | Vask 40° | Vask 40° | Skipped |
| APP-511 | Skötselråd NO | — | Maskinvask 40°, ikke tørketrommel | Will change |
| APP-518 | Skötselråd NO | — | Maskinvask 40°, ikke tørketrommel | Will change |
What you can do in bulk.
Actions
Set a value
Write the same value across the whole selection, choosing whether filled fields are overwritten or skipped.
Find and replace
Change part of a text across every selected item — unit labels, brand names, misspellings.
Add to a list
Extend multi-choice attributes without losing existing values — certifications, for instance.
Recalculate numbers
A percentage or fixed adjustment to numeric fields, such as cost price or weight.
Move category
Change category or add a secondary placement across the whole selection.
Publish or unpublish
Release the selection into a channel, or pull it, with a completeness check before the run.
Hard to get wrong
The preview shows before and after per row
Fields owned by the ERP are locked in the selection
Completeness rules stop half-finished products publishing
Permissions per attribute group govern who may run it
Everything is traceable
Every job gets an id and a row in the activity log
The whole run can be rolled back for 30 days
Errors are reported per row and the rest of the job continues
The same actions exist in the API for scheduled runs
Questions about bulk editing.
Common questions
How many items can one run handle?+
The whole catalogue. The job runs in the background with per-row status, so you can keep working while it goes.
Can we roll back a bad run?+
Yes. The job stores the previous values and can be rolled back in full for 30 days. Individual rows can be restored from the activity log.
Can it run across several languages at once?+
Yes. You choose which languages and channels the change applies to. Fields with no value in one language can be filled without touching the others.
Can bulk edits be scheduled?+
Yes, through the API. A saved selection plus an action can run on a schedule — a price adjustment at month end, for example.
Who is allowed to run bulk changes?+
Permissions are set per attribute group and channel. An editor might be allowed to change copy but not prices.
Pick a field you never get round to filling.
We run it on an extract of your catalogue during the demo and show the preview before anything saves.