Amazon SP-API Fitment

Amazon utilizes vehicle fitment codes, often referred to as KCodes, to specify vehicle compatibility for automotive parts and accessories. These codes are integral to Amazon's fitment system, enabling precise matching of parts to specific vehicle makes and models. Amazon's product type schemas include attributes specifically designed for vehicle fitment, facilitating accurate automotive parts compatibility

First of all our idea is to utilize our existing Kcodes logic and make it usable for both Amazon and eBay since they both use the same types of kcodes (Ktype for eBay and TecDoc for Amazon, which are essentially the same). In order to do this, we first need to start by amending our existing infrastructure. We want to rename the table and some fields, and also add some new fields.

“eBay Kcodes” table should be renamed to “Fitment” table. It is still dependant table of Product AccountPlease find the structure below.

Also we want to make sure the table is also visible for Amazon listings.

After we have the info we need, we then have to send it to Amazon. This is done via the listing create/update (Amazon SP API Listing Create) using the JSON schemas. In the vehicle JSON schemas, there is a vehicle_fitment object in which we provide the info.

Example: (please note this example is strictly for the vehicle_fitment object, all other objects part of the payload are excluded here) :

{
  "vehicle_fitment": [
    {
      "standard": [
        {
          "value": "TecDoc",
          "language_tag": "en_GB"
        }
      ],
      "code": [
        {
          "value": "0035AFR, 59799",
          "language_tag": "en_GB"
        }
      ],
      "note": [
        {
          "value": "0035AFR: Only for model years 2008 and higher, 59799: Only for models with automatic transmissions",
          "language_tag": "en_GB"
        }
      ],
      "marketplace_id": "A1PA6795UKMFR9"
    }
  ]
}

Mapping :

There are no triggers, no validations etc. as this is part of our Listing process and everything related is in there.

As additional note to make things extra clear - even if it seems that nodes code and note are arrays in the example everything we’ve seen so far is that we need to pass the info into only one code and note, combined and separated with a comma (,). This means we need to pick all kcodes associated with the listing and put them all in one value (example: kcode_1, kcode_2, kcode_3, kcode_4, kcode_n) and if they have any notes against them put them in the notes field together again based on the structure explained above (example: kcode_1: note_1, kcode_4: note_4, kcode_n: note_n)