Fake orders and customer bans
A COD store takes orders from anyone who fills in a form, so some of them are not real. DZBuild gives you a probability score on every order, a ban list per store, and two add-ons that slow floods down. None of them decides for you: calling the customer before you hand a parcel to a courier is still the only certain filter.
The fake-order probability score
Every order carries a number that the dashboard labels Probabilité de fausse commande in French and احتمالية طلب وهمي in Arabic. You see it in four places:
- as a coloured badge next to the customer name in the order list and in the mobile order cards, shown only when the number is above 0;
- in the order popup, next to the phone number, with the risk word and, on recent orders, the IP address the order came from;
- as a column on the Customers page, written as the word plus the number, for example
Faible (24); - on the Blacklist tab of that same page.
The scale runs from 0 to 100 and a higher number means more suspicious.
| Score | Word shown | Colour |
|---|---|---|
| 0 to 19 | Safe | green |
| 20 to 39 | Low | green |
| 40 to 59 | Medium | amber |
| 60 to 79 | High | red |
| 80 to 100 | Critical | dark red |
A 5 is therefore nothing to act on. It sits in the green band and the badge only appears because one small event was recorded once. A 60 is worth a phone call before you ship.
The number belongs to the phone number rather than to the order, so it carries what that number has done before, on your store and on the rest of DZBuild. Moving an order to cancelled or returned pushes it up, whether you do it by hand or the courier's tracking does, and so does banning the number. An order that reaches delivered pulls it back down. The details button on a customer row opens the event log behind the number, so you can see what produced it.
The score is a hint read from past order signals, not proof, and it never blocks or cancels anything on its own. When it is high, confirm by phone before shipping and cancel the order if the number is unreachable.
Banning a customer from an order
Open the order in the list and use the Ban status row of the popup:
- Click Ban.
- Choose a reason: fraud, fake orders, refusing to pay on delivery, abuse, spam, chargebacks, or other.
- Add a note if you want the reason on record.
- Set the scope with the checkbox
حظر رقم الهاتف أيضاً("ban the phone number too"). It is unticked by default, and the line under it says so: the default bans the device only. - Confirm.
That checkbox is the part that matters. Left unticked, the ban is recorded but nothing is refused at checkout: the phone number stays free and the next order goes through, from that browser or from any other. Tick the box whenever you want the person actually stopped.
Bans are per store. Banning someone on one of your stores has no effect on another store you own.
Banning from the Customers page
The Customers page in the dashboard carries the same action without the device question: the shield button on a customer row bans that customer's phone number and email address for this store. The Blacklist tab lists everyone you have banned with the reason, the ban date and an unban button, and the counter at the top of the page shows how many bans are active.
When the same person has ordered under several names or numbers, the Multiple identities column shows a warning button. Opening it lists the linked names and numbers, and Ban all identities bans each of those phone numbers in one pass.
Unbanning takes effect immediately and is written to that customer's event log.
Why a banned customer can still order
Four reasons cover the cases that reach support:
- The ban was device-only. This is the default when you ban from an order, and on its own it refuses nothing at checkout. Ban the phone number instead.
- The person changed number. A ban is matched on the phone number and the email address saved on the ban record. A number that has never ordered from you is a new customer as far as the store is concerned.
- The order came through a landing page. Landing-page forms check the phone number and the device, but not the email address, so a customer banned by email alone can still submit one. Banning the phone number closes that path.
- A shared device or IP is not enough to block. Families and internet cafés share both, so DZBuild records the match as a signal for you to read instead of rejecting the order.
A buyer who is blocked sees a message telling them the store owner blocked them and that this is not a technical fault of the site.
Limiting order floods
Limit Orders Per IP caps how many orders one visitor can place inside a window, 3 per 12 hours by default. Since 10 August 2026 the counter is keyed on the IP address and the phone number together, because Algerian mobile carriers put thousands of subscribers behind a single public IP and a pure IP counter was refusing strangers who happened to share one.
The trade-off is worth knowing: someone who submits each order with a different phone number starts a fresh counter every time. A second, looser counter still watches the IP address alone and stops it at five times your limit, never below 15 orders per window, which is what catches a flood from one connection with rotating numbers. Lowering your own limit tightens both counters.
Orders you create yourself from the dashboard are never counted.
Captcha at checkout
Captcha Protection (Pro and above) verifies fast checkout, the full checkout page and landing-page forms. On Normal, the default, real customers see nothing. High and Aggressive also reject visitors coming through a VPN, a proxy or Tor, and a genuine customer browsing with a VPN gets the same generic error as a bot does. If your orders drop right after you raise the level, put it back on Normal before looking elsewhere.
What is not available
- Filtering or blocking by traffic source. Each order shows where it came from, but you cannot ban a source or filter the list by it, and this is not planned.
- Bulk deletion of orders. Fake orders already in your list are cancelled one at a time. Bulk delete is planned, with no date.
- Automatic banning by score. Nothing bans a customer for you, however high the number climbs. Every ban starts with you clicking it.