Skip to main content
GullySystem

Kotdwar · LocationsKotdwar’s wholesalers supply the Garhwal hills, and every truck up the road carries credit.

Kotdwar stands where the plains road meets the Garhwal hills, and goods for Pauri, Lansdowne and the villages above are sold wholesale here. Everything goes up by truck on credit. Stock, ledgers and trips for these trades are the work GullySystem takes on from its Bengaluru base in Nagarbhavi.

At a glance

The town sits on the Khoh river at the foot of the hills, and consignments for Pauri Garhwal begin here. Wholesalers receive goods from Najibabad, Bijnor and Haridwar, and send them up in smaller loads.

Retail shops in the town serve families, army households connected to Lansdowne and visitors to the Siddhabali temple, while farmers on the plains side grow sugarcane and paddy. Nearby villages sell milk, vegetables and fruit.

Around Kotdwar

The areas, estates and markets that matter in Kotdwar.

Wholesale lanes

Grocery, cloth, hardware and building material are sold to hill shopkeepers on credit, and each load goes up on the next available truck.

Transporters to the hills

Small goods carriers and trucks run daily to Pauri and beyond, and trip sheets, loading charges and return loads are their main records.

The grain and farm input market

Farmers buy seed and fertiliser on credit and sell produce after harvest. Dues follow the crop calendar.

Around the Siddhabali temple

Shops, sweet makers and small lodges serve devotees. Weekend rush and festival crowds shape their stock.

How software gets chosen

How Kotdwar businesses pick and use software.

A wholesaler to the hills wants a ledger by shop that shows what is owed and what is promised.

A goods carrier wants each trip’s load, freight and return load on one sheet.

A farm input dealer wants dues set against the next harvest.

Where it breaks

Where Kotdwar businesses lose time and money.

Hill shops order by phone and the load is picked from memory

A call comes in and the godown hand fills it from memory. Printed pick lists cut errors.

Return loads travel empty

Trucks come back down with nothing because nobody knew a load was waiting, and a shared list of pending loads fills the trip back.

Old dues sit unspoken

A shop that owes from last season keeps buying, and an ageing view lists the oldest dues before the next load is sent.

Temple weekends sweep the shelves clean

Sweet makers and general shops run short on peak days. Sales history by day of the week suggests what to prepare.

How it works

How the work runs from Bengaluru for Kotdwar.

  1. 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. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to Kotdwar. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Make an informed decision

Make the scope specific to your business.

Work through a real example from your operation and agree the handoffs, controls and support the project needs.

Old dues sit unspoken

Can you explain the balance from its original documents?

Select a partly settled example in “Old dues sit unspoken”. Ask for the invoice, allocated receipts and remaining balance to be shown together before agreeing the opening figures.

Background reading: ERPNext: outstanding invoices

Common questions

Questions Kotdwar owners ask before they call.

Can hill shopkeepers place orders by phone and have them recorded?

Yes. Staff can key an order into a phone or desktop screen while on the call. The order prints as a pick list and becomes the bill when the load is dispatched.

Can a carrier match return loads to empty trucks?

A list of pending loads and a list of trucks heading back can sit together, and the dispatcher assigns one to the other and records the freight.

What happens after I share my requirements?

We review your brief and clarify the work with you. 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.

Talk to us

Tell us what your Kotdwar 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

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements