Partners and SaaS resellers who deploy ERPNext for their own clients keep hitting the same wall: the standard Desk still says "Frappe" and "ERPNext" in a dozen places, ships one navy accent color, and offers no dark mode or typography control. ERPNext core lets you swap the app logo and a favicon under Website Settings and Navbar Settings, but it stops well short of a coherent branded experience — the login screen, the loading splash, the sidebar accents, the portal pages, and the boot payload still carry upstream branding. For an agency reselling ERPNext under its own name, that leakage undermines the value proposition on the very first screen a client sees.

We build a proper Frappe app (for example ecosire_branding) that installs cleanly alongside erpnext and frappe and owns your entire visual identity. The theme layer ships multiple modern Desk skins (Fluent- and Material-inspired) as bundled CSS/SCSS compiled through the Frappe asset pipeline, layered over Desk's existing CSS variables so upgrades don't break them. A single "Branding Settings" DocType (a Single) holds your logo, favicon, brand colors, accent presets, font family, and dark-mode toggle; changes are pushed to every session by overriding app_include_css, app_include_js, and website_context in hooks.py, plus a boot_session hook that injects the active theme into frappe.boot so the correct skin paints before first render — no flash of upstream styling. Custom fonts are self-hosted and registered via @font-face so nothing depends on an external CDN.

Technically, the white-labeling reaches past cosmetics. We wire on_update doc events on Branding Settings to regenerate the compiled theme bundle and bust the asset cache, expose a small set of @frappe.whitelist() methods so an admin can read and update branding through the Frappe REST API (useful when you provision tenants programmatically), and gate the configuration screen behind a dedicated role profile so only your staff — not the end client — can change it. The branded login and portal pages are delivered as overriding web templates and a website_context hook, giving you a custom logo, background, color scheme, and footer on /login, the password-reset flow, and the customer portal. Where a reseller runs many sites, a scheduler event can (optionally) re-apply approved branding on a cadence so a client's manual tweak never sticks.

Because this is build-to-order, nothing is a black box. We start from your brand assets and target ERPNext version (v15 or v16), agree the exact themes, presets, and pages in scope, then build and hand you the installable app source. Typical delivery is one working week from confirmed scope. You get UAT on a staging bench first, a documented install, and the full git repository — so your team can extend the SCSS, add another skin, or fold it into your own deployment pipeline without being locked to us.