Customers
Every order creates or updates a customer record. The Customers page gives you a searchable list, a fraud score that flags risky buyers, a linked-identity view that ties one buyer's aliases together, and a blacklist tab for buyers you don't want to ship to again.
A staff member needs the customers.view permission to reach this page at all — see Team & roles. You don't have to come here to check risk, though: the same fraud score shows up in the order preview on the Orders page.
Video
The customer list
Open Dashboard → Customers at /dashboard/customers. The table columns are:
- Customer (name)
- Phone
- Location (wilaya / commune)
- Orders
- Total purchases
- Identity — a badge that opens the linked-identities modal, shown only when the buyer has more than one alias
- Fraud score badge —
safe/low/medium/high/critical - Actions
The page has two tabs:
| Tab | What it shows |
|---|---|
| All customers | The full list, default view. |
| Blacklist | Customers you've banned — orders from these phones are blocked. |
There are no filters. You get a search box, a rows-per-page selector (10 / 20 / 50, default 20) and pagination. The list is always ordered newest-customer-first and cannot be sorted by spend, orders or date.
Search matches first name, last name and phone, and additionally matches an exact IP address or an order number (full or prefix) from that customer's orders — handy for tracing a fraudulent order back to the buyer. It does not match email.
A brand-new customer can take up to half a minute to appear in the list.
Where customer records come from
Every customer record is created automatically the first time an order is written for that phone number — from the storefront, a landing page, a manual dashboard order, an abandoned-cart conversion, or the API. A record is identified by its phone number and belongs to a single store, so the same buyer in two of your stores is two separate records.
Buyers have no accounts on DZBuild storefronts; they look up an order anonymously via the Track order page. There is no customer CSV import.
The fraud score
Every customer carries a badge — safe, low, medium, high or critical — summarising their delivery history.
What pushes the score up: cancelled orders, returned orders, refused deliveries, chargebacks, and being banned by a store. What brings it back down: successfully delivered orders, and being unbanned. Having several names or phone numbers tied to the same buyer also raises it, and a customer inherits the highest score of any identity linked to them.
The exact weighting behind the number is deliberately not published — publishing it would just tell fraudsters how to stay under the badge.
The score updates as orders flow in. A high or critical badge is your cue to check the order before confirming.
What you can open from a row
There is no per-customer page. From a row you can open two modals, plus Ban / Unban:
- Fraud details — the score plus a breakdown of which events produced it.
- Linked identities — other names, phones and emails tied to the same buyer.
- Ban / Unban.
To see a customer's orders, search their phone — or an order number — on the Orders page. There is no per-customer notes field; the only note you can leave is the reason attached to a ban.
Linked identities
The Identity badge appears on a row when DZBuild has tied more than one alias to the same buyer. Open it and you get a table of the aliases: name, phone, email, link method, first seen, and order count — plus a one-click ban all linked identities action.
Linking is automatic and runs in the background, so it can lag a few seconds behind a brand-new order. DZBuild only ties two aliases together on a strong signal that they are the same person — a shared address or a shared internet connection is never enough on its own, precisely to avoid flagging unrelated buyers.
The Blacklist tab
Columns: Customer, Phone, Reason, Fraud score, Ban date, Actions. The ban date, the reason you picked and the free-text note are all recorded, so the tab doubles as an audit trail of who banned whom and why. Unban from the row's action button.
Banning a customer
Click Ban on the customer's row. The dialog asks for a reason (dropdown) plus an optional free-text note; both are shown back on the Blacklist row. Once banned:
- New orders from that phone number are rejected at the storefront checkout and on landing pages.
- The customer's row moves to the Blacklist tab.
- Existing orders are not changed. Cancel them manually if needed.
Three things to know:
- Bans are per-store. Banning someone in one of your stores does not affect your other stores.
- The phone number is what actually blocks. The banned email address is checked too, but only on forms that ask for one: the landing-page checkout never collects an email, so on that surface the phone number does all the work. Device or network matches are advisory only, and on their own they never block a buyer.
- Not every way an order can be created runs the check. A banned buyer can still turn up on your orders list, which is why banned customers keep a red badge on their order rows. Read that badge before you confirm.
To reverse, open the Blacklist tab and click Unban, or use the Unban button that replaces Ban on the customer's row.
Segmentation
DZBuild has no segment builder, and no VIP or loyalty tier: nothing in the dashboard groups customers by spend or awards them a badge for it. The groupings below are worth tracking, but you build them outside the dashboard by exporting the customers CSV page by page and slicing it in a spreadsheet. Note the list is always sorted newest-customer-first, cannot be sorted by spend, and does not record a last-order date at all, so an "at risk" grouping has to come from the Orders page instead.
- Best spenders. Sort the exported total purchases column and pick your own threshold. Worth special handling and early-access offers.
- Repeat — ≥ 2 orders. Already trust you; cheapest to win again.
- At risk — last order ≥ 90 days ago. Win-back campaign target.
- One-and-done — exactly 1 order. Test if your follow-up brings them back.
- High fraud risk —
highorcriticalscore. Confirm by phone or skip COD.
Bulk export
Click Export CSV to download the customers currently displayed on the page. This is a per-page export, not a whole-list export, so with the default 20 rows per page you get 20 customers. Raise the rows-per-page selector to 50 and export page by page for a full list.
Columns: first name, last name, email, phone, wilaya, commune, address, orders, total purchases.
The search box narrows the export; there are no other filters. Use the file for SMS campaigns, mailing lists, or to import into another CRM.
Customer data is regulated under Algerian privacy law and DZBuild's terms. Don't share or sell the list. Customers can request deletion.
Working with the API
If you need programmatic access, see the Customers API. Common uses:
- Sync customers to a third-party CRM.
- Build a custom segmentation tool.
- Trigger SMS / email automations on new customers.
Tips
- Check the fraud score before confirming an order from a new customer.
criticalmeans call before spending COD shipping. - The only note you can leave is on a ban. The ban dialog has a reason dropdown plus a free-text note, and both show on the Blacklist row. There is no general per-customer notes field, so flags for complainers, no-shows and VIPs have to live in your own spreadsheet.
- Bulk-export your best spenders monthly and run a separate SMS campaign for them.
- Win-back is yours to run. The dashboard has no win-back tool and no last-order date on the customer row, so build the list from the Orders page and call or SMS from there.
- Unban with intent. If you ban for fake orders, don't unban without a real reason.
- Keep the Blacklist tight. Banning everyone who returns once turns into a customer-service bottleneck.