Take a sale at the till
Scan, take payment, print. The full Point of Sale flow, the payment buttons and the keyboard shortcuts that actually exist.
7 min read
How a plan is created, how the schedule is built, and how to take each payment as it falls due.
5 min readUpdated
This is the single thing people get stuck on, and the screen says it out loud. A plan is created when a sale is saved with instalments switched on. It cannot be started from the Instalments screen, and changing one means changing the sale behind it.
So there is no Add button here. If the list is empty, no sale has been saved with instalments on yet.
Open a plan from the list with View Details. The top shows Customer, Started, Months, Price, Additional amount, Total amount, Down payment, Paid so far and Still owing, with a link to Open the invoice.
Schedule is one row per payment and the date it falls due. Each row is Paid, Not paid or Overdue, and Overdue is worked out from the date rather than stored.
The first instalment carries any odd amount left over, so the schedule adds up to the total exactly. That is why row one is sometimes a few naira different from the rest.
To reverse one, use the row action in Payments taken. The confirmation says the instalment goes back to unpaid and the invoice behind it is owed that amount again.
Reports, then Instalment report. Filter by Show, which offers All plans, Still owing, Overdue and Fully paid, and by a due date range. It totals Plans, Total on plan, Paid, Still owing, Overdue and Plans overdue, and exports to CSV.
Scan, take payment, print. The full Point of Sale flow, the payment buttons and the keyboard shortcuts that actually exist.
7 min read
Raise a quotation, send it, and turn it into a sale or a purchase when the customer agrees.
4 min read
A sale return refunds and restocks. An exchange does both halves on one document. Here is which to reach for.
6 min read