Checkout fields Free

StoreMaster can add a field to your checkout — a purchase reference, a delivery note, a required confirmation. The free edition supports one field.

The rule this module follows

Fields are registered through WooCommerce’s own additional-checkout-fields API and nothing else. StoreMaster does not modify the checkout markup, override a template or inject a hidden input.

That constraint is why a field added here behaves identically on classic checkout and on the Checkout block, and why a WooCommerce update does not break your checkout. It also means StoreMaster can only offer what that API offers.

Supported field types

Text, select and checkbox — the three types WooCommerce’s Checkout block supports.

If you ask for something else, StoreMaster refuses when you configure it and explains why, rather than accepting the configuration and failing in front of a customer. Richer inputs belong on the product or basket page, where they can be validated properly.

Locations

A field can sit in the contact, address or order information section of checkout.

Adding one

StoreMaster → Checkout fields → Add field. Give it a key, a label, a type and a location, and say whether it is required.

The key is permanent. Once a field has been used on a real order, its type can no longer change — the value stored on that order means what the old definition said, and reinterpreting it would quietly change a customer’s record. Archive the field and add a new one instead.

Where the value appears

On the order in wp-admin, in the order emails you have enabled it for, and in WordPress’s privacy export and erase tools. It is stored on the order through WooCommerce’s own data layer, so it works the same under high-performance order storage.