Product
Where is the money from my delivered orders?
In COD, a delivered order is not a paid order: the customer pays the driver, the carrier collects, then the carrier pays you — sometimes weeks later, sometimes short. Nawras moves money along its own axis, separate from the parcel's status, with eight distinct states and a table that refuses impossible transitions. The customer paid, the transfer landed, the amount is disputed, the return has been refunded: these are four different situations, and they never carry the same name.
The parcel and the money move along two separate axes
A single "paid: yes / no" field forces you to pick which lie you prefer: either it follows the parcel and gets the money wrong, or it follows the money and gets the parcel wrong. Nawras has no such field. The parcel status says where the goods are, the financial status says where the money is, and they do not have to agree. An order delivered three weeks ago and never paid out therefore has nowhere to hide.
The parcel axis
Created, confirmed, packed, shipped, delivered, returned. It answers "where are the goods?" and says nothing about what you have collected.
The money axis
To collect, collected, paid out, disputed, refunded. It answers "where is the money?" and moves at its own pace: a customer can pay before the parcel leaves, and a parcel can be delivered weeks before the transfer arrives.
The eight states of money, and what each one means
To collect
The order exists, nothing has been collected. It is the starting state, and it says nothing about the parcel: an order created this morning and an order delivered last night whose collection has not been reported yet carry the same state.
Collected, awaiting payout
The customer has paid. The money exists, but it is not with you: it is with the carrier, or in the driver's pocket. This is the most misunderstood state in COD, and confusing it with the next one means believing you have the money.
Paid to merchant
The carrier's transfer has landed and you have verified it. This is the only state that means "the money is in my account". A single action leads there, and it is manual: nobody decides on your behalf that you have been paid.
Carrier dispute
You and the carrier disagree on an amount. The money is neither lost nor earned, it is suspended — and the order remembers the exact state it came from, so it can return to it untouched.
Refund to issue
The customer paid and the sale has been undone: you owe them money. That is a debt, not a loss, and it stays visible until it is settled.
Refund completed
You gave the money back. Terminal state: no transition leaves it, and nothing that happens afterwards can reopen it.
Cancelled, not collected
The sale did not happen and nothing had been collected, so there is nothing to refund. Showing "refund pending" on an order that was never paid would be an imaginary debt — and it would end up in your totals.
Written off
The money is not coming back, and you record that. Terminal state, deliberately kept apart from a refund: giving money back to a customer and never recovering it are not the same loss.
These eight states do not follow one another in any order: a table declares, once and for all, which transitions are possible and refuses the rest. "Refund completed" and "written off" have no exit at all.
From the customer to your account, in three moments that never merge
Between the customer's hand and your bank account, the money changes holder twice. Each of those moments has its own date, amount and state. Crushing them into a single figure called "revenue" is exactly what makes a merchant plan purchases with money they do not have yet.
1
The customer pays
On delivery, in person, by transfer or online: Nawras no longer assumes payment arrives at the moment the parcel does. The collected amount is compared with what was actually handed over — a partially refused order is not collected at the amount on the order form.
2
The carrier pays you
It wires you a sum after withholding its fees, often covering several orders at once. That transfer, and nothing else, is what moves an order from "collected" to "paid out".
3
You verify
Payouts are ticked off one order at a time. You can attach the transfer reference, which later lets you find everything a single transfer covered.
The payout amount is not typed, it is computed
It used to be typed, and a typo was final: 1,500 instead of 150 saved without a word, and the only correction path brought the same wrong figure back. The free-text field was not paired with a warning, it was removed. Nawras shows what the payout must be worth — collected minus the carrier fee — recomputes it as it saves, and refuses if the two do not agree to the cent.
A missing fee blocks the payout, it is not worth zero
As long as the carrier's fee is unknown, the expected payout cannot be computed: Nawras says so and offers to enter the fee. Replacing it with zero would produce a higher amount, credible and wrong — the one you would confirm without arguing, before discovering the gap days later.
The gap between expected and collected is a figure, not a feeling
On every order, the difference between what should have come in and what did is shown as it is. It is not treated as an error to be silently corrected: a customer paying 150 out of 199 MAD is a fact, and you are the one who decides whether it becomes a dispute.
When it goes wrong — and it does
In COD, refusals, returns and disputes are not exceptions: they are ordinary outcomes of the trade. What matters is not hiding them, it is that each one has a named exit — and that none of them leaves an order stuck in a state nobody knows what to do with.
An amount is disputed
You open a dispute with the carrier. The order holds on to the exact state it came from: this is not a disguised cancellation, it is a parenthesis.
The dispute is settled in your favour
The previous state is restored and the normal cycle resumes: an order that was collected becomes collected again, and can be paid out. A dispute you win leaves no scar in your totals.
The dispute is abandoned
The money is not coming back: the order is written off. That is terminal, and deliberately so — a loss you can reopen is not a loss, it is a figure that will move again.
The parcel comes back after being paid
Rare, but real: collected, then refused at the door. The sale is undone and you owe the money back, including when the carrier had already paid you. The movement reverses, it is not erased.
The parcel comes back without having been paid
This is by far the most common case, and it creates no debt: nothing was collected, so there is nothing to refund. The money axis closes, and the goods travel their own way back to stock.
What you actually earn
Delivered revenue is the easy figure: it is what customers paid for what they kept. Margin is the hard one, because it depends on two things no tool can guess for you — what your goods cost, and what your business costs every month. Nawras asks you for both, and does not fill the gaps on its own.
Five expense categories, monthly or one-off
- Rent
- Salaries
- Subscriptions
- Advertising
- Other
Raising the rent in June does not rewrite March's margin
Changing a recurring expense does not overwrite its past: the old value closes on the previous month, the new one starts on the month you name. Every past month keeps what it actually cost. A tool that applies the new amount everywhere makes your old months better or worse in one click, without asking.
An expense that ends is bounded, not deleted
You give its last month. The months it ran stay billed, because they happened. Erasing the line would make your past six months look more profitable than they were.
A month's total is recomputed every time it is read
It is frozen nowhere. Fixing an expense entered wrong updates every month concerned, with nothing to rerun and no screen left holding the old figure.
A line with no purchase price leaves the calculation, it does not enter it as zero
If you have not entered what an item costs you, it is not counted as free: it is set aside. A missing cost treated as zero turns the whole selling price into profit — the one error in this table that makes the figure prettier, and therefore the one nobody goes looking for.
Why your figures do not move on their own
Your carrier tells you twice that the parcel was delivered. That is not a fault on their side: it is a guarantee — better to say it twice than to stay silent once. What should not be normal is the second announcement changing your accounts. It did. The same delivery reached us through three paths, and depending on which one carried it, it produced two different money outcomes — one of them cancelling a refund that had already been issued. Nothing turned red: both paths were doing exactly what they had been asked to do, each on its own side.
The rule left the pipes and moved into the model
"Is this transition allowed?" now has a single answer, written in a single place, and everything that touches money goes through it — whatever path the information arrived by. A repeated announcement no longer does anything, because it no longer has the right to.
What is terminal really is
"Refund completed" and "written off" have no exit. An event arriving later does not reopen them, does not route around them, and does not write a quiet correction next to them.
One authority writes the money
The amounts you read in analytics are read, never recomputed: they come from here. Two independent calculations of the same amount always end up diverging, and the day they do, nobody knows which one to believe.
The questions we get about the money
My carrier sends me one lump sum for forty orders. How do I know which one is paid?
Payouts are ticked off one order at a time, never in bulk. For each one, Nawras already shows the expected amount — what the customer paid, minus the carrier's fee — and you confirm. You can attach the transfer reference, which later lets you find everything that transfer covered. Until an order is ticked off it stays "collected, awaiting payout" and does not count towards what you have actually received.
Does Nawras touch my money?
No, at no point. The customer pays your carrier, your carrier wires you directly, and that sum never passes through any account of ours. Nawras records what happens — what was collected, what was paid out, what is missing. We have neither the means nor the right to move a single dirham of it.
The customer paid but the transfer has not arrived. What figure do I have?
You have two, and they are shown separately: what is collected but not yet paid out, and what has landed in your account. The first is money that exists and that you cannot use; the second is money you can spend. A screen that adds them gives you a third figure, which matches nothing.
How do I enter my rent and salaries without distorting past months?
You enter them once, as monthly. The day the amount changes, you say from which month: the old value closes on the month before, the new one takes over. Months already gone keep what they actually cost, so your March margin does not move because the rent went up in June. An expense that ends is bounded to its last date instead of being erased, for the same reason.
A parcel came back. What happens on the money side?
It all depends on one question: had the customer paid? If they had not — by far the most common case — there is nothing to refund, and the money axis closes on "cancelled, not collected". If they had, you owe them the amount: the order moves to "refund to issue", even if the carrier had already paid you. In both cases the goods travel their own way back, which does not depend on the money.
Ready to take back control?
Create your workspace in 2 minutes and see the impact in the first week.
Zero dirhams. Zero commitment. Cancel in one click.
