Skip to Content

Autonet B.V.

Autonet started with Odoo Helpdesk and Website to connect customer support and online processes in a manageable first phase.

Autonet develops software for the vehicle dismantling sector and supports customers from Dordrecht. Because its processes were not integrated, the company chose a manageable first step with Odoo Helpdesk and Website. This created a central base for service, online interaction and further expansion of business processes in Odoo.

Autonet and Odoo for support and online processes

Customer profile

Autonet is a software and automation company focused on the Dutch vehicle dismantling sector. From its office in Dordrecht, the company develops solutions that help dismantling businesses manage stock, sell parts online and streamline daily operations. On its website, Autonet presents itself as a platform for used car parts , combining software, online sales channels and integrations that connect supply and demand across the market.

That mix of software development, service delivery and customer support creates a strong need for clear internal processes. Alongside product development, the helpdesk plays an important role in daily operations. For Autonet, the move to Odoo was therefore not just a system change. It was also a step toward better organisational alignment , creating one central foundation for service, communication and the further development of digital processes across the business.

Reason for change

The main reason for change was simple: the existing setup was not integrated. In an organisation where support, online interaction and commercial activities all influence one another, disconnected tools quickly create unnecessary manual work and limited visibility. Information ends up scattered across multiple places, process steps do not flow naturally and employees must switch constantly between separate systems. Over time, that makes daily work less efficient and can affect the consistency of customer service.

Autonet wanted to move toward a future situation in which Odoo could support all business processes. At the same time, it was important to keep the project realistic and manageable. For that reason, the implementation was deliberately phased. Instead of introducing every process area at once, the company started with a clearly defined first phase : Helpdesk combined with Website. That decision created a practical starting point and made it easier to define the next steps later on.

Challenge

The challenge was not only to replace separate tools, but also to choose a sensible route forward. Autonet operates across support, customer contact, online services and commercial processes that are closely connected. A large-scale implementation covering everything at once could have placed unnecessary pressure on the organisation. The solution therefore had to be future-oriented without becoming too heavy, giving Autonet room to expand gradually based on real experience in daily use.

Another challenge was prioritisation. Not every process area had the same importance in the initial scope. Autonet occasionally also supplies hardware such as computers to customers, but this happens only sporadically. For that reason, it was not considered logical to introduce Purchase and Inventory from the start. The project therefore required careful scope choices , focusing on functionality with immediate relevance so Odoo could deliver value quickly without becoming unnecessarily broad.

Odoo solution

The chosen solution was a standard-first Odoo setup, with the first focus on Helpdesk and Website. Through Odoo Helpdesk, customers can create tickets through the website, while internal teams gain immediate visibility into incoming service issues through the Kanban view. This creates one central place for follow-up, prioritisation and collaboration around support work. By implementing Website at the same time, customer contact and online access could be connected naturally inside the same working environment.

Autonet also wanted a solution that the organisation could manage independently after the initial rollout. For that reason, the implementation included key-user training for Helpdesk, Website and other relevant applications. The setup stayed close to standard Odoo wherever possible. Small adjustments could be handled with Studio, helping to balance maintainability and flexibility . This approach supports a broader vision in which Odoo becomes a lasting platform for phased expansion across more business processes.

Apps and processes

In the first phase, the most important applications were Helpdesk and Website . Helpdesk supports the intake and management of service tickets, while Website plays a central role in online customer interaction. The project also covered practical topics such as system settings, page structure, templates, website blocks and the links between these elements and other apps. That means the implementation was not only technical, but also focused on shaping practical daily processes for support and online service.

The wider scope also considered process areas supported by Sales, Subscriptions, Invoicing, Documents and Sign. Sales supports quotations and order follow-up, while Subscriptions fits recurring services and Invoicing supports administrative handling around those activities. Documents and Sign contribute to a more digital way of working through folders, workflows and approvals. Studio was used as a tool for minor adjustments , helping Autonet avoid unnecessary complexity while still adapting Odoo where small refinements were useful.

Result

The clear result of this first phase is that Autonet established a structured starting point on the path toward one integrated platform. By beginning with Helpdesk and Website, the company created a foundation for stronger customer support and a more connected online way of working. Teams gain more visibility into incoming tickets and service processes can be managed in one central environment. That makes the phased approach tangible and gives the organisation a practical base it can build on.

At the same time, this project is also the start of a broader roadmap. The intended future situation is for Odoo to support all business processes, but the exact next phase is to be determined after the first phase is operational in practice. This gives Autonet a realistic launch point while keeping a long-term direction in view. The expected value lies in further step-by-step integration , creating more process control, clearer ownership and a platform that can continue to grow with the business.