Timsoll's Experience: How Odoo ERP Manages 7,000+ SKUs

Short answer: Timsoll has sold spare parts for Uzbek-made cars for more than 15 years and runs 18+ branches, one central warehouse, one distribution hub and over 7,000 SKUs. Odoo ERP brought the branches, sales and the warehouse into one system. Because every item now automatically gets a code and its own storage bin, launching a batch of 2,000–3,000 new SKUs dropped from 6–8 months to 2–3 days. Management now sees the profit or loss of every outlet and decides based on numbers, not guesswork.

If you run a retail or distribution network with thousands of items, this will sound familiar. A new shipment arrives, but coding each item, shelving it and putting it on sale in every branch takes weeks or months. Branch managers phone the central warehouse to ask whether a part is in stock. At month end nobody can say for sure which store actually makes money, so decisions come down to gut feeling.

Timsoll went through exactly this. Below are the facts from founder Abduhakim Abdurahmonov's account of implementing Odoo ERP with Deep Vision: the problem, the choice, the processes and the results. Every figure about Timsoll comes from the founder's own words; explanations of how Odoo typically handles such tasks are general, not a technical description of his project.

Who is Timsoll?

Timsoll is a multi-branch company that has been selling spare parts for cars made in Uzbekistan for more than 15 years. Its founder is Abduhakim Abdurahmonov.

The business today:

• more than 18 branches across 18 cities;
• one central warehouse and one distribution hub;
• more than 7,000 SKUs, each tracked as a separate stock item.

Timsoll started with three branches in Namangan, Andijan and Fergana. When the company planned to grow its network, the need to run every branch in one program became one of the main reasons for moving to Odoo.

Why is managing 7,000+ SKUs of spare parts so hard?

An SKU (stock keeping unit) is a unique code for each distinct item in stock; products with the same name but a different size, model or manufacturer are separate SKUs. For how an SKU differs from an article number, see What is an SKU.

Auto parts are one of the hardest categories for inventory control, for reasons that apply to any spare-parts business:

• Many look-alike items. The same part for another car model or maker is a different item; a wrong pick means a return.
• Small items in large numbers. Without a storage address, filters, bearings and gaskets are slow to find.
• A changing range. A new model, supplier or substitute can add thousands of items at once.
• A long chain of movements. Central warehouse, hub, branch: every transfer needs a document.
• Regional demand. A part that sells fast in one city may sit for months in another.

Simple arithmetic: 7,000 SKUs across 18 branches means up to 126,000 "item + branch" combinations, each with its own stock, price and movements. Tracking that on paper, in Excel or in disconnected programs is close to impossible. That is why the Timsoll team went looking for an ERP system.

What problem did Timsoll face before Odoo?

The core problem was a lack of information for making the right decisions. The founder says so openly: management decisions were often based on guesswork and experience rather than precise numbers.

The second factor was growth. The company planned to open many new branches, and if each one keeps its own records, the overall picture only gets blurrier. Hence the requirement to run the whole network through one single system.

In general, a lack of data in multi-branch retail looks like this (a general observation, not a claim about Timsoll):

1. Stock data arrives late: one branch runs out while another is overstocked.
2. Purchasing repeats "what we ordered last time".
3. Branch profit is estimated; costs are not allocated.
4. Reports reach the owner already out of date.

Why did Timsoll choose Odoo?

Abduhakim Abdurahmonov names flexibility as the main reason. In his words, business changes all the time: you work one way today, the situation shifts tomorrow, and processes need reconfiguring. A growing company needed software that could adapt quickly, and Odoo met that requirement.

The second deciding factor was the ability to run all future branches in one system.

In general, Odoo's flexibility means:

• Modularity. Start with the apps you need, add others later; all share one database.
• Configuration without code. Warehouses, categories, pricelists, access rights and most reports live in settings.
• Extensibility. The open architecture allows custom modules.
• Scalability. A new branch is a new warehouse in the same system, not a rebuild.

Which processes does Timsoll run in Odoo?

According to the founder, Odoo gave the company real-time numbers not in one department but across sales, the warehouse and every other process. That made management much simpler and let decisions rest on data. The case explicitly mentions automatic product codes, storage bins, all branches in one system and profit-and-loss analysis per outlet.

Below is a general map of which Odoo apps usually handle such tasks. It is not a technical description of the Timsoll project:

• Inventory: multiple warehouses, zones and bins, putaway rules, transfers, real-time stock. More in Odoo Inventory: digitizing warehouse management.
• Sales and Point of Sale: orders, pricelists, discounts, in-store sales.
• Purchase: supplier orders and reordering rules.
• Accounting with analytic accounts: revenue and costs per branch, cost of goods sold, profit and loss.
• Product catalogue: categories, references, barcodes and units, entered once and reused everywhere.

How did new product onboarding drop from 6–8 months to 2–3 days?

Timsoll's most striking result: fully setting up and launching a batch of 2,000–3,000 new SKUs used to take 6–8 months on average; since Odoo went live it takes 2–3 days. That is roughly 60–80 times faster.

The founder is specific about why: every item now automatically receives a code and its own storage location (bin). Before, this was manual work, and thousands of items took months.

In Odoo, bulk onboarding of new products is typically set up like this (a general description):

1. Import the product list. The supplier's Excel file loads through a template in one go.
2. Codes follow a rule. Internal references are generated from an agreed rule (at import or via a small customization), so no duplicates.
3. The category sets the rules. Storage zone, costing method and accounts follow from the product category.
4. Putaway rules point to the bin. On receipt, the system tells the storekeeper where each item goes.
5. Labels are printed. Barcodes go on items and bins, and every later movement is scanned.
6. Price and stock appear in every branch at once. Pricelists in UZS for all outlets are managed in one place.

The key idea: manual work should not grow with the number of products. Once the rules are right, receiving 3,000 items instead of 300 takes hours longer, not months.

How do you run branches in 18 cities in one system?

Today Timsoll operates in 18 cities, and every branch is controlled through one system. Stock flows through one central warehouse and one distribution hub.

In Odoo, a multi-branch setup usually rests on these principles (a general description):

• One product catalogue. Every branch uses the same codes and names.
• Each branch as a warehouse or location. Stock is visible per branch and network-wide.
• A chain of transfers. The route "central warehouse → hub → branch" is set once; each step is documented.
• Replenishment rules. When branch stock drops below a minimum, the system proposes a transfer or a purchase.
• Access rights. Branch staff work with their own data; management sees the whole network.

For companies with a similar distribution model, see Odoo ERP for wholesale and distribution.

How can you see profit per store and per product?

Odoo gave the Timsoll team a clear view of whether each store (outlet) makes a profit or a loss. The company is now going deeper and working out profitability for each individual product, because a product that looks profitable may not bring real profit.

Why does that happen? Common reasons:

• a good markup, but the item sits for months and ties up working capital;
• delivery and transfer costs missing from the price;
• high returns and defects;
• discounts pushing the real price below plan.

In an ERP, branch profit usually comes from analytic accounting: every sale, cost of goods and expense (rent, salaries, utilities) is tagged to its branch. Product-level profitability also needs correct cost valuation and a rule for allocating indirect costs. It is built in steps: branch, then category, then item. For the logic behind such reports, see What is management accounting.

What does Timsoll's founder say about Odoo?

"With Odoo we can now clearly see the profit and loss of each outlet… Now you make well-grounded decisions."

— Abduhakim Abdurahmonov, founder of Timsoll

At the end of the conversation, Timsoll's founder thanks the Odoo and Deep Vision teams for the partnership.

Video: the Timsoll story in the founder's own words

In the video, Abduhakim Abdurahmonov walks through the company's journey with Odoo ERP in detail.

Watch on YouTube. A short companion article: How Odoo works at Timsoll.

What lessons can other companies take from Timsoll?

The main lesson: an ERP project starts not with installing software but with getting the data you need for decisions into one place. The points below follow from the case but are general advice:

1. Prepare the system before you grow. Timsoll saw the need for one system when it planned to expand. Building early is cheaper than copying old problems into each new branch.
2. Make flexibility a selection criterion. A system that must be rewritten whenever a process changes soon becomes a bottleneck.
3. Standardize product data. Without one coding rule and addressed storage, no ERP will bring order.
4. Measure your slowest process. At Timsoll it was launching new products; for you it may be purchasing or stock counts.
5. Deepen profitability analysis in stages. Start with branch profit, then move to products.

Does your business need a similar solution? A checklist

If three or more of these sound familiar, it is time to think seriously about ERP:

• You have over a thousand items, and counting.
• Branches or warehouses keep records in different files or programs.
• A new batch takes more than a few weeks to reach the shelves.
• Storekeepers hunt for items; there is no bin system.
• You cannot say for sure which branch makes a profit and which a loss.
• To check stock, you call the branch or ask in Telegram.
• Purchasing runs on intuition, not reports.
• You plan to open new branches in the next one to two years.

How does an Odoo rollout work for a multi-branch retailer?

An Odoo rollout for a multi-branch trading company usually covers diagnostics, catalogue clean-up, warehouse design, configuration, data migration, training and go-live. This is Deep Vision's general approach, not the Timsoll project schedule:

1. Diagnostics. Study product flows, purchasing and reporting; find the bottlenecks.
2. Catalogue clean-up. Remove duplicates; agree on the coding rule, categories and units of measure.
3. Warehouse design. Warehouses, zones, bins, routes and replenishment rules.
4. Configuration and integrations. Sales, POS, purchasing and accounting; where needed, e-invoicing via Didox and payment services such as Payme and Click.
5. Opening balances. Products, stock, customers and suppliers are imported from Excel or 1C.
6. Training. Hands-on sessions for each role, from storekeepers to management.
7. Go-live and support. Close monitoring and quick fixes in the first weeks.

In Deep Vision's experience, a project usually takes 2–6 months; standard Sales and Inventory modules often go live in 6–8 weeks. The exact timeline depends on branches, catalogue quality and integrations. Full methodology: Odoo ERP implementation: an end-to-end guide.

How can Deep Vision help?

Deep Vision is an official Odoo Gold Partner in Tashkent, and Timsoll implemented Odoo ERP in partnership with us.

• Our team has 7 certified Odoo specialists, and 26 of our client projects are listed in the odoo.com partner catalogue (partner page).
• Implementation, customization, integrations, data migration, training and support: see our Odoo implementation service.
• Ready-made modules for e-invoicing via Didox (Didox, Soliq and ERP integration) and for Asl Belgisi digital marking, if your goods fall under mandatory marking.
• Other clients include Optika.uz and RockBeton; see the portfolio.

We do not promise results up front, since every company starts from a different place, but diagnostics will show which process costs you the most. Start with a short brief.

Frequently asked questions

Who is Timsoll?

Timsoll has sold spare parts for Uzbek-made cars for more than 15 years. It has 18+ branches, a central warehouse, a distribution hub and over 7,000 SKUs. The founder is Abduhakim Abdurahmonov.

Why did Timsoll choose Odoo?

Mainly for flexibility: when the business changes, processes can be reconfigured quickly. The second reason was the plan to open many new branches and run them all in one system.

How did onboarding new products drop to 2–3 days?

In Timsoll's Odoo setup, every item automatically gets a code and its own storage bin. Launching a batch of 2,000–3,000 new SKUs now takes 2–3 days instead of 6–8 months.

Can Odoo handle 7,000+ SKUs?

Yes, Timsoll manages more than 7,000 SKUs in Odoo. In general, well-configured coding rules, categories and warehouse structure matter more than catalogue size.

How do you see profit for each branch?

Tag every sale, cost of goods and expense to a branch through analytic accounting, and the branch P&L builds itself. Timsoll already sees each outlet's result and is moving to product level.

How long does a project like this take?

The Timsoll timeline is not covered here. Deep Vision projects usually take 2–6 months; standard Sales and Inventory often go live in 6–8 weeks.

Is this approach only for auto parts?

No. Any trading network with branches, thousands of SKUs and a central warehouse (building materials, appliances, pharmacies, clothing) faces similar problems; the configuration varies by industry.

Conclusion

The Timsoll case shows that ERP is not only for large international corporations. A local company with 18+ branches, 7,000+ SKUs and a central warehouse used Odoo to:

• cut new product onboarding from 6–8 months to 2–3 days;
• gain precise profit and loss control for every outlet, with product-level analysis under way;
• bring branches, sales and the warehouse into one real-time system.

Many branches, thousands of products and scattered data: does that sound like your business? Fill in a brief for a free consultation or call +998 77 093 00 07.