Sign Customiser

Navigation

Dark mode

Translate custom form fields, choices, guidance and submission messages while leaving shopper answers unchanged.

Last updated:

Configure the source form first. Then translate its shopper-visible wording under Settings -> Languages -> [target language].

Configure the source form

  1. Open Customisers -> [customiser].

  2. Use Features -> Forms to configure form names, descriptions, fields, choices, submission messages and file guidance.

  3. Use Core Setup -> Custom Designs for shopper links between the custom design and text flows.

  4. Save the source configuration.

The Forms page showing the Manage your forms list and the Form Settings card with the Title and submission message fields

The Form Settings card on the Forms page has the Title, the submission messages, the file error messages and Accepted Files Label. Each form also has its own Label, Description and Submit Button Label.

For field setup, see Add and edit custom form field options.

Translate the form

  1. Go to Settings -> Languages.

  2. If the target language is not in the list, select Add language. See Add, translate, preview and publish a language.

  3. Open the target language.

  4. Find the form and custom-design rows. Translate the shopper-visible wording.

  5. Find the wording for each form in the Form section. Find the messages and file wording in the Custom design & forms section.

  6. Select Save draft. Then select Preview to see the target language. Preview is not available when you have unsaved changes.

  7. Submit a test form. Read the warning below first. Check the validation and success messages.

  8. Select Publish.

The Languages page with the Add language button above the English language card marked Default and Published

Custom design and form wording shown beside its French translations in the language editor

Publish is not available until you save all changes and every required wording has a translation. When a required row is empty, the editor shows a Required translations missing banner. Select Show N missing in the banner to see those rows.

A test submission is a real submission.

It sends data to your webhooks. It sends an email to the Receiver Email on the form. If Receiver Email is blank, it sends the email to your Store’s default email. It also sends the customer confirmation email to the address that you type, when that email is on. Use an address that you own.

A test submission works only when your Store has an active subscription or a trial. On Universal, a trial also needs a saved payment method. Without these, the form fails and you cannot see the success message.

Covered form wording

  • Form Title, label, description and submit button label.

  • Field labels, descriptions, placeholders and choice labels (the text that shoppers see).

  • Validation, upload guidance, file limits, and success and error messages.

  • Links between the custom design and text customiser flows.

Choice values are not translated. A choice value is the value that Sign Customiser stores and shows in the submitted form.

Sign Customiser does not translate answers that shoppers type. It does not translate uploaded filenames.

Source form edits can mark target translations Stale. Review them before the next publish. Follow Add, translate, preview and publish a language for the complete draft, stale-field and publishing workflow.

Type a question and press Enter. Use the arrow keys to move between the results.