Beside your global systems, not instead of them.
Run the Ghana-local work around your OEM systems, and mark each domain as authoritative in one place or the other.
Meludu does not overwrite an OEM system you have marked authoritative.
For each domain you choose who holds the truth. Global warranty and connected-car status can stay with the manufacturer, while Meludu keeps the gate, local tenders, tax documents and branch control.
What runs beside the incumbent.
- Gate and release
- Every movement is recorded, and a car leaves only on a single-use token that is checked again at the gate.
- Local tenders
- Cash, terminal and bank-transfer tenders are recorded and reconciled in Ghana, beside your existing systems.
- Tax documents
- Where your approved existing system issues the tax invoice, Meludu records the genuine document with its source number and attachment. It never manufactures a certification code.
- One authority per domain
- At cutover each domain has one authoritative system. A temporary bridge between two systems is reconciled daily, not left to drift.
OEM integration is a project, not a promise.
Each manufacturer connector is built and verified on its own, against current access and a sandbox. Meludu works without OEM API access, and never claims a live status it has not verified.