Botica di Servicio

Botica di Servicio

Customer profile

Botica di Servicio is a well-known pharmacy and drugstore chain in Aruba with multiple stores and a central warehouse. On its public website, the company presents itself as a provider of personal medication, beauty products, cosmetics and attentive healthcare support. That mix creates operational complexity beyond a standard retail environment. In this project, the main focus is on the non-pharmacy side of the business, where retail and business sales both play an important role in day-to-day operations.

The company serves private customers as well as business clients, so its processes go beyond walk-in transactions alone. It also needs coordinated replenishment, structured follow-up on commercial opportunities and consistent execution across locations. In that kind of setting, shared visibility on stock, sales activity and customer data becomes essential. This is why the organization wanted one central working environment where commercial and logistical processes could connect more effectively and teams could work from the same information.

Reason for change

For pharmacy functionality, Botica di Servicio already relied on a specialized AIS that supports medication-related requirements. At the same time, other activities were spread across separate tools and partly manual routines. This affected point-of-sale transactions, inventory handling, purchasing and parts of the B2B sales process. The result was limited integration between stores, the warehouse and commercial channels.

The need was to connect fragmented processes without disrupting the specialist pharmacy environment that was already in place. The trigger for change was therefore cumulative rather than isolated. Inventory accuracy was harder to maintain, reporting was less unified and stock visibility by location was not always readily available. In addition, customer information and sales opportunities for business accounts were not managed centrally enough. Odoo was chosen to support a more integrated operation in which stores, warehouse and sales channels can work together through a shared platform that also leaves room for future expansion.

Challenge

The main challenge was to support several different business realities in one practical solution. On one side, there is retail with fast store transactions, shelf stock and day-to-day customer service. On the other, there are business customers, sales pipelines, order handling and centralized purchasing and logistics. At the same time, a clear boundary had to remain between medication management in the AIS and settlement in Odoo.

That required clear process boundaries as well as an intuitive setup for employees. Operational requirements were equally specific. The stores needed a stable POS environment, while the central warehouse needed better control over replenishment and stock levels by location. Orders and deliveries had to align more closely with actual availability, and B2B customer information had to be managed in a more structured way. The challenge was therefore not only software replacement, but creating cohesion between sales and logistics without adding unnecessary complexity to the store floor.

Odoo solution

The solution uses Odoo as the central environment for all non-pharmacy processes. This creates one foundation for sales, customer relationship management, point of sale, inventory, purchasing and supporting administrative work. Core setup activities include user access rights, language settings, company information and document layouts so the system fits the organization from the start. On that basis, the implementation was designed around usability and scalability , making daily work easier for both store teams and back-office users.

A key design principle is the separation between specialist pharmacy workflows and broader commercial processing. Prescribing and dispensing remain in the existing AIS, while Odoo records the sales transaction and handles it within the POS and related processes. In this way, Odoo supports settlement and operational coordination without taking over the role of the pharmacy system. At the same time, it links the remaining activities into an integrated operational flow , from customer follow-up and order handling to stock movements and subsequent administration.

Apps and processes

On the commercial side, CRM and Sales support centralized management of customer data, leads, quotations, orders and follow-up. For stores, Point of Sale is a core component, with each transaction updating Inventory directly. Because the POS can continue operating during temporary internet interruptions and synchronize later, it matches the reality of physical retail well. This creates a direct link between POS and stock , so everyday sales translate into more reliable inventory visibility across locations.

On the logistics and support side, Inventory, Purchase, Barcode, Invoicing, Employees and potentially additional configuration through Studio work together to support the operation. The central warehouse replenishes the stores, while reordering rules, supplier handling and incoming goods registration are managed more consistently. Limited employee setup is also included for staff records and POS pin codes. Specific extensions, such as support for multiple barcodes per product and POS-related analytical handling, help align the solution more closely with operational practice.

Result

With this implementation, Botica di Servicio gains a stronger foundation for its non-pharmacy processes. Sales, store transactions, inventory control and purchasing are no longer treated as isolated activities, but as connected processes based on shared data. That makes it easier to monitor availability by location, align replenishment more accurately and manage customer information more centrally. A clear realized outcome of this approach is better operational alignment between stores, the warehouse and business sales activities.

The broader value lies in the improvements this setup is expected to support over time. More standardized ways of working should help reduce avoidable errors, while shared and current information should enable faster decisions and smoother execution. The platform also offers room for future expansion as needs evolve. The intended result is therefore not just a new system, but greater control by location , more consistent processes and a scalable basis for continued development.