Creating a product availability form

Store Framework Using components Creating a product availability form

Learn how to create a product availability form with this step-by-step guide.

While browsing through a store's catalog, the user may feel disappointed if they are interested in a product not available for purchase at the moment.

To avoid frustration, you can make a product availability form available whenever your store's products are displayed as unavailable. Therefore, users can fill out a form linked to the product, expressing their interest in requesting the purchase as soon as the product is available again.

To set up the product availability form, follow the step-by-step below.

This configuration does not include sending automatic e-mails to users. The product availability form only stores the user data filled out in the form to the store's Master Data entity.

Instructions

Step 1 - Creating a Master Data entity

The first step is to create a new entity in the VTEX Master Data module, responsible for creating database architectures for a store.

The new module’s entity will cover the set of user data filled in and sent in the availability form. Therefore, your first step is to create a new Master Data entity.

It must be named AS and contain the fields stated above to properly work with the form:

Field name	Field type
`skuId`	`Integer`
`name`	`Text`
`email`	`Email`
`notificationSend`	`Boolean`
`createdAt`	`Varchar 100`
`sendAt`	`Varchar 100`

Step 2 - Creating the JSON Schema in Master Data

Once you created the entity to work with the form correctly, it is time to define how it will communicate with the availability form, which will happen through a JSON schema.

The JSON schema will be responsible for telling your form fields which data they must receive, i.e., which kind of input they should expect from users according to the Master Data entity's fields.

In addition to that, the schema will also be responsible for saving all user data fetched from the form in the Master Data's Entity AS created in the previous step.

Using a tool of your preference, run the Master Data's Get Schemas API, replacing the data_entity_name value with AS;
In the response, look for fields added previously to the entity and copy the structures in which these are being displayed. This will help you to create another JSON Schema for the form, including those fields now as properties;
Run the Master Data's Save Schema by name API, pasting the schema structure copied in the second step in the request's body. Remember that this schema structure is using the entity fields, and you should replace them for the schema's properties as stated in the example below:


_40{
_40  "title": "Person",
_40  "type": "object",
_40  "properties": {
_40    "skuID": {
_40      "type": "string",
_40      "title": "SKU ID",
_40      "description": "The SKU ID desired by user, which will be watched for changes in the product quantity."
_40    },
_40    "name": {
_40      "type": "string",
_40      "title": "User's name",
_40      "description": "The user's name."
_40    },
_40    "email": {
_40      "type": "string",
_40      "title": "User's email",
_40      "description": "The user's email."
_40    },
_40    "notificationSend": {
_40      "type": "string",
_40      "title": "Availability notification",
_40      "description": "Whether the availability notification has been already sent or not."
_40    },
_40    "createdAt": {
_40      "type": "string",
_40      "title": "Form creating.",
_40      "description": "Date when the form was created. e.g.: ISO (2011-10-05T14:48:00.000Z)."
_40    },
_40    "sendAt": {
_40      "type": "string",
_40      "title": "User notification",
_40      "description": "Date when the user was notified regarding the product availability. e.g.: ISO (2011-10-05T14:48:00.000Z)."
_40    }
_40  },  
_40  "v-security": {
_40    "publicWrite": [ "publicForWrite" ],
_40    "publicJsonSchema": true
_40  }
_40}

This will create the JSON Schema, which the Availability Subscriber block will use, a native component from Store Framework, to store the users’ data in the Master Data entity AS.

Step 3 - Configure the Availability Subscriber block

Lastly, it is time to configure the Availability Subscriber block to make your store render the native Store Framework component for an availability form.

Access the Availability Subscriber app documentation and follow the step-by-step to complete its configuration.

Once the availability form is configured in your store, users interested in unavailable products will be able to share their e-mails using the component.

The best part about it is that your store will receive this data and automatically save it in Master Data for subsequent communication actions.