# Store Events

> The store events COD Order Calls acts on - order.created starts a confirmation call, order.cancelled and order.paid stop pending calls - and what happens to other events.

Source: https://edesy.in/docs/order-calls/connect-your-store/store-events

COD Order Calls acts on three store events. `order.created` can start a confirmation call. `order.cancelled` stops any pending call for that order. `order.paid` stops a pending cash-on-delivery call, because the customer has paid online. Any other event type is stored in the events log and marked ignored.

## Events

| `event` | What we do |
|---|---|
| `order.created` | Each enabled call rule for this store checks its [conditions](https://edesy.in/docs/order-calls/call-rules/conditions). A match schedules a call; a non-match is recorded as skipped with the reason |
| `order.cancelled` | Pending calls for the same `order.id` are cancelled ("order was cancelled on the store") |
| `order.paid` | Pending COD confirmation calls for the order are cancelled ("order was paid online") |
| anything else | Stored and shown as **Ignored**, for example `order.updated`, `order.shipped`, `order.fulfilled` or `payment.captured`. No call is made |

Call rules are triggered by **Order created**.

Send `order.cancelled` and `order.paid` whenever you can. They are what stop a customer getting a call about an order that is already cancelled or paid.

## When an order is skipped

An `order.created` event does not schedule a call when:

- it does not match the rule's conditions (for example, it is a prepaid order)
- the order is already cancelled (`cancelled: true`)
- it has no valid Indian phone number
- the number is on your do-not-call list
- the same order already has a job for that rule

Skipped orders appear on the Orders screen with state **Skipped** and the reason.

## A call already in progress

A cancellation that arrives while a call is ringing does not hang the call up. The call finishes, and the outcome reflects what the customer and your store did.

## Event statuses

Every delivery appears in the store's **Events** tab:

| Status | Meaning |
|---|---|
| Received | Stored, about to be processed |
| Processed | Handled; the detail says what happened, for example "call scheduled for 9 Oct 3:04 PM", "1 pending call(s) cancelled" or "no enabled automation for this event" |
| Ignored | Not an event we use for order calls |
| Failed | Something went wrong while processing; the error is shown and you can replay it |

Open an event to see its headers and body. **Replay** processes it again; see [Retry, Replay and Cancel](https://edesy.in/docs/order-calls/orders/retry-replay-cancel).