A policy is a named promotion campaign — your Black Friday stack, your VIP loyalty deal, your clearance weekend. Each policy holds a condition tree (who qualifies) and one or more discount rules (what they get). Create unlimited policies, drag-sort by priority, activate or pause individually without touching code.

Each rule can run in Simple mode (flat % or fixed amount on cart, products or shipping) or Promotion mode with access to all 20 formulas. Per-rule settings include discount code, priority, min/max discount caps, date range (valid from / valid to), optional rule-level conditions and multilingual checkout label shown on the cart line.

Stop on first match ends evaluation after the first qualifying policy — useful when campaigns must not overlap. Merge strategy per policy controls how multiple rules inside one policy combine: stack all discounts, first wins, priority cascade, highest discount only, or unique codes. A global default merge strategy and global discount cap in Settings protect your margin across the whole shop.

Policies list view shows status, merge strategy, rule count and quick actions. Duplicate, export JSON, import from file, or toggle active — all from the policies panel with every change written to the audit log.

The condition builder is a nested AND/OR tree editor — the same pattern used in professional rule engines, rendered as drag-friendly groups in your back office. Add a group, pick a field, choose an operator, set a value. Nest groups for logic like: (VIP group OR 5+ past orders) AND (cart total ≥ €100) AND (category Summer Sale has 3+ items).

30+ condition fields cover the full cart context: cart total, product subtotal, shipping cost, product count, unique SKU count, weight, existing cart rules count, customer order count, lifetime spend, day of week, hour, date, postcode, currency, country, invoice country, zone, customer group, carrier, payment module, logged/guest status, products, categories, manufacturers, suppliers, virtual/physical flags, customization and existing discount detection.

Compound fields combine entity + threshold in one condition — e.g. product #123 qty ≥ 3, category #45 line total ≥ €50. Operators include equals, not equals, greater/less than, between, in list, not in list, contains, starts with, regex, empty and not empty.

Product, category, manufacturer and group pickers use built-in autocomplete search. A live preview sentence explains what the tree matches. Power users can toggle raw JSON for copy-paste between environments. Conditions re-evaluate on every cart sync — add to cart, change qty, login, change address — the engine reacts immediately.

Switch a rule to Promotion mode and the flat value fields are replaced by a tile grid of 20 promotion types, grouped by family: adjustments, Nth-unit deals, quantity tiers, spend promos, BOGO, line discounts, gifts and product pairs. Click a tile — only the fields relevant to that formula appear.

The scope selector defines which cart lines enter the calculation: entire cart, hand-picked products, whole categories or manufacturers. BOGO types get buy/get product lists with visual pickers. Spend types get threshold and step inputs. Tier types get a stair-step table. Pair types get list A + list B. Cheapest item free gets a free unit count field. Line promos let you pick cheapest-first or most-expensive-first.

Behind the UI, ConorderdisPromotionCalculator delegates to dedicated math: unit pool expansion for BOGO cycles, line sorting by total value for cheapest-line-free, repeating step arithmetic for spend ladders. The result is a precise discount amount — not a rounded guess from a generic cart rule.

Promotion config syncs bidirectionally with JSON. Import a policy from staging, open the visual builder, tweak one threshold, save — structured data stays consistent. Rule summary chips in the admin show the active formula at a glance without opening the editor.

The Simulator tab is a three-step workflow against real data in your database — not a mock cart. Step 1: search carts by ID, customer name or email. Step 2: pick a cart from the live list (shows customer, email, cart total, last update). Step 3: run evaluation and read the full result breakdown.

Results show which policies matched, which were skipped (and why), per-rule calculated amounts, gift lines that would be added, free shipping flags and the final total discount. Optional customer filter narrows the cart list to one account — ideal for reproducing a support ticket.

Every simulation run is logged in the audit log with event type simulation_run, cart ID, actor (employee) and result snapshot. Marketing can verify a campaign before enabling it. Support can explain why a specific customer cart did or did not get a discount — without placing a test order on the live shop.

Use the simulator after every policy edit, before Black Friday go-live, and when importing policies from staging. It is the safety net that separates enterprise promotion management from "change and hope".

The Dashboard tab is your promotion control room. KPI cards over a selectable period (30 / 90 / 180 / 365 days) show: total discount applications, orders affected, rounded discount total in shop currency, and active policy count. Numbers come from the audit log — real events, not estimates.

Chart.js trend charts visualize discount activity across three granularities: daily (configurable window), weekly and monthly. Switch the default chart type in Settings. A pie chart breaks down applications by discount code so you see which COD-* rules actually fire in production.

The dashboard also surfaces recent audit entries — last policy changes, last simulations, last front-office discount applications — for at-a-glance troubleshooting without opening the full log. Analytics period, chart day/week/month windows and default chart type are all configurable under Settings → Analytics.

For agencies and multistore operators: the dashboard answers the question marketing always asks — "Is our promotion actually running?" — with data, not gut feeling.

The dedicated Audit log tab is a full event journal — not a debug file buried in server logs. Every row stores timestamp, event type, actor (employee name, customer name, or SYSTEM), human-readable summary, linked order reference, discount code, amount, cart ID and policy ID.

11 event types are tracked: discount_applied (live cart sync), order_discount (order placed), policy_created, policy_updated, policy_deleted, policy_toggled, policy_duplicated, policy_imported, policy_exported, settings_updated and simulation_run. Each event records its source: front office, back office or system.

Click View on any row to open a detail modal with the full JSON snapshot — applied discount lines, policy diff, simulation output or settings change payload. Discount applications store a discount_snapshot so you can reconstruct exactly what the customer saw at checkout time.

The list supports PrestaShop native CSV export for finance and compliance reviews. Joined columns show order reference, customer name and employee name without manual cross-referencing. When a customer asks "why did I get this discount?", the answer is one search away.

On the order page in back office (displayAdminOrder hook), a panel shows which Conditional Order Discounts policies contributed to that order — policy name, discount code, amount and snapshot. Historical truth survives even if the policy is later edited or deleted.

Policies are portable JSON documents. Export downloads the full policy — condition tree, all rules, promotion configs, merge strategy, positions — ready for version control or handoff to another shop. Import uploads a JSON file and creates a new policy (or updates, depending on workflow) with audit log entry policy_imported.

Duplicate clones a policy with one click from the list actions menu — copies every rule, renames with a suffix, logs policy_duplicated. Perfect for creating "Black Friday v2" from "Black Friday v1" without rebuilding 15 rules by hand.

Typical agency workflow: build and simulate on staging → export JSON → import on production → run simulator again → enable. Black Friday setups move between client shops in minutes. Every transfer is traceable in the audit log.

The Settings tab centralizes shop-wide behaviour. Master enable/disable switch. Global merge strategy default for new policies. Global discount cap — maximum total discount per cart across all policies (0 = unlimited). Free items as gift toggle — materialize free products as native PrestaShop gift lines vs inline discount.

Disable auto-add prevents automatic cart rule injection when you want manual control. Debug log writes verbose engine traces for support. Analytics section configures default chart period, daily/weekly/monthly windows and default chart type.

Every settings save logs settings_updated to the audit log with before/after snapshot. No silent configuration drift.

Discounts materialize as native PrestaShop cart rules prefixed COD-*. They appear in cart summary, checkout, order confirmation, invoices and credit slips — exactly like manually created cart rules. No theme hacks. No fake negative product lines.

The engine hooks into actionCartSave, product add/remove, front controller init, order validation and cart rule validation — recalculating whenever the cart context changes. Cart state is persisted in conorderdis_cart with applied snapshot, gift snapshot and linked cart rule ID for idempotent sync.

Policies are shop-scoped (id_shop) for multistore setups. Each shop in your group can run independent promotion stacks. PrestaShop 9.x, 8.x and 1.7.x share one codebase via the built-in compatibility layer.

Multilingual checkout labels per rule (conorderdis_rule_lang) ensure the discount line reads correctly in every active shop language.