Improved unit price import and exports

Unit price imports just got simpler. You can now use individual columns for each unit price field instead of dealing with JSON formatting.

🚀 What’s New

#

• Separate columns – use dedicated columns for Unit Price Total Measure, Unit Price Total Measure Unit, Unit Price Base Measure, and Unit Price Base Measure Unit.
• Export field group – select the new Unit Price Columns group when creating product exports to get the separate column format.
• Clear unit prices – set either measure value to 0 to remove unit pricing from a variant.

🔧 Improvements

#

• Backwards compatible – the original JSON format in Variant Unit Price column still works exactly as before.
• Pre-import validation – file analysis now validates separate column values before import starts.
• Better error messages – new error code PRD031 helps identify issues in the separate columns, while PRD019 covers JSON format errors.

📝 How It Works

#

Instead of JSON:

{
  "quantityUnit": "G",
  "quantityValue": 500.0,
  "referenceUnit": "KG",
  "referenceValue": 1
}

Use separate columns:

Both formats are supported in the same import file. If both the JSON column and separate columns have values for the same row, the JSON column takes priority.