From quota to production: vehicle orders in VEGA
Ordering new vehicles is the point where the network’s plans meet the factory’s reality: quotas, restrictions, production months.
In many networks that meeting still happens in spreadsheets and mailboxes. In VEGA we took a different path: we separated ordering from selling — and gave each its own system.
Ordering, separated from selling
The Vehicle Orders module carries the whole ordering side: dealers prepare and confirm orders, follow quotas, restrictions and production months, and cancel what is no longer current. The sales module stays focused on offers and contracts for the end customer — and when a contract for a known customer is created, its order is created with it and joins the same flow.
A dealer sees allocated and used quantities by model and by location at all times, orders stock vehicles without drafting a contract first, and configures every vehicle in the brand configurator built directly into the flow.
Quotas, restrictions and the production month
The importer sets the frame: quotas per location, restrictions by version, option or colour, and the production months into which orders are placed with a live view of what is still available. Confirming orders in bulk and copying an order for identical stock configurations keep the routine part of the job short.
When quotas or restrictions change, the system flags the orders that no longer fit and leads the user to resolve them — nothing silently falls through.
Communication on the order, not around it
Change requests — a different colour, a different version — used to travel by e-mail, detached from the order they were about. Now the conversation lives on the order itself: the dealer submits a comment, the importer responds and manages its status from new through in-progress to resolved or rejected. The author, their superiors and other participants are notified automatically; filters by status and export keep the overview.
Both sides see the same picture at practically the same moment: what is open, what is being worked on, what has been agreed — order by order.
There is one order — so everything agreed about it should live in one place.
A closing thought
Process optimisation in a network is not about sending e-mail faster.
It is about the network and the importer working in the same rhythm — on the same record, with the same view.
One system, one rhythm: the network orders, the importer governs, and both see the same picture.