Check. Review. Learn.

Example events below are made up. Your store makes the final purchase decision.

1. 1

   A customer checks out.

   Your server sends protected household IDs and the signals it has. Fair Drop returns a result.

   Continue
2. 2

   Another attempt looks connected.

   A matching address and apartment suggests a repeat purchase. A shared IP alone does not prove that.

   Review
3. 3

   Your team checks the evidence.

   Record whether the flag was right or mistaken. A review note does not automatically release stock or bypass a purchase limit.

   What if we made a mistake?

   The shopper contacts your store. Verify the details, then use your store’s approved recovery process. Never promise stock that is no longer available.

4. 4

   Learn before the next drop.

   A drop report shows recorded reasons and reviewed outcomes. Replay compares supported routing changes without changing live rules.

   Test before changing

If a check is unavailable

Your developer must set a timeout and an agreed fallback: pause checkout or continue with your store’s own limits. A waiting page alone cannot stop someone from calling an unprotected checkout endpoint.