In this video, you'll see how improved field visibility and smarter AI guidance help you build rules using supported system data, reduce errors, and ensure compliance rules can be accurately applied and enforced.
SOP: Create and Validate AI Compliance Rules in Point of Sale Settings
Objective
Use the AI Compliance tab to review available fields, build enforceable compliance rules, and validate them with AI Optimize before saving. This SOP helps prevent unsupported rule creation, reduces setup errors, and ensures compliance rules can actually be enforced.
Key Steps
1. Open the AI Compliance tab in Point of Sale settings 0:01
Navigate to your Point of Sale system.
Open the Settings section.
Select the AI Compliance tab.
Confirm you are in the correct area before creating or editing compliance rules.
2. Review the field reference panel before building rules 0:15
Locate the field reference panel on the AI Compliance screen.
Review the full list of available fields shown in the panel.
Use the field descriptions to understand what each field means and how it can be used.
Verify that the fields you want to use are supported before writing a rule.
3. Use the field list to confirm rule feasibility 0:25
Check whether the information you want to use is actually available in the system.
Use the field descriptions to determine whether a rule can be validated.
Avoid drafting rules based on unsupported or unclear data points.
Confirm the system can support the rule before moving forward.
4. Search available fields to find relevant data 0:38
Use the search function in the available fields panel.
Enter a keyword such as tax to filter the list.
Review the matching fields returned by the search.
Select the field that best fits the compliance rule you want to create.
5. Build compliance rules only from supported fields 0:56
Create your compliance rule using only fields shown in the available fields panel.
Double-check that each rule condition references a supported field.
If a field is not listed, do not use it in the rule.
This helps ensure the rule can be validated and enforced by the system.
6. Run AI Optimize to validate the rule 1:09
After drafting the rule, click AI Optimize.
Let the system review the rule for supported field usage.
Confirm that AI Optimize only generates rules that can be enforced.
Use the output to refine the rule before saving.
7. Correct unsupported rule language when prompted 1:23
If you enter a condition the system does not recognize, expect the system to stop the rule from being created.
Review the message explaining that the field is not available.
Remove or replace unsupported language with a valid field reference.
Re-run AI Optimize after making changes.
8. Review AI feedback and accept only valid rules 1:33
If AI Optimize flags a rule such as one referencing unsupported criteria, read the feedback carefully.
Do not force the rule through if the system says there is no matching field.
Edit the rule so it references only available fields.
Continue only after the rule is valid.
9. Accept validated rules and finalize setup 1:59
Once the rule is supported and validated, click Accept.
Confirm the system no longer shows errors about unavailable fields.
Save the finalized compliance rule.
Repeat the process for any additional rules you need to create.
10. Use the guardrails to maintain reliable compliance rules 2:08
Rely on the field reference panel and AI Optimize as guardrails.
Use them to avoid creating rules that cannot be enforced.
Expect fewer setup errors and less troubleshooting when you validate rules first.
Keep rule creation focused on accurate, dependable, and supported compliance logic.
Cautionary Notes
Do not create rules using fields that are not listed in the available fields panel.
If AI Optimize reports that no matching field exists, stop and revise the rule before saving.
Unsupported rules cannot be enforced and should not be accepted as-is.
Always validate rules before finalizing them to avoid setup errors.
Tips for Efficiency
Use the search bar in the field reference panel to quickly find relevant fields.
Review field descriptions before writing rules to reduce trial and error.
Build rules from supported fields only to minimize rework.
Run AI Optimize early in the process so unsupported logic is caught before saving.
Keep a standard list of commonly used fields for faster rule creation.