Lampgigant scales with Odoo and 360 ERP (without the integration spaghetti)

Before Lampgigant started working with Odoo and 360 ERP, their accounting ran on SnelStart. That became a less comfortable fit for the scale at which Lampgigant was operating. “SnelStart started to slow us down,” says Linda van Kessel, Business Analyst at Lampgigant. “We constantly had to clean things up, so we could keep going for a few more months. But it wasn’t sustainable.”

At the time, order handling mainly ran through Magento and the WMS. Orders came into Magento, went to Picqer and then moved back towards Magento. Lampgigant was also already using Akeneo for product information. Individually, those systems worked. Until growth started asking harder questions. Because the existing warehouse became too small, Lampgigant started using a second warehouse. From that moment on, each order had to be routed to the warehouse that could handle it best. “When a customer places an order, it can be processed from either warehouse,” Linda explains. “Or from both, in the case of larger orders. That’s where the complexity came in.”

Lampgigant explored several ERP options. One colleague looked into Microsoft Dynamics 365, while Linda explored Odoo. Pretty quickly, Odoo stood out as a good fit for the way Lampgigant likes to work. “We’re a compact organisation, so we can switch quickly,” Linda says. “After our own research, I had an exploratory conversation with Cas from 360 ERP. He gave us a test database we could play around with ourselves. That worked really well for us.” Lampgigant also spoke with a 360 ERP reference customer.

Lampgigant consciously works with several specialist systems. Magento for the webshop. Akeneo as the PIM. Picqer for warehouse processes. Different payment providers for payments. BigQuery and Power BI for data and reporting. For Lampgigant, that best-of-breed approach makes sense. Each system does what it’s good at. Odoo’s role is to be the central hub that gets the right information to the right place at the right time.

“We did look at whether Odoo could replace some of our existing systems,” Linda says. “But we wanted to execute the ideas we had in mind. For some of our rules, Odoo was a little too standard. In the separate systems, we can go deeper.” And that is exactly where a good integration setup proves its value: making sure all those specialist systems work together properly.

The Odoo implementation was split into two phases. Phase 1 focused on sales orders and accounting. “That was already quite a project in itself,” Linda remembers. “We had a weekly call with 360 ERP, a plan of action and a test file we all worked in together.”

The original goal was to go live on 1 January. That turned out to be slightly too ambitious. No disaster. Better to go live a little later and properly than exactly on time and in full panic mode. Lampgigant went live on 1 February. “Frankie and Niall from 360 ERP came to our office, and we ran the first live morning together. Problems that came up could be fixed immediately.”

Phase 2 followed soon after. The second warehouse had to open, which meant that orders could no longer automatically go to one location. They had to be assigned to the right warehouse based on rules. Because orders could be processed from one or both warehouses, the process became more complex, with different rules, steps and scenarios.

Lampgigant and 360 ERP again worked with fixed check-ins and test scenarios. “Every Wednesday afternoon, we had a call,” Linda says. “We tried to come up with as many test scenarios as possible to catch the teething problems.” That required dedication from both sides. “Especially in phase 2, the pressure was high. In the end, we really did it together. It took some extra effort, but luckily it was manageable.” The result: an order flow where Odoo determines where an order needs to go.

A Lampgigant customer places an order in Magento. Magento sends the order to Odoo. Odoo then uses rules to determine which warehouse should process that order. After that, Odoo creates a shipment towards the right warehouse through the integration. Once the order is scanned for shipment there, a signal is sent back to Odoo. The track & trace information then goes back to Magento, where the order is also completed.

Meanwhile, stock levels in Odoo are automatically updated. Important detail: “Stock in Odoo is leading,” Linda says. “That is continuously communicated back to Magento, so we don’t have to sell ‘no’.” That’s the kind of integration customers don’t notice when it works well. Exactly the point, because nobody likes ordering a lamp only to find out afterwards that it wasn’t actually in stock.

Product information also plays an important role in the best-of-breed stack. Lampgigant uses Akeneo as its PIM. Product information from Akeneo flows into Odoo every night. Think of new products or price changes. “When new products are added or a cost price changes, that goes from Akeneo to Odoo,” Linda explains. “That really makes Odoo the central source of truth.” That matters because product data is not only relevant for the webshop. It also touches stock, purchasing, sales information, margins and reporting.

One of the biggest benefits of Odoo for Lampgigant is overview. Previously, Linda had to do a lot with exports and Excel. That meant a lot of manual checking and VLOOKUP gymnastics. Now, she can use filters in Odoo to quickly see what is going on. “I feel like we’re in control,” Linda says. “With one filter, you can immediately see which invoices have not been paid.”

The payment provider integrations help too. “We can see every day what has been collected and whether something has been reconciled. We’re on top of it and can inform customer service based on that information.” The same goes for other colleagues. Finance can see more quickly which invoices need to be checked and paid. Purchasing can see in one overview which orders are still pending. “That overall view was what we were missing before.”

Lampgigant doesn’t only sell through its own webshop, but also through marketplaces such as Bol.com and Praxis. Odoo helps keep control there too. Linda downloads and uploads files, which are then linked to invoices or cost accounts. “That’s done within a minute,” she says. “It means I can immediately see how a marketplace is performing and whether all the numbers are correct.” In the past, that kind of overview was practically impossible.

Odoo is the operational foundation, but Lampgigant also uses BigQuery and Power BI for reporting. 360 ERP prepared tables towards BigQuery for sales and invoice data. Those exports are refreshed every night. Linda writes her own queries on that data and builds views, which then flow into Power BI. “In Power BI, I create all kinds of reports for myself and colleagues. For example, to see which countries are performing well. Together with the Odoo data, we can quickly adjust and optimise.”

Linda appreciates the short lines with 360 ERP. “They always respond quickly, usually the same day. One time something went wrong and I could easily call Kees. He picked it up right away and fixed it.” The way of working also matched well. “We don’t necessarily need small talk. I explain the situation and they get to work.” That makes us happy. Not because we’re against being friendly, but when there’s an order flow, warehouse integration or finance issue on the table, we prefer to talk about the solution first.

According to Linda, the teams quickly spoke the same language. “They often understand immediately what we mean.” That helps. Especially if you also switch quickly, have little hierarchy and only meet when it’s actually needed. “That’s what working with 360 ERP feels like too: if something comes up, we talk. Online was totally fine as well. They came on-site once, but video calls work just as well for us.”

After the Odoo implementation, tickets still came in. As they do in every ERP project. But towards the end of 2025, that became less and less. “Then it really became stable,” Linda says. And that’s when a solid foundation starts paying off. The operation runs. Finance has an overview. Stock is accurate. Orders are automatically sent to the right warehouse. Data is available. That is the moment when new optimisations can be tackled step by step.

The next steps are already on the horizon. New developments in logistics will again require smart integrations and further system optimisation. “We still have more ideas,” Linda says. “But we do it step by step.” Continuing to improve without making the processes unnecessarily complicated, that sounds like the way to go to us.