Value Changes let you change a CSV value before 3Dsellers writes it, on any field of any CSV import or update. Remove the "SC" a supplier puts in front of every SKU, turn "$65" into a price with a 10% markup, capitalize titles or strip HTML from descriptions, all without editing the file first. Each change is an ordered list of steps on one field, with a live preview of the result for the selected row.
Value Changes are available on every CSV import in 3Dsellers, in both the Listings Manager and the Products Catalog, and the same steps can be sent through the 3Dsellers Public API and MCP tools.
⭐ Value Changes replace the old "SKU prefix / suffix" row of the Update Inventory import. Anything that row did is now a Value Change on the SKU column, plus 19 more operations on any field.
In this article:
Where do I find Value Changes?
Open any CSV import in 3Dsellers and upload your file. At the end of every mapped row in the mapping table there are now two buttons: the funnel (Import Filters, which decides which rows are imported) and a pen (Value Changes, which decides what value is written).
The pen is also on the single-column pickers of the simpler imports: the SKU Column row of Update Inventory, and the SKU and New SKU rows of Replace SKUs. It is greyed out while a row is set to "Don't import", because there is no value to change.
Every change you save is listed as a chip on the Value Changes line, directly under Import Filters, with the note "Values are changed after filtering and before they are written."
How do I change a value?
Map the column as usual, then click the pen at the end of that row. The "Change value" popover opens and names the 3Dsellers field and the CSV column it reads.
Pick an operation in the dropdown. It has two groups, Text operations and Number operations, and every field offers both because 3Dsellers cannot know in advance whether a column holds text or numbers.
Fill in what the operation needs: the text to add or remove, the text to find and its replacement, or the number to multiply, add or increase by.
Click + Add step for a second operation. Steps run in order, from top to bottom, each one on the result of the one before.
Check the result line. It shows the file value for the row selected in the Preview column ("Preview uses Row 1") and what will be imported for it.
Click Save. A chip appears on the Value Changes line, the pen on that row is filled in, and the Preview column shows the file value struck through with the new value in green.
To edit a change later, click its chip or the filled pen on the row. To remove it, click the x on the chip, or open it and click Remove change.
Which operations can I use?
Text operations (14)
Add prefix and Append text (suffix) add text to the start or the end of the value.
Remove prefix and Remove suffix take text off the start or the end, only when the value actually starts or ends with it.
Find and Replace replaces plain text (not patterns), with optional Match case and Whole word.
Capitalize only first character, Capitalize first character per word, Lowercase all characters, Capitalize all characters.
Remove non-numeric characters keeps digits, the decimal point and a leading minus, so "$65.50" becomes 65.50. Use it before a number operation on a price column that carries a currency sign.
Remove digits, Remove linebreaks (line breaks become a space), Remove HTML from text, Trim spaces.
Number operations (6)
Multiply, Divide, Add, Subtract, Increase by %, Decrease by %, each with the number to use.
As soon as a change has a number step, two extra controls appear under the steps: Result (Don't round, the default; Round to 2 decimals; Round up; Round down) and an End with .99 checkbox. Both apply once, after the last number step.
A number operation on a value that is not a number is skipped and the value stays as it is. The result line says "Not a number, number step skipped" so you can see it before importing.
In what order do filters and changes run?
Import Filters and Value Changes work together on every import, and the order is fixed:
Import Filters check the original file value. A filter such as "SKU starts with SC" is evaluated against the text as it is in the CSV, before any change.
Value Changes run on the rows that passed, after filtering and before the value is written to 3Dsellers.
⚠️ A change on the key column (SKU or Item ID) changes the value 3Dsellers uses to match the file row to your listings or products. That is exactly what you want when the supplier's SKU differs from yours, but a wrong step here means no rows match and nothing is updated. Always check the result line on a real row before you start the import.
A change applies only to the field it is set on. If one CSV column feeds two fields, for example a "Supplier Cost" column mapped to both Cost and Price with +30% on Price only, Cost keeps the file value.
Examples
The supplier's SKUs have an extra prefix
The stock file says SCMN1107M and your listing is MN1107M. On the SKU row add one step, Remove prefix with the text SC. The result line shows SCMN1107M becoming MN1107M, and the import now matches your listings.
The supplier's price has a currency sign and needs a markup
The file says $65 and you sell at 10% above cost, rounded up to a .99 price. On the Price row add Remove non-numeric characters, then Increase by % with 10, set Result to Round up and tick End with .99. The result line shows $65 becoming 71.99. Without the rounding and the .99 ending, Remove non-numeric characters followed by Multiply by 1.1 turns $65 into 71.5.
Clean up titles and descriptions
Add Trim spaces and Capitalize first character per word on the Title row, and Remove HTML from text on the Description row, to import a plain, tidy version of a messy supplier feed.
Saving changes with a preset or a schedule
Value Changes are saved with a Mapping Preset, together with the mapping and the Import Filters. Select the preset next time and the chips come back.
A scheduled import carries its Value Changes on every run, so a recurring supplier feed keeps stripping the prefix or applying the markup without anyone opening the file.
Value Changes in the Public API and MCP
Everything the pen does in the app is available to API and AI-agent users through the 3Dsellers Public API and its MCP server, so a supplier feed set up by code or by an agent can use the same steps.
create-import-csv, create-import-schedule and update-import-schedule accept a valueChanges object. It is keyed by the target field name (SKU, Price, Title and so on) or by item_id_column for the key column, which then changes the value the rows are matched by.
Each entry has ordered steps using the same 20 actions as the app: add_prefix, add_suffix, remove_prefix, remove_suffix, find_replace (find, replace, match_case, whole_word), capitalize_first, capitalize_words, lowercase, uppercase, remove_non_numeric, remove_digits, remove_linebreaks, remove_html, trim, multiply, divide, add, subtract, increase_percent and decrease_percent. Text steps take text, number steps take value. Optional round (none, two_decimals, up, down) and charm_price (end with .99) apply once after the number steps.
get-import-catalog returns the full list of actions as valueChangeActions, so an agent can discover them instead of guessing.
On a schedule, sending valueChanges replaces the stored changes as a whole, sending an empty object clears them, and leaving the field out keeps what is stored. A step that is wrong, such as multiply without a numeric value, is rejected with a 400 error that names the exact path.
Removing the "SC" prefix from the example above looks like this on create-import-csv:
{
"action": "node_all_inventory_update",
"sellerId": 12345,
"keyColumn": "SKU",
"valueChanges": {
"item_id_column": {
"steps": [{ "action": "remove_prefix", "text": "SC" }]
}
}
}And a 10% markup rounded up to .99 on the Price field:
"valueChanges": {
"Price": {
"steps": [
{ "action": "remove_non_numeric" },
{ "action": "increase_percent", "value": 10 }
],
"round": "up",
"charm_price": true
}
}⚠️ Two gaps for API users today. The dryRun of create-import-csv shows the raw file values in its sample rows, not the changed ones, so it does not preview a Value Change. And Import Filters are not part of the MCP import tools, so a feed that needs to skip rows still has to be filtered in the file or set up as a schedule in the app.
Limits
Value Changes work on the value in the CSV row only. They do not read or change anything already in 3Dsellers.
An empty cell stays empty, so the mapping Fallback still applies. A change that empties a value shows "(empty)" in the result line and also falls back.
Find and Replace matches plain text. Patterns and wildcards are not supported.
Rounding and End with .99 only appear, and only apply, when the change has a number step.
On the Update Inventory import the SKU Column row has no Preview cell, so a change on it is visible only inside the pen popover.
Troubleshooting
The import ran but no listings or products were updated
A change on the SKU or Item ID column rewrites the value used for matching. Open the pen on that row and check the result line against a SKU you know exists in 3Dsellers. A prefix typed with the wrong case, or an extra space, is enough for every row to miss.
My number operation did nothing
The value was not a number when the step ran, so it was skipped. If the column carries a currency sign, thousands separator or text, put Remove non-numeric characters before the number step.
The pen button is greyed out
That row is set to "Don't import". Map the column to a 3Dsellers field first, then the pen becomes available.
I cannot find the SKU prefix / suffix box on Update Inventory
It was replaced by Value Changes. Click the pen on the SKU Column row and add an Add prefix or Append text (suffix) step. If you still see the old box, reload the app with a hard refresh so your browser loads the current version.
FAQ
Do Import Filters see the changed value or the original one?
No, Import Filters always check the original value in the CSV. Value Changes run afterwards, on the rows that passed the filters, and only then is the value written.
If one column is mapped to two fields, does a change on one affect the other?
No, a Value Change belongs to the field it was set on. The other field mapped to the same column keeps the file value, and the Preview column shows both.
Are Value Changes saved in a Mapping Preset?
Yes, a preset stores the mapping, the Import Filters and the Value Changes together, and scheduled imports keep them on every run.
Can I use Value Changes to match SKUs that differ from the supplier's?
Yes, that is the main reason the feature exists. A change on the SKU or Item ID column is applied before matching, so removing or adding a prefix makes the supplier's SKU line up with yours.
Can I set Value Changes through the API or an AI agent?
Yes, the Public API and the 3Dsellers MCP tools create-import-csv, create-import-schedule and update-import-schedule take the same steps in a valueChanges object, and get-import-catalog lists the available actions.
Do Value Changes work when creating new listings or products, not only when updating?
Yes, the pen is on every CSV import, including Create new products, Bulk Upload to drafts and Replace SKUs, as well as the update imports.