Skip to main content

Configure Guest Form Fields

Guest form fields collect the information staff need to fulfill an order, and checkout validation keeps the submitted values consistent with the configured field types.

Quick Reference​

Field TypeUse It ForExample
Guest nameIdentifying the guest.Name for delivery or pickup.
Room numberRoom delivery or charge-to-room checks.1208
Email or phoneGuest follow-up.Confirmation or issue handling.
Table numberRestaurant or venue delivery.Table 7.
NotesSpecial instructions.Allergy or delivery note.
Display text or linkGuest instructions or policy reference.Link and wording are approved.
Custom fieldProperty-specific fulfillment data.Field type, options, and translations are clear.
Selection or radio fieldGuests choose from a fixed list of valid options.Keep the saved option values and translated labels aligned.
Furama First membership numberSends a guest membership number to POS as the order member number.Use FURAMAfirst Membership Number or FURAMAfirst Membership Number (Optional) when the property needs this value on the order.
Pax or Total Pax guest countSends a numeric guest count with eligible POS orders.Use a whole-number Total Pax or Pax field when Micros Simphony Gen 2 needs the guest count.

Before You Start​

  • Confirm fulfillment requirements with operations.
  • Confirm which fields should be required.
  • Confirm privacy expectations for guest information.
  • Plan selection and radio options carefully. Checkout only accepts answers that match the configured option values.

Configure Fields​

  1. Open Catalogue V3 settings or the catalogue setup.
  2. Go to guest form fields.
  3. Enable fields required by the fulfillment process.
  4. Reorder fields so guests see the most important fields first.
  5. Choose the field type for custom fields, such as text, options, checkbox, or display content.
  6. Mark fields active, mandatory, or hidden carefully. Display Text and Link fields are informational, and disabled fields cannot stay mandatory.
  7. Add options and translated labels where required.
  8. Save changes.
  9. Test checkout and confirm staff can see the submitted details.

Additional Fields​

Catalogue additional fields are useful when the property needs information beyond the standard guest form.

Use them for:

  • Allergy or dietary details.
  • Pickup or delivery instructions.
  • Cutlery or packaging choices.
  • A policy acknowledgement.
  • A custom operational note that staff need on the order.

Some properties also collect a Furama First membership number. Catalogue V3 passes either FURAMAfirst Membership Number or FURAMAfirst Membership Number (Optional) to POS as the member number when the guest submits a value.

If the property uses Pegasus POS, Catalogue V3 also copies Allergy (Optional) into POS as Allergy when the guest enters a value.

Guest Count for Micros Simphony Gen 2​

When a property uses Micros Simphony Gen 2 and needs guest count in POS, collect the value in a custom guest form field named Total Pax or Pax.

  1. Confirm the catalogue uses Micros Simphony Gen 2.
  2. Open the catalogue guest form fields.
  3. Add or enable a custom field named Total Pax or Pax.
  4. Ask guests to enter the count as whole-number digits.
  5. Save the field and place a test order.

Catalogue V3 checks Total Pax first and falls back to Pax when Total Pax is empty. It includes the value only when it contains whole-number digits. Blank, non-numeric, or non-whole-number values are not included as a guest count.

If you use Selection or Radio Button fields, keep the underlying option values stable even when translated labels change. Guest checkout validates the submitted value against the configured list.

Keep mandatory fields limited to information staff truly need to fulfill the order. Too many required fields increase checkout abandonment and support questions.

Troubleshooting​

Staff cannot see guest details on an order​

What you see: An order appears, but needed guest details are missing.

Do this:

  1. Check guest form field setup.
  2. Confirm the field is enabled and required if needed.
  3. Open the order detail page.
  4. Contact support if submitted data is missing from order details.

Guest cannot submit checkout​

What you see: Checkout is blocked by guest form validation.

Do this:

  1. Confirm mandatory fields are still required.
  2. Check hidden or disabled fields are not marked mandatory in a way guests cannot complete.
  3. Review option labels, translated values, and selection or radio choices.
  4. Test checkout again with the required fields completed and valid option values selected.

Membership number does not appear in POS​

What you see: The guest submits a Furama First membership number, but POS does not show the member number on the order.

Do this:

  1. Confirm the guest form uses FURAMAfirst Membership Number or FURAMAfirst Membership Number (Optional).
  2. Confirm the guest entered a value other than -.
  3. Recheck the POS mapping on the order.
  4. Contact support if the member number is still missing from POS.

Allergy note does not appear in POS​

What you see: The guest enters an allergy note, but the POS order does not show Allergy.

Do this:

  1. Confirm the guest form uses Allergy (Optional).
  2. Confirm the guest entered a value other than -.
  3. Confirm the catalogue uses Pegasus POS.
  4. Recheck the order in POS after testing checkout again.

Guest count does not appear in POS​

What you see: The guest enters a count, but the Micros Simphony Gen 2 order does not show a guest count.

Do this:

  1. Confirm the catalogue uses Micros Simphony Gen 2.
  2. Confirm the custom field name is exactly Total Pax or Pax.
  3. Confirm the submitted value contains whole-number digits only.
  4. Place another test order and check the guest count in POS.