Personalization
The storefront concern of the buyer-supplied made-to-order custom INPUTS an offer collects — the input SLOTS a listing exposes for the buyer to fill: a field's buyer-facing label, the data-kind of input it takes (a line of text, a number, a date, an uploaded image), whether it must be filled, and any length limit. The orthogonal concern axis (L6), never a product kind. It holds the field DEFINITIONS (grammar — the slot), NEVER the buyer's entered value: the actual engraved text, the uploaded photo, the chosen font are realised line-item data held downstream (L1), not pool values. Distinct from `variation` (a seller-defined axis whose cells the catalogue prices and stocks as separate SKUs — colour, size) and from what the product IS (Axis K): an engraving field creates no SKU and adds no product kind; it is a per-order input the offer captures.
1 question in all: 1 free-text or code field (personalization field).
The storefront concern of the buyer-supplied made-to-order custom INPUTS an offer collects — the input SLOTS a listing exposes for the buyer to fill: a field's buyer-facing label, the data-kind of input it takes (a line of text, a number, a date, an uploaded image), whether it must be filled, and any length limit. The orthogonal concern axis (L6), never a product kind. It holds the field DEFINITIONS (grammar — the slot), NEVER the buyer's entered value: the actual engraved text, the uploaded photo, the chosen font are realised line-item data held downstream (L1), not pool values. Distinct from `variation` (a seller-defined axis whose cells the catalogue prices and stocks as separate SKUs — colour, size) and from what the product IS (Axis K): an engraving field creates no SKU and adds no product kind; it is a per-order input the offer captures.
| personalization fieldhost · carries 3 | “free text |