IMEI and serial tracking
Each unit is entered by its IMEI or serial when received and picked by it when sold. The invoice carries it, so "which phone was this" is a search, not an argument.
Every handset tracked by its IMEI, every warranty on record, every repair on a job card. When a customer comes back nine months later, the answer is on the screen instead of in somebody's memory.
A mobile shop sells the same model fifty times, but never the same phone twice. The difference matters the day a customer returns with a fault: which unit did he buy, when, at what price, and is it still under warranty? A till that records "Redmi 13C × 1" cannot answer any of that, so the shop answers from a register, a photograph of a box, or a guess — and one of those guesses eventually costs a replacement handset.
Codipy POS records the unit, not just the model. The IMEI goes in when the stock arrives and leaves with the sale, warranty months are attached to the product, and repairs live on job cards with the parts fitted against them. Large purchases can go out on instalments with the plan tracked to the rupee, which is how most of the market actually buys a phone.
Choose this business type during setup and these are the modules Codipy switches on for you.
Each unit is entered by its IMEI or serial when received and picked by it when sold. The invoice carries it, so "which phone was this" is a search, not an argument.
Warranty months live on the product and start from the date of sale. Pull up the invoice and the answer is immediate — no counting back from a date somebody wrote on a box.
Item in, fault noted, parts fitted against the job, collected and billed later. Parts consumed come out of stock properly rather than disappearing into a drawer.
Sell a handset on a plan, record what was paid up front, and track the remaining instalments per customer. The recovery screen shows who is behind without you keeping a separate notebook.
Cables, glass protectors and covers bill by barcode at the same counter, so a two-hundred-rupee sale takes the same five seconds as a fifty-thousand-rupee one.
Goods can leave before the invoice is written, then be billed against the challan. Useful when a repaired set or a bulk order goes out ahead of the paperwork.

Purchase → New Purchase, then each handset by IMEI. Warranty months come from the product, so they need setting once, not per unit.
Pick the model, pick the IMEI from what you actually hold, take payment — cash, card, split, or an instalment plan with a down payment.
Open a job card with the fault and the customer. Fit parts to the job as you work; they leave stock at that moment, not at billing time.
Search the IMEI. The invoice, the date and the warranty status are on one screen, which usually ends the conversation in your favour or theirs, but quickly.
Day Close: cash, card, credit, instalments collected, and profit per line so you know whether the accessories or the handsets paid for the day.
Yes. The IMEI is stored against the unit and printed on the invoice, so searching it brings back the sale, the date, the price and the warranty position.
No. Serial tracking is set per product, so handsets are tracked by unit while cables and covers are ordinary stock that bills by barcode.
The sale records the down payment and the plan. Each later payment posts against the customer's balance, and the recovery screen lists who is behind — the same screen used for ordinary credit, so there is only one place to look.
That is what job cards are for. The set is booked in with its fault, parts are fitted against the job as they are used, and the bill is raised when the customer collects.
No. Everything runs on your own PC and network. Internet is only used for the optional extras — WhatsApp, FBR invoicing, backups and the phone app.
Same installer, a different set of modules.