Frappe Developer

@ambar

DocTypes should be fully new, or some of them must link to existing ERPNext masters like Customer / Item? Will this module run on one site only, or bench has multiple sites? Should email / notifications run async (background job) or normal workflow trigger? I went through your description carefully. This looks like a fresh Frappe app build, not editing existing apps. I’ve done similar module work before where everything had to install clean with bench. Hi, this is Ambar Shome, I work independently but also run Shome & Associates for larger projects. Plan is simple. First check your current site so I know which tables we must link and which must stay separate. Then create new app, new module, new DocTypes from start. I prefer doing DocTypes first, then child tables, then workflow, otherwise permissions become confusing later. During build I normally keep these things fixed: use separate app (not inside erpnext) use hooks + patch file for schema change email events via enqueue, not direct server validation in python also query report first, script only if needed pytest with frappe test runner after_install hook so bench install works basic cache for repeated lookups README will have exact bench commands + small demo no problem. One small thing to confirm — should status change emails go through Frappe Email Queue only? Yes / No.

@vishal1145

Your module will fail bench migrations if you hardcode DocType links instead of using Frappe's dynamic linking system. I've seen teams lose weeks debugging permission conflicts because they skipped proper role hierarchy mapping during the design phase. To ensure your module stays upgrade-safe when ERPNext releases new versions, I need clarity on two things: 1. What's your current ERPNext version and are you planning to upgrade to v15 within the next 6 months? Version-specific hooks behave differently. 2. Do your workflows need to interact with existing ERPNext modules like Sales Invoice or Stock Entry, or is this completely standalone? Cross-module dependencies require careful fixture management. Here's the architectural approach: - FRAPPE FRAMEWORK: Build custom DocTypes with proper naming series, field-level permissions, and server-side validations using controller hooks to prevent data corruption during concurrent transactions. - PYTHON BACKEND: Implement document events (before_save, on_submit, on_cancel) with proper error handling and database transactions so partial failures don't leave orphaned records. - JAVASCRIPT + JINJA: Create custom forms with client scripts that validate data before server submission, reducing round trips and improving UX for high-frequency data entry. - WORKFLOW ENGINE: Configure state transitions with role-based approval chains and email notifications using Frappe's built-in notification framework instead of custom SMTP logic. - API DEVELOPMENT: Expose whitelisted methods with proper authentication decorators and rate limiting to prevent abuse if you integrate external systems later. - PYTEST COVERAGE: Write integration tests that spin up test sites, create sample records, trigger workflows, and assert database state changes to catch regression bugs before production. I've built 7 custom Frappe apps for manufacturing and distribution companies that handle 50K+ transactions monthly without breaking during ERPNext upgrades. I don't take on projects where the workflow logic isn't documented upfront - let's schedule a 20-minute call to map your business rules and edge cases before I commit to a timeline.

@kaustubhbawa123

Hi, I am an IIT Grad, PMP Certified Professional, ex-BFSI and worked at fortune 500 companies. I will make it a reality for you. As a Frappe Developer, I will analyze the existing database schema to identify necessary hooks for my module, then design a custom DocType, child tables, workflows, and role permissions from scratch, ensuring Frappe best practices for upgrade safety. Kindly click on the chat button so we can discuss and get started. Will share you my prior projects done and my resume too. I have been doing freelancing since 2019 worked at top MNCs in both USA and India. Lets connect

@Syedh1998

I specialize in **custom module development on Frappe/ERPNext** and can build your module from the ground up with a clean, scalable architecture that remains fully upgrade-safe. I’ll begin by analysing your current instance to identify **database hooks, dependencies, and integration points**, then design structured **DocTypes, child tables, workflows, and role-based permissions** aligned with Frappe best practices. On the backend, I’ll develop robust Python logic with proper validation, events, and automation, while the frontend will use **JS and Jinja templates** for a seamless Desk experience. The module will be packaged cleanly so it installs via **bench get-app / install-app without manual changes**, ensuring portability across environments. I’ll also implement **workflow triggers, notifications, and email events**, ensuring smooth state transitions, and include **pytest-based unit tests** covering critical logic to meet your ≥80% coverage requirement. My focus is on **clean code, maintainability, and zero console errors**, delivering a stable module ready for production use. You’ll receive a **clear README and a short demo walkthrough**, plus milestone-based delivery with transparent timelines. I’m ready to start immediately and deliver a reliable, well-structured Frappe module that fits seamlessly into your ERPNext stack. Syed

@mariamz24

Hello, We would like to grab this opportunity and will work till you get 100% satisfied with our work. We are an expert team which have many years of experience on PHP, JavaScript, Python, Django, Software Development, Web Development, Backend Development, Frontend Development, Database Design, API Development Please come over chat and discuss your requirement in a detailed way. Thank You

@iconicdev4

Hi, I’ve built custom modules on the Frappe Framework and extended ERPNext with clean, upgrade-safe architectures—your requirement aligns perfectly with how we structure greenfield modules. Proposed Architecture App Structure: Isolated custom app (bench new-app) with modular separation (doctype, api, hooks, workflows). DocTypes: Core + child tables with strict naming conventions, indexing, and validation hooks. Business Logic: Python controllers + whitelisted APIs (service layer pattern to keep logic reusable/testable). Frontend: JS controllers + Jinja templates (minimal overrides, maximize standard UI for upgrade safety). Workflows & Permissions: Role-based access + state-driven workflows using Frappe’s Workflow Engine. Events: Hook-based triggers for emails/notifications (doc_events, scheduler_events). Testing: Pytest + Frappe test runner (fixtures + factories for ≥80% coverage). Packaging: Bench-installable app with zero manual patching. Milestones & Timeline Analysis & Schema Mapping – 1–2 days DocType & Workflow Design – 2–3 days Backend (APIs + Logic) – 3–4 days Frontend (Forms, Pages) – 2–3 days Permissions + Notifications – 1–2 days Testing (≥80% coverage) – 2 days Packaging + Demo + README – 1 day Total: ~10–15 days Happy to share a quick demo of similar modules we’ve delivered. Best regards,

@andersond73

Hello, As I am a senior Frappe/ERPNext developer, I can build your new custom module in 7 days for ₹28,000. This project needs more than small ERPNext customization. You want a fresh module built cleanly from scratch inside an existing Frappe/ERPNext environment, with its own DocTypes, child tables, workflows, reports, permissions, notifications, and packaging so it installs properly through bench on a clean site. I would start by analyzing your current ERPNext instance and identifying only the schema hooks the new module truly needs, so the app stays decoupled from existing customizations as much as possible. Then I would build everything as a proper installable app, test bench get-app / bench install-app on a clean site, verify desk visibility and permissions, confirm workflow-triggered notifications, and finish with concise documentation plus a walkthrough demo. The goal will be a module that works cleanly today and still survives future ERPNext upgrades without hidden manual edits. Thank you.

@ibrahiman58

Hi, I’m confident I can build a fully upgrade-safe Frappe module from scratch for your ERPNext instance, following best practices and delivering a clean, maintainable solution. With experience in Frappe/Python backend development, JS/Jinja frontend, and ERPNext module architecture, I’ll ensure your module installs cleanly and functions flawlessly. I will start by analyzing your current ERPNext instance to determine the required schema hooks and define DocTypes, child tables, workflows, and role permissions. Next, I will implement the backend and frontend logic, configure notifications and workflow triggers, and package the module for bench installation with no manual edits. Finally, I will write unit tests (≥80% coverage), verify all doctypes and workflows work as expected, and provide a concise README plus a screen-share demo to confirm all core actions run without errors. The result will be a polished, standalone module that installs seamlessly, respects role permissions, executes workflows reliably, and is fully testable and maintainable. Looking forward to designing and delivering your custom Frappe module efficiently.

@abhishekd2151

Hello, I have reviewed your requirement to build a fresh, upgrade-safe module on the Frappe framework integrated with your existing ERPNext instance. I will develop this from scratch following Frappe best practices, ensuring clean architecture, scalability, and seamless installation via bench. --- ### ? Proposed Architecture **1. App Structure** * New custom Frappe app (fully isolated, no core modification) * Modular design: * `/doctype` – All custom DocTypes & child tables * `/workflow` – Workflow definitions * `/report` – Script & query reports * `/page` – Custom UI pages (if required) * `/public/js` – Frontend logic * `/templates` – Jinja templates **2. Backend** * Python-based controllers using Frappe ORM * Event hooks (validate, on_submit, on_update, etc.) * Background jobs (if needed via Frappe scheduler) **3. Frontend** * Clean Desk UI integration * Custom JS for forms, validations, dynamic behavior * Jinja templates for printable/views **4. Permissions & Security** * Role-based access control (RBAC) * Permission rules per DocType * Workflow-driven state transitions **5. Notifications** * Email alerts via workflow triggers * System notifications using Frappe events --- ### ? Reusable Components (If Needed) * Frappe standard utilities (email queue, scheduler, REST API) * ERPNext base models (only for reference, not modification) * No dependency on third-party apps unless explicitly required -

@garryghuge

Hello, I can develop a fully standalone, upgrade-safe module on the Frappe framework, built from scratch and installable via bench without manual steps. Approach Analyze your ERPNext instance to identify required schema hooks Design DocTypes, child tables, workflows, and role permissions Implement backend logic (Python) using hooks and service layers Build frontend with JS and Jinja following Frappe standards Configure notifications and workflow triggers Package as a clean installable app Architecture Modular app structure: doctype, api, services, workflows, tests Strict separation of business logic and UI Use of Frappe Workflow Engine and Role Permissions Timeline Analysis & Schema: 1–2 days Core Development: 4–5 days Frontend & Workflows: 2–3 days Testing (pytest ≥80%): 2 days Packaging & Demo: 1 day Total: 10–13 days Deliverables Bench-installable app Fully configured DocTypes and workflows Test suite with ≥80% coverage README + demo walkthrough I ensure clean code, no console errors, and full compliance with your acceptance criteria. Ready to start immediately.

@karthikresonite

Greetings from Resonite Technologies! Our team specializes in Frappe/ERPNext module development and can build your clean, upgrade-safe module from scratch, fully compatible with your existing ERPNext instance. Proposed Approach: • Analysis: Review your current database schema and define hooks required for the new module • DocTypes & Workflows: Design fresh DocTypes, child tables, role permissions, and workflows according to Frappe best practices • Backend & Frontend: Implement Python server logic, JS interactions, and Jinja templates ensuring full upgrade safety • Packaging & Installation: Deliver as a fully installable app via bench get-app / bench install-app with no manual edits required • Testing & Demo: Unit tests (pytest ≥80% coverage), console-error-free operations, email/notification triggers, and a short screen-share demo • Documentation: Concise README covering installation, usage, and configuration We follow modular, maintainable architecture, leveraging reusable ERPNext components where applicable, and can provide milestone-based timelines for analysis, development, testing, and deployment. Best regards, Resonite Technologies

@vivekmojidara26

Hi, I've built ERP modules on Odoo (Python/DocType architecture) — Frappe follows the same pattern, so I can work in ERPNext natively. **Proposed Architecture:** - Standalone Frappe app (bench get-app pattern) — clean install, zero impact on existing stack - DocTypes with parent/child tables, Link fields, naming conventions per Frappe best practices - Python hooks: before_save, on_submit, on_cancel for workflow + email/notification triggers - JS Form scripts + Jinja print templates for any reports/views - Role-based permissions at DocType level **Milestone Plan (14 days):** - Day 1–3: Schema review + DocType design → sign-off - Day 4–8: Core development (Python backend + JS client + workflows) - Day 9–11: Reports, print templates, pytest unit tests (≥80%) - Day 12–14: bench install test on clean site + README + screen-share demo All acceptance criteria met: bench install, doctypes in desk, workflows trigger correctly, zero console errors, pytest ≥80%. Quick question: What domain does the module cover — procurement, HR, or custom workflow? That'll finalize the DocType design upfront. Ready to start today. Vivek

@bhavyaj81

I am Bhavy Jhaveri, an ERPNext/Frappe developer with approximately 1.5 years of hands-on experience. I specialize in customizing ERPNext solutions, including report development, scripting, and workflow optimization. In addition to my professional experience, I have also worked on freelance projects, delivering tailored ERPNext and Frappe solutions based on client requirements. I am currently seeking freelance opportunities where I can contribute my technical expertise and help businesses streamline their operations through efficient ERP implementations.