TRACT runs two rounds of validation on every file:
• File Check — runs immediately when you upload the file and validates formatting, required fields, and accepted values. Issues here are caught before any data is processed.
• System Check — runs after the file check passes and validates records against existing data in TRACT.
Before you upload: mandatory fields
Some fields are required for every record. If any mandatory field is left empty, your upload will fail. Always make sure the following are filled in before uploading:
• Product
• StartNodeID
• SubProduct
• ProductCertification
• SupplyChainType
• UnloadDate
Important: Traceability records reference your Master Data via StartNodeID and EndNodeID. Your Master Data must be uploaded and correct before uploading Traceability data. If the IDs in your Traceability file do not match existing Master Data records, the upload will fail.
1. Wrong Date Format
Occurs during: File Check
UnloadDate and other date fields must match one of the accepted formats. Free text, custom formats, or incomplete dates will be rejected.
Accepted formats
• DD/MM/YYYY (e.g. 23/04/2025)
• MM/YYYY (e.g. 04/2025)
• MMM/YYYY (e.g. Apr/2025)
• YYQQ (e.g. 2501 for Q1 2025)
• YYYY (e.g. 2025)
• ISO 8601 with timezone offset (e.g. 2025-04-23T14:30:00Z)
Where separators are used, /, -, and . are accepted.
Applies to: UnloadDate, SalesContractDate, DeliveryPeriodStartDate, DeliveryPeriodEndDate
How to fix it
• Use one of the accepted formats listed above
• Make sure the date is complete — partial or ambiguous dates will fail
• Check for typos such as letters mixed into date fields
Example
UnloadDate |
❌ April 2025, 23-Apr, 04.23.2025 |
✅ 23/04/2025, 04/2025, 2025 |
2. Missing Mandatory UnloadDate
Occurs during: File Check
UnloadDate is a required field for every Traceability record. If any row is missing an UnloadDate, the entire upload will fail.
How to fix it
• Check every row has a value in the UnloadDate column
• If the exact date is unknown, use a year (YYYY) or month/year (MM/YYYY) format
3. Missing Mandatory ProductCertification
Occurs during: File Check
ProductCertification is a required field. It must be filled in for every record and must be a valid certification for the selected Product.
How to fix it
• Make sure no ProductCertification cells are blank
• Check the value matches an accepted certification for your product (see #10)
4. Node ID Not Found in Master Data
Occurs during: System Check
The StartNodeID or EndNodeID is correctly formatted but does not exist in your Master Data. TRACT cannot process a Traceability record that references a location it does not recognise.
How to fix it
• Make sure your Master Data has been uploaded before the Traceability file
• Copy the exact Node ID from your uploaded Master Data rather than typing it manually
• Check for extra spaces, typos, or formatting differences
5. Duplicate Node ID in Master Data
Occurs during: System Check
This error is caused by an issue in your Master Data and prevents TRACT from validating the Traceability record. The Node ID you are referencing as a Start or End Node has a duplicate Node ID in Master Data, which means TRACT cannot uniquely identify which record to link to.
How to fix it
• Go to your Master Data and resolve the duplicate Node ID first
• Re-upload the corrected Master Data
• Then re-upload your Traceability file
6. StartNodeID Invalid Format
Occurs during: File Check
The StartNodeID is not in a valid format and cannot be checked against Master Data. The StartNodeID must be either a 32-character system-generated Node ID or a user-defined Node ID from your Master Data.
How to fix it
• Copy the exact ID directly from your uploaded Master Data
• Do not shorten, abbreviate, or manually type Node IDs
• Check for extra spaces or hidden characters
Example
StartNodeID |
❌ farm001, FARM 001, 123 |
✅ a1b2c3d4... (32-character ID) or your exact Node ID |
7. Duplicate TransactionId
Occurs during: System Check
Every transaction must have a unique TransactionId, both within your file and against all previously uploaded records. TRACT rejects any TransactionId it has already seen.
How to fix it
• Check your file for rows with the same TransactionId
• Check if the same TransactionId was used in a previous upload
• Assign a new unique ID to the duplicate
Example
TransactionId |
❌ TXN-001 (row 3) and TXN-001 (row 12) |
✅ TXN-001 (row 3) and TXN-002 (row 12) |
8. TransactionId Wrong Format
Occurs during: File Check
TransactionIds must contain only letters, numbers, and the following separators:
• Period (.)
• Underscore (_)
• Hyphen (-)
Spaces and other special characters are not allowed.
How to fix it
• Remove spaces and unsupported special characters
• Use only . _ - as separators
Example
TransactionId |
❌ TXN 001, TXN@2025, TXN/001 |
✅ TXN-001, TXN_2025, TXN.001 |
9. TransactionId Required When EndNodeID Is Missing
Occurs during: System Check
If you leave the EndNodeID blank (an open-ended segment), TRACT requires a TransactionId to track the shipment. Without it, the record cannot be processed.
How to fix it
• If EndNodeID is blank, enter a TransactionId
• Alternatively, provide an EndNodeID if one is available
• Make sure at least one of these fields is populated before uploading
10. Product Certification Not in Scope
Occurs during: File Check
The certification you entered is not valid for the product you selected. Each product has a defined list of accepted certifications. Values outside that list will be rejected.
How to fix it
• Check that the ProductCertification matches an accepted value for your specific product
• Make sure the ProductCertification field is populated (see #3)
• Contact your TRACT customer success manager if you are unsure which certifications are valid for your product
Tip
Before uploading Traceability data, confirm that:
• Your Master Data has already been uploaded
• All referenced Node IDs exist in Master Data
• All TransactionIds are unique
• Required fields are populated and dates use an accepted format
These are the most common causes of Traceability upload failures.