Table 02 - Sellers
- This article presents the fields of the Seller integration layout. To better understand the concept of a salesperson, see our article on Concept of Salesperson.
| Order | Description Field | Format and Size | Required | Version | Remarks |
|---|---|---|---|---|---|
| 1 | Table identifier (IDENTIFICADOR) | FIXO=02 (2) | Yes | 1.0 | |
| 2 | Seller Code (code) | Integer (10) | Yes | 1.0 | |
| 3 | Name of Seller (name) | Text (100) | Yes | 1.0 | |
| 4 | Device Identifier (IMEI) | Text (50) | No | 1.0 | If informed, the The seller will only be able to use the Demander on the device with the IMEI provided, otherwise you will be able to log in to any Android device. Demander, the password must be configured on Demander Web. |
| 6 | User Type (codTipoUsuario) | Integer (1) | Yes | 1.0 | 1 – Seller; 2 – Sales Manager. If you have any questions, please consultSeller Registrationin our Knowledge Base or contact our support |
| 7 | Current Order Number (numPedidoAtual) | Integer (10) | No | 1.0 | Seller’s Current Order Number, when placing a new order this number + 1 will be used. If the ERP does not have this control, the field in question can be sent empty, as Demander does this control. If in doubt, consultOrder Rangein our knowledge base or contact our support |
| 8 | Initial Order Number (numPedidoInicial) | Integer (10) | Yes | 1.0 | Seller’s starting order range number. Order ranges may conflict between sellers, if in doubt, consultOrder Rangein our knowledge base or contact our support |
| 9 | Final Order Number (numPedidoFinal) | Integer (10) | Yes | 1.0 | Seller’s order range ending number. Order ranges may conflict between sellers, if in doubt, consultOrder Rangein our knowledge base or contact our support |
| 10 | Active (active) | Integer (1) | Yes | 1.0 | 1 = Active or 0 = Inactive. Inactive sellers cannot log into Demander. |
| 11 | Price List (listasDePreco) | Text (2000) | No | 1.6 | Send in this field the code of the price lists separated by commas that each seller can view. Example: 3,4,9. If you do not send anything, the seller will have access to all lists. |
| 12 | Product Group (gruposProduto) | Text (200) | No | 1.8 | Send in this field the code of the groups separated by commas that each seller may or may not view. Example: 3,4,9. Use the Show or Hide Product Groups field to define whether they should be visible or hidden to the seller. Until version 2.18 the default behavior was to display. |
| 13 | Show or hide Product Groups (ocultarGruposDeProduto) | Text (200) | No | 2.19 | If the “gruposProduto” field is empty, display all, regardless of the value of this field. If you send “0”, only the Groups entered in the Product Groups field will be displayed to the seller. If you send “1”, only the Groups entered in the Product Groups field will be hidden from the seller. |
| 14 | Flex Balance in ERP (saldoFlex) | Decimal (15.2) | No | 2.22 | The seller’s Flex Balance must be sent here based on the invoiced orders. Orders with pending billing should not be considered in this balance. (If you are going to integrate flex, you must also integrate the return of orders and items, sending the quantity of each item qthat has already been invoiced or cancelled. |
| 15 | Current Password (senhaAtual) | Text (255) | No | 2.48 | Field used to update/change the password; It serves as a validator of the current password that the seller is currently using. |
| 16 | New Password (senhaNova) | Text (255) | No | 2.48 | Field used to enter a new password for the seller. In the case of a new seller, no validation will be done, only the password passed in this field will be added. In the case of a seller update, field 15 will be used to validate the Seller’s current password before adding the new password. The new password must contain at least 6 digits. |
| 17 | Related segments (segmentosRelacionados) | Text (500) | No | 2.48 | Field used to reference which segments the seller is in linked. |
| 18 | Released branches (branches) | Text (200) | No | 3.8 | |
| 19 | Parent seller code (codVendedorPai) | Integer (10) | No | 3.20 | Defines whether the seller is an agent. If so, this field must contain the seller code to which the agent must be linked. If not prefixed, the field must be sent blank. |
| 20 | Order release hierarchy code (codHierarquiaLiberacaoPedido) | Text (255) | No | 3.42 | |
| 21 | Value of the flex balance that the seller has accumulated (saldoFlexAcumulado) | Decimal (15.2) | No | 3.42 | If you have any questions, consultFlex Balancein our Knowledge Base or contact our support. |
| 22 | Allows you to register customers (permiteCadastroCliente) | Integer (1) | No | 3.64 | Determines whether the seller has permission to register new customers. |
| 23 | Allows you to edit customers (permiteEdicaoCliente) | Integer (1) | No | 3.64 | Determines whether the seller has permission to edit customers. |
| 24 | Allows you to register photos of products (permiteCadastroDeFotoDeProduto) | Integer (1) | No | 3.64 | Determines whether the seller is allowed to register product photos directly through the Android App. |
| 25 | Allows registration of new routes (permiteAdicionarRota) | Integer (1) | No | 3.64 | Determines whether the seller has permission to register new routes in the Mobile App. |
| 26 | Allows you to edit route registration (permiteControlarRota) | Integer (1) | No | 3.64 | Determines whether the seller has permission to change and delete routes on the Mobile App. |
| 27 | Allows you to add customers to the route (permiteAdicionarRotaClientes) | Integer (1) | No | 3.64 | Determines whether the seller has permission to add customers to an existing route on the Mobile App. |
| 28 | Allows you to edit customers on the Route (permiteControlarRotaClientes) | Integer (1) | No | 3.64 | Determines whether the seller is allowed to change the position and remove customers from a route in the Mobile App. |
| 29 | Capture the Geographic Position when issuing the Order (capturarPosGeoNoPedido) | Integer (1) | No | 3.64 | Determines whether or not the Geographic Position should be captured when issuing the order on the Mobile App. |
| 30 | Capture the Geographic Position when registering an event (exigeCapturaGPSEventos) | Integer (1) | No | 3.64 | Determines whether or not the Geographic Position should be captured when registering an event on the Mobile App. |
| 31 | Requires photo at the Event (exigeFotoEventos) | Integer (1) | No | 3.64 | Determines whether it is mandatory to take a photo when registering an event on the Mobile App. |
| 32 | Requires Checkin (exigeCheckinCheckout) | Integer (1) | No | 3.64 | Determines whether it is mandatory to check in on the Mobile App. |
| 33 | Check-in radius in meters (checkinRaio) | Integer (10) | No | 3.64 | Configuration used in the check-in/check-out module, determines the radius in meters within which the salesperson can check-in a customer. |
| 34 | Check-in days (checkinDias) | Integer (10) | No | 3.64 | |
| 35 | Display Team Sales Summary in Sync (permiteVisualizarResumoVendas) | Integer (1) | No | 3.64 | View summary Team Sales in Sync. This option is recommended for Sales Managers. |
| 36 | Requires Checkout (exigeCheckout) | Integer (1) | No | 3.65 | Determines whether it is mandatory to check out on the App Mobile. |
| 37 | Allows billing registration (permiteRegistroCobranca) | Integer (1) | No | 4.0 | 1 = Active (Allows the seller to register the billing or 0 = Inactive (Does not allow the seller to register the billing). To use this configuration, it is necessary to have integration with the ERP and have the Charge Registration module active. |
| 38 | Minimum order value (valorMinimoPedido) | Decimal (15.2) | No | 4.18 | It will not be allowed to issue an order with a value lower than the configured value. |
| 39 | Customer Order Rule from another Seller (regraPedidoClienteOutroVendedor) | Varchar (30) | No | 4.45 | One of the following tags can be sent in this field: CONFORME_COMPANY_CONFIG -According to the Company’s configuration: It will be validated according to the configuration, “Allow the issuance of orders and visits without sales to inactive customers”. related place an order for a customer from another seller if the customer is active or inactive.ONLY_INACTIVE -Only Inactive: Only allows a related seller to place an order for a customer from another seller if the customer is inactive.NEVER -Never:Does not allow a related seller to place an order for a customer from another seller. If the record field is sent empty, it will be assumed CONFORME_CONFIG_EMPRESA |
| 40 | Order Types released to the seller (tiposPedidoLiberados) | Text(100) | No | 4.53 | The codes of the order types to which the seller has access must be sent, separately by comma. Ex: 2,3,4. If you do not send anything, the seller will have access to all Order Types |
| 41 | Flex Balance Calculation (comportamentoSaldoFlex) | Integer(1) | No | 4.53 | Defines how the calculation will be made. flex balance: 0 - According to the Company Configuration:It will be calculated according to the settings contained in the company. 1 - Enabled:The flex balance will always be calculated regardless of the company settings. 2 - Disabled: The flex balance will not be calculated. |
| 42 | Phone number (telephone) | string(40) | No | 5.26 | If it is not included or sent empty, the information will not be updated. To clear the field, send an empty space ( | | ) in this position. |
Registration Example:
02|25|THOMAS|123456789012345|email@site.com.br|1|754120|750000|800000|1|3,4,9|