Import files explained

Template company_import

The company_import is used to import all existing customers into Qargo.

Column name	Required/optional	Remarks	Example
name	Required	Customer name to be used in the application	Qargo
vat_number	Optional	customer's VAT number (no specific format is enforced)	BE1234567890
accounting_code	Required	Unique id	134
legal_name	Required	Legal customer name to put on official documents	Qargo Tech NV
iban_code	Optional
bic_code	Optional
is_customer	Required	If TRUE, will be created as a customer	TRUE or null
is_subcontractor	Required	If TRUE, will be created as a subcontractor	TRUE or null
archived	Optional	To import archived (not longer in use) customers	TRUE or null
note	Optional	Extra textual information regarding the customer. Usually this contains interesting information that is not part of one of the other categories described here.
website	Optional	Website of the customers	www.qargo.io
payment_term	Optional	To derive from the default customer payment_term
subcontractor_payment_term	Optional	To derive from the default subcontractor payment_term
currency	Optional		EUR
tax_type	Optional	To derive from the default tax_type. Tax_type is by default auto selected using vat_number.
locale	Optional
address	Required	street + number + eventual bus number	Gaston Crommenlaan 4
address_second_line	Optional
city	Required		Gent
postal_code	Required		9050
country	Required		Belgium
state	Optional
factoring_code	Optional
contacts__name	Use contacts import instead	Use contacts import instead	Use contacts import instead
contacts__email	Use contacts import instead	Use contacts import instead	Use contacts import instead
contacts__phone	Use contacts import instead	Use contacts import instead	Use contacts import instead
custom_fields__example	Optional	To import custom field values. Remark: 2 underscores are used in the column name.

Template contact_import

The contact_import template is an addition to the customer_import. Each customer can have multiple contacts. Each contact can have a specific role to differentiate between contacts purposes.

Column name	Required/optional	Remarks	Example
company_name	Required	Customer name used in the application	Qargo
company_accounting_customer_code	Required	Unique id used in the application. It's 'accounting_code' in the customer_impory	134
name	Required	Name of the contact	Thomas Smith
email	Required	E-mail of the contact	[email protected]
job_title	Optional
has_portal_access	Optional	Give a contact access to their company portal.	TRUE or null
note	Optional	Extra textual information regarding the contact. Usually this contains interesting information that is not part of one of the other categories described here.
phone	Optional		+324723372
has_role_billing	Optional	To send out invoices to this contact	TRUE or null
has_role_bookings	Do not use	Do not use	Do not use
has_role_cleaning	Do not use	Do not use	Do not use
has_role_container_release	Do not use	Do not use	Do not use
has_role_driver	Do not use	Do not use	Do not use
has_role_heating	Do not use	Do not use	Do not use
has_role_notifications	Do not use	Do not use	Do not use
has_role_operations	Optional	To send out operational documents such as transport orders or CMRs.	TRUE or null
has_role_storage	Do not use	Do not use	Do not use
has_role_other	Optional	To use in individual created tasks.	TRUE or null
custom_fields__example	Optional	To import custom field values. Remark: 2 underscores are used in the column name.

Template order_import

This template is mostly used to have some test data available in a sandbox tenant.

Column name	Required/optional	Remarks	Example
transport_service	Required	On which transport service the order needs to be placed. See configuration>transport service.	Container
customer_code	Required	Unique id used in the application. It's 'accounting_code' in the customer_impory
customer_name	Required	Customer name used in the application
customer_reference_number	Optional	How the order is know at customer side.
order_reference_number	Required	Unique ID only used during import.
order_requested_price	Optional
order_service_level_code	Optional
cmr_reference_number	Optional	CMR number on the top right of a CMR.
container_number	Optional	Number of the container
container_scenario	Optional
container_notes	Optional
container_date	Optional
container_yard_name	Optional
container_yard_full_address	Optional
container_yard_address_line_1	Optional
container_yard_address_line_2	Optional
container_yard_postcode	Optional
container_yard_city	Optional
container_yard_country	Optional
container_reference_number	Optional
pickup_date	Required	Date of collection	08/06/1989
pickup_time	Optional	Time of collection	06:00
pickup_name	Required	The name of the collection location. Locations unknown by the system will be created.
pickup_full_address	Optional	Only use when you're address data is not structured.	Boomsesteenweg 12, 2730 Boom, Belgium
pickup_address_line_1	Required	street + number + eventual bus number	Boomsesteenweg 12
pickup_address_line_2	Optional
pickup_postcode	Required		2730
pickup_city	Required		Boom
pickup_country	Required		Belgium
pickup_notes	Optional	Notes to be displayed to the driver at collection stop
pickup_reference_number	Optional
delivery_name	Required	The name of the delivery location. Locations unknown by the system will be created.
delivery_date	Required	Date of delivery	28/06/1989
delivery_time	Optional	Time of delivery	06:00
delivery_full_address	Optional	The name of the delivery location. Locations unknown by the system will be created.	Boomsesteenweg 12, 2730 Boom, Belgium
delivery_address_line_1	Required	Only use when you're address data is not structured.	Boomsesteenweg 12
delivery_address_line_2	Optional	street + number + eventual bus number
delivery_postcode	Required		2730
delivery_city	Required		Boom
delivery_country	Required		Belgium
delivery_notes	Optional	Notes to be displayed to the driver at delivery stop
delivery_reference_number	Optional
absolute_min_temperature_value	Optional
absolute_max_temperature_value	Optional
volume_lt	Optional
quantity	Optional	How many items will be loaded.	1
weight_kg	Optional		21485
goods_description	Optional	Description of the goods.
pallet_spaces	Optional
loading_meters	Optional
adr_un_number	Optional
packaging_type	Optional	Can only be used when packaging types are configured	Pallet
packaging_size	Optional
product_name	Optional	Can only be used when products are configured	Aardappelen

Template driver_import

To import own or subcontractor's drivers.

Column name	Required/optional	Remarks	Example
name	Required	Driver name displayed in Qargo	Steve Johnson
code	Optional	Unique code	12
first_name	Required		Steve
last_name	Required		Johnson
phone_number	Optional		+334717727
date_of_birth	Optional		27/12/1991
email_address	Required if driver app will be used.		[email protected]
note	Optional
subcontractor_company	Optional
archived	Optional
locale	Optional
custom_fields__example	Optional

Template vehicle_import

To import own or subcontractor's vehicles.

Column name	Required/optional	Remarks	Example
vehicle_type	Required	TRACTOR/VAN/RIGID/TRAILER	TRAILER
name	Required	Vehicle name displayed in Qargo	12BLT2 or VAN2
code	Optional
license_plate	Optional		12BLT2
subcontractor_company	Optional
trimble_object_id	Optional
trimble_active	Optional
webfleet_object_id	Optional
webfleet_active	Optional
archived	Optional
tare_weight	Optional
gross_weight	Optional
capacity_weight	Optional
capacity_volume	Optional
capacity_ldm	Optional
capacity_pallet_spaces	Optional
capacity_length	Optional
capacity_width	Optional
capacity_height	Optional
exterior_height	Optional
exterior_width	Optional
exterior_length	Optional
validity_start_timestamp	Optional
validity_end_timestamp	Optional
validity_description	Optional
custom_fields__example	Optional

Template combinations

To create combinations between a driver, TRACTOR/VAN/RIGID and or a trailer. In the below example, 'Steve Johnson' will by default be driving with Tractor '12BLT2'.

Column name	Required/optional	Remarks	Example
Vehicle_name	Required	Name as used in vehicle_import	12BLT2
Driver_name	Required	Name as used in driver	Steve Johnson
always_on_planning	Required	To be displayed every day on the planning board	TRUE

Template container_import

To import own or subcontractor's regularly used containers.

Column name	Required/optional	Remarks	Example
name	Required	Container name displayed in Qargo
code	Optional
manufacturer	Optional
container_number	Optional
standard_size	Optional
note	Optional
subcontractor_company	Optional
gross_weight	Optional
tare_weight	Optional
capacity_volume	Optional
capacity_weight	Optional
exterior_length	Optional
exterior_width	Optional
exterior_height	Optional
custom_fields__example	Optional

Template product_import

To import products used in order creation.

Column name	Required/optional	Remarks	Example
name	Required	Product name displayed in Qargo	Aardappelen
description	Optional
code	Optional
product_type_name	Required	Product type configured in Qargo. One product type can have multiple products.
adr_internal_code	Optional
adr_edition	Optional
adr_class	Optional
un_number	Optional
packing_group	Optional
specific_gravity	Optional
absolute_min_temperature	Optional
absolute_max_temperature	Optional
loading_meters	Optional
pallet_spaces	Optional
actual_pickup_temperature	Optional
actual_delivery_temperature	Optional
custom_fields__example	Optional

POD import/export

Customer Own Paperwork (import only)

Feature releases March 2024

Feature Release November 2024