Pricing engine logic

Identifies pricing-engine implementation logic in Australian contexts: executable pricing rules, formulas, thresholds, and named pricing variables used to calculate prices or discounts. Topic-only pricing references (dynamic pricing, pricing model) remain discovery-level context and do not enforce.

Type

regex

Engine

boost_regex

Confidence

medium

Confidence justification

category-aware structural regex with anchor and context constraints replaces phrase-only detection.

Detection quality

Topic false positive

Jurisdictions

global

Regulations

AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth), GDPR

Frameworks

ISO 27001, ISO 27701

Data categories

pii

Scope

wide

Risk rating

8

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:pricing\s+engine\s+logic|pricing\s+algorithm|pricing\s+model|dynamic\s+pricing|price\s+calculation|margin\s+formula|discount\s+logic|trade\s+secret|proprietary\s+pricing|competitive\s+pricing)\b

Corroborative evidence keywords

pricing engine logic, pricing, engine, logic, intellectual, property, trade, secrets

Proximity: 300 characters

Should match

• pricing engine logic — Primary topic phrase match
• pricing algorithm — Case-insensitive topic phrase match
• pricing model — Alternative topic phrase match
• dynamic pricing — Additional topic phrase match
• if inventory_days > 45 then discount_rate = 0.18; price_floor = cost * 1.12 — Named inputs, a threshold, and executable pricing assignments reveal implementation logic (enforcing branch)

Should not match

• unrelated generic text without domain phrases — No relevant topic phrases present
• placeholder value 12345 — Random text should not match topic-specific regex
• algorithm schematic — Generic word pair from old broad template should not match
• The conference panel covered dynamic pricing trends. — Topic prose without a calculation must not reach the enforcing tiers
• The engine price increased after the vehicle service. — Physical-engine pricing prose is outside scope
• Tutorial example: margin_pct = 20 and sample price_floor = 10. — Tutorial/example/sample markers block the enforcing branch via the template exclusion
• discount applies once the threshold is reached — Prose exercising the removed keyword-gap branch must not enforce (no operator-bound expression)

Known false positives

• Common words and phrases related to pricing engine logic appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
• In Australian English, similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
• High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.

References

• https://www.accc.gov.au/business/competition-and-exemptions/misuse-of-market-power
• https://www.accc.gov.au/business/competition-and-exemptions/cartels