Evolution of a complex e-commerce: the case of Bodeboca
Natiboo has collaborated for more than four years as a technology partner in the evolution of Bodeboca's e-commerce ecosystem, one of the most complex wine marketplaces in Europe.
The project started from a fragmented architecture, with a core in Drupal 6, multiple subsystems in Drupal 8, and a high technical debt that directly impacted the business: errors in campaigns, synchronization issues, scalability limitations, and a high time-to-market.
From an integrated team position, Natiboo has participated in the entire cycle: progressive migration to modern Drupal, architecture redesign, optimization of logistical and editorial processes, system stabilization, and improvement of operational capacity.
The result has been a more robust, scalable platform aligned with the business, capable of handling critical peaks such as Black Friday or Christmas campaigns normally, reducing incidents and improving the speed of product evolution.
Evolution of a complex e-commerce: the case of Bodeboca
Bodeboca is one of the most relevant wine marketplaces in Europe, with millions of users and international presence. Its growth and operational complexity have demanded a constant evolution of its technological platform.
Since October 2020, at Natiboo we have collaborated as a technology partner integrated into their IT team, actively participating in the evolution, stabilization, and redesign of their digital ecosystem.
A complex ecosystem from the starting point
When we joined the project, the platform was already a highly complex system in production. It was not a single application, but a distributed ecosystem composed of multiple subsystems:
- Frontend in Drupal 8
- Legacy backend in Drupal 6
- Logistics system in Drupal 8
- Data lake in Drupal 8
- Independent editorial platform
- Marketplace for external vendors
This context generated a high interdependence between systems, making any evolution involve significant technical and operational risks.
The problem: technical debt and operational friction
The main challenge was not only technical but structural. The platform carried a high technical debt, especially in Drupal 6, and an architecture that hindered product evolution.
This translated into specific business problems:
- Errors in caching and data synchronization systems
- Blockages in private sales campaigns
- Difficulty launching new features
- Performance issues during high traffic times
- Extreme complexity in stock and logistics management
At certain critical moments, such as Black Friday, the platform could suffer scalability problems that directly impacted revenue.
Our role: beyond an external provider
At Natiboo, we do not act as a one-off provider but as part of the team. We work continuously, in direct contact with business and technology, participating in strategic decisions and technical execution.
Our contribution covered the entire product lifecycle:
- Progressive migration from Drupal 6 to modern versions
- Backend and frontend development
- Integrations with ERP and logistics systems
- Architecture design
- Performance optimization
- Continuous support and evolution
Additionally, we participated in internal training, team onboarding, and defining business initiatives, aligning technology with real objectives. :contentReference[oaicite:0]{index=0}
Key technical decisions
One of the biggest challenges was to evolve the platform without interrupting the business. To achieve this, a strategy of progressive migration was chosen, avoiding a “big bang” approach.
Some of the most relevant decisions we participated in:
- Partial migration of users and functionalities
- Reduction of multiple logistics integrations to a more controlled model
- Implementation of asynchronous synchronization systems based on queues
- Automation of translation processes with robust pipelines
- Design of editorial systems based on components (paragraphs)
This last point allowed for a drastic reduction in the time taken to generate newsletters, improving the efficiency of the marketing team and reducing manual errors. :contentReference[oaicite:1]{index=1}
An architectural challenge: modeling product complexity
One of the most complex challenges was designing the data model to support product variations by store, country, and context.
This led to the definition of a new type of entity (contextual product) capable of persisting variable attributes without breaking the coherence of the system.
This decision affected the core of the architecture, requiring a high degree of precision and long-term vision.
Operational complexity: beyond standard e-commerce
Bodeboca is not a conventional e-commerce. Its complexity lies in the combination of multiple factors:
- More than 2 million users
- Operation in multiple countries
- Distributed and synchronized stock between systems
- Complex and overlapping pricing rules
- Private sales with specific logic
- Integrations with multiple external systems
This level of complexity forces the design of resilient systems, with asynchronous processes, error control, and high data consistency.
Results: stability, scalability, and capacity for evolution
After years of continuous work, the impact has been significant:
- Drastic reduction of critical incidents
- Stability in high traffic campaigns (Black Friday, Christmas)
- Improvement of platform scalability
- Greater speed of development and deployment
- Optimization of editorial and marketing processes
The transition has moved from an environment where errors were frequent to a platform where incidents are occasional and controlled.
Beyond code: impact on business and organization
Our contribution was not limited to technical development. We actively participated in:
- Definition of product initiatives
- Technical feasibility analysis
- Improvement of internal processes
- Training and onboarding of teams
This approach allowed for the alignment of technology, product, and business, reducing the risk of decisions disconnected from real operations. :contentReference[oaicite:2]{index=2}
Learnings
This project has been particularly relevant to deepen understanding of:
- Complex e-commerce architectures
- Catalog and logistics management
- Asynchronous systems and queues
- Integration of multiple external systems
It has also highlighted the importance of making strategic decisions in early phases.
Reflection: what we would do differently
With the current perspective, a viable alternative would have been to rethink the architecture from scratch on platforms like Shopify, migrating only the data and redesigning the processes.
However, in the context of the moment, this option was not viable due to technological and business limitations.
Conclusion
The case of Bodeboca is not that of a one-off project, but of a long-term collaboration in a highly complex environment.
More than developing functionalities, we have contributed to building a more robust, scalable platform aligned with the business.
These types of projects are not resolved with standard solutions, but with teams capable of understanding the context, making complex decisions, and continuously evolving the system.