Real modularity
You start with the area that hurts most today and expand the system in stages, not in a monolithic project.
Modular architecture for diesel shops
Total control of your diesel shop module by module
Turn on only the modules your operation needs: intake, yard, labs, quoting, inventory, imports and more. They all share context, but none forces you to implement the rest from day one.
10 Operational modules
+4 AI add-ons
4 Product layers
1 Single data source
Modules that talk to each other
Orders, diagnostics, parts and statuses travel between areas without re-entering information.
No forced dependency
If you haven't turned on imports, invoicing or AI yet, the operational core keeps running.
Modular architecture Request a modular demo
Implement DieselOS in blocks, not as a closed package
Each card sums up a real shop area. Open it only if you want to see how it fits within the operation.
01 Operational core Intake Registers clients, orders, vehicles, devices and the initial assignment to the right lab. View details
Ideal for
The best starting point if shop intake today moves between WhatsApp, memory and loose sheets of paper.
Connects with
Opens the base order later used by Yard, Labs, Quoting and tracking.
- Clients
- Orders
- Photos
02 Vehicle inspection Yard Engine inspections, checklists, parts and evidence for full cargo or heavy-duty vehicles. View details
Ideal for
Ideal if you receive trucks or machinery and need to separate vehicle diagnostics from the component lab.
Connects with
Shares order, client and statuses with Intake, Quoting and reports.
- Checklist
- Photos and video
- Parts
03 Technical diagnostics Labs Manages diagnostics by lab, references, parts, protocols and repair statuses. View details
Ideal for
For shops with a technical flow specialized in modules, pumps, Common Rail, HEUI, EUI or turbos.
Connects with
Consumes devices from Intake and feeds Quoting, Inventory and the technical history.
- References
- Diagnostics
- Protocols
04 Commercial flow Quoting Turns diagnostics into estimates, deliveries, partial authorizations and commercial follow-up. View details
Ideal for
Key when the bottleneck is organizing prices, approvals and customer responses.
Connects with
Reads real diagnostics and moves the flow toward Inventory, Production or commercial close.
- Estimates
- Authorizations
- Follow-up
05 Internal flow Production Internal parts requests for shop jobs that do not go through a customer sale. View details
Ideal for
Useful for internal consumption, DMS or lab jobs where the technician needs to request without opening a sale.
Connects with
Integrates with Inventory and dispatch, but lives as an independent internal flow.
- Internal use
- Dispatch
- DMS
06 Supply control Inventory Groups parts dispatch, catalog, equipment loans and item loans. View details
Ideal for
When you need real control of stock, loans and deliveries by lab.
Connects with
Responds to Quoting and Production and keeps availability visible across the operation.
- Stock
- Loans
- Dispatches
07 Purchasing and costing Imports Manages international purchases, documents, expenses, costing and financial close per import. View details
Ideal for
For companies that bring in their own goods and need real cost per item before selling or dispatching.
Connects with
Feeds Inventory and margins without forcing the shop to have this module from day one.
- Costing
- Documents
- Logistics
08 Commercial close Electronic Invoicing Issues and manages DIAN electronic invoicing connected with the operation. View details
Ideal for
Activates when you want to close the commercial cycle without leaving the DieselOS ecosystem.
Connects with
Leverages existing orders and authorizations, but can be added later.
- DIAN
- Invoices
- Close
09 Advanced layer Pro Modules Advanced layers such as history by license plate and specialized tools for electronics. View details
Ideal for
For shops that already master the base flow and want additional operational depth.
Connects with
Extends Labs and operations without replacing the core that is already running.
- Advanced
- History
- Specialization
10 Continuous improvement PQR & continuous improvement A channel to report errors, suggest improvements and close the system's evolution loop. View details
Ideal for
Important when the operations team wants to iterate fast and keep traceability of feedback.
Connects with
Does not block operations: it supports the product's continuous improvement.
- Feedback
- Support
- Continuous improvement
System design
Modules talk to each other, but they don't blindly depend on one another
The right business logic is simple: you start with the area that hurts today and turn on the rest when the operation really calls for it.
You start with the real pain
You can start with Intake + Labs, just Inventory, or any other combination that solves your current priority.
They share context
Orders, clients, statuses, diagnostics, parts and documents are reused across areas when the operation needs it.
No forced dependency
If you don't turn on Imports, Invoicing or AI today, the rest of the system keeps working with its own flow.
Example journey
A single operation can chain together when it makes sense
A compact example of real integration between areas, not a purchase requirement.
Intake
Intake and Yard register the arrival and the initial evidence.
Diagnostics
Labs structure references, parts and technical statuses.
Authorization and supply
Quoting, Inventory and Production use that same data to approve and dispatch.
Advanced layers
Imports, Invoicing, Pro and AI come in once they add real value.
Integration exists to avoid double work. Mandatory dependency does not.
Add-ons
Assistants and advanced layers you can add later
AI and Pro layers are optional expansions. They work better with operational data, but you don't need them to get started.
Virtual Assistant
Answers questions in natural language using real shop data.
Reads orders, clients, statuses and devices on the same operational base.Orders Agent
Creates orders through conversation to speed up shop intake.
Extends Intake without changing the system's central flow.Plates Agent
Extracts license plates from photos and reduces friction in vehicle intake.
Speeds up Intake and Yard as an optional automation layer.Inventory Assistant
Looks up stock, parts and locations without browsing tables or filters.
Sits on top of Inventory when the team needs faster lookups. FAQ
Key questions about modularity
The point isn't to sell rigid software, but a platform that adapts to the shop's level of maturity.
Do I have to implement every module from the start?
No. DieselOS can start with the most urgent area — for example Intake + Labs, or just Inventory — and then grow in phases.
How do the modules talk to each other?
They share base entities like orders, clients, statuses, diagnostics, parts and documents. That way each area builds on prior work without duplicating data entry.
Which modules are usually turned on first?
The initial core is typically Intake, Yard or Labs and Quoting. Then Inventory, Production or Imports are added depending on the shop's complexity.
Can I add Pro or AI assistants later?
Yes. Pro layers and assistants are understood as system expansions, not as a requirement to operate.
DieselOS demo
Turn on only the modules your shop needs
The right pitch for DieselOS isn't to sell a monolithic block. It's to show a platform that can start with the essentials and grow with the client's real operation.