# Truck Manifest Export **File type:** Pipe delimited. **Location:** `/dti/exchange/cm`. The regular manifest will be named `manifest`, where \ is the system ID of the process that generated the file. The advance truck manifest will be named `advmanifest`.

Record	Field	Max Length
Truck Time Data	A1	2
	Truck ID	8
	Truck time	8

Subscription Data	Note: Subscription Data records will only be exported for throwoff routes (when the subscription is delivered by the truck driver)
	S1 (Subscription data begins)	2
	Main Product ID	8
	Subscriber ProductID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Drop order or “unassigned”	8
	Route ID	8
	"THROWOFF"	8
	Edition	8
	Number of copies	3
	Subscription ID	10
	Address Line1	30
	Address Line 2	30
	Address Line 3	30
	Address Line 4	30
	Address Line 5	30
	Address Line 6	30
	Map Reference	4
	Map Number	4

Route Detail	R1 (Route Detail begins)	2
	Main Product ID (may be different from the route’s product ID if this is a combined publishing day)	8
	Product ID (the route’s product)	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Truck Drop Order	8
	Route ID (or Relay Truck ID, if drop is to relay truck)	8
	Route Type or Single Copy Type	8
	Route Type Indicator (“HD” for Home Delivery, “SC” for Single Copy, and “Relay” for Relay Truck)	5
	Depot ID	8
	Depot Drop Order	8
	Edition (or paper section if advance manifest)	8
	Draw Total	7
	Number of Standard Bundles	5
	Number of Key Bundles	5
	Key Bundle Size	3
	Carrier Name (last name first name)	30
	Carrier Phone Number	14
	Insert Mix Combination	17
	Drop Location	N/A
	Drop Instructions	N/A
	Ad Zone	8
	Preprint Demographic	8
	Insert Exception Indicator (“y” if sorted separately because of insert mix)	1
	Bulk Indicator (“y” if bulk)	1
	Hand Tie Indicator (“y” if below minimum bundle size)	1
	Minimum Bundle Size	3
	Maximum Bundle Size	3
	Standard Bundle Size	3
	Route Name (for home delivery routes) or Single Copy Location (for single copy routes). Not exported if using Syncronex.	30
	Map reference	4
	Map number	4
	Multipack ID	8
	Weight of product/route combination	11
	Total drop weight	11
	Standard bundle weight	11
	Single copy rate (optional, based on Business Rules)	15
	Supply truck ID (optional, based on Business Rules)	8
	Carrier ID	8
	Chute number (format is defined in Business Rules)	8
	Departure order	10

Draw Totals (actual draw by draw type/class)	D1 (Draw Totals by Draw Class begin)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Truck Drop Order	8
	Route ID (or Relay Truck ID, if drop is to relay truck)	8
	Draw Type/Class	9
	Draw Total	7
	Supply truck name (relay parent). Only exported if the Business Rules are configured to print the supplying truck, and the truck dropping the route is a relay.	20
	Main publication name	30
	Daily publication name (from Publication Days setup). If not defined, the main publication name exports.	30

Previous Draw Totals (previous week’s draw for the route)	P1 (Previous Draw Totals begin)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Truck Drop Order	8
	Route ID (or Relay Truck ID, if drop is to relay truck)	8
	Total Draw for previous publishing date	7
	Total Draw for current publishing date minus total draw for previous publishing date	7

Previous Draw Totals by Draw Type (previous week’s draw for the route by draw type)	P2 (Previous Draw by Draw Type begin)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Truck Drop Order	8
	Route ID (or Relay Truck ID, if drop is to relay truck)	8
	Draw Type/Class	9
	Total Draw for previous publishing date	7
	Total Draw for current publishing date minus total draw for previous publishing date	7

Advance Section Detail	Note: Advance Section Detail records will only be created for live truck manifests if a route has updraws (i.e. actual draw is greater than advance draw)
	R2 (Advance Section Route Detail begins)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Truck Drop Order	8
	Route ID (or Relay Truck ID, if drop is to relay truck)	8
	Paper Section	8
	Updraw	7
	Insert Mix	17
	Carrier ID	8
	Chute number (format is defined in Business Rules)	8
	Departure order	10

TM Product Detail	Note: TM Product Detail records will be created if a route is delivering additional publications or TM products and the publication is set up to print additional products on bundle tops
	R3 (TM Product Route Detail begins)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Truck Drop Order	8
	Route ID (or Relay Truck ID, if drop is to relay truck)	8
	TM Product ID	8
	TM Draw Total	7
	Number of Standard Bundles	3
	Number of Key Bundles	3
	Total Key Draw	7
	Minimum Bundle Size	3
	Maximum Bundle Size	3
	Standard Bundle Size	3
	Weight	9
	Standard Bundle Weight	9
	Supply Truck ID (optional, based on Business Rules)	8
	Carrier ID	8
	Chute number (format is defined in Business Rules)	8
	Departure order	10

Truck Weight Detail	W1 (Truck Weight Detail begins)	2
	Edition	8
	Truck ID	8
	Run Date	8
	Run Type (will be Actual, Advance, or Extra)	7
	Total weight

Truck Totals	Note: 1 record will be created for each truck/insert mix combination
	T1 (Truck Totals begin)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Insert Mix Combination	17
	Number of Bundles	8
	Total Draw	8
	Key Draw	8
	Number of Standard Bundles	8
	Number of Key Bundles	8
	Bulk Draw Total	8
	Bulk Key Draw Total	8
	Number of Bulk Standard Bundle Tops	8
	Number of Bulk Key Bundle Tops	8
	Number of Hand Ties	8
	Number of Throwoffs	8
	Rounded Draw (if advance run and IM connected)	10
	Total weight	6
	Supply truck name (relay parent). Only exported if the Business Rules are configured to print the supplying truck, and the truck dropping the route is a relay.	20
	Chute number (format is defined in Business Rules)	8
	Driver’s name	40
	Departure order	10
	Publication Name of the Main Product ID (above)	30
	Publication Name of the Product ID (above) - The daily publication name, when publication names are defined by weekday	30

Advance Section Truck Totals	Note: Advance Section Truck Total records will only be created for live truck manifests if a truck’s advance draw is rounded
	T2 (Advance Section Truck Totals begin)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	Paper Section	8
	Updraw	8
	Chute number (format is defined in Business Rules)	8
	Driver’s name	40
	Departure order	10

TM Product Totals	Note: TM Product Total records will be created if a truck is delivering additional publications or TM products and the publication is set up to print additional products on bundle tops
	T3 (TM Product Truck Totals begin)	2
	Main Product ID	8
	Product ID	8
	Run Type (will be Actual, Advance, or Extra)	7
	Run Date	8
	Truck ID	8
	Truck Name	20
	TM Product ID	8
	Total Drops	8
	Total Bundles	8
	TM Draw Total	8
	Total Standard Bundles	8
	Total Key Bundles	8
	TM Total Bulk Draw	8
	Total Bulk Standard Bundles	8
	Total Bulk Key Bundles	8
	Bulk Key Size	3
	Total weight	9
	Chute number (format is defined in Business Rules)	8
	Driver’s name	40
	Departure order	10

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.navigaglobal.com/circulation-user-manual/14-appendix-b-file-formats/truck-manifest-export.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.