Product CSV product variant names

[jtrotsky]

The name column in the product CSV should not contain the variant option values.
The variant values are added automatically to the name once already imported.

Take the example product called hi.
Here's how it looks now, notice it shows hi / 13:

Here's how it needs to look:

The fix is to use base_name rather than name from /api/products.

products: [
{
id: "b8ca3a65-0109-11e4-fbb5-a75acaaa630d",
handle: "hi",
variant_parent_id: "",
variant_option_one_name: "Amount",
variant_option_one_value: "13",
variant_option_two_name: "",
variant_option_two_value: "",
variant_option_three_name: "",
variant_option_three_value: "",
active: true,
name: "hi / 13",
base_name: "hi",

[pulkitsinghal]

Very cool, good to know about base_name! I'm thinking that I should distinguish between just an export for external usage w/ 3rd party software and an export which will be imported right back into Vend ...

[jtrotsky]

Good point @pulkitsinghal .
I suppose it is useful to keep the format as similar as possible, but you could format the CSV drastically differently if it were better for use by 3rd parties.

id, name, handle, sku, retail_price, tax_name are the only mandatory fields for importing to an inclusive store, for example.

[pulkitsinghal]

I'm thinking of an explicit flag to enable the functionality, something like:

1. --formatForVend true, or
2. --vendCompatible true, or
3. --vendFriendly true, or
4. --vendFormatted true, or
5. --dataFormat vend

[jtrotsky]

As in the other issue, I like #3 personally :)