Table 115 - Delivery Address
- This article introduces the fields of the shipping address integration layout. To better understand the concept behind addresses, see our article on Delivery Address Concept.
- To carry out this integration it is necessary to send the information along with Table 18 - Customers.
| Order | Field Description | Format and Size | Required | Version | Note | ||||
| 1 | Table Identifier (IDENTIFICADOR) | FIXO=115 (3) | Yes | 2.48 | Table used to register multiple addresses per customer | ||||
| 2 | idERP (idERP) | Integer (10) | Yes | 2.48 | Id or unique code in your ERP | ||||
| 3 | Customer Code (codCliente) | Integer (10) | Yes | 2.48 | Customer code at which address does this address belong to | ||||
| 4 | Description (description) | Text (255) | Yes | 2.48 | Description to facilitate identification of the address | ||||
| 5 | Rua (street) | Text (255) | Yes | 2.48 | |||||
| 6 | Number (number) | Text (255) | Yes | 2.48 | |||||
| 7 | Neighborhood (neighborhood) | Text (255) | Yes | 2.48 | |||||
| 8 | City Code (codCidade) | Integer (10) | Yes | 2.48 | |||||
| 9 | CEP (CEP) | Text (10) | Yes | 2.48 | |||||
| 10 | Reference (reference) | Text (255) | No | 2.48 | Reference, to make it easier to find the address | ||||
| 11 | Active (active) | Integer (1) | Yes | 2.48 | Informs if the configuration is active, send 1 for active or 0 for inactive. | ||||
| 12 | uniqueID of the delivery address (uniqueID) | Text (100) | No | 3.0 | This field is the unique id of the delivery address in Demander; To insert new records, you must enter blank or zero; To update records, the ID that the table generated when importing into your ERP must be passed in this field. (phone2) | Text (255) | No | 3.0 | |
| 15 | Main Contact (contact1) | Text (255) | No | 3.0 | |||||
| 16 | Secondary Contact (contact2) | Text (255) | No | 3.0 | |||||
| 17 | Address type (tipoEndereco) | Text (255) | No | 3.0 | Free text for better identification of the address type. Example: Street, house, apartment, street, etc… | ||||
| 18 | Unique Customer Identifier in Demander (idCliente) | Integer (10) | No | 2.10 | This field is used to identify the customer if they do not have one code, that is, being a new customer registered through the mobile system. This field is filled with the same value as field 38 in the customer table | ||||
| 19 | Latitude (latitude) | Text (50) | No | 3.4 | This field is used to plot routes and is also used to check-in at the client | ||||
| 20 | Longitude (longitude) | Text (50) | No | 3.4 | This field is used to trace routes and is also used to check in with the client | ||||
| 21 | Customer’s CPF or CNPJ (cpfCnpj) | Text (18) | No | 3.22 | |||||
| 22 | Related sellers (vendedoresRelacionados) | Text (500) | No | 5.6 | Determines which sellers have access to this address. When empty, everyone has access. Send comma separated values. Ex.: 65,38,02 | ||||
| 23 | Related branches (filiaisRelacionadas) | Text (255) | No | 5.9 | Determines which branches have access to this address. When the branch is selected in the order, only addresses that have that branch will be listed in the Related Branches field. When empty, all have access. Send comma separated values. Ex.: 101,102,103 |
Registration Example:
115 |