Set Up Product Forms

Enable Omnichannel

1. In CMS, go to Store Management | Store Settings | Store Fulfillment.
2. Under Omni Settings, click on the pencil icon to open the modal.
3. Turn on the flag, "Enable omni fulfillment options V2".
4. Set and save your changes.

Create a Product Form

1. In the CMS, navigate to Layouts | Layout Templates | Product Forms.
2. Click "Add From Template" to use a preconfigured form, or select "Add Blank Layout" to create a new one from scratch.
3. Customize the form by configuring the required fields, including input validation (e.g., regex), field types (e.g., dropdowns, text inputs, checkboxes), and pre-populated metadata. See Layouts - Cell Configuration for more details.
   For any Form Element type, the value under "Field" will display as a header on the Product Form when viewing it via Order History screen. It is recommended to match the "Field" value with the "Placeholder Text" value or, at the very least, format it for user display.
   For a Form Element type of Dropdown List, it is recommended to match the "Key" values to the "Display Name" values.
4. (Optional) You can make specific fields mandatory, ensuring they must be filled out before the checkout process by disabling "Is Optional".
5. Save your changes and publish the form.
   

   Note In Step #3, each field creates a "key" in the Key-Value pair used in reporting.

Configure Product Form Mapping

1. In the CMS, go to Store Management | Store Settings | Product.
2. Under the Product section, click the pencil icon next to Product Form Mapping.
3. A modal will appear, allowing you to set up rule mappings. For instance, you can select a product attribute like "Size" and specify its possible values, such as "S" for small and "M" for medium.
4. Choose a product form to associate with this rule. This rule means that when a customer adds a product with a size attribute of "S" (small) to their cart, they will be required to fill out the associated product form before proceeding to checkout.
5. You can configure multiple rules in this modal. Keep in mind that the order of the rules matters, as the first one in the list will be validated first. For example, if a product with a size attribute of "small," is added to the cart it will trigger the form. However, if the product's size is "large," it will follow the second rule on the list. It should be noted that not all mappings need to be met simultaneously to trigger the form.
   

   Note Only one form is displayed for each product. If a product matches multiple rules, the first matching rule will be applied. All fields, regardless of amount, will be presented on the POS app as a single scrollable page.

Test a Product Form

1. Launch the POS app and add a product to the cart. If the product matches the configured mappings, a form button icon will appear below the product. A red icon indicates that the form has not been filled out.
   
2. To have individual forms for products with the same ID, you can enable the CMS Store Setting, "Treat Each Item As Separate Line Item" (CMS | Store Management | Store Settings | OMS | Advanced). When enabled, if you have a product with a quantity of two, you'll be prompted to complete two separate forms.
   Conversely, with this setting disabled, you'll only need to fill out one form.
3. Before proceeding to checkout, the user must complete the form. Note that even if none of the fields are marked as mandatory (optional), the form must be viewed at least once to bypass the validation.
   Fields can be entered using a terminal. See Capture Customer Information From Payment Terminal for more information.
4. To access the form, simply tap on the icon, and it will pop up for you to fill out. You can revisit the form to edit your answers by tapping the icon again.
5. When the form is complete (indicated by it turning black), you can proceed with the checkout.
6. You can view the form answers by going to the Order History screen and clicking the form button icon.

Receipt Printing

The form fields and answers can be printed on receipts using receipt products tags:

Receipt Type	PS Tag
Print Receipts	:ps_p_form
E-Receipts	{ProductFormAttributes} Note Only applicable on the Order Print Receipt and Transaction Print Receipt templates

Reporting

FormAttributes="[{"key":"ps_phone","value":"Phone"},{"key":"Name","value":"diana"},{"key":"Email","value":"diana@ gmail.com"},{"key":"Phone","value":"6174120987"}]"

Known Issues & Restrictions