What a workshop needs from its own system, and what an invoicing package will never give it

A workshop does not sell a product; it sells a measured job. The customer arrives with a wall or a kitchen, the workshop takes dimensions, quotes, cuts, delivers, and is paid in instalments. An invoicing package models the last step and none before it: it has no place for a quote, a board, a cutting list or an instalment. A workshop selling standard pieces off a shelf needs only an invoice; everyone else fights the shape of the tool.

Why does the quote need a number of its own?

Because the quote is the document the job gets accepted on, and it gets revised: the price starts high, the board gets thinner, the job is accepted on the second version. If that version lives in a chat thread and the invoice is raised weeks later from memory, nothing connects the accepted figure to the money that arrives.

The number has to come from the system, not the person. Assigned when the row is created, never reissued after a cancellation, it gives each job an identity the customer, the delivery note and the payment can cite. Our case study works this way: sequential numbers generated by the system, each order carrying a client, an amount, a delivery date and a status.

Can material and labour sit on the same order?

They must, because the question is not what the workshop sold but whether the job made money. Material is consumed at the saw; labour is hours, which vary per job more than the price does. A single amount per order, which is what an invoice records, answers neither half.

Only the pair tells you whether the job that took three visits was worth taking. This needs no costing module, just a place where a material expense and a labour entry attach so a per-job report can subtract. Without it, the month's profit is true and the profit per job is a guess that shapes the next quote.

What changes when the customer pays in instalments?

The balance becomes the question, and it must be derived rather than typed: a deposit with the order, a payment at delivery, sometimes a third after fitting. The workshop needs the jobs still carrying a balance, and for how long.

That works only if a payment can name the order it settles. When payments land in a cash book as income, the balance is evening arithmetic, and the customer who paid a deposit looks like one who paid nothing. In the case study a payment carries a source, a method — cash, CCP or bank transfer — and an optional link to the order. Optional is deliberate: some money arrives with no job, and forcing a link pushes the operator into inventing one. The dashboard counts money on the date it moved, not the date the row was typed.

What do you do with the offcut?

An offcut is either stock or waste, and deciding which is a policy, not a data-entry habit. A workshop that records only whole boards consumed has a material cost wrong in the direction of optimism: every job appears to have eaten a full sheet, so the quote creeps up to cover a loss that never happened.

Settle it once per material, in writing. Offcuts above a usable size go back on the rack with a location and count as stock; anything below is waste, charged to the job. Leaving it blank is not a decision: those pieces count as full consumption and never as available.

Question	An invoicing package	The workshop needs
What was agreed?	A price for a product	A job with dimensions, board and finish
What did it cost?	Nothing	Material and hours on that job
What is owed?	A customer total	A balance per job
What is left over?	Nothing	Offcuts in stock, or waste

Why is a system at the counter often the right answer?

Because the record has to be kept where the work is. The counter is a tablet beside a saw, the connection is unreliable, and the person entering the order has a customer in front of them. A web package that stalls when the network drops teaches the operator to write on paper and enter it later — and that parallel record is where the drift starts.

A system holding its own copy of the data on the machine in front of you is not a compromise; it is the shape the work has. The case study was built Arabic right-to-left as its only direction, installable as an app on the counter tablet, with a backup file and a restore. That matters more than the hosting model: the file is yours and it opens without the vendor.

What should you settle before you compare products?

Do these in order; each turns the next into a requirement.

1. Write the job down as it happens, noting where a document changes hands — that is where a number is lost.
2. Separate price from cost. For a recent job, state what it consumed in board and hours. If you cannot, that gap is the requirement.
3. Decide the offcut rule per material: a size, a place for it, who may return it to stock.
4. List the payments you accept and what each must name, and whether one attaches to a job in one step.
5. Fix the numbering before the data. Ask what happens after a cancellation, and who may create a number by hand.
6. Test the export and the restore on a clean machine, in the format your accountant accepts.
7. Only then compare products. A package that fails two of those answers shows up in a demo, not in the third month.

Where this goes wrong

• The quote stays in the chat. The accepted price is a message, the order is opened from memory, and the gap appears on delivery day.
• Payments are one lump. Income is recorded with no order attached, and the customer who is behind looks like one who just paid.
• Labour is never entered. Wages sit in monthly expenses, right for the month and useless per job.
• The offcut rule keeps everything. The rack fills with pieces nobody can find, and the stock becomes waste with extra handling.
• The report leaves as codes. Statuses and payment methods arrive as machine values, and the accountant retypes the rows.
• The backup has never been restored. Nobody knows whether it opens until the machine is gone.

What this does not cover

This treats the order as the centre of the record. It leaves out costing method — first-in-first-out against weighted average — which changes what a material cost means, not whether you can see it. It leaves out cutting optimisation, which decides how many boards a set of parts needs. It says nothing about tax rules or the legal shape of an invoice; those belong with your accountant. And it assumes one counter: several sites add a transfer question this does not settle.

We build workshop systems around the job — the quote, the board, the hours, the instalments and the offcut rule — in Arabic, on the machine at the counter, with a backup you can restore.