As I mentioned in one of the previous columns, there is still no single IT solution that successfully handles all aspects of logistics, especially at the operational level. It is good when a Warehouse Management System (WMS) can cooperate with a superior system covering the management of the entire enterprise, ideally an ERP class system, and even better when the WMS is an element (module) of an integrated ERP class IT system. Observed reality shows that the functions of a system superior to WMS are most often performed by financial and accounting (FA), material management (MM), or sales systems, in which responsibility for the correct identification of materials lies with the office staff. It does not take long to realize that the quality of material item identification for a warehouse system in this type of approach is questionable at best. Accounting creates identifiers that are certainly unambiguous, because such conditions are set by the Material and Financial Management system, but their symbolism is often not tied to the physical characteristics of the material, but to entries on delivery documents, in particular invoices. Cases can be observed where materials similar in terms of general characteristics are “attached” to the same material indices. There are also cases where the same material has several different indices – e.g., a different one for each price. This tactic may be good, but only for the needs of FA systems. Logistics systems cannot accept such a situation. After all, a warehouse worker does not have to know what prices are assigned to materials that do not differ in physical characteristics yet are identified by different indices. Unambiguous identification of logistic units is a key issue in logistics, and any irregularities are immediately exposed by the system. This is one of the most important manifestations of the impact of IT on logistics. Identification ambiguities slow down the operation of the IT system or make its operation impossible. The users’ reaction is then unequivocal: the system is poor, it does not work, it is broken, it does not take our important specifics into account, etc. It is best to blame others and push the issue away from oneself, instead of looking at one’s logistics system through the “eyes” of the IT system.