CE Phoenix Cart Forum

I have made an admin interface that allows shopowner to set up "Rules" for creating a "Fraud Score" which will alert shopowner to things he/she needs to know about.

Admin Page


Editing/Adding Rules


And then on the Orders Page

What other sorts of Rules could be set in place ?
Any ideas/feedback would be golden.

Note that most Rules are flexible from shopowner to shopowner, so for example;

Large Order for one shopowner might mean > 1000
For another it might mean > 100
and so on.

Some rules are inflexible (eg address mismatch) - if your buyers address mismatches...well that's a problem for all shopowners equally.

Some more testing this morning lead to a bottleneck in the code, where the shopowner would have had to actually change code. I don't like that. So, the system has been refactored for "no code".


The two interesting bits in this particular page

1. The new Column showing the "Watchdog" score
2. The bit at the bottom of the right hand column showing how the "Watchdog" score was computed

Watchdog score;
170

Made up of;
High Risk Billing Country 50
Throwaway Email 45
Mismatched Address 75

Also notice the different coloured Watchdog scores. That's a nice indicator.

Obviously this system is NOT designed to prevent fraud, it is designed to make you, shopowner, aware of discrepancies that you might like to checkout before processing the order.


This whole system is done with NO CORE CODE CHANGES.
That's the beauty of Phoenix shining through.

I will put this into the July Code Drops - later on in the month after it's been tested a bit more.

I'm all ears for any other "Rules" anyone can think of.
Let's make this system the best it can be.

maybe some "Rules" for black list customers
eg. some customer order by phone and they never pay the invoice (Some phone orders result in unpaid invoices).

Perhaps a "Time" Rule might be of use to some shopowners.
EG, any orders that come in between 2am and 4am?

Perhaps a "First Order by this Customer" Rule ?

We now have a "First Time Customer" rule, see the two latest orders here;


Order ID 21 has a Watchdog score of 15 (which is what I set for a "first time customer").
Order ID 22 has a Watchdog of 0 (as this is the second order of the Customer).

Obviously this customer triggered no other rules.

We now have an Order Time module which might be useful for some shopowners?

Rule Set Up


Shown Rule


Best of all, it's coded in such a way that these Rules can run as many times as is needed;

(eg)
Order Time: 11:00 - 14:00 - score 20
Order Time: 23:00 - 23:45 - score 30
and so on

Or you could have (eg)
"really dodgy countries" - score 100
"ok but be aware countries" - score 50
and so on

Omar_one wrote: ↑Thu Jul 10, 2025 4:29 pm maybe some "Rules" for black list customers
eg. some customer order by phone and they never pay the invoice (Some phone orders result in unpaid invoices).

When someone orders by phone, what is the process that you take to actually create an order (ie, so that the order is in adin/orders.php and you can view an invoice etc as normal).

I'm -guessing- that you are on the phone with "Mr XYZ", you log in as him ... performing a checkout, choosing some sort of "pay in the future" payment module (a bit like cash on delivery, or check). Then you end up waiting for payment which sometimes never arrive. Which leaves you;

1. having wasted time on a phone call Mr XYZ
2. not knowing if this order is going to be paid
3. more than likely wasting time chasing for payment

Is that how it works?

Let's say that happens one time.
And then Mr XYZ does the same again <--- is this what you want to stop?

burt wrote: ↑Mon Jul 14, 2025 3:21 pm Let's say that happens one time.
And then Mr XYZ does the same again <--- is this what you want to stop?

Yes. this idea more rules.


Order Handling in Our Shop:
1- Occasionally, customers place orders over the phone.( we create an order in the admin side) In some cases, we dispatch these orders before receiving payment.
2- To manage this risk, we’ve added a new column to the customers table( or orders table not sure right now ) to flag such cases. If a customer has previously failed to pay for an order, they are marked as "Not Trusted". This status also appears on the orders page.
3-If the same customer attempts to order by phone again, we can quickly identify them. Since collecting payment from them is likely to be difficult, we no longer ship orders to such customers unless payment is made in advance.

Omar_one wrote: ↑Mon Jul 14, 2025 7:13 pm Order Handling in Our Shop:
1- Occasionally, customers place orders over the phone.( we create an order in the admin side)

The simplest way for you would be to use javascript to popup a "this customer doesn't pay" message when you select the customer in whatever process/addon you have for making an order in admin side.

This watchdog won't work in this case.