eTIMS Item Class Codes: How the List Works and How to Pick Yours

eTIMS asks for two different identifiers on every product, and confusing them is the root of most of the trouble. The item classification code is KRA’s category for the kind of thing you sell: a standard, shared value that means the same for you as for a shop in Kisumu selling the same category of goods. The item code is yours: it identifies your particular product, in your particular packaging, at your particular size.

The split exists because the two answer different questions. KRA needs the classification to understand the economy in aggregate, which is why the list follows an internationally recognised structure rather than something invented locally. You need the item code so that your invoice says "Bamburi cement 50kg" rather than "portland cement products", and so that your stock counts mean something.

The classification list itself is hierarchical, the way product taxonomies usually are: broad segment at the top, narrowing through family and class down to a specific commodity. That structure is what makes searching work. If you cannot find the exact commodity, you move one level up and pick the class that contains it, which is a legitimate answer rather than a fudge.

Your own item code is assembled from a few standard components rather than being free text: the origin of the goods, what type of item it is, how it is packaged, the unit it is measured in, and a sequence number that makes it unique within your business. eTIMS presents most of these as dropdowns during item registration, which is deliberate, because it stops two shops using the same letters to mean different things.

The practical consequence of all this is that item setup is a one-time job with a long tail. You will map your main lines in an afternoon and then spend the next few months adding a class here and there as new products arrive. That is normal, and it is much less painful than it sounds if the mapping lives in your POS rather than in somebody’s memory.

This is the workflow that gets a real shop’s catalogue mapped without turning into a week-long project.

1. 1

   Start from the list inside eTIMS, not a copy

   The authoritative list is the one in the portal, because it is the one being validated against when you submit. Downloaded copies circulating online go stale quietly: a class gets retired, a new one is added, and the copy gives no hint that anything changed. Use the search inside eTIMS and treat any other list as a rough guide at best.

2. 2

   Group your catalogue before you touch the system

   Write out your products and put them into buckets by what they are, not by supplier or shelf. A shop with four hundred lines usually has twenty or thirty genuine categories. Mapping the buckets is fast; mapping four hundred lines one at a time is what makes people give up halfway.

3. 3

   Search by the plain name of the thing

   Search for the ordinary word first, so sugar, cement, shampoo or consultancy, rather than your brand name or your internal shorthand. The list is organised around what things are. If the plain word returns nothing, try the material or the function instead.

4. 4

   When the exact commodity is missing, go one level up

   Not every product in Kenya has its own line in a global taxonomy, and it is not supposed to. Choosing the class that genuinely contains your product is the correct answer, not a compromise. What you must not do is pick an unrelated class because it was easier to find.

5. 5

   Set the item type honestly

   Items are distinguished by whether they are raw materials, finished goods or services, and this affects how your purchases and sales reconcile. A hardware shop selling cement is selling a finished good; a contractor consuming that cement on a site is holding a raw material. Pick the one that matches your business, not the one your supplier used.

6. 6

   Get packaging and quantity units right the first time

   These two fields cause more invoice disputes than the classification ever will. A crate is not a bottle and a kilo is not a bag. Decide how you actually sell the item, whether per piece, per kilo or per carton, and register it that way, because changing it later means your historic sales are measured in one unit and your new ones in another.

7. 7

   Register once, sell many times

   Item registration is a setup activity, not a per-sale activity. Once the product exists with its class and code, the cashier scans and sells; nobody is choosing categories at the counter. If your process has staff picking classifications during a sale, something is wired wrong.

8. 8

   Keep a plain-language note of your mapping decisions

   For anything ambiguous, write one line saying which class you chose and why. Six months later, when a similar product arrives, that note stops a second person choosing differently and splitting your reporting across two classes for what is effectively one category.

9. 9

   Review the additions, not the whole catalogue

   Once a quarter, look at the items added since the last review rather than re-checking everything. New items are where drift enters. A ten-minute review of thirty new lines is sustainable; an annual audit of the full catalogue never actually happens.

In Veira the classification and item code live on the product record, set once when you add the product. From then on a sale is a scan: nobody at the counter sees a classification field, and nobody can accidentally change one mid-queue.

When you add a new product, the class of a similar existing product is offered as the starting point, so your conventions propagate instead of depending on whoever happens to be doing the setup that day.

Because the mapping is attached to the product rather than to the invoice, your category reporting works on your own data too. You can see which classes actually earn money in your shop, which is the part of all this that pays you back rather than only paying KRA back.