Fields & choices

The question types Print Options offers, how each one can be displayed, and how to show or hide fields based on earlier answers.

An option set is made of sections, and each section holds fields — the individual questions your customer answers.

Field types

Type	Use it for
Single choice	Pick exactly one — paper, finish, binding.
Multiple choice	Pick any number — extra finishes, add-ons.
Quantity	Copies or print run. Drives all per-unit pricing.
Quantity per option	A count for each option, such as the sizes of a T-shirt run. The total is the quantity.
Number	Any free numeric value, like page count.
Text	Customer-entered text, such as a job reference.
Dimensions	Width × height, for area, length and formula pricing.
File upload	Artwork or documents — see Artwork uploads.
Info / summary	Not a question: a static note, or a live recap of everything chosen.

One quantity is in play at a time. It is what “per unit” pricing multiplies by, so the stepper, the summary and the price can never disagree. You can still have several Quantity fields when each has a visibility rule, so that one shows at a time: see Quantities & size runs.

Choosing how a field looks

The Display setting changes the control without changing the data:

• Single / multiple choice — Pills, Image cards, Image grid, Color swatches, Dropdown, or List.
• Quantity — Stepper, Preset pills, Preset dropdown, or Plain input. Presets are ideal for print runs: 100 / 250 / 500 / 1000.
• Quantity per option — Grid of steppers, or List.
• Number — Input, Stepper, or Slider.
• Text — Single line, or Multi-line.
• Dimensions — width and height inputs with a unit selector.
• File upload — Dropzone, or Designer only (no direct upload) when artwork comes from the Print.App designer. See Artwork uploads.
• Info / summary — Static note, or Live summary.

Image cards and grids show a picture per choice. Upload it on the choice — it is downscaled and embedded automatically, so there is nothing to host.

Making a field required

Turn on Required in the field’s Basics tab. If a customer tries to add to cart without answering, the configurator marks the field and scrolls to it — so the button never simply refuses without explanation.

Showing fields only when they apply

Every field can carry visibility rules under the Logic tab: show this field only when an earlier answer matches. A “Hardcover binding colour” field, for instance, appears only when the binding choice is hardcover.

Hidden fields are also excluded from pricing — a customer never pays for an option they were never shown.

Requiring an agreement before upload

An artwork declaration, a copyright confirmation, or terms the customer must accept: a tick box they have to check before they can upload. There is no separate checkbox type — a one-option Multiple choice field shown as a List is a checkbox, and the Logic tab keeps the upload hidden until it is ticked.

1. Add the tick box. Add a Multiple choice field, label it (for example Artwork declaration), set Display to List and turn on Required.
2. Give it one option. On the Options tab, keep a single option value and label it with the short sentence the customer ticks — I agree to the artwork declaration. Open its Details and put the full wording in Description; it appears in small print under the box. Delete any other option values.
3. Gate the upload. Select your File upload field, turn on Required, and on its Logic tab turn on Only show this option under a condition with the rule Artwork declaration is set.
4. Drag the tick box above the upload, then Publish.

The upload stays hidden until the box is ticked and disappears again if it is unticked. A customer who tries to add to cart without ticking is stopped at the tick box with Please make a selection.

The order records the option’s label, not its description — that line is your record of what the customer agreed to. Keep the label short and put the full wording in the description, which you can change at any time and republish.

If the product also offers the Print.App designer, its button sits in the same upload step, so the agreement is required before designing too.

Roles

Fields can carry an optional Role (Size, Pages, Material, Orientation). Roles let connected tools find the right field no matter what you named it — for example, a design tool reading your four size options instead of asking you to define them twice. Leave it as None unless you use such an integration; see the Page API.

SKUs

Each choice can carry a SKU fragment. When the customer configures a job, the fragments combine into a resolved SKU that travels with the order — so your production system sees BC-350-MATTE-500, not a paragraph of prose.

Labels on the order

Each answer reaches the cart and the order under its field’s label, so give every field one. A field without a label is named after its section title when it is the only question in that section. See How fields are named.