jugaad
studio
Trading & distribution

Orders, stock, credit and dispatch in one place.

In a trading business the margin is thin enough that the cost of a lost order, an overdue payment or stock sitting in the wrong godown is the whole month's difference.

How it runs today, and what changes.

Today
  • Orders arrive on WhatsApp, phone and email, and land in different places
  • Stock across godowns is reconciled in a spreadsheet, weekly
  • Credit limits are known by one person rather than enforced
  • Dispatch status is a phone call to the driver
  • Rate lists by customer live in a file that may or may not be current
After
  • Every order in one queue the moment it arrives, whatever channel it came from
  • Live stock by godown, updated as goods move
  • Credit position visible at order entry, with approval when it is exceeded
  • Dispatch and delivery status visible without calling anyone
  • Customer-specific rates applied automatically, with a change history

What matters most here

Order capture from every channel

WhatsApp, phone, email and field sales into a single queue, so nothing depends on which person happened to receive it.

Multi-godown stock

What is where, what is reserved against an order, and what is actually available to promise a customer right now.

Credit control that holds

Outstanding and ageing visible at the point of order entry, with a real approval step when a limit is crossed rather than a conversation afterwards.

Dispatch and delivery proof

Picking, packing, challan and a delivery confirmation with a photograph or signature attached to the order.

Customer and product movement

Who is buying less than last season, which lines are not moving, which customers are drifting. Visible early enough to do something about it.

Questions people actually ask

We already use Tally. Do we need anything else?
Tally records what happened. It is not built to run what is happening right now — order queues, picking, credit checks at entry, delivery proof. Most of our trading clients keep Tally for accounts and put the operational layer beside it, connected.
Can salesmen take orders on their phones?
Yes, with catalogue, customer-specific rates, outstanding balance and last-order history in hand, and the order placed on the spot instead of written down and typed up that evening.
We sell on marketplaces too. Can that come in?
Where the marketplace offers an API, yes — orders pulled in and status pushed back so you are not reconciling portals by hand.
How do you handle schemes and discounts?
As rules in the system rather than as memory. Slab discounts, scheme quantities and customer-specific rates applied at entry, with a record of what was applied and who overrode it.
Let's talk

Tell us what wastes the most time.

Fifteen minutes is usually enough to know whether it's worth building. If it isn't, we'll say so.

No pitch deck. A 15-minute call to see if it's worth building.