Skip to main content
Eaglecart fires webhooks for events across orders, products, customers, and inventory. Each event is identified by a dot-separated topic string such as order.created or inventory.low_stock. Subscribe to exactly the topics your integration needs so your endpoint only receives relevant payloads.
Subscribe only to the event topics you actually need. Receiving irrelevant events adds latency to your handler, increases the risk of processing errors, and makes your delivery logs harder to read. You can always add or remove subscriptions later from Settings → Developer → Webhooks.

Event Topics

Order events fire whenever the lifecycle of an order changes — from placement through fulfilment, cancellation, or refund.

order.created

Fired when a customer successfully places a new order. Use this event to trigger fulfilment workflows, send order confirmation emails via a third-party provider, or sync the order to an external ERP.
Sample payload — order.created

order.updated

Fired when one or more fields on an existing order change — for example, when a shipping address is corrected, a note is added, or the order status transitions. The payload includes the full updated order object.
Sample payload — order.updated

order.fulfilled

Fired when an order (or a fulfilment within an order) is marked as fulfilled. The payload includes the tracking number and carrier if they were entered at the time of fulfilment.
Sample payload — order.fulfilled

order.cancelled

Fired when an order is cancelled, either by the merchant or by an automated rule. The payload includes the cancellation reason and who initiated it.
Sample payload — order.cancelled

order.refunded

Fired when a refund is issued against an order. The payload includes the refunded amount, the line items affected, and whether the refund was full or partial.
Sample payload — order.refunded
Product events fire when items in your product catalogue are created, modified, or removed. Subscribe to these events to keep external search indexes, product feeds, or warehouse systems in sync.

product.created

Fired when a new product is published or saved to the catalogue for the first time.
Sample payload — product.created

product.updated

Fired when any field on a product or one of its variants changes — including price, description, images, or stock levels updated through the product editor.
Sample payload — product.updated

product.deleted

Fired when a product is permanently deleted from the catalogue. Note that archiving a product does not fire this event; it fires product.updated with "status": "archived".
Sample payload — product.deleted
Customer events fire when shopper accounts are created, updated, or removed. Use these to sync customer records to a CRM, marketing platform, or loyalty programme.

customer.created

Fired when a new customer account is created, either by the customer registering on the storefront or by the merchant creating one manually in the admin.
Sample payload — customer.created

customer.updated

Fired when a customer updates their profile information — such as their email address, password, default shipping address, or marketing preferences.
Sample payload — customer.updated

customer.deleted

Fired when a customer account is permanently deleted. This can occur when the merchant deletes the account from the admin or when a customer submits a data deletion request (GDPR/CCPA).
Sample payload — customer.deleted
Inventory events fire when stock levels change or fall below a critical threshold. Subscribe to these events to automate reordering, update external warehouse systems, or alert operations teams.

inventory.updated

Fired whenever the stock quantity of a variant changes — due to a sale, a manual adjustment in the admin, a stock receive, or a return.
Sample payload — inventory.updated

inventory.low_stock

Fired when the available stock of a variant drops to or below its configured reorder point. Set each variant’s reorder point in Products → [product] → [variant] → Inventory → Reorder point.
Sample payload — inventory.low_stock