Menu
Feedback
Start here
Tutorials


Tutorials
Master Data Settings
How to structure Master Data entities to store B2B sales data
4 min read

Through Master Data - the VTEX platform’s module that allows the creation of database architectures - it is possible to collect, store and make available data in various formats for the customers and administrative users of a store. There are two ways to configure it:

  • By using a Content Management System (CMS) internal to the store's administrative dashboard.
  • By sending requests to Master Data’s API.

The stored data is described by Data Entities, which are representative models that allow Master Data to validate the information received and create forms. The system allows the creation of connections between the data of different entities, in addition to providing a series of automation possibilities.

An example is the Triggers that can be activated by changes in stored data and can have effects such as sending emails and other changes to that data. Learn more about all the possible configurations of this module in Master Data’s official documentation.

Modeling sales structures and goals

One of Master Data’s recurring applications is the representation of the sales structures of a B2B operation. Stores have several sales representatives with different functions, and it is of great value to be able to track their sales, in addition to establishing and monitoring their goals. Here are some examples of Data Entities that can be created or customized for B2B applications.

Representatives

A table of representatives or Autonomous Commercial Representatives can be useful to monitor those that make sales on behalf of a B2B operation, in addition to allowing better-filtered reports.

Here are some relevant fields you can add to this table:

  • Representative’s name and email
  • Supervisor’s name and ID
  • Represented brands
  • Acting region
  • Are you an administrative user?
    • Administrative user’s ID

Supervisors

A table of supervisors allows you to associate each sales representative or Autonomous Commercial Representatives with a supervisor who will manage their work, in addition to providing control over that supervisor's data.

Here are some relevant fields you can add to this table:

  • Supervisor’s name
  • Supervisor’s email
  • Phone number
  • Administrative user’s ID

Customers

Every store has a Data Entity that configures the table of customers. You can add fields to that entity by following the walkthrough in the article Creating a field in Master Data. This way, when a customer visits a store, the front-end has access to relevant information regarding their position in the sales structure and can provide a custom experience. In addition, it is possible to limit the access to the store to only approved customers, as explained in the article Configuring B2B on VTEX.

Here are some relevant fields you can add to this table:

  • Representative’s ID
  • Is it a company?
  • Company’s data
    • Company registration number
    • Legal business name
    • Trade name
    • Contact number
    • State registration
  • Registration approved?
  • Sales channel

Goals

A table of goals allows controlling the sales goals of representatives and Autonomous Commercial Representatives, and you can define policies for such goals, such as the active goal cycle, in addition to specifics such as active geographic areas and goals by brands and products.

Here are some relevant fields you can add to this table:

  • Representative’s ID
  • Cycle region
  • Cycle start date
  • Cycle end date
  • Goal value
    • By product
    • By Brand
  • Successful sales value per cycle
  • Canceled sales value per cycle

Data entry in Master Data

In addition to providing a powerful data structure’s modeling tool, Master Data’s content management system, accessed through VTEX’s administrative dashboard, offers several ways to fill the tables that structure the content.

Forms

Master Data’s CMS allows you to configure forms to fill in the modeled tables. It is useful for information that will be entered and edited by administrative users, since it is possible to limit usage through roles.

To learn how to configure these forms, check out the article Creating forms in Master Data. It is also possible to create an Application, which is a grouper of forms, following the steps detailed in the article Creating applications in Master Data.

Front-end or API

Forms can also be submitted via front-end for customers to fill them, as described in the article Creating Contact Us forms using Master Data. Another way to access data on the front-end or in different integrations is through Master Data’s API.

Triggers

Events in a Master Data’s data entity can trigger changes to the data. For more on this, check out the article Creating triggers in Master Data v1.

Bulk import

It is also possible to fill tables in bulk by uploading spreadsheets, as explained in the article Importing data into Master Data.

Learn more

Contributors
1
Photo of the contributor
+ 1 contributors
Was this helpful?
Yes
No
Suggest Edits (GitHub)
Data entity
« Previous
Creating custom queries in Master Data v1
Next »
Contributors
1
Photo of the contributor
+ 1 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX Community
Join our community
Request VTEX support
For personalized assistance, contact our experts
Open a support ticket
GitHubDeveloper PortalCommunityFeedback