Amazon MVL Import Technical Scope
| Version | Date | Created / Updated | Notes |
|---|---|---|---|
| v1.0 | 21.01.2025 | Bogomil Pavlov | First Publish |
The purpose of this document is to give good overview how the MVL import should work.
Amazon does not split the Kcodes into MVLs and MMLs however they simply call the MVLs for both car and motorcycle. Also they have the same file structure which will make it easier for us to import.
The MVLs can be downloaded from here - https://sell.amazon.it/en/imparare/vendita-di-componenti-automobile
Despite that Amazon is using just MVLs we still want to split them into two separate structures one for cars (mvl) and one for motorcycle (mml) thus we will have dedicated table for each mvl.
| MVL tables | MML tables |
|---|---|
| mvl_amazon_uk | mml_amazon_uk |
| mvl_amazon_de | mml_amazon_de |
| mvl_amazon_es | mml_amazon_es |
| mvl_amazon_it | mml_amazon_it |
| mvl_amazon_fr | mml_amazon_fr |
| mvl_amazon_se | mml_amazon_se |
| mvl_amazon_nl | mml_amazon_nl |
| mvl_amazon_pl | mml_amazon_pl |
Each MVL we download from Amazon will have the same structure
| Make | Model | VariantName | BodyStyle | DriveType | Energy | EngineOutputKW | EngineOutputHP | Product Start Month-Year | Product End Month-Year | LastProcessedDate | Ktype | LatestStatus |
|---|
Thus our logic for the import should not use the field index number but the field header name and we agree that is the correct field names. However if we have a case where the the header names do not match or any of them is missing we want to return an error and stop the whole process of truncate and import.
| MVL header name | Hemi field name |
|---|---|
| Make | mvlMake |
| Model | mvlModel |
| VariantName | mvlVariant |
| BodyStyle | mvlStyle |
| DriveType | mvlDriveType |
| Energy | mvlEnergy |
| EngineOutputKW | mvlEngineKW |
| EngineOutputHP | mvlEngineHP |
| Product Start Month-Year | mvlStartYear |
| Product End Month-Year | mvlEndYear |
| LastProcessedDate | N/A |
| Ktype | mvlKtype |
| LatestStatus | N/A |
Before each MVL import if we can add additional step to truncated the table automatically and then import the new data.
In order to import the MVL we want to use our FTP credentials from where we can set the credentials and paths.
We want to check for FTP Credentials > Type = “Amazon MVL and MML Import” and for each territory to have separate path for example
FTP Path > Label = MVLUK
FTP Path > Label = MVLDE
FTP Path > Label = MVLES
FTP Path > Label = MVLFR
FTP Path > Label = MVLIT
FTP Path > Label = MVLPL
FTP Path > Label = MVLSE
FTP Path > Label = MVLNL
FTP Path > Label = MMLUK
FTP Path > Label = MMLDE
FTP Path > Label = MMLES
FTP Path > Label = MMLFR
FTP Path > Label = MMLIT
FTP Path > Label = MMLPL
FTP Path > Label = MMLSE
FTP Path > Label = MMLNL
The file name should be the same as the path with extension .xlsx