From the beginning it was very clear, I will define new ID's for my products. It's much more easier to take over the article number of the supplier, but if you have different suppliers for the same product? What do then?
I started thinking, how to define the ID's. It's more sophisticated than you can imagine.
First question: "With business logic, yes or no?" I've chosen the yes answer. Why? I have the possibility to group the articles as needed. And when somebody calls and says: "I've a question to article number 1-..." I know that he is talking about Window Color. So I defined main groups (numeric code)
Second question: "With business logic within the group?" Once again I've chosen yes. Reason: Colors have a certain code, and now it's part of the number together with the bottle size.
The most curious part of this whole stuff is the fact, that for more than 10 years, as ERP implementation consultant, I was saying to all my customers : "Chose numbers without business logic. You have other possibilities to group." And I personally don't listen to my own advice. That's it.
Not taking over the product number of the suppliers, I put the needed functionality: 1 Tinker ID - n Supplier ID's on the list of software requirements.
ToDo's:
- definition of article number
Conclusions:
- eCommerce software is no ERP system
- business logic makes ID's long. And long numbers are not feasable
- allocation of new ID's with business logic is time consuming
- difficult to change ID's after GoLive


