Use standard Item Naming Series for Item Variants

apr · September 6, 2023, 12:34pm

The standard naming convention for Item Variants is PN-V1-V2, with PN being the parent name code and V1,… an abbreviation of the variants attribute. With several attributes, however, the name gets quite long and unwieldy. Is there a way to customize naming of item variants to preferably to use the standard naming series Items in general use?

alp · March 8, 2025, 6:24am

I have the same problem. I asked our consultants. One said, it is not possible. One said, “Maybe if you were to write scripts…”

And old post about the same problem suggests using import-export:

github.com/frappe/frappe

Auto-naming for Item Variant

opened 05:48AM - 17 Jun 16 UTC

closed 04:40AM - 19 Nov 21 UTC

niethaheng

So when you try to make a variant, the Item Name will be automatically written a…s [item_code]-[item_variant] like this: ![screen shot 2016-06-17 at 11 13 40 am](https://cloud.githubusercontent.com/assets/19649986/16141766/97283f22-347c-11e6-8edd-bddc218f0155.png) However, not all company use extensive item code. Example for our business, every item is very unique that the Generic Name is used for our documentation. I just made up new item code to comply with the system. However no one knows about the item code and don't see the importance. So we are trying to maker the new item name as the [item_name]-[item_variant] automatically such as this: ![screen shot 2016-06-17 at 11 16 12 am](https://cloud.githubusercontent.com/assets/19649986/16141802/ec5cc044-347c-11e6-99fb-908e53ca41ea.png) We can change it manually by typing. It is not a problem. Except if your portfolio includes this amount of item: ![screen shot 2016-06-17 at 11 17 09 am](https://cloud.githubusercontent.com/assets/19649986/16141811/1869b7d2-347d-11e6-992f-5b8b6be996d7.png) I tried to convince the team to use export-import feature instead but it is proven to be very complicated for them. Note that for each item in Pharmaceutical we have up to 5 variants. Is there any way I can make this more efficient? Best regards, Nietha

Docs say:

The naming of the variant will be based on the name (ID) of the template Item with a number suffix. e.g. “Screwdriver” will have variant “Screwdriver-1”.

I looked here (v15) but could not find it:

/app/document-naming-rule
/app/document-naming-settings
/app/item-variant-settings/Item%20Variant%20Settings
/app/stock-settings/Stock Settings

We are just starting to use ERPNext and so far the concept of Item Variant been more of a problem than convenience. The problems I experienced:

Different syntax during Data Import
Having to explain yet another concept to the users
Wondering whether X, Y, Z attributes of the variants will change when I update the Template
Not being able to show the attribute (such as S/M/L/XL) in a separate column
Attribute is suffixed to name, but a prefix would have been better (similar to reverse-DNS)

And it does not help at all where I need it the most: Numerical variants. We have numerous calipers which can measure distances within an interval such as [200mm, 250mm]. There is no logic in variants: You’ll either create them one-by-one or create multiple variants and have one caliper that measures from 200mm up to 250mm and another caliper that measures from 250mm up to 200mm. Add in calipers using imperial units, and you have no way of setting a sane increment. I’d have to create them by hand anyway.

I think I’ll do away with the variants. It’s simpler. Use duplication, Data Import, the API or simply create them manually. I’ll closely monitor new Items anyway. I don’t need the additional accuracy Item Attributes would bring to the table.