A basic system can be built in 4–6 months, a mid-level system in 8–12 months. A large corporate ERP with custom logic takes 12 months or more.
Case study · ERP · logistics company, Estonia
ERP system for a tank container washing station
Orders, warehouse, invoices and a client portal in one system. We took over another team's project in 2021, strengthened its security and added new modules.
49 modules
in the system today, and the number keeps growing
2 servers
the public part is isolated from the admin part
5.0 on Clutch
client rating for quality, schedule and cost
Client
A logistics company from Tallinn, Estonia, with 51–200 employees. It runs a tank container washing and repair station: it receives containers from clients, washes and repairs them, stores them on site and issues invoices.
Station staff, administrators and the company's clients all work in the system.
Before
The system was built from scratch by other developers, and the client had been using it for a long time. In January 2021 the project was handed over to us.
01
A live system that cannot stop
Clients worked in the system every day, so rewriting it from scratch made no sense.
02
One project for everyone
Staff, administrators and clients all worked in the same project.
03
Financial data at risk
Clients had access to invoices and commercial information, so data security became the first priority.
04
New features needed
Besides security and stability, the system needed further development.
How we did it
-
Stage 1 · January 2021
Project takeover
The system is built on Symfony, our main framework, so the transition went smoothly for everyone.
-
Stage 2
Security audit
We audited the server the project ran on and prepared a list of actions to strengthen security.
-
Stage 3
Separate client portal
We moved the client portal into a separate project on a separate server. The public part is now isolated from the admin part, and the shared database gives clients updates right away.
-
Stage 4
New modules
We developed orders, warehouse, calendar and reports. The last and probably the largest was the Finance module, because it affects every part of the system.
Key decision
Do not rewrite the system from scratch. Clients were already using it every day, so we split security, stability and new features into separate tasks and moved the client portal into a separate project.
The solution on screen
All washing orders in one list
The order module automates the company's core process: fewer errors and less time per order. Next to it there are two similar modules for repairs and a module that brings all types of work together.
Tank container number. Every order is linked to a specific container and is easy to find by its number.
Planned washing date. Staff see when an order is due and plan the station's work.
Order type. Washing, repair or another service is marked right in the list.
Actions in one row. View, edit and print an order without switching pages.
A yard map instead of searching for a container
The warehouse is shown as a map with cells. A forklift driver sees where a tank container stands, finds it by number and moves it between cells. The cell colour shows its status.
Invoices built from completed work
An invoice is generated from services and their prices. It can be exported to the accounting software, and the client gets a PDF. Advance invoices are supported too.
Reports for management decisions
Reports show the workflow, warehouse stock and how changes affect the company's work. For detailed analysis they are exported to Excel.
Clients submit requests themselves
In the portal, clients create requests, see their statuses and download invoices as PDF. The company spends less time on processing requests, emails and calls.
Results
The company works in a system that covers the station's full cycle: from an order to an invoice and a report.
49 modules
The system is configurable and manages all processes, and the number of modules grows over time.
Separate client portal
Clients submit requests, track statuses and download invoices themselves, and the public part is isolated from the admin part.
Invoices straight from the system
Invoices are generated in the ERP and exported to the accounting software.
Client notifications
Clients are notified when each stage of work on their tank container is completed.
Client review on Clutch
Technologies Used
To implement the project, we used modern technology stacks focused on stability and scalability:
-
PHP 7.4
A time-tested language version providing a balance of speed and compatibility.
-
Symfony 3.4
A stable framework version for maintaining and developing classic PHP projects.
-
MySQL 8
Popular database management system for secure and efficient data storage.
-
Linux Ubuntu 22.04
Stable OS providing a high-performance and secure server environment.
-
Nginx
High-performance web server for fast content delivery and request handling.
-
-
From €10,000. The cost depends on the number of modules, roles and integrations, so we give an exact price after analyzing your processes.
-
Yes. This ERP was built by another team, and we took it over in January 2021. First we study the code and infrastructure and check security, then we keep developing the system.
-
Not always. Here clients used the system every day, so we kept it and split security, stability and new features into separate tasks.
-
By separating access and infrastructure. In this project the client portal runs on a separate server, and the admin part is isolated from the public one.
-
Yes. In this system invoices are exported to the accounting software and reports to Excel. Other services can be connected through APIs.
Need an ERP built around your company's processes?
About custom ERP developmentGreat!
We will contact you shortly