ERP, job work and dealer software for Ludhiana.
Ludhiana is Punjab’s largest industrial city, making hosiery, cycles, auto parts and machine tools, and its units range from decades-old family workshops to plants that run an ERP. Units record work in Tally, Excel, job work challans and WhatsApp orders, and pending stock at job workers is known only after every challan is checked. GullySystem provides ERP, job work and dealer software from Nagarbhavi, Bengaluru, and can also take over support of an existing system whose original vendor is no longer available.
Focal Point and the industrial areas around it hold units making cycle parts, auto components, fasteners and machine parts. Gill Road has machine tool and engineering workshops. Many are decades old.
The hosiery trade knits through the year for a short winter selling season, with wholesale through Chaura Bazaar and Ghumar Mandi. Work passes through job workers for knitting, dyeing and stitching, and yarn, grey fabric and garments move between them on challans that are counted by hand. Counts are tracked on challans.
The areas, estates and markets that matter in Ludhiana.
How Ludhiana businesses pick and use software.
Ludhiana’s trade associations and family networks mean firms in the same trade share suppliers and dealers. A system built for cycle parts job work is relevant to other engineering units, such as the machine tool and forging workshops around Focal Point and Gill Road. Support arrangements matter too, because some businesses run locally installed software that is no longer maintained.
Hosiery firms need last season’s sales by design and dealer. Engineering firms need job cards and dispatch. The two trades are scoped separately.
Existing Tally data and Excel files are the starting point for either. Reports are built from them. New entry begins once the reports look right.
Where Ludhiana businesses lose time and money.
Winter production is planned without season-wise sales
Designs are chosen in spring and produced through summer. Sales by design and region from earlier seasons inform that plan, which is otherwise set in spring and carried out through the summer before any winter orders are placed. Without them, unsold stock builds up in the godown.
Yarn and garments at job workers are tracked in challan books
Yarn, grey fabric and garments move between knitters, dyers and stitchers. Pending stock by job worker is known only after every challan is checked. A job work ledger shows it directly.
Locally installed software has no active support
A local package was installed years ago and modified over time. The original vendor is no longer reachable, and even a report change is difficult. A review of the database and code shows what can be maintained, and whether a report change or a move to a maintainable platform is realistic.
Dealer returns after the season are settled late
Unsold woollens come back from dealers when the season ends. Without recorded return terms, credit notes are discussed for months after unsold woollens come back from dealers at the end of the season. Terms held against each dealer settle the question sooner.
What we would build for Ludhiana businesses.
Usually in this order, starting with whatever the audit ranks first.
ERP, CRM and Business Software Implementation
One record of stock, orders, customers and accounts, set up so your team opens it every day.
Learn moreSoftware Maintenance, Support and Rescue
Taking over the system your last vendor stopped answering for: fixing it, documenting it and keeping it running.
Learn moreData Engineering and Business Intelligence
Dashboards that answer the owner’s Monday questions without anyone building an Excel sheet first.
Learn moreBusiness Process Automation
Approvals, reminders, follow-ups and reports that run on their own instead of on someone remembering.
Learn moreAPI and System Integration
Accounting software, WhatsApp, payment gateways, tax portals and your own apps sharing one set of numbers.
Learn moreHow the work runs from Bengaluru for Ludhiana.
- 1
The audit, by call
A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.
- 2
A written proposal
Scope, what we build first and the cost, agreed in writing before anything starts.
- 3
Build in short rounds
Working screens shared every few weeks. Your team tests them from your own office.
- 4
Go-live, in person when it helps
For data migration and training we can come to Ludhiana. Travel is agreed in advance.
- 5
Support online
Fixes, changes and hosting handled remotely by the same team that built it.
The work we have published.
We don’t claim Ludhiana clients we don’t have. These are systems our team built; the way we work is the same wherever you are.
PetSeva: matching owners to the right vet, at any hour
A two-sided veterinary platform where vets are searchable by specialisation and bookable outside clinic hours. It now carries more than 2,000 veterinary doctors.
Read the case study Paying guest accommodationSAM Atithi Pavathi: bed-level occupancy as the source of truth
PG management software where allocation, rates and invoices are derived from bed-level occupancy and not maintained in parallel spreadsheets.
Read the case study School transport servicesSAM Tours: school transport on a single ledger
Registration, fee collection, routing and finance write to the same records, closing the gap between journeys run and fees collected.
Read the case study Microfinance and Self Help GroupsVikasa RDO: making SHG loan recovery auditable
Loan proposals, recoveries and commissions sit on one record, with a person attached to every state change, so a business handling a bank’s money can show where each rupee went.
Read the case studyQuestions Ludhiana owners ask before they call.
Our old software vendor has disappeared. Can you take over the system?
It depends on access to the database and, ideally, the source code, and on the current state of the system, which a review would show first. With those, the system can be kept running, faults fixed, and a move to a maintainable platform planned. A review of its current state is the first step.
Can the system show hosiery sales by design and dealer from past seasons?
Yes, where the data exists in Tally or in old Excel files. It is combined into season-wise reports by design and dealer, so the next winter plan starts from recorded sales.
What happens after I share my requirements?
An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.
How much will the software cost?
We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.
Industries we build for in Ludhiana.
Tell us what your Ludhiana business runs on today.
Send a short note on the spreadsheets, software or WhatsApp groups your team depends on. We reply the same working day.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements