Teams that run their work inside ERPNext quickly hit the ceiling of the stock board. Frappe's native Kanban only groups cards by a single Select field, so a sales pipeline keyed on a Link-to-Territory, a project board grouped by assigned engineer, or a support queue split by priority all force you to bolt a throwaway Select field onto the DocType and keep it in sync by hand. There are no swimlanes, no WIP limits, no inline card editing, and every user is stuck with whatever list filters and columns the last person left behind. The result is that project and sales teams either export to a spreadsheet or buy a separate board tool, and ERPNext stops being the single source of truth.

Enhanced Kanban & List Views closes that gap as a proper Frappe app (its own module, installable with bench get-app / bench install-app) rather than a fragile customization. We add a configurable board layer that can build Kanban columns directly from Link fields — grouping a Sales Order board by Customer Group, a Task board by Project, or a Lead board by Sales Person — resolving the linked records through the Frappe ORM and honoring the same read permissions and role profiles the rest of ERPNext uses. On top of columns we add horizontal swimlanes (a second grouping dimension), per-column WIP limits with visual over-limit warnings, and conditional row and card coloring driven by field-value rules you define (for example, overdue delivery dates in red, high-value deals in green).

Technically, moves and edits are transactional. Dragging a card writes through a whitelisted server method (@frappe.whitelist()) that runs standard document validation and hooks.py doc_events (validate, on_update), so a board move can't bypass your business logic — it triggers the same workflow state changes, notifications and permission checks as editing the form. Inline card editing uses the Frappe REST API and client scripts to patch individual fields without opening the full form. Saved view presets — the exact columns, filters, sort order, board grouping, swimlane and color rules — are stored per user in a custom DocType, so each person keeps their own working views while shared team presets stay stable. Where a board needs periodic recalculation (aging counters, stale-card flags), we wire a scheduler_events job. Everything is built and tested against Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is a generic download. On a short scoping call we confirm which DocTypes get boards, which Link fields drive columns and swimlanes, your WIP and coloring rules, and the permission model. We then build your version of the app, test it on a staging bench, run UAT with your team, and deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope depending on how many DocTypes and rules are in play. You receive the full source code and git repository, so you are never locked to us.