mandothrasher

You might try doing a merge after your import. In a merge, it looks up the sku and then updates any other fields you include in the file. So, your merge file would only have two columns and look like this:

sku,tax:product_shipping_class

fyi…sku should be one of the values you are importing initially.

Looks like you’re using a tab delimited file format. Have you tried CSV (comma seperated values) format? That’s what I’m using. If you’ve got your data in Excel, choose CSV from the SaveAs dialogue.

Here’s the first two lines in my data file. If you copy this and paste into a text editor, it will be easier to read. Turn off word wrap if you’re using notepad. You’ll see the last field is shipping class this product is in the General shipping class that I have setup.

meta:Manufacturer,post_title,sku,post_content,images,meta:NDCItemCode,regular_price,tax:product_cat,tax:product_shipping_class
Alere Toxicology,ALERE TOXICOLOGY ISCREEN (DIP CARD) On-site testing. Saves time and money. Simple dip and read procedure. Laboratory accurate. Room temperature storage. Results in minutes. Detects 1-10 drugs. 24-month shelf life.,DOA-454,"Drug Test, 5 Test Dip Device, 25/bx",,INS DOA-454,143,Lab – Point of Care>Rapid Tests,General

Can you post a few lines from your csv file here, including the header?

Just wondering if the items already exist in the catalog? If so, be sure you’re doing a merge and not an import. Otherwise, I think the import skips items that it finds an existing SKU for.

Are you doing this as a Merge or Import?

Just found the answer and tested. This works. If you get to the mapping screen after uploading a file, just click one of the drop downs and you’ll see all the available columns names and taxonomies. That’s how I found it.

You column heading should be labeled as follows:

tax:product_shipping_class

Did you get an answer to this? I’m about to have the same need with an import. Would that be considered a taxonomy? Have you tried naming the column heading like this?

tax:shipping_class