How Trekiva moved a fast-growing footwear brand onto a real operational platform.
Trekiva is a sustainable footwear brand based in Indore, India, crafting handmade sandals from eco-conscious materials. As the brand scaled across warehouses and channels, the back-office stack started to fight the business. Galaxy helped to eliminate the chaos with Odoo ERP implementation services providing a single operational system underneath sales, purchasing, inventory, and finance.
Trekiva's growth as a sustainable footwear brand had outpaced the systems behind it. Products move through multiple warehouses, get sold in two different units (individual pairs and bulk cartons), pass through sales and purchasing workflows that need to talk to inventory, and roll up into accounting that has to comply with Indian regulations.
Each piece was being handled in isolation. Warehouses tracked stock locally, with no central source of truth. The two-unit problem — a single SKU stocked in pairs and sold in cartons — produced regular mismatches between physical inventory and what the system reported. Sales orders and purchase orders moved through disconnected processes. Financial entries were happening outside the system entirely, in spreadsheets that then had to be reconciled back manually. Invoices didn't carry the brand's visual identity or the line-item detail Indian tax compliance required.
The cost was steady and distributed. Stock counts drifted between physical and system. Order fulfillment slowed because someone always had to check actual inventory before committing. Month-end took days because financial entries had to be assembled from multiple sources. Each piece worked on its own — the connections between them were where the cost lived.
Each system handled its slice. Nothing knew about the others. The owner spent half their time being the human integration layer between warehouses, sales, purchasing, and accounting.
Trekiva considered the alternatives. Larger ERPs like SAP B1 or NetSuite were over-engineered for a fast-growing footwear brand at this stage — too expensive and too rigid for a business still shaping its operational rhythms. A combination of point tools (Zoho Inventory, Tally for accounting, a separate invoicing tool) would have multiplied the integration problem rather than solved it. Sticking with spreadsheets was no longer viable.
Odoo's structural fit was clear: one platform covering sales, purchasing, inventory, invoicing, and accounting — with the customization headroom to handle multi-warehouse setup, two-unit inventory tracking, and Indian compliance. The licensing math worked at the brand's scale, and the customization flexibility meant the system could be shaped around how Trekiva actually operates rather than the other way around. Odoo inventory tracking could help in real-time stock monitoring, automated reordering, and multi-warehouse control.
The deal-breaker for stock Odoo was the customization required to handle three specific things: two-way inventory tracking for products sold in both pairs and cartons, multi-warehouse stock segregation with real-time visibility, and custom invoice templates aligned with both Trekiva's brand identity and Indian compliance requirements. None of this was insurmountable. All of it was real configuration and customization work, not out-of-the-box deployment. That's where Galaxy came in with Odoo ERP implementation services to manage everything seamlessly.
The implementation ran across four workstreams. Each one solved a specific operational gap. Together, they replaced the system-by-system patchwork with a connected platform where data flowed from stock movement to financial entry without manual rekeying.
Designed a centralized company structure with multiple warehouse locations mapped to Trekiva's physical operation. Configured Odoo to ensure accurate stock segregation across locations, with real-time visibility into stock levels at every warehouse from a single view. Internal transfers between warehouses tracked as first-class operations, not after-the-fact reconciliations.
Warehouse-level stock tracking accuracy improved by 70-80%. Cross-warehouse visibility achieved without manual reconciliation.
Standard Odoo inventory works in a single unit of measure per product. Trekiva sells the same SKU in two units — individual pairs to retail customers, bulk cartons to wholesale buyers. We customized the Inventory module to handle two-way tracking, so the same physical stock could be transacted in either unit without breaking inventory math or producing stock mismatches downstream. Real-time stock tracking propagated across both unit views, ending the discrepancies that had been a constant source of friction.
Inventory control and order fulfillment improved by 60-70%. Stock mismatches between unit views largely eliminated.
Automated the end-to-end workflow from sales order through purchasing through stock movement. Linked vendor transactions and stock activity into the same data layer, so a sale automatically reduced available inventory and a purchase order automatically updated incoming stock projections. Supply chain planning shifted from manual reconciliation to integrated tracking — purchasing decisions could be made against real demand and stock data rather than estimates.
End-to-end supply chain planning efficiency improved by 40-60%. Purchasing decisions now made against live data.
Configured Odoo's accounting processes around Indian compliance requirements, including GST handling, tax filing logic, and the line-item detail Indian regulations require. Built custom invoice templates that match Trekiva's brand identity — the visual presentation customers receive aligns with the brand's sustainable, design-forward positioning rather than looking like a generic system-generated document. Financial entries from sales, purchase, and inventory activities flow into accounting automatically instead of being assembled manually at month-end.
Accounting accuracy and compliance improved by 60-75%. Month-end financial entries now generated by the system rather than assembled by hand.
D2C brands moving from spreadsheets to real ERP often stall in the same places. The configuration looks straightforward on paper; the customization required to fit how the business actually operates is where projects either land or drift. Three things mattered for this engagement to work.
Discovery before configuration. We mapped Trekiva's actual operation — the way pairs and cartons flow, the way stock moves between warehouses, the way Indian tax compliance shapes invoicing — before touching the platform. Most Odoo implementation services skip this and pay for it later through rework. Two weeks of mapping prevents months of mid-project pivots.
Custom work where Odoo's defaults didn't fit. Two-unit inventory tracking and Indian-compliant invoice templates weren't configuration tasks. They required real customization at the data model and template layer. Stock Odoo handles a single unit per product cleanly. Stock Odoo's invoice templates produce a functional but generic document. Bridging the gap took Python and template engineering — exactly the kind of work most Odoo partners walk away from.
One operational platform, not five integrated tools. The temptation for a growing brand is to keep Tally for accounting, add Zoho Inventory, and integrate them. That approach multiplies integration points and recreates the patchwork that originally caused the problem. Odoo's value is that all five modules share a data model — stock movement is already accounting context, sales orders are already inventory context, purchases are already finance context. The integration isn't bolted on. It's the platform.
The percentages Trekiva reports matter, but the deeper change is structural: the owner no longer spends half the day reconciling between systems. The systems do that themselves.