Make your business rules easier to apply consistently and give staff useful context when reviewing an order decision or a customer exception.
Purpose
Some products need ordering policies that reflect the way your business operates. Order Guard is for teams that want to make those policies clearer within WHMCS, including how legitimate exceptions are considered and how staff understand an order decision.
Typical workflow
Your team defines a policy for a selected product and identifies customers who should be treated differently. It reviews representative situations, including valid orders and exceptions, then evaluates whether the resulting customer journey reflects the intended policy.
Role in WHMCS
Order Guard adds a business-policy layer to the ordering journey. It sits alongside your existing WHMCS billing, customer-management and fraud-screening arrangements, giving staff context for the decisions made by the configured rules.
Scope and boundaries
An ordering rule is not a guarantee that an order is legitimate or fraudulent. Payment verification and third-party screening remain separate responsibilities. Administrative and API ordering routes, external data sources and additional review processes should be checked against the supplied release.
Key Features
Turn business ordering policies into understandable rules, with explicit exceptions and useful information for your team.
Product & Client Rules — Apply agreed rules to selected products, product groups or client groups. Distinguish new visitors from existing customers where that is relevant to your ordering policy.
Configurable Conditions — Combine supported criteria such as IP/CIDR ranges, customer fields and product choices. If country or reputation checks are required, agree the data source and matching behaviour before implementation.
Allowlists & Exceptions — Give administrators a clear way to exempt approved customers or addresses. Define rule priority and exception precedence so that an intended exception behaves predictably.
Checkout Messages — Return helpful customer-facing validation messages without exposing internal rules or sensitive security details. Agree the supported checkout routes and any additional review workflow.
Decision Logs — Show staff which rule matched, when it ran and the relevant order context. Include searchable decision logs, role-based access and an agreed retention period.
Reporting Mode — Provide a reporting mode to review likely matches before blocking orders. Test both matching and legitimate checkout scenarios against the agreed products and payment flow.
Rule scope
Identify products, client groups and checkout routes covered by the first release.
Matching and priority
Define supported conditions, allowlists, rule ordering and customer-facing messages.
Reporting and enforcement
Agree reporting-only behaviour, enforcement settings, staff roles and log retention.
Additional checks
Third-party fraud, country, proxy or IP-reputation services require a separately confirmed integration and may carry provider charges.
✓ Compatible with WHMCS v9.1
Your ordering policy
Bring examples of orders you want to allow or decline, including legitimate exceptions.
Compatibility review
Confirm the WHMCS/PHP versions, checkout template and any existing fraud or order-management addons.
Acceptance checks
Use representative staging orders to verify rule priority, account exceptions and the checkout response before enforcement.
From Setup to Daily Use
A clear path from installation to a workflow that fits your business.
01
Map your ordering rules
Agree the products, conditions, exceptions and checkout routes to cover.
02
Review matches in staging
Check representative orders in reporting mode and refine the decisions.
03
Enable the agreed controls
Confirm customer messages, administrator guidance and the deployment plan.
12 months of updates & support
Your purchase includes the initial support and update period. Continued use of the downloaded version is covered by its licence.
Optional $15 annual renewal
Renew access to updates and support after your first year when you need it.
Technical refund policy
Read the eligibility and support process before purchase.
It implements the agreed ordering rules. Payment verification, identity checks and any third-party fraud screening remain separate parts of your workflow.
Can we test rules without blocking customers?+
A reporting mode can be included so staff can review the decisions a rule would produce before enforcement is enabled.
Will it apply to admin and API orders?+
Those routes must be explicitly included in the project scope. A client-area checkout rule does not automatically cover every administrative or external ordering route.
Is it ready to download?+
Order Guard is available as a ready-to-install standard module. Confirm the release requirements and delivery details before purchase; request Custom Development for additional rules or integrations.