Overview
Additional Order Fields allow you to collect extra information from learners or purchasers during the WebLink checkout process. These fields appear during the checkout flow and the submitted data becomes part of the resulting order and booking record inside Administrate.
This capability is useful when your registration process requires more information than the default learner details captured during checkout.
If you have not yet configured WebLink, start with WebLink Overview and Installation. For the checkout stage of the storefront journey, see Checkout Widget.
How additional order fields work
Additional Order Fields extend the information collected during checkout. When a learner registers for training through WebLink, the checkout form can include extra questions or required data fields.
The information collected is stored alongside the resulting order and can be referenced by administrators when managing bookings.
This makes it possible to gather operational information such as:
- purchase order numbers
- internal reference numbers
- custom learner information required for the training
- additional registration details required by the provider
Common use cases
Organizations often use additional order fields to capture information required for internal processes.
Typical examples include:
- purchase order or billing references
- department or cost center information
- special requirements related to the training
- information required for compliance or certification programs
Because the data becomes part of the order record, it can be referenced later during booking management, reporting, or invoicing workflows.
Where the fields appear
Additional Order Fields appear within the checkout experience presented by the WebLink Checkout Widget.
The learner encounters these fields during the registration process, usually after confirming the course or event and before completing the order submission.
This means the checkout configuration must be working correctly before additional fields can appear.
Configuring additional order fields
The exact configuration process may vary depending on your Administrate setup, but the general approach is:
- Create the additional order field within the system configuration.
- Define the field type and label.
- Specify whether the field is required.
- Ensure the field is available to the checkout process.
Once configured, the WebLink checkout flow will display the field when the learner completes the booking process.
Field types and data mapping
Additional Order Fields function as point-of-sale inputs presented to the learner or purchaser during the WebLink checkout process.
These fields can be mapped to existing system fields, including Booking, Contact, or Account records. When a booking is completed, the values entered during checkout are stored alongside the order and may also populate the mapped fields.
If a mapped field already contains a value, the checkout input may overwrite that value depending on your configuration.
Fields will only appear on WebLink portals where they have been explicitly configured.
Configuring fields in WebLink portals
In addition to creating the field, you must configure it on the WebLink Portal where it should appear.
- Go to Control Panel → Portals.
- Select the portal you want to configure.
- Open the Additional Fields tab.
- Add a new field and select the corresponding Booking or custom field.
- Define the label that will be displayed to the learner during checkout.
- Save your changes.
Once configured, the field becomes available in the checkout flow for that portal.
Design considerations
When creating additional order fields, keep the learner experience in mind.
Too many required fields can make the checkout experience slower or more confusing. Whenever possible, limit required information to what is truly necessary for the booking or operational process.
Fields should also be clearly labeled so the learner understands why the information is required.
Testing additional order fields
Before publishing changes to your storefront, test the checkout flow carefully.
- Open the storefront page containing your catalog or event listing.
- Select a course or event.
- Proceed to checkout.
- Confirm the additional order fields appear correctly.
- Submit a test booking.
- Verify that the information appears in the resulting order or booking record.
This step ensures that the collected data flows correctly from the storefront into Administrate.
Common issues
The field does not appear during checkout
- Confirm the field has been configured correctly.
- Confirm the field is enabled for the checkout process.
- Confirm the learner has reached the correct checkout page.
The data does not appear in the order record
- Confirm the field mapping is configured correctly.
- Confirm the booking was created successfully.
- Review the order record to confirm where the field data is stored.
Best practices
- Collect only the information required for your booking workflow.
- Use clear labels so learners understand what information is required.
- Test the checkout flow whenever additional fields are added or changed.
- Confirm that internal teams know where the collected data appears in Administrate.