Tally TDL Textile Production Scheduler
Budget: ₹600 – ₹2,000 INR
I need a seasoned TDL developer to extend Tally so it genuinely supports production-scheduling tasks for a textile-manufacturing setup. My present Tally environment handles accounts well, but it gives me no way to plan, track and adjust loom, dyeing and finishing orders in real time.
What I expect you to build
• A TDL module that lets me create production orders inside Tally, assign them to machines or job-work parties, set planned start/finish dates and quantities, and view their live status.
• Smart screens that draw on existing item masters and BOMs, so the scheduler instantly shows yarn and grey-fabric requirements and flags shortages.
• A calendar or Gantt-style view—however you can best achieve it in Tally—to see overlaps, delays and machine utilisation at a glance.
• Custom reports summarising work-in-progress, idle capacity and expected completion dates; they must be exportable to Excel.
• Clean installation script (.tdl files), version notes and a short user guide so my in-house team can maintain it.
Acceptance criteria
1. All data is stored natively in Tally; no external database.
2. Scheduler reflects any change (date, quantity, routing) instantly across related vouchers and reports.
3. Code is well commented and passes Tally’s syntax checker without warnings.
4. I can create, edit and close at least 100 concurrent production orders without lag on a standard TallyPrime license.
Time frame is flexible; quality and reliability outweigh speed. Let me know your approach, past TDL examples—especially manufacturing modules—and the milestones you propose for development, testing and hand-over.
What I expect you to build
• A TDL module that lets me create production orders inside Tally, assign them to machines or job-work parties, set planned start/finish dates and quantities, and view their live status.
• Smart screens that draw on existing item masters and BOMs, so the scheduler instantly shows yarn and grey-fabric requirements and flags shortages.
• A calendar or Gantt-style view—however you can best achieve it in Tally—to see overlaps, delays and machine utilisation at a glance.
• Custom reports summarising work-in-progress, idle capacity and expected completion dates; they must be exportable to Excel.
• Clean installation script (.tdl files), version notes and a short user guide so my in-house team can maintain it.
Acceptance criteria
1. All data is stored natively in Tally; no external database.
2. Scheduler reflects any change (date, quantity, routing) instantly across related vouchers and reports.
3. Code is well commented and passes Tally’s syntax checker without warnings.
4. I can create, edit and close at least 100 concurrent production orders without lag on a standard TallyPrime license.
Time frame is flexible; quality and reliability outweigh speed. Let me know your approach, past TDL examples—especially manufacturing modules—and the milestones you propose for development, testing and hand-over.