[Initiative] Admin & Vendor Full Extensibility #695
Description
Summary
We are making the Admin and Vendor panels fully extensible without requiring forks and without losing the ability to receive updates.
The goal is to allow deep customization of backoffice experiences while keeping a clear and sustainable upgrade path.
Motivation
Customizing Admin and Vendor panels today often requires forking or tightly coupling to core implementations. This makes long-term maintenance difficult and upgrades risky.
As Mercur targets more complex marketplace use cases, teams need the ability to customize specific parts of the UI without taking ownership of the entire panel.
This initiative introduces a clear override model that removes that tradeoff.
Scope
This initiative introduces an extensibility model where:
- every core UI component is overrideable
- overridden components are fully owned and maintained by the project
- all non-overridden components remain auto-updatable
- overrides can be applied:
- globally
- per route
- per context
This allows teams to replace only what is necessary while relying on upstream updates for everything else.
Impact
- Developers gain precise control over customization with minimal maintenance overhead
- Integrators can adapt panels to different marketplace needs without long-term coupling
- Marketplace operators benefit from custom workflows without sacrificing upgrades
This initiative significantly improves developer experience and long-term sustainability.
Relationship to the Roadmap
This initiative is tracked on the public Mercur roadmap.
Current status: In Progress
Feedback & Discussion
This issue is intended for high-level discussion and feedback.
Implementation details and task-level work are tracked internally and are intentionally out of scope for this issue.