Customer fields (registration and profile fields)
Most stores need one or two things from a customer that the standard sign-up form does not ask for — a tax number, a trade licence, a “how did you hear about us”, an opt-in for a printed catalogue. Settings → Customer Fields is where you add those questions. A field you add there appears on the registration form and in the customer’s My Account profile, is stored against the customer, and shows on their record under Customers → Customers. This article explains what the page does, what it does not do (it does not change the checkout), and how to change or remove a field without losing data.
In one sentence: custom fields in the Contact information section are live on registration and the profile; the built-in rows are listed for reference, and the checkout, address book and order forms are fixed and are not controlled by this page.
1. The page
Open Settings → Customer Fields. Fields are grouped into three sections, each a collapsible header: Shipping address, Contact information and Billing address. Every row shows:
- Pos. — the field’s position within its section (lower numbers first). Type a new number and click Save to reorder.
- Description — the label the customer sees.
- Type — the kind of input (see section 3).
- Show / Req — two tick boxes: Show this field and Make required.
- A × on fields you added yourself. Built-in fields cannot be deleted.
Changes to Pos., Show and Req are saved together with the Save button at the top (it confirms with ✓ Saved). Adding a field saves immediately.
2. Adding a custom field
- Click + Add custom field.
- Section — choose Contact information. This is the section that renders on the storefront; fields added to Shipping address or Billing address are stored but never shown anywhere today (see section 4).
- Field type — see section 3 for what each one really produces.
- Field name — the internal key: lowercase letters, numbers and underscores (
tax_id,how_heard). It must be unique within the section and cannot be changed later. Do not reuse a built-in name such asphoneorcompany— a field with a built-in name is treated as one of the standard inputs and is never shown. - Label (shown to customer) — the wording on the form, for example “VAT number”.
- Show on form (on by default) and Required (off by default).
- Click Add field. The new field goes to the end of its section; change its Pos. and Save to move it.
Both the name and the label are required (“Field name and label are required.”); a name already used in the section is refused with “This field already exists in this section.”
3. Field types
The type list is longer than the set of inputs the storefront can actually draw. Pick from the first five; the rest fall back to a plain text box.
| Type | What the customer gets | Notes |
|---|---|---|
| Input field | Single-line text | The safe default. |
| Textarea | Multi-line text | |
| Checkbox | A tick box next to the label | Stored as yes / no. If you make a checkbox Required, the customer must tick it — use that for “I agree” style questions. |
| An e-mail input | The browser checks the format; the value is cleaned as an e-mail address on save. | |
| Phone | A telephone input | Mobile keyboards switch to the number pad; no format is enforced. |
| Selectbox | Single-line text | There is nowhere to enter the choices, so no drop-down is produced. Use an Input field and say the allowed values in the label, or a Checkbox for a yes / no. |
| Country ››, State/Province ››, Zip/postal code | Single-line text | No country or state picker and no postcode check — these types exist for the built-in address rows. |
| Date | Single-line text | No date picker; customers type the date in whatever format they like. |
4. Where customers see your fields — and where they do not
Custom fields in the Contact information section appear in three places:
- The registration form (the stand-alone Register page and the register panel of the all-in-one My Account page), after the standard name / e-mail / phone rows. A required field that is left empty stops the registration with “<Label> is required.” before the account is created; the other values the customer typed are kept on the form.
- My Account → Profile, under the heading Additional Information, pre-filled with what the customer entered. The same required check applies when they save. A profile save that touches these fields is mentioned in the “account updated” e-mail as Additional profile fields (the values themselves are not mailed).
- Customers → Customers → the customer’s record, in a Custom Fields card. You can read and change the answers there. The card is shown for existing customers only, and the admin save does not enforce Required — you can leave a required field blank from the admin side.
They do not appear:
- At checkout. The checkout’s contact, billing and shipping forms are fixed. Which inputs they show and which are required (name, e-mail, phone, address, city, postcode, country; company and address line 2 optional) does not come from this page — ticking or unticking Show / Req here changes nothing at checkout, and a custom field in any section is never asked for during checkout. A developer can extend the required list with the
titancart_billing_required_fieldsandtitancart_shipping_required_fieldsfilters. - In the My Account address book. Its form is fixed in the same way.
- On orders. Answers are stored on the customer, not copied onto orders, so they are not on the order page, the invoice, the packing slip or any order e-mail. If you need a value on every order, ask for it at checkout in the order note instead.
- In e-mail templates. There is no placeholder for a custom field’s value.
- In the customer CSV export or import (Settings → Import / Export). Those files carry the standard columns only.
The customer’s own data download (the GDPR “Download my data” action, when enabled) does include the stored answers, keyed by field number.
5. The built-in rows
Each section comes pre-filled with the standard inputs of that form: First name, Last name, Address (twice — the second row is address line 2), City, Country, State/province, Zip/postal code, Phone and Address type under the two address sections; First name, Last name, Company, Phone and E-mail under Contact information. They are a reference list of what the standard forms ask for. Their Show and Req boxes have no effect in the current release: the registration, address book and checkout forms decide for themselves which standard inputs to show and require (the page’s “How it works” note says otherwise — it is ahead of the code). Two things that do change the standard forms live elsewhere:
- Phone and Company on the registration form are controlled by Settings → General Settings → Quick registration (“Require only contact information for registration”). With it on (the default) the form asks for name, e-mail and password only; switch it off to add Phone and Company.
- Required address fields at checkout are fixed (see section 4) and only a developer filter changes them.
A few of the built-in rows (address line 2, Phone, Address type, Company) show the × because they were not flagged as system rows. Deleting them does no harm to customer data, but there is no reason to, and a row with a built-in name cannot be re-created as a working custom field.
6. Changing, reordering and removing a field
- Reorder: edit Pos. and click Save.
- Hide temporarily: untick Show and Save. The stored answers are kept and come back when you show the field again.
- Make optional / required: tick or untick Req and Save. Making a field required does not touch existing customers until they next save their profile.
- Rename or change the type: not possible on the page. The label, the internal name and the type are fixed once the field exists. To rename, add a new field with the new label, hide the old one, and remove the old one later if you no longer need its answers.
- Delete: the × asks Delete custom field “…”? and then removes the field and every customer’s stored answer for it. There is no undo. Hide the field instead if you may want the data back.
7. TitanCart Lite and Pro
Customer Fields works the same on both editions; nothing on this page needs a Pro key.
Troubleshooting
- I added a field and it does not show on the registration form. Check that its Section is Contact information, that Show is ticked, and that its field name is not one of the standard names (phone, company, first_name, last_name, email). Fields in the Shipping address and Billing address sections are not rendered anywhere today.
- I ticked Req on Company but checkout still treats it as optional. Expected — checkout does not read this page (section 4). The same goes for hiding Address 2 or Phone.
- My Selectbox field shows as a text box. Expected; there is nowhere to define its options (section 3).
- A customer cannot register — “<Label> is required.” A required custom field was left empty. If the question should be optional, untick Req and Save.
- I need the answer on the order / invoice. Custom field values stay on the customer record. Open Customers → Customers and the customer to read them, or collect the information at checkout in the order note.
- I deleted a field by mistake. The field and its answers are gone; re-create the field and ask customers to fill it in again from My Account → Profile.
See also
- Managing customers — the customer list and record, where custom field answers are shown.
- Store setup checklist — the General Settings worth checking before launch, including Quick registration.
- GDPR / cookie consent — the customer data download that includes custom field answers.
- E-mail notifications and templates — the account-updated e-mail and its placeholders.