Huhtamaki ITC Pilot — Lane Data Collection

Completed

Processed 03 Aug 10:46 Exported 03 Aug 10:47

Procurement event draft

Review and correct every generated section before export.

Name

Type

Currency

Contract starts on

Duration months

Bidding starts at

Bidding ends at

Quantity per load

Load type

Load condition

Additional notes

Stable route identities. Period rows reference these lane IDs.

	column_key	name	scope	period	description	formula
No rows.

	column_key	name	bid_type	description	negotiated
No rows.

	name	type	expected_value	number_comparison_operator	presence_required	compliance_required
No rows.

Warnings

Tender.currency is missing
Tender.contract_starts_on is missing
No explicit lane ID column was present in the procurement event workbook; sequential Lanes.lane_id values starting at 1 were assigned.
Tender currency, contract duration, contract start date, bidding start date, and bidding end date were not present in the parsed workbook facts.
The procurement event workbook contains lane volume and LTL bid group reference data but no explicit carrier rate-entry table; bid columns were created from the FTL and pallet-band definitions.
Several source postal-code fields were parsed as numeric values, so leading zero preservation should be reviewed before launching the procurement event.
Some postal-code-like values are fragmented numeric prefixes; they were preserved as imported lane columns and not always included in geocodable origin or destination strings.
Instructions has no obvious table region
Lane Data Destination Postal Code contains numeric postal-code-like values; review leading zero preservation