Hook System

Nazmart's hook system is modelled after WordPress actions and filters. Hooks decouple core code from plugin extensions.

Global Helper Functions

• do_action(string $hook, ...$args): void — Fire an action hook. All registered callbacks for this hook are called in priority order. Return values are ignored.
• apply_filters(string $hook, mixed $value, ...$args): mixed — Pass a value through a chain of filter callbacks. Returns the final modified value.
• has_action(string $hook): bool — Check whether any callbacks are registered for a hook.

Priority

• Lower number = runs earlier. Default priority is 10.
• Use priority < 10 to run before core callbacks, > 10 to run after.
• Callbacks with the same priority run in the order they were registered.

Filters Must Return a Value

Example: Adding a Filter in boot()

public function boot(): void
{
    // Filter the cart total — add a surcharge
    $this->add_filter('nazmart:cart_total', function (float $total) {
        $surcharge = $this->get_option('surcharge_percent', 0);
        return $total * (1 + $surcharge / 100);
    }, 20);

    // Action — fire and forget
    $this->add_action('nazmart:after_order_create', function ($order) {
        // notify Slack, push to CRM, etc.
        \Log::info('Order created: ' . $order->id);
    });
}

Commerce Hooks Reference

These hooks are fired by the Nazmart core at the appropriate moments. Prefix: nazmart:.

Cart Hooks

Order Hooks

Payment Hooks

Product Hooks

User / Auth Hooks

Content Filters

Frontend Layout Actions

User Dashboard Hooks

These hooks let plugins add content to the customer-facing user dashboard (logged-in shop customers, not admin):

Pair these hooks with a web route registered via register_web_routes(). See §12 for the full pattern.

Extension Hooks

These hooks let plugins integrate with built-in Nazmart subsystems: