Bulk setup / data upload

Mass product, price and availability configuration from a validated file — Product Module F-A-21 (P3).

All-or-nothing

If any row fails, nothing is written. A part-applied price file leaves rows that are indistinguishable from deliberate configuration, which is harder to unpick than a rejected upload.

Column set is ours

F-A-21 is a single line — “mass product/price/bundle configuration via validated file upload” — and the spec's own assumption A-10 records it as P3, not required for the demo core, cut-line still open. So which columns exist and what counts as valid are our decisions, not written requirements.

Order matters

Prices and availability reference products by id, so upload products first. Each file is validated against what is already in the database, not against the other files in the same session.