Table 18 - Customers

This article introduces the fields of the customer integration layout. To better understand the concept behind customers, see our article on Customer Concept.

Order

Field Description

Format and Size

Required

Version

Note

Table Identifier (IDENTIFICADOR)

FIXED=18 (2)

Yes

1.0

Customer Code (codigo)

Integer (10)

Yes

1.0

Customers registered by the salesperson take code "0"; the key to updating the code of these customers is the CNPJ/CPF field.

CNPJ/CPF (cpfCNPJ)

Text (18)

1.0

Send with mask EX: 01.010.101/0001-72; field becomes mandatory when codigo and uniqueID are null, blank, or zero.

Payment Term Code (codCondicaoPagamento)

Text (20)

1.0

Determines the default payment term for this customer. This is the payment term that will be selected when starting to enter a new order. *When the payment term is locked, it cannot be changed on the order.

If bloqueiaCondPagamento = 1, only the defined payment term is shown when creating an Order and cannot be changed.
If bloqueiaCondPagamento = 0 and has a defined payment term, it is loaded as default, but can be changed.
If bloqueiaCondPagamento = 0 and DOES NOT have a defined payment term, no default payment term is loaded, but allows selecting another payment term.

This field is not cleared when sent empty from ERP to Demander. To clear the field, send the code of an unregistered payment term.

Payment Method Code (codFormaPagamento)

Text (20)

1.0

Determines the default payment method for this customer. This is the payment method that will be selected when starting to enter a new order. *When the payment method is locked, it cannot be changed on the order.

If bloqueiaFormaPagamento = 1, only the defined payment method is shown when creating an Order and cannot be changed.
If bloqueiaFormaPagamento = 0 and has a defined payment method, it is loaded as default, but can be changed.
If bloqueiaFormaPagamento = 0 and DOES NOT have a defined payment method, no default payment method is loaded, but allows selecting another payment method.

This field is not cleared when sent empty from ERP to Demander. To clear the field, send the code of an unregistered payment method.

Region Code (codRegiao)

Text (30)

5.18

Region Code

Salesperson Code (codVendedor)

Integer (10)

1.0

ATTENTION: If the salesperson code is sent, the customer appears only for the specified salesperson; otherwise, the customer appears for all salespersons.

Price List Code (codListaPreco)

Text (20)

1.0

Determines the default price list for this customer. This is the price list that will be selected when starting to enter a new order. *When the price list is locked, it cannot be changed on the order.

If bloqueiaListaPreco = 1, only the defined price list is shown when creating an Order and cannot be changed.
If bloqueiaListaPreco = 0 and has a defined price list, it is loaded as default, but can be changed.
If bloqueiaListaPreco = 0 and DOES NOT have a defined price list, no default price list is loaded, but allows selecting another price list.

This field is not cleared when sent empty from ERP to Demander. To clear the field, send the code of an unregistered price list.

Customer City Code (codCidade)

Integer (10)

Yes

1.0

Branch Code (codFilial)

Text (15)

1.0

Determines the default branch for this customer. This is the branch that will be selected when starting to enter a new order. *When the branch is locked, it cannot be changed on the order.

If bloqueiaFilialUnidade = 1, only the defined branch is shown when creating an Order and cannot be changed.
If bloqueiaFilialUnidade = 0 and has a defined branch, it is loaded as default, but can be changed.
If bloqueiaFilialUnidade = 0 and DOES NOT have a defined branch, no default branch is loaded, but allows selecting another branch.

This field is not cleared when sent empty from ERP to Demander. To clear the field, send the code of an unregistered branch.

Corporate Name (nomeRazao)

Text (100)

Yes

1.0

Trade Name (nomeFantasia)

Text (100)

Yes

1.0

Person Type (tipoPessoa)

Text (1)

Yes

1.0

F = Individual; J = Legal Entity

Visit Interval (intervaloVisitas)

Integer (10)

1.0

ID or State Registration (rgIE)

Text (20)

1.0

Primary Phone (telefone1)

Text (255)

1.0

Send with mask. EX: (51) 3714-7017

Secondary Phone (telefone2)

Text (255)

1.0

Buyer Email Address (emailComprador)

Text (255)

1.0

NF-e Email Address (emailNfe)

Text (255)

1.0

Financial Email Address (emailFinanceiro)

Text (255)

1.0

Contact Person at Customer (contato)

Text (50)

1.0

Customer Address (endereco)

Text (100)

1.0

Neighborhood (bairro)

Text (50)

1.0

ZIP Code (cep)

Text (10)

1.0

Send with mask EX: 95900-000

State (uf)

Text (2)

1.0

Note (observacao)

Text (2000)

1.0

Active (ativo)

Integer (1)

1.0

1 = Active or 0 = Inactive

Blocked (bloqueado)

Integer (1)

1.7

1 = Does not allow sales to Customer, 0 = Allows sales to Customer

Number (numero)

Integer (10)

1.11

Address Number

Address Complement (complemento)

Text (200)

1.11

Latitude (latitude)

Text (50)

1.12

Longitude (longitude)

Text (50)

1.12

Lock Branch/Unit editing (bloqueiaFilialUnidade)

Integer (1)

1.15

Prevents the salesperson from changing the customer default Branch during order entry.

Lock Price List editing (bloqueiaListaPreco)

Integer (1)

1.15

Prevents the salesperson from changing the customer default Price List during order entry.

Lock Payment Term editing (bloqueiaCondPagamento)

Integer (1)

1.15

Prevents the salesperson from changing the customer default Payment Term during order entry.

Lock Payment Method editing (bloqueiaFormaPagamento)

Integer (1)

1.15

Prevents the salesperson from changing the customer default Payment Method during order entry.

Individual State Registration (inscricaoEstadualPessoaFisica)

Text (30)

2.6

Demander Customer Unique Identifier (idCliente)

Integer (10)

2.10

ATTENTION: If the salesperson registered a new customer without entering CPF/CNPJ, the customer assumes code Zero. However, when the ERP returns the customer info it already comes with a code, so this field is used as a key to update the customer since CPF/CNPJ was not filled in. Therefore, your ERP must store this field to return it to Demander; otherwise, customers will duplicate in Demander or salespersons will not be allowed to register customers without entering CPF/CNPJ.

Tax Customer Type (codTipoClienteTributario)

Text (20)

2.13

This field is used by some companies in IPI and ICMS ST calculations; only be concerned with it if you integrate Tax configuration.

Related Salespersons (vendedoresRelacionados)

Text (500)

2.17

Send here the codes of the Salespersons who serve the customer separated by commas. This field only needs to be sent from ERP to Demander if more than one salesperson serves (views) the Customer. Example: "24, 75, 145" (If only one salesperson serves the customer, use only the codVendedor field). If a salesperson registers a new customer in Demander, only the codVendedor field is filled; this field starts empty.

Customer in Prospecting (prospecto)

Integer (1)

2.30

0 - Not a Prospect, already a Customer. 1 - Is a prospect, not yet a Customer. Demander allows salespersons to register prospects they are currently contacting. Normally these Prospects do not want to provide all registration details; therefore, in the Demander app we have a separate feature for prospect registration, including separate mandatory field settings. Even though they are not customers, Prospects can be exported to the ERP in the customer table layout; if your ERP is not structured to import prospects, configure them not to be exported by accessing "Company Settings", tab "Additional settings" and search for the setting "Export prospects" and set Yes or No. (Currently we do not support importing prospects without code or CNPJ, unless you use the "Demander Unique Identifier" field)

Change Identifier (idAlteracaoERP)

Text (255)

2.31

Field exclusively for ERP control. Demander only imports and returns it to the ERP. This field can be used for the ERP to implement change conflict control between ERP and salesperson.
(Internal note: See task #31145 in Redmine)

Commercial agreement percentage (percAcordoComercial)

Decimal

2.36

Currently the commercial agreement field is used to decrease or increase the customer maximum discount.
EX: If the company has a maximum discount of 25%, but the customer has a commercial agreement of 5%, then for this customer the salesperson can give up to 30% discount.
If it is necessary to decrease the customer maximum discount to 20%, -5 can be sent in the commercial agreement field.
(Customer Maximum Discount = Company Maximum Discount + Commercial Agreement)

Preferred Carrier Code (codTransportadora)

Text (30)

2.41

Customer preferred Carrier Code. If this field is filled during order entry, the system will automatically select this carrier, but will still allow changes.

Preferred Redispatch Carrier Code (codRedespacho)

Text (30)

2.41

Customer preferred Redispatch Carrier Code. If this field is filled during order entry, the system will automatically select this carrier, but will still allow changes.

Date of Birth (dataNascimento)

Date

2.47

Related segments (segmentosRelacionados)

Text (500)

2.48

Field to identify the segments that a given customer uses.
Ex: Motorcycle utilities, Bicycle utilities

Regional Council of Dentistry Number (cro)

Text (50)

3.5

Customer maximum discount percentage (percentualDescontoMaximo)

Decimal

3.6

Maximum discount percentage that the customer can receive on an order.
When filled, this field overrides any other discount rule.

Freight Rate Table Code (codFaixaFrete)

Text (30)

3.14

Freight Rate table code used to calculate the suggested freight amount.

Economic group code (codGrupoEconomico)

Text (100)

3.20

Defines which economic group the customer belongs to. It is necessary to integrate Table 35 - Economic Group.

Additional price lists (listaPrecosAdicionais)

Text (255)

3.20

Additional price lists that the customer can access.
If the customer has a locked list, the additional lists will NOT appear as options to be chosen.

Check-in radius (checkinRaio)

Integer (10)

3.20

Customer radius in meters, used for the Check-in Module.

Check-in days (checkinDias)

Integer (10)

3.20

Number of days since last Check-in, used for the Check-in Module.

Additional payment terms (condicoesAdicionais)

Text (255)

3.28

Additional payment terms that the customer can access.
If the customer has a locked payment term, the additional payment terms will NOT appear as options to be chosen.

Integration note (observacaoIntegracao)

Text (2000)

3.34

When integrated, an eye icon is displayed in the customer record, and this note is shown when clicking it.

Credit limit (limiteCredito)

Decimal

3.37

Used to block orders for customers that exceed the credit limit. Also used for the Financial Collections Module.

Contribution margin percentage (percMargemContribuicao)

Decimal (8,2)

3.38

Used for calculation in the Contribution Margin Module.

Appointed Salespersons (VendedoresPrepostos)

Text (500)

3.42

These are salespersons/representatives managed directly by the salesperson/representative. Example: The representative of ABC Company hires a Salesperson to sell for them; this person will be an Appointed Salesperson under this Representative.

Customer default hierarchy (codHierarquiaLiberacaoPedido)

Text (255)

3.42

Customer Type (codTipoCliente)

Text (30)

4.18

Code from table Customer Type.

Sales Division (codDivisaoVenda)

Text (30)

4.18

Code from table Sales Division.

Default order type (codTipoPedido)

Integer

4.22

Defines the default order type for the customer. This order type will be automatically selected when starting a new order. When locked, changing the order type is not permitted, as shown in the examples below.

If bloqueiaTipoPedido = 1.
Only the defined order type is shown when creating an Order and cannot be changed.

If bloqueiaTipoPedido = 0 and has a defined order type.
It will then be loaded as default, but can be changed.

If bloqueiaTipoPedido = 0 and DOES NOT have a defined order type.
No order type will be loaded, but allows selecting another order type.

This field is not cleared when sent empty from ERP to Demander. To clear the field, send the code of an unregistered order type.

Lock order type editing (bloqueiaTipoPedido)

Boolean

4.22

This field prevents the salesperson from changing the customer default order type when placing an order.

Additional order types (tipoPedidoAdicionais)

Text (255)

4.22

Additional order types that the customer can access.
If the customer has a locked order type, the additional order types will NOT appear as available options.

Unloading fee (valorDescarga)

Decimal (10,5)

4.47

Unloading fee per kg of net weight of the Order.

Can be used in calculating Ancillary Expenses.

Allows changing Ancillary Expense value
(permiteAlterarDespesaAcessoria)

Boolean

4.51

Determines whether or not the salesperson can change the suggested amount for "Ancillary Expense" in orders for this customer.

Requires purchase order
(exigeOrdemDeCompra)

Boolean

4.55

Determines whether the "purchase order" field is required for this customer.

* Only takes effect when the "Order Type" also "requires purchase order";
* If the requirement of the "Purchase Order" field is "Hidden", this setting has no effect.

Registration Example:

18|3004007|23.596.536/0001-17||0|0|170895|0|4322509|2|VILMAR MACIEL DE MORAES 78145171091|AUTO DESIGN CENTRO AUTOMOTIVO | 991127156|macieldemorais@bol.com.br|||ALINE|EST DO MARMELEIRO, 35|MAUA|95214410|RS||1|0||||||0|0|||9695140|G||0|2020-08-11 08:19:23|0||||||0||||0|0|||

Table 18 - Customers

Related articles