Blog / Features

ToDo in ERPNext is NOT What You Think

After 200+ ERPNext implementations, I keep seeing the same pattern: tasks on WhatsApp, follow-ups forgotten, responsibilities unclear. The fix was already inside ERPNext all along — hiding in plain si

April 1, 2026 · 3 min read

Series: Inside Frappe — Going beyond the basics to show how ERPNext features work when used to their full potential.

The Problem You Already Know

Walk into any company that has been running ERPNext for a few months. The system is live. Data is being entered. Invoices are going out.

But somewhere outside the system, this is happening:

Follow-ups are being managed in a WhatsApp group
Tasks get assigned verbally in meetings — and forgotten by morning
Deadlines slip because nobody was clear on who was responsible
The answer to every missed action is the same: "I thought someone else was handling it"

This is not a people problem. It is a system design problem. The ERP is capturing data but not driving action.

What ToDo in ERPNext Actually Is

The Frappe ToDo doctype is not a sticky note. When configured correctly, it operates as a responsibility and execution layer that sits across every transaction in your system.

Here is what it gives you when used properly:

Responsibility Tracker

Every ToDo has an Assigned To field. A named person is on the hook — no ambiguity, no grey area. The system knows who owns what.

Follow-Up Engine

ToDos carry a Due Date. ERPNext notifications alert users about pending and overdue items. Your follow-up process stops depending on human memory.

Cross-Department Visibility

Managers can filter ToDos by user, date, status, and linked document. "What's pending with your team?" becomes answerable in seconds — no status meeting required.

Built-In Task Management

No extra tools. No third-party integrations. ToDo is already inside the system your team logs into every day.

The One Shift That Changes Everything

Most companies use ToDo like this:

A personal reminder you create manually — and usually forget by Friday.

The companies that extract real value use ToDo like this:

A system-driven action, automatically triggered by a business event.

That single shift — from manual to automatic — is where ERPNext starts to feel like it is actually running your business, not just recording it.

Think about what becomes possible:

A Sales Order is submitted → a ToDo automatically appears for the warehouse team
A Support Issue crosses its SLA → the manager gets notified without anyone making a call
A Purchase Order needs approval → the right person is assigned before they even open their inbox

This is the execution layer. And ERPNext already has all the tools to build it — Assignment Rules, Notifications, and Automation hooks — right out of the box.

Start Here: Your First Automated ToDo in 5 Minutes

You don't need a developer. Try this right now:

Go to Setup → Automation → Assignment Rule
Create A new rule for any DocType — start with Sales Order
Set Condition For example: Status = "To Deliver and Bill"
Assign To A specific user, or use round-robin for team distribution
Test It Submit a Sales Order — ERPNext creates the ToDo automatically

From this point forward, every matching document triggers an action — with zero manual effort.

Coming Up Next in the Inside Frappe Series

In the next post, we go deeper:

Linking ToDo directly with Sales Orders, Issues, and Purchase Orders
Building a complete auto-assignment workflow — no code required
Using ToDo as a real-time visibility dashboard for managers

Because at the end of the day, ERP is not about storing data. It's about making things happen.

Is your team still tracking tasks outside ERPNext?

If follow-ups are falling through the cracks — or your team is running operations on WhatsApp — there's a better way. We've helped 150+ businesses across Kerala and beyond get more out of their ERPNext investment.

Talk to Us →