Industries Tea
Odoo ERP for tea, from garden intake to the retail shelf.
Leaf collection, factory batches, blending, depots and secondary sales on one system, so finance sees the same numbers as the factory floor.
How leaf moves through one system
- GardenSupplier weights and deductions recorded once
- FactoryBatches and grade output tracked by lot
- AuctionLots, broker valuations and sale prices recorded, step by step
- Blend & packRecipes and packing costed as you produce
- DepotStock visible by location
- RetailShop demand captured on sales visits, as built with Ispahani
Where tea businesses lose track.
Leaf moves fast. Registers, spreadsheets and separate sales apps don't keep up with it.
- Green leaf on paper
- Supplier weights, moisture deductions and payments written by hand, then typed in again.
- Grades you can't trace
- No clear link from a finished pack back to its garden, batch and grade.
- Blend costs after the fact
- Auction purchases, recipes and packing materials costed once the month has closed.
- Market demand arrives late
- Retail orders taken on calls and in notebooks reach the depot days later, or not at all.
From 10+ years of QAD to Odoo 19 in 8 months.
How Ispahani moved off a decade-old ERP and connected retail demand to its depots.
- The problem
- After 10+ years on QAD, retail demand gathered on sales visits still had no direct route to the right depot, or into the central ERP.
- What we built
- A move from QAD to Odoo 19, completed in 8 months. Alongside it, a secondary sales solution: reps capture demand during the visit, it's assigned to a depot, and it flows into the central ERP.
- Who uses it
- Sales networks across Ispahani's group companies. Implemented together with the Ispahani team.
An order's route
- Retail visit. The rep logs the shop's demand on the spot.
- Demand. Orders are pooled by route and outlet.
- Depot. Each order goes to the right depot.
- Central ERP. Stock, invoicing and reporting stay in sync.
10+ years
on QAD before the move
8 months
from QAD to Odoo 19
[N]
[Depots connected]
[N]
[Group companies covered]
“[Client quote from the Ispahani team, pending approval.]”
Running a sales network across depots? Talk to us about yours →
Two processes that make or break a tea business
The auction decides what your tea earns, or what your blend costs. Secondary sales decide whether it reaches the shelf. Here's how each runs in Odoo.
Auction process
Most made tea in Bangladesh is sold through the weekly Chattogram auction, run by licensed brokers under the Tea Traders Association of Bangladesh. Growers must sell at least 75% of their produce this way.
- Lots sent to the warehouseEach garden invoice is recorded as a lot, with grade, weight and the licensed warehouse it went to.
- Broker sampling and valuationBrokers taste each lot and set a valuation, logged against the lot so you can compare it with the final price.
- Catalogue before the saleThe broker's catalogue is imported. Buyers mark the lots they want and set price limits for their blends.
- Weekly auction resultsSold price and buyer are recorded per lot. Unsold lots roll over to the next sale automatically.
- Settlement and releasePayment, brokerage and warehouse charges post to accounts. For buyers, the landed cost flows straight into blend costing.
Secondary sales process
Primary sales move tea from you to distributors and depots. Secondary sales move it from there to shops. That's the part most ERPs never see.
- Route and outlet planEach rep gets a daily route with the outlets to visit and what they usually order.
- Order at the shopDemand is captured during the visit, not written up later. Built with Ispahani.
- Assigned to a depotEach order goes to the depot or distributor that serves the outlet. Built with Ispahani.
- Delivery, invoice and collectionDeliveries, cash collected and trade scheme claims are recorded against each outlet.
- Synced with the central ERPSecondary sales sit beside primary sales, so you see real sell-through by region and outlet. Built with Ispahani.
What we set up in Odoo
Standard Odoo apps, configured for how tea is bought, made and sold. Most projects start with two or three of these.
Estate & leaf purchasing
Supplier records, weighbridge entries, deductions and supplier payments.
Auction
Lots, broker valuations, catalogues, sale results, unsold carry-over and settlement.
Manufacturing
Production batches, grade output, blend recipes and packing bills of materials.
Quality & traceability
Lot tracking, tasting checks and first-expiry-first-out stock rotation.
Inventory & depots
Multiple warehouses, transfers between depots and reorder rules.
Sales & distribution
Secondary sales, routes and outlets, depot assignment and distributor sales. This is the part we built with Ispahani.
Finance & group reporting
Multi-company accounts, batch costing, VAT and management dashboards.
How a project runs
We usually start with the season that matters most, then roll out estate by estate and depot by depot.
- Step 1Agree the scopeMap gardens, factories and depots, and pick the first release.
- Step 2Prove the workflowConfigure leaf intake to sales and test it on real batches.
- Step 3Prepare people and dataClean supplier and outlet data; train factory and field teams.
- Step 4Go live and keep improvingSupport through the season, then plan the next phase.
ERP23 has completed 50+ projects in 25+ countries, and has been an Odoo partner since 2016.
Questions tea producers ask us
Something else? Talk to our team.
Can Odoo handle green leaf from many small suppliers?
Yes. We set up supplier records, intake weights, deductions and payment runs, so each collection is recorded once and paid correctly.
Can we trace a pack back to its garden and batch?
Lot tracking links leaf intake, production batches, grades, blends and finished packs, so recalls and quality checks start from one record.
Can it handle the Chattogram auction?
Yes, from either side. Estates track lots from warehouse to sale price; blenders and buyers track catalogues, purchases and landed cost. We agree broker file formats during scoping.
Will it connect our field sales team to the ERP?
That's what we built with Ispahani: demand captured on retail visits, assigned to a depot and passed to the central ERP.
Do we have to implement everything at once?
No. Start with what matters most, often finance and sales, then add estates, factories or depots in later phases.
Can you move us off QAD or another ERP?
Yes. Ispahani moved from more than 10 years on QAD to Odoo 19 in 8 months. We plan data migration, cutover and training around your season.
We already use Odoo. Can you help?
Yes. ERP23 offers support, upgrades, integration and project rescue. We review what you have and recommend what to keep, fix or replace.
Tell us what's slowing your tea business down.
30 minutes, no slides. We look at your actual setup and show where Odoo can help.