---
title: "Why questions: understand the cause, not just the number · Adea"
description: "\"Why did sales drop?\" and \"why was the order cancelled?\": the whole sequence from your own data."
url: https://adea.app/questions/why
---

# Why questions: the cause, not just the number.

It is the why questions that cost the most developer hours, because the answer lies in both code and data. Adea follows the trail, shows the sequence and points to the cause.

[Ask your first question](https://adea.app/signup) [See the demo](https://adea.app/demo)

## Questions like these

Why was order 20417 cancelled?

Cancelled automatically because the payment was declined three times. Timeline: ordered and 1st decline 28 Sep, 2nd decline 29 Sep, 3rd decline and cancellation 30 Sep.

Why did orders between €65 and €80 drop in the last 9 days?

They fell 17%, while the average order rose from €58 to €60. The free-shipping limit was raised from €65 to €80 in a code change 9 days ago.

Why is the customer's payment shown as declined?

The card was declined by the bank on the first attempt, and the second attempt is not scheduled until tomorrow at 06:00.

## What you get

### The whole story

The events in order, with dates and the rules that triggered them.

### From your own data

Nothing is guessed. Every step can be opened and checked.

### One click and you are in the case

Open the order or the customer straight from the answer.

## Common questions

### Can Adea always find the cause?

Not always. When data or code does not give a safe answer, Adea says so and suggests what a developer can look at. A question Adea cannot answer is free.

## The other kinds

[What](https://adea.app/questions/what) [How](https://adea.app/questions/how)

## What do you want to know?

[Start free](https://adea.app/signup) [Book 20 minutes](mailto:hello@adea.app?subject=20%20minutes%20about%20Adea)