Magento product uploadsfrom your supplier’s spreadsheet

It does that job, with nothing typed by hand. Each product is matched to the real thing, and its specifications go in as attributes your store already has. The name, description, meta_title and meta_description are written from checked values to enforced lengths. Adobe’s guidance is a meta title under 70 characters and a meta description of 150 to 160, in a field that takes 255.

No. The file comes to you, and you run the import under System, Data Transfer, Import. Check Data validates it before you click Import. You choose Stop on Error or Skip error entries, and how many errors are allowed before the import is cancelled, 10 by default. Each run is then kept in Import History, with the imported file and its error file to download.

Yes. Adobe documents one product import for both, so the file suits either. Its guide does carry a note for Adobe Commerce on Cloud: when a file includes the categories or url_key column, URL rewrites are regenerated for every product in it, which lengthens the import and can cause timeout errors there. For large catalogues, Adobe advises leaving both columns out unless they are changing.

Yes, and in Magento the code is worth getting right. Adobe marks the SKU as the one required column and puts it first. Once a product exists, it is also the one field an import cannot change: “you can update all fields except SKU through import”. So each code is checked against the real product before it goes in, and the rest is filled from sources you can check.

Yes. A configurable product is the one a customer picks options on. In Magento each size or colour behind it is “a separate product with a distinct SKU”, which can be kept out of listings with the visibility Not Visible Individually. The configurable_variations column links them, giving each variation’s SKU and values, such as color=red,size=xs. Every value is written in your attributes’ own spelling.

With Add/Update, the file’s values replace the ones in your store. Adobe’s pages disagree on whether a blank cell clears a value, so an update file should carry only the columns you mean to change. With Replace, matching products are deleted and created again from the file, so Adobe tells you to take care with it.

Not with Add/Update. Adobe says multiple field values, such as websites or categories, “cannot be removed using the Add/Update import behavior”: a category missing from the file stays on the product. A wrong category from one file is therefore not undone by the next, so every product is filed into your own categories before the file is built.

It depends on the attribute’s default. On a new product, a required attribute left blank or invalid stops the row importing when there is no default, and takes the default when there is one. On an existing product, the old value stays. So a required value missing from the supplier’s sheet is found from a source where one exists, and flagged for you where none does.