A reference of technical terms, concepts, and acronyms used throughout Order Daemon documentation and the plugin itself.

A

AbstractGatewayAdapter
The PHP base class that third-party gateway adapters must extend. Located at src/Core/Events/Adapters/AbstractGatewayAdapter.php. Developers must implement getSupportedEventTypes(), canHandle(), validateAuthenticity(), normalize(), computeIdempotencyKey(), extractTransactionId(), and extractGatewaySpecificMetadata(). Registered via the odcm_register_gateway_adapters hook.

Action
The “THEN” part of a rule that executes when all conditions are met. Actions include completing the order, adding order notes, sending emails, and triggering external integrations. Implemented via ActionInterface. See: Component.

Action Scheduler
WooCommerce’s built-in system for managing background tasks and scheduled events. Order Daemon uses Action Scheduler to process orders asynchronously without blocking the checkout process.

Audit Log
A comprehensive log of all decisions and actions taken by Order Daemon. Every rule evaluation, condition check, and action execution is recorded for transparency and debugging. Stored in the odcm_audit_log and odcm_audit_log_payloads database tables. Viewed through the Insight Dashboard or queried via the Audit Log API.

C

Component
Collective term for the three building blocks of a rule: Triggers, Conditions, and Actions. Each component is a PHP class implementing a corresponding interface (TriggerInterface, ConditionInterface, ActionInterface) plus the shared ComponentInterface. Components are discovered and managed by RuleComponentRegistry. Custom components are registered via odcm_register_components.

Completion Rule
A set of triggers, conditions, and actions that define when and how an order should be automatically processed. Rules are stored as the odcm_order_rule custom post type.

Condition
The “IF” part of a rule that must be satisfied for actions to execute. Conditions check order properties like product types, totals, and customer information. Implemented via ConditionInterface with a single evaluate(WC_Order $order, array $settings): bool method. See: Component.

Consolidated View
An audit log display mode (view=consolidated) where related log entries are grouped by process_id before pagination. Results are capped at 500 grouped entries per request; use is_truncated in the response meta to detect truncation. Contrast with: Flat View.

CPT
Custom Post Type. Order Daemon stores automation rules as the odcm_order_rule CPT.

D

Debug Mode
A development setting that enables verbose logging and additional diagnostic information. Enable with define('ODCM_DEBUG', true) in wp-config.php.

Dual-Table Architecture
Performance-optimized database design that separates frequently accessed audit log metadata from detailed payload data. The odcm_audit_log table holds core fields; odcm_audit_log_payloads holds the JSON payload.

E

EvaluationContext
A PHP class (src/Core/Events/EvaluationContext.php) that holds the enriched context for a rule evaluation pass – including the order, the triggering event, and computed metadata.

Evaluator
The core class (src/Core/Evaluator.php) responsible for evaluating a rule against a WooCommerce order: checking the trigger, evaluating each condition in sequence, and returning a structured result including per-condition pass/fail traces.

Event Type
Classification system for audit log entries (e.g. rule_evaluation, webhook_received). Used for filtering and organizing the audit trail. Custom event types can be registered and referenced in odcm_log_event() calls.

F

First Rule Wins
Order Daemon’s processing logic where the first rule whose conditions are all met executes, and no subsequent rules are evaluated for that order and trigger.

Flat View
An audit log display mode (view=flat) where raw log rows are returned and paginated directly at the database level. No grouping by process ID. Use for data export, counting, or high-volume logs. Contrast with: Consolidated View.

G

Gateway Adapter
A PHP class that bridges a specific payment gateway’s webhook format to Order Daemon’s internal event model. Extends AbstractGatewayAdapter. Custom adapters are registered via odcm_register_gateway_adapters.

I

Idempotency Key
A stable unique key generated by each gateway adapter for a given webhook event. Used to detect and discard duplicate webhook deliveries. Generated by computeIdempotencyKey(array $input): string.

Insight Dashboard
Order Daemon’s audit log analysis interface. Features a log stream with filters and a detail pane showing component-level results for each event. Accessed via Order Daemon → Insight Dashboard. Requires view_woocommerce_reports capability.

O

ODCM
Abbreviation for “Order Daemon Completion Manager.” Used as a prefix for function names (odcm_log_event), database tables (odcm_audit_log), hooks (odcm_register_components), and the CPT slug (odcm_order_rule).

odcm_log_event()
Global helper function for writing structured audit trail entries. Signature: odcm_log_event(string $summary, array $data, ?int $order_id, string $status, string $event_type, bool $is_test, ?string $process_id, ?string $parent_event_type). Defined in src/Includes/functions.php.

Order
A record of a customer’s purchase transaction in WooCommerce, stored as the shop_order post type. The central data object passed to condition evaluate() methods via WC_Order.

P

Payload
The detailed data package logged with each audit trail entry. Stored in odcm_audit_log_payloads separately from the main log row for performance. Contains structured JSON with comprehensive event context.

Primary Action
The single main action object in a rule: {id, settings}. Executes when all conditions pass. Contrast with: Secondary Actions.

Process ID
A stable string identifier (process_id) used to correlate related audit log entries belonging to a single unit of work (e.g. one webhook reception plus its rule evaluations). Pass the same process_id to all odcm_log_event() calls within a unit of work.

R

Rule Builder
The WordPress admin interface where rules are configured. Backed by the RuleBuilderApiController REST API.

RuleComponentRegistry
The PHP class (src/Core/RuleComponents/RuleComponentRegistry.php) that discovers and manages all registered triggers, conditions, and actions. Loads lazily. Custom components are registered by hooking into odcm_register_components (or the more specific odcm_register_triggers, odcm_register_conditions, odcm_register_actions).

S

Secondary Actions
An array of additional action objects that execute after the primary action. Each item has the same {id, settings} shape. Stored as secondaryActions in the rule data structure.

T

Trigger
The “WHEN” part of a rule that initiates evaluation. Implemented via TriggerInterface with a should_trigger(array $context, array $settings): bool method. See: Component.

U

UniversalEvent
A normalized PHP class (src/Core/Events/UniversalEvent.php) representing any inbound event from any source – payment gateway webhook, WooCommerce hook, or manual trigger. Gateway adapters produce UniversalEvent instances in their normalize() method.

W

Webhook
An HTTP callback mechanism. Order Daemon receives inbound webhooks from payment gateways at POST /wp-json/odcm/v1/webhooks/{gateway}, normalizing them into UniversalEvents for rule processing. Custom inbound adapters extend AbstractGatewayAdapter.

WP-CLI
WordPress Command Line Interface. Order Daemon Pro provides WP-CLI commands for managing rules and logs from the terminal. See: CLI & Automation.