How Codilar Re-engineered the TGR Webstore on Magento and Won Two Awards for It

TGR had a problem that is more common than most commerce teams admit. The platform had not been designed for where the business ended up. It had been built incrementally, instance by instance, as new markets, languages, and customer groups were added. By the time the complexity became impossible to ignore, TGR was running multiple Magento instances that shared none of their operational efficiency and all of their maintenance burden.

Each instance needed to be managed separately. Configuration changes had to be replicated. Updates carried compounding risk. And the customer experience, which should have felt seamless regardless of whether the buyer was a B2B retailer ordering in bulk or a B2C collector browsing the catalog, was fractured across environments that were never designed to work together. The platform was not broken. It was just never meant to carry this much.

Before any consolidation could happen, we had to confront what was sitting underneath the platform. A database exceeding 60GB. Over 150 customer groups. More than 160 catalog rules. Ten websites running simultaneously on a single Magento instance, each with its own indexing demands, its own configuration complexity, and its own contribution to a system that was slowing down under its own weight.

Indexing at this scale is not a tuning problem. It is an architectural one. We restructured the indexing configuration, implemented better code and configuration management practices, and reduced the surface area for the kinds of technical issues—security vulnerabilities, slow queries, inconsistent data states—that accumulate when a platform grows faster than its governance. The result was a database that served 15,000 products, 150+ customer groups, and 10 websites with the kind of speed and reliability that the business had been running without for too long.

For a global wholesale distributor, inventory accuracy is not a convenience. It is the product. When a retailer places a B2B order expecting a certain stock level and the platform is working off data that is minutes or hours behind, the downstream consequences move fast—canceled orders, broken trust, lost accounts.

TGR's inventory updates were not happening in real time. We resolved this by integrating ODOO directly into the Magento platform, creating a live synchronization layer between TGR's business operations and the storefront. Stock levels, product information, and order data became consistent across every touchpoint, not as a periodic batch but as a continuous, accurate reflection of what was actually in the warehouse.

TGR serves customers across multiple countries and languages. The existing approach to multilingual delivery—separate store views for each language—was expensive to maintain, slow to update, and created operational overhead that scaled badly as new markets were added.

We replaced this with a cleaner architecture: Bablic for server-side translation, combined with virtual store views that delivered localized content without the cost and complexity of duplicating entire store environments. Language became a configuration, not an infrastructure problem, and TGR's multilingual customers received a consistently localized experience without the platform needing to multiply itself to deliver it.