Basic requirements for the CSV file

• File size limit: 100MB
• File format: CSV
• Link to a template: download here
• CSV template headers must match the field values listed in the template. Fields that don’t match the values will be ignored during the import process.
• Only part_external_id field is a mandatory field, however, for the item to be listed in the Ovoko marketplace you need to add part_ovoko_category_id, part_photo_urls, car_ovoko_model_id, part_price fields. Otherwise parts will be created as Drafts(not available on the marketplace)

Update vs. Remove

“Import parts via CSV” has two import options that you can select after uploading the file:

• Update: Parts that already have the same part_external_id field value are updated. New parts will be created if part_external_id does not exist within the system
• Update & Remove: Parts will be removed If you already imported them via CSV before and they don’t exist in the new file. Parts that already have the same part_external_id field value are updated.

Field requirements

Download this CSV template and follow the field requirements below.

• part_external_id(required): Must be unique. If the part with the same part_external_id already exists within the Ovoko it's values will be updated
• part_ovoko_category_id: Provide a category identifier that matches Ovoko part category identifier. If the field does not match any Ovoko categories it will be left blank and the part will not be added to the Ovoko marketplace. Refer to this sheet to get specific Ovoko part category ID values.
• part_photo_urls: Comma separated list of URLs that Ovoko will attempt to download photos from. All URLs must be accessible publicly and not have any specific request header requirements for Ovoko to be able to download them. The first photo in the URL is going to be used as a main/cover image within the listings. Supports .PNG, .JPEG file formats.
• part_price: Floating point number. A final price, with all tax included that is going to be displayed to the buyer. Expressed in the default currency of your Ovoko SaaS account. E.g. 230.39Eur should be added as 230.39
• part_manufacturer_code: Also known as OEM code. A part code that can help buyers better identify the part and decide if it will work for their vehicle.
• part_additional_codes: A comma separated list of additional codes found on the car part.
• part_quality: Must match one of the following values. If no values are present used will be added as a default:
  • used
  • with_defects
  • restored
• part_status: Can be one of the following values. If no values are present "in_stock" will be used as a default:
  • in_stock
  • reserved
  • sold
• part_description: A public-facing text description that will be visible within the Ovoko marketplace. Only supports text. HTML syntax will not be supported
• part_internal_notes: An internal note that is only visible to your internal employees with the Ovoko SaaS
• part_position: Used for parts that have a specific position. For example Side-view mirrors, doors, handles etc.. Must match one of the following values:
  • all
  • left
  • center
  • right
  • set
  • left_rear
  • right_rear
  • left_front
  • right_front
  • in_front
  • rear
• car_external_id: A unique value of the car. If the car already exists within your Ovoko account all parts will be attached to that car
• car_ovoko_model_id: Must match one of the Ovoko car models. Here's a list of Ovoko car model IDs. If the model ID is not present the part will still be created, however, it will not be listed on the Ovoko marketplace.
• car_year: A year when the car was manufactured. A number from 1900 to the current calendar year. Does not accept full dates with months or days.
• car_vin_code: A unique vehicle identification number. Also known as Vehicle chassis number.

Category specific requirements

Some Ovoko SaaS categories have additional information requirements to make them available on Ovoko marketplace and to be more likely to sell. Fill in the required information categories listed below. Leave these fields blank if they don’t apply to the category that you are entering.

• car_fuel_id: Needed for some of the engine parts. You can check the specific engine part categories and their IDs here. Can be one of the following values:
  • diesel
  • petrol
  • petrol_lpg
  • petrol_electricity
  • electric
  • diesel_electricity
  • diesel_lpg
  • bioethanol
• car_engine_power: Number that expresses Kw power of an engine. Needed for some of the engine parts. You can check the specific engine part categories and their IDs here.
• car_engine_cubic_capacity: Number that expresses cubic centimeters of an engine capacity. 2.3 Liter engine capacity should be added as 2300. Needed for some of the engine parts. You can check the specific engine part categories and their IDs here.
• car_engine_number: An engine number. Needed for some of the engine parts. You can check the specific engine part categories and their IDs here
• part_manufacturer_code: Also known as OEM code. A part code that can help buyers better identify the part and decide if it will work for their vehicle. Needed for some of the engine parts. You can check the specific engine part categories and their IDs here.
• part_wheels_amount: Only applies to rims and tires categories. If values are present for other categories, this field will be ignored. A number that represents the quantity of parts.
• part_rims_spacing: A floating point that expresses rim spacing. Needed for all rim categories. You can check the specific rim categories and their IDs here.
• part_rims_fixing_points: A number between 3 and 16. Needed for all rim categories. You can check the specific rim categories and their IDs here.
• part_rims_pitch_circle_diameter: A floating point number that expresses the pitch circle diameter. Needed for all rim categories. You can check the specific rim categories and their IDs here.
• part_rims_central_hole_diameter: A floating point number that expresses the central hole diameter. Needed for all rim categories.Needed for all rim categories. You can check the specific rim categories and their IDs here.
• part_tires_height: Floating point number that expresses the tire height. Needed for all tire categories. You can check the specific tire categories and their IDs here.
• part_tires_width: Floating point number that expresses the tire width. Needed for all tire categories. You can check the specific tire categories and their IDs here.
• part_tires_thread_depth: Floating point number that expresses the thread depth of a tire. Needed for all tire categories. You can check the specific tire categories and their IDs here.