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.

ℹ️ Info — Permission-gated

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.

Open Dashboard → Customers at /dashboard/customers. The table columns are:

The page has two tabs:

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.

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.

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.

There is no per-customer page. From a row you can open two modals, plus 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.

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.

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.

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:

Two things to know:

To reverse, open the Blacklist tab and click Unban, or use the Unban button that replaces Ban on the customer's row.

DZBuild has no segment builder. The segments below are worth tracking, but you have to build them outside the dashboard — export the customers CSV page by page and slice 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" segment has to come from the Orders page instead.

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.

⚠️ Warning

Customer data is regulated under Algerian privacy law and DZBuild's terms. Don't share or sell the list. Customers can request deletion.

If you need programmatic access, see the Customers API. Common uses: