Order booking on a phone
A booker takes orders in the bazaar against live stock and the party's real balance. If the signal drops, the orders queue on the phone and post themselves when it comes back.
Bookers take orders in the market on a phone, the office builds the load sheet that night, and a van goes out in the morning. Codipy POS runs the whole loop — including the part where the money comes back.
Distribution is not retail with bigger quantities. The customer is not standing in front of you: an order is booked today, loaded tonight, supplied tomorrow and paid for a fortnight later, and every one of those four steps is a place where the number can change. Most businesses close that gap with phone calls, a WhatsApp group and a recovery register that only one person understands.
Codipy POS makes the loop the system. Bookers take orders on a phone against real stock and real party balances. The office turns the day's orders into a supply run. The van goes out on a load sheet, delivers against challans, and the invoices follow. Recovery then works from the same party ledgers rather than a separate book — which is the only way the money side ever agrees with the goods side.
Choose this business type during setup and these are the modules Codipy switches on for you.
A booker takes orders in the bazaar against live stock and the party's real balance. If the signal drops, the orders queue on the phone and post themselves when it comes back.
Plan which booker covers which market on which day, and see who was actually covered. Coverage gaps are visible instead of anecdotal.
The day's orders become a load sheet for the van. What went out is recorded, so what comes back unsold is a figure rather than a dispute.
Goods leave against a challan and are billed afterwards. Stock moves when the van is loaded, not when somebody gets to the paperwork.
Trade prices per carton, retail per piece, one stock figure underneath. Unit conversions are part of the product rather than a spreadsheet.
Every shop you supply has a ledger. The recovery screen orders them oldest first with today's call list on top, and reminders go over WhatsApp from that same screen.

Bookers work their route on the phone, taking orders against live stock and each party's balance.
The day's orders become a supply run. Short items are visible before the van is loaded, not after it has left.
Load sheet printed, van loaded against it. What is on the sheet is what is on the vehicle.
Delivery against challans, invoices raised, party balances updated as the round completes.
Recovery. Oldest balances first, WhatsApp reminders from the list, and a party ledger sent when a figure is questioned.
It helps, but it is not required. The app works against the shop's server when it can reach it and queues orders on the phone when it cannot, then sends them when the signal returns. A booker in a bazaar needs the app to open, not an explanation.
Through a short shop code issued with your licence. The shop's PC reports its current address every few minutes, so the code keeps working even if the address changes.
Yes. Routes are planned per booker per day, and coverage is reported against the plan rather than against what was said on the phone.
No. Delivery challans exist for exactly that: stock moves when the van is loaded, and the invoice is raised afterwards against the challan.
From the party ledgers themselves. The recovery screen lists parties by how old the balance is, with today's call list at the top and a WhatsApp reminder available from the same row.
Same installer, a different set of modules.