Product configuration

Choose the setting

Both screens offer Add and Edit. Neither controller implements a delete action. Inspect the existing rows before adding another mapping; the forms are not a validation of the business choice.

What changes after saving

Private label feeds classification. A new classifier reads the current brand memberships and uses them to set private-label flags. Saving the form does not reclassify historic transactions or recalculate their margin. To apply a change to history, identify the affected dates, reclassify them, and let calculation follow. Refresh expected margin separately if its amount guard would keep an old result. See recalculate margin.

Size mappings are stored configuration. The current repository lists and edits them but has no pipeline reader applying them to classification or margin. Do not expect a size edit to change a transaction figure. Size choices themselves come from config/reference/productsizesoptions.json and are reloaded by the installer.

The memberships and category mappings survive a deploy. They are different from reference choices that the installer replaces. See configuration and boundaries.

Verify an edit

Reopen the listing and check the saved category/option or brand. For a private-label correction, check a representative transaction's flag after reclassification, then verify any rule whose filter uses that flag. A saved mapping proves persistence, not downstream recalculation.

Related

• Products
• Classifications
• Learn from existing rules

Evidence

Code-checked: app/http/configuration/productsizes.php, productprivatelabel.php, their templates, app/models/products.php::getproductsizes(), app/models/classify.php and app/jobs/install/install.php. Repository references to productsizes are its installer, listing and editor; no calculation consumer is present.