PrestaShop Guide d'installation

Architecture

The module listens to PrestaShop hooks (actionProductSave, actionObjectCmsUpdateAfter, combination events, order validation, etc.) and sends webhook events to Emporiqa using deferred delivery: events are queued during the request and flushed after the response reaches the browser via register_shutdown_function. Saving a product completes locally; the webhook delivery runs asynchronously after the response.

All translations and channels for a single product or page consolidate into one webhook event. Combinations cascade up: editing a child triggers a parent re-sync so search always sees the full catalog state.

Requirements

Configuration Reference

All settings live at Modules → Emporiqa → Configure. Connection Settings is the main section and is expanded by default. Sync toggles and advanced settings (languages, webhook URL, batch size) are collapsed under Advanced.

Connection Settings

Advanced Settings

Most stores don't need to change these.

Always-on capabilities

• Cart operations — add, update, remove from inside the chat.
• Conversion tracking — chat sessions linked to completed orders for revenue attribution.
• Multi-shop mapping — each PrestaShop shop auto-maps to a slugified channel.

Features

Webhook Payload

Each product or page is sent as a single webhook event containing all languages and channels. Translatable fields are nested by channel and language code.

Product Event

{
  "type": "product.updated",
  "data": {
    "identification_number": "product-42",
    "sku": "product-42",
    "channels": ["my-shop"],
    "names":        {"my-shop": {"en": "Hiking Boots", "fr": "Chaussures de randonnee"}},
    "descriptions": {"my-shop": {"en": "Waterproof leather boots...", "fr": "Bottes en cuir impermeables..."}},
    "links":        {"my-shop": {"en": "https://store.com/hiking-boots", "fr": "https://store.com/fr/chaussures-randonnee"}},
    "categories":   {"my-shop": {"en": ["Footwear > Hiking"], "fr": ["Chaussures > Randonnee"]}},
    "attributes":   {"my-shop": {"en": {"Material": "Leather"}, "fr": {"Material": "Cuir"}}},
    "brands":       {"my-shop": "TrailPeak"},
    "prices":       {"my-shop": [{"currency": "EUR", "current_price": 129.99, "regular_price": 149.99}]},
    "images":       {"my-shop": ["https://store.com/img/boots-front.jpg"]},
    "availability_statuses": {"my-shop": "available"},
    "stock_quantities":      {"my-shop": 42},
    "is_parent": false,
    "parent_sku": null,
    "variation_attributes": {}
  }
}

Field Structure

Customization Hooks

The module dispatches PrestaShop hooks you can listen to from your own module to control sync behavior and modify data before it's sent.

Example: skip inactive products

// In your custom module
public function hookActionEmporiqaShouldSyncProduct($params)
{
    $product = $params['product'];

    if (!$product->active) {
        $params['should_sync'] = false;
    }
}

Order Tracking

Emporiqa can look up order status on behalf of customers during chat conversations. The module registers a signed front controller that PrestaShop calls when a customer asks about their order.

Flow

1. Customer asks "Where is my order #12345?" in the chat.
2. Emporiqa sends an HMAC-SHA256 signed POST to your store.
3. The module looks up the order, verifies the billing email matches, and returns the status.
4. The salesperson presents the order information to the customer.

Endpoint

Setup

The endpoint is always active once the module is installed. Email verification is always required — the customer must provide the email on the order before any data is returned. To enable order lookup from chat, set the Order Tracking API URL in your Emporiqa dashboard (Store Settings → Integration) to:

Troubleshooting