Koskii

The challenge

Koskii is a 150-year-old Indian fashion brand — its name comes from the Navayati word for “girl” — known for vibrant Indian occasion-wear, including lehengas, gowns, sarees, fusion wear, and bridal attire. Today the brand operates 22+ stores across Bengaluru, Hyderabad, Delhi, Chennai, Coimbatore, and Kochi alongside an online channel.

The retail back-office had grown into a four-system patchwork:

• Tally for accounting
• Ginesys for offline / store sales
• Command Center for inventory management
• Increff for warehouse management

That stack created four daily problems:

• Interoperability — Each system had its own data model. Reconciling sales-to-inventory or inventory-to-accounting required nightly exports and manual matching.
• Costing — Multiple licenses for separate applications meant ongoing subscription overhead and four vendors to manage.
• Reporting — Cross-system reports (e.g. SKU profitability across online + offline + warehouse) couldn’t be produced without manual stitching.
• Customization — None of the four tools allowed deep workflow customization for Koskii’s specific retail flows (e.g. their bridal-trial booking process or their bespoke alteration tracking).

Koskii needed a single platform that could run accounting, retail POS, online sales, inventory, and warehousing under one license — and that the team could shape to their actual workflows.

Our solution

TechUltra recommended Odoo Enterprise as a unified suite covering accounting, sales, purchasing, POS, inventory, and e-commerce within a single license. We delivered the implementation in 18 weeks, sequenced so a single store proved each capability before the rollout went wide.

Sales + POS — Configured POS for in-store transactions across all 22+ outlets, with offline fallback so a connectivity blip at any store doesn’t stop sales. Pricing rules, loyalty, and the bridal-segment workflows from the old Ginesys setup were re-implemented natively in Odoo.

Inventory + Warehouse — Replaced Increff with Odoo Inventory configured for multi-location: each store carries its own stock, the central warehouse routes replenishment, and inter-store transfers are tracked end-to-end. Bridal-trial reservation workflows (an Increff customization) were rebuilt as a native Odoo flow.

Accounting — Migrated from Tally with a clean chart-of-accounts redesign. Books now close in a fraction of the prior time because store sales, online sales, and warehouse transfers all post directly — no nightly Tally import.

eCommerce + CRM — Online-channel orders flow into the same inventory and accounting backbone as store sales. Customer profiles unify across online + offline, so the loyalty programme works for the same customer regardless of where they shop.

The cutover was sequenced store-by-store with a bridge period where the legacy systems and Odoo ran in parallel for one stocktake cycle — discrepancies between the two were investigated and resolved before the legacy systems were decommissioned.

The results

Four systems collapsed into one. Tally, Ginesys, Command Center, and Increff are decommissioned. License + vendor-management overhead is cut to one platform; the team learns one UI rather than four.

One source of truth. Inventory across 22+ stores, the central warehouse, and the online channel reconciles continuously. The previous “is this SKU really in stock?” question — which used to require checking three systems — is answered at the till by Odoo.

Faster reporting. Cross-channel reports (SKU profitability, store-level margin, category trends) now run directly from Odoo with no manual stitching. Buying decisions for the next bridal-season run on real numbers, not yesterday’s spreadsheet.

Customization the legacy stack couldn’t offer. Bespoke flows — bridal trials, alteration tracking, festival-season pricing waves — are now native Odoo configurations rather than Excel side-tracks.

Foundation for further growth. New stores and new channels (e.g. marketplaces) plug into the existing Odoo configuration without additional license purchases or new system integrations. See Odoo Implementation for the engagement format used.