Skip to content
Sajilo Stores

Every order from the route, in your books the same day

Your salesmen take orders on a phone, signal or no signal. The order syncs up, stock drops, you confirm it from the office, and it posts to the party's khata.

Request a demoSign in
Hari Kirana Store

Lakeside beat, Pokhara

Today

Opening balanceRs 42,800
Order 1184, 14 linesRs 18,650
Payment, cash−Rs 25,000
Return, 2 cartons−Rs 1,240
Running balanceRs 35,210
Works offline
Orders queue on the device and push when signal returns
Stock per store
One catalogue, separate quantities per outlet
Party & supplier khata
Append-only ledgers on both sides of the business
Roles that scope
Store-scoped staff only ever see their own stores

Everything between the visit and the payment

Everything a distributor needs between a salesman's visit and a paid invoice. Nothing built for a shop counter.

Order-taking on the phone

Browse products with cached stock, build an order against a party, and submit. Stock is reserved the moment it reaches the cloud.

Offline-first sync

Every order is written locally first and queued in an outbox. Retries with backoff survive app restarts, so an order is never lost.

Stock per store

One tenant-wide catalog, separate quantities per outlet. Taking an order decrements the fulfilling store; rejecting it puts the stock back.

Admin order review

A live pending feed. Confirm, partial-confirm or reject. Confirmed orders post to the party's ledger automatically.

Party & supplier khata

Append-only ledgers: credit sales, payments and returns for every shop; a proper accounts-payable subledger for every supplier.

Returns that reconcile

Customers return items; resellable stock goes back, damaged is written off, and a credit note lands on the khata, approved like an order.

From a shop visit to a settled invoice

Four moves. The salesman never waits on a network, and you never chase a missing order.

A store counter with its terminal, tablet and stock, and the office dashboard behind it
  1. 1

    Salesman visits the shop

    Opens the app, picks the shop from today's route and takes the order from the catalogue on the phone, signal or no signal.

  2. 2

    Order syncs up

    The moment there's signal, the phone sends it. Stock is held for it straight away, and if something has run out you're told, not left guessing.

    Works with no signal
  3. 3

    Office confirms

    It appears in your pending list. Confirm it and the amount goes onto the shop's khata.

  4. 4

    Cashier settles

    Cash, Fonepay, cheque or bank transfer is written against the order. The order closes once it's fully paid.

Every way a shop pays, on one khata

Credit, cash, Fonepay, cheque or bank transfer. Each one lands on the shop's khata with the rule that goes with it, so the balance is always the real one.

  • On credit

    Unpaid orders go straight onto the shop's khata, inside the limit you set for it.

    Gupta General Store
    x

    Rs 31,050 of a Rs 50,000 limit

    Over the limit, new orders wait until the shop pays.

  • Cash

    Collected at the shop or the counter and logged against the order.

  • Fonepay

    Counts as paid only once Fonepay confirms the payment.

  • Cheque

    Held until it clears, and flagged on the day it can be banked.

  • Bank transfer

    Recorded with its reference, so it matches your statement.

One price, every seat

No per-user fees. Pick a term. The longer you commit, the less you pay. Custom periods are set up with our team.

Basic

One store Order taking & admin review Party khata & payments Salesman, cashier & admin roles

Rs 12,000/ year

  • Rs 40,000 / 5 years
  • Rs 80,000 / 10 years
One store
Order taking & admin review
Party khata & payments
Salesman, cashier & admin roles
Request a demo

Growth

Everything in Basic Upto 2 Stores 200 Daily orders

Rs 20,000/ year

  • Rs 70,000 / 5 years
  • Rs 1,50,000 / 10 years
One store
Order taking & admin review
Party khata & payments
Salesman, cashier & admin roles
Request a demo

What people ask before they switch

Yes. Products, stock hints and parties are stored on the device. Orders are written locally and queued; the moment a connection returns they sync in dependency order with retry and backoff.