Mobile and electronics shop software in Nepal that shows which models pay

A customer wants the black one with the larger storage. That combination is its own item, because colour and storage were set up once and every combination you buy was created from them. The line takes that variant’s own price, the bill carries your PAN and 13% VAT on the taxable lines, and stock for that exact variant drops when the invoice is approved.

Next is a dealer who buys a few units at a time and pays later. Picking them applies their dealer discount, and a banner says whether this invoice takes them past their credit limit. It does, so the old dues are settled first. Part payments are normal here: pay some of a bill and it stays open, with the balance and every payment shown on the invoice.

Then somebody comes back with a handset that has stopped charging. The warranty period is on the product, and the customer’s page lists their orders and bills, so the original bill and its date are one search away. The unit goes back to the supplier on a debit note against the supplier bill, and once approved, what you owe that supplier drops. A repair on a different handset is billed as a service line on the same invoice as a screen protector, priced and taxed, without moving any stock.

In the afternoon a new range lands. The variants are imported from a spreadsheet, not typed, the batches open as the supplier bill is approved, and Code 128 labels are printed in the shop for boxes that arrived without a usable barcode. Then purchase insights flag what nobody was watching: the rate on one accessory has jumped against its own monthly history, which is a cost spike worth a phone call.