Lessons from real ERPNext and Frappe work in production, written by the team behind 1,300+ merged PRs. We publish what we learn so the open-source community we build on keeps getting better.
Featured
Most ERPNext upgrade pain starts in custom code. Lens reads your apps the way a senior reviewer would and flags the patterns that break - before they reach production.
Upgrades stall on one question - will our customizations still work? Lens answers it up front with a per-app compatibility report against your target version.
System freezes under heavy load, lock wait timeouts, 'server is too busy' errors: we kept tracing them back to customization bottlenecks on client sites. So we built Optimus to find them, then open-sourced it for the Frappe ecosystem.
Most ERPNext upgrade pain starts in custom code. Lens reads your apps the way a senior reviewer would and flags the patterns that break - before they reach production.
Upgrades stall on one question - will our customizations still work? Lens answers it up front with a per-app compatibility report against your target version.
Forking is easy; contributing upstream is hard and worth it. The habits that got our patches merged into the framework your ERPNext runs on.
NEFT, RTGS, UPI and host-to-host files in a regulated workflow. The retries, idempotency, and audit trails that kept it reliable when money was on the line.
Years of migration reviews turned into a tool. What we automated, what still needs a senior human, and what we learned shipping our first product.
No posts match your search
Try a different keyword or category.
We turn hard implementation problems into shipped software. Tell us yours.