Custom ERPNext System Build
Budget: ₹12,500 – ₹37,500 INR
The project centers on deploying a fresh ERPNext instance (Frappe Framework v14+) and tailoring it to match our daily operations. Core configuration covers the basic Accounting, Human Resources, and Inventory modules, plus two custom requirements:
• Car-Washing Service module – booking slots, tracking vehicle status, linking parts and consumables to each service, and generating service-specific invoices.
• Payment Integration – real-time card and mobile-wallet processing at the wash bay and within the customer portal, with payments flowing straight into ERPNext’s Accounting.
. IoT based integration to automatically raise the barricades when payment is done.
Beyond configuration, I’ll need:
1. Workflow tweaks (leave approvals, purchase requests, etc.) to mirror our existing sign-off chain.
2. Role-based dashboards so supervisors see only their branch data.
3. Data migration scripts for legacy customer, supplier, and payroll records (CSV to ERPNext).
4. Light training materials: a set of short Loom videos or a PDF quick-start guide.
Acceptance criteria will be a live demo on a staging server showing all five modules working together, followed by successful migration of a sample data set and clean push to production.
Development can happen on GitHub; pull requests into the main branch should pass the default Frappe test suite.
If you have recent ERPNext custom-app work—especially around services or payment gateways—share a link or repo snapshot so I can gauge fit. I’m ready to start as soon as we align on milestones and timeline.
• Car-Washing Service module – booking slots, tracking vehicle status, linking parts and consumables to each service, and generating service-specific invoices.
• Payment Integration – real-time card and mobile-wallet processing at the wash bay and within the customer portal, with payments flowing straight into ERPNext’s Accounting.
. IoT based integration to automatically raise the barricades when payment is done.
Beyond configuration, I’ll need:
1. Workflow tweaks (leave approvals, purchase requests, etc.) to mirror our existing sign-off chain.
2. Role-based dashboards so supervisors see only their branch data.
3. Data migration scripts for legacy customer, supplier, and payroll records (CSV to ERPNext).
4. Light training materials: a set of short Loom videos or a PDF quick-start guide.
Acceptance criteria will be a live demo on a staging server showing all five modules working together, followed by successful migration of a sample data set and clean push to production.
Development can happen on GitHub; pull requests into the main branch should pass the default Frappe test suite.
If you have recent ERPNext custom-app work—especially around services or payment gateways—share a link or repo snapshot so I can gauge fit. I’m ready to start as soon as we align on milestones and timeline.