Shiloh/brotherton-erpnext
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[docs]

Browse Source
This commit is contained in:
Priya 2013-08-14 13:59:02 +05:30
parent 88d409cc83
commit c2f2103e4c
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/docs.user.setup.codification.md
View File

@ -3,16 +3,16 @@
"_label": "Item Codification"
}
---
If you already have a running business with a number of physical items, you would have probably coded your items. If you have not, you have a choice. We recommend you should codify, but its your call.
If you already have a full-fledged business with a number of physical items, you would have probably coded your items. If you have not, you have a choice. We recommend that you should codify if you have lot of products with long or complicated names. In case you have few products with short names, it is preferable to keep the Item Code same as Item Name.
Item codification is always a sensitive topic and wars have been fought on this (not joking). In our experience, when you have items that cross a certain size, life without codification is a nightmare.
Item codification has been a sensitive topic and wars have been fought on this (not joking). In our experience, when you have items that cross a certain size, life without codification is a nightmare.
### Benefits
- Standard way of naming things.
- Less likely to have duplicates.
- Explicit definition.
- Help you quickly find if a similar item exists.
- Helps to quickly find if a similar item exists.
- Item names get longer and longer as more types get introduced. Codes are shorter.
### Pain
@ -23,7 +23,7 @@ Item codification is always a sensitive topic and wars have been fought on this
### Example
You should have a simple manual / cheat-sheet to codify your items instead of just numbering them sequentially. Each letter should mean something. Here is an example:
You should have a simple manual / cheat-sheet to codify your Items instead of just numbering them sequentially. Each letter should mean something. Here is an example:
If your business involves wooden furniture, then you may codify as follows:
@ -52,7 +52,7 @@ The last few letters could be sequential. So by looking at code **WM304** - you
### Standardization
If you have more than one person naming items, the style of naming items will change for everyone. Sometimes, even for one person, he or she may forget how did they name the item and may create a duplicate name _"Wooden Sheet 3mm" or "3mm Sheet of Wood"?_
If you have more than one person naming items, the style of naming items will change for everyone. Sometimes, even for one person, he or she may forget how they had named the item and may create a duplicate name _"Wooden Sheet 3mm" or "3mm Sheet of Wood"?_
### Rationalizing