The Order Configuration app, designed for B2B scenarios, displays a form responsible for collecting order data in a modal.

Once the form is submitted, the order data collected will be available at Master Data and saved in the current VTEX session.

This app can be used to enable customization of all kinds of behaviors, such as custom prices, custom products, etc. Keep in mind the Order Configuration app does not offer these functionalities, it only enables other apps to do so.

Follow the steps below to install and set up the Order Configuration app in your store.

First, you must add the order-configuration app to your theme's dependencies in the manifest.json file:

This will enable you to use the blocks exported by the order-configuration app. Check out the full list below:

Block name	Description
order-config	Parent block only responsible for rendering its children blocks, that in turn build the Order Configuration component.
order-config.title	Renders the component title, that is, the message text displayed for users to present the component. On the image above, the component title is Order Configuration.
order-config.modal	Renders the modal responsible for displaying the component content.
order-config.form	Renders the component content, that is, a form to be filled out by users.

Add the order-config block in the Header component, as shown in the example below.

Then, declare the order-config#header block and its children blocks: order-config.title and order-config.modal. Example:

If the order-config.form block does not have any children configured, a default form will be rendered automatically based on the React Hook Form JSON Schema library. To declare children blocks according to your business needs, check out the Advanced configuration section below.

You must create a schema named main in Master Data, using the order_configuration data entity.

You can place a request using the Save schema by name endpoint of the Master Data v2 API to do so.

The schema should contain all the data that you added in the form above, otherwise the data will not be persisted.

Request body example

Refer to Master Data API - v2 documentation for more details.

It is also necessary to configure a new app in the orderForm.

First, place a GET Get orderForm configuration request to retrieve the current orderForm settings before updating them. By doing so you ensure that you will only change the properties you want in the next step.

Then, place a POST Update orderForm configuration request, setting the following object inside the apps object in the request body:

Request body example

You can refer to Checkout API documentation for more information.

If desired, you can declare the order-config.form block by adding and configuring the formFields prop and an array of form children blocks (whose descriptions you can find below).

Block name	Description
order-config.submit	Renders a Submit button.
order-config.dropdown	Renders the a dropdown field.
order-config.radiogroup	Renders a radiogroup field.
order-config.text	Renders a text field.
order-config.textarea	Renders a text field with a wider range of available characters.
order-config.checkbox	Renders a checkbox field.

Props

Check out the description of the available props below.

Prop name	Type	Description	Default Value	Block name
pointer	string	Path to which the block must point in the formFields prop in order to properly work.	undefined	order-config.dropdown, order-config.radiogroup, order-config.text, order-config.textarea, and order-config.checkbox
formFields	object	Object responsible for defining the form fields.	undefined	order-config.form

The formFields object contains the following props:

Prop name	Type	Description	Default Value
name	string	Name of the field (only used as an identifier in your code).	undefined
type	enum	Value type accepted by the field. Possible values are string and number.	string
fieldType	enum	Input type accepted by the field. Possible values are: text, textarea, select, radio, and checkbox.	text
label	string	Field name shown to users.	undefined
showInTitle	boolean	Whether to display the value type accepted by the field on its name (true) or not (false).	false
options	object	Field options to be defined in case select, radio, or checkbox values were declared in the fieldType prop.	undefined

The options object contains the following props:

Prop name	Type	Description	Default Value
label	string	Option name shown to users.	undefined
value	string	Option value.	undefined

In order to apply CSS customizations in this and other blocks, follow the instructions given in the recipe on Using CSS Handles for store customization.

CSS Handles
formSubmitButton
formSubmitContainer
formErrorServer
formErrorUserInput
loader
orderConfigFormWrapper
formObject
title
titleValues
titleWrapper
wrapper