TRADACOMS ›
Customer Information › CUSINF
CUSINF: Customer Information Details
The CUSINF message is part of the TRADACOMS Customer Information file: customer master data including delivery locations.
The Customer Information file contains: CUSHDR → CUSINF → CUSTLR.
Message structure
| Segment | Name | Usage |
|---|---|---|
MHD | Message Header | One message for each location |
NOI | Nature of Information | Not repeatable in this message |
CLO | Customer's Location | |
NAM | Location Name and Address | |
LTY | Location Type | |
INT | Invoice To | |
STT | Statement To | |
TRA | Transmission To | |
LMI | Miscellaneous Information | |
DNA | Data Narrative | Repeat if necessary |
MTR | Message Trailer |
Segments and data elements
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
MSRF | Message Reference | M | V | 9(12) | Consecutive count of messages within the transmission |
TYPE | Type of Message composite | M | 'CUSINF' '8' for this version | ||
| Type | M | F | X(6) | ||
| Version Number | M | F | 9(1) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First Level Sequence Number | M | V | 9(10) | Starts at 1 and is incremented by 1 for each segment of this type in the message. Always 1 for this message |
TYPC | Type of Change | M | V | X(6) | "ADD", "DELETE", "AMEND" or "REPORT". "REPORT" is used in 'complete transmissions' for sending information which has not changed since previous transmissions |
DARA | Date of Change composite | C | Format: YYMMDD Start date is mandatory for ADD, AMEND and DELETE | ||
| Start Date | C | F | 9(6) | ||
| End Date | C | F | 9(6) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
CLOC | Customer's Location composite | M | One of the following 3 customer's references must be present EAN Location number identifying the customer's location Customer's own identity for the location Supplier's reference for the customer's location | ||
| Customer's EAN Location Number | C | F | 9(13) | ||
| Customer's Own Location Code | C | V | X(17) | ||
| Supplier's Identification of Customer's Location | C | V | X(17) | ||
CNAM | Customer's Name | C | V | X(40) | Customer's registered legal name |
CADD | Customer's Address composite | C | A maximum of five lines to give customer's address | ||
| Customer's Address Line 1 | C | V | X(35) | ||
| Customer's Address Line 2 | C | V | X(35) | ||
| Customer's Address Line 3 | C | V | X(35) | ||
| Customer's Address Line 4 | C | V | X(35) | ||
| Customer's Post Code | C | V | X(8) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
LNAM | Location Name | M | V | X(40) | |
LADD | Location Address composite | M | A maximum of four lines plus post code to give the address of the location | ||
| Location Address Line 1 | M | V | X(35) | ||
| Location Address Line 2 | C | V | X(35) | ||
| Location Address Line 3 | C | V | X(35) | ||
| Location Address Line 4 | C | V | X(35) | ||
| Location Post Code | C | V | X(8) | ||
LTEL | Location Telephone Number | C | V | 9(15) | |
LTLX | Location Telex Number | C | V | 9(15) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
ORDF | Order From | M | F | X(1) | Y = Yes, N = No |
DELT | Deliver To | M | F | X(1) | Y = Yes, N = No |
INVT | Invoice To | M | F | X(1) | Y = Yes, N = No |
STAT | Statement To | M | F | X(1) | Y = Yes, N = No |
DESF | Despatch From | M | F | X(1) | Y = Yes, N = No |
PMNT | Payment To | M | F | X(1) | Y = Yes, N = No |
ETFT | Electronic Transmission From/To | M | F | X(1) | Y = Yes, N = No |
REGC | Customer's Region Code | C | V | X(17) | Code allocated by customer to classify region of the location |
OUTY | Type of Outlet Code | C | V | X(2) | Code allocated by customer to classify type of branch (eg. by selling space) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
ILOC | Invoice Location composite | C | Location to which invoices should be addressed. Quoted if location receives invoices but not deliveries EAN Location number to identify invoice point Customer's own code identifying invoice point | ||
| EAN Location Number | C | F | 9(13) | ||
| Customer's Invoice Location Code | C | V | X(17) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SLOC | Statement Location composite | C | Address to which statement should be sent EAN Location number identifying statement location Customer's own code identifying statement location | ||
| EAN Location Number | C | F | 9(13) | ||
| Customer's Statement Location Code | C | V | X(17) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
ITRA | Invoice Transmission Recipient composite | C | Location to which invoice transmission should be made. Quoted if different from ILOC EAN Location number identifying point to which invoice transmissions should be made Customer's own code identifying point to which invoice transmissions should be made | ||
| EAN Location number | C | F | 9(13) | ||
| Customer's Code for Transmission Recipient | C | V | X(17) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
BINN | Booking in Necessity | C | F | X(1) | Is it necessary to book in before delivering to the branch being described? Y = Yes, N = No |
TFAC | To Follow Acceptability | C | F | X(1) | If a part order is delivered is it acceptable to deliver the balance later? Y = Yes, N = No |
DINS | Delivery Instruction Narrative composite | C | Narrative covering special instructions applicable to orders | ||
| Delivery Instruction Narrative Line 1 | C | V | X(40) | ||
| Delivery Instruction Narrative Line 2 | C | V | X(40) | ||
| Delivery Instruction Narrative Line 3 | C | V | X(40) | ||
| Delivery Instruction Narrative Line 4 | C | V | X(40) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First Level Sequence Number | M | V | 9(10) | Starts at 1 and incremented by 1 for each repeat of this segment |
DNAC | Data Narrative Code composite | C | Standard data narrative previously defined and agreed by sender and receiver Number of relevant code list Code Value from code list · code list 22 | ||
| Code Table Number | C | V | 9(4) | ||
| Code Value | C | V | X(3) | ||
RTEX | Registered Text composite | C | Essential text, where not provided for by specific fields may be communicated using this element. Application codes to define the function of the text must be registered with the ANA prior to use. The same application code may be repeated up to four times, or up to four different codes may be used · code list 24 | ||
| First Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Second Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Third Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Fourth Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
GNAR | General Narrative composite | C | |||
| General Narrative Line 1 | C | V | X(40) | ||
| General Narrative Line 2 | C | V | X(40) | ||
| General Narrative Line 3 | C | V | X(40) | ||
| General Narrative Line 4 | C | V | X(40) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
NOSG | Number of Segments in Message | M | V | 9(10) | Control count of the number of segments comprising message. The count includes the MHD and MTR segments surrounding the message |
Need to exchange TRADACOMS messages with a UK retailer?
SupplyLens connects your ERP, e-commerce or accounting system to any TRADACOMS or EDIFACT trading partner: orders in, invoices out, fully managed.
Book a demo Learn about retail EDI →