Customer Order

type: flight-item-type
uses-route: Customer Order Route
created_at: 2026-10-11

Where do Flight Items of this type come from?

From customers: a fleet operator or depot orders DC chargers through Sales, an installer orders wallboxes through the portal. One item is one order, entered in the ERP.

Why are you working on these? What is the customer value?

A charger delivered on the confirmed date, configured as ordered and invoiced correctly. Nothing about an order is interesting to the customer — until it goes wrong.

To whom is the finished Flight Item delivered?

To the customer — chargers on site and an invoice — and, for the orders that needed the studio, a reason code back into the Order Exceptions Review.

How long does it take?

Two to six weeks from order to delivery, set by the plant’s schedule. A studio case should add no more than two working days.

Like what you see? → Start — build your own org folder in ~2 min

Customer Order.md

---
type: flight-item-type
uses-route: "[[Customer Order Route]]"
created_at: 2026-10-11
---

## Where do Flight Items of this type come from?

From customers: a fleet operator or depot orders DC chargers through [[Sales]], an
installer orders wallboxes through the portal. One item is one order, entered in the ERP.

## Why are you working on these? What is the customer value?

A charger delivered on the confirmed date, configured as ordered and invoiced correctly.
Nothing about an order is interesting to the customer — until it goes wrong.

## To whom is the finished Flight Item delivered?

To the customer — chargers on site and an invoice — and, for the orders that needed the
studio, a reason code back into the [[Order Exceptions Review]].

## How long does it take?

Two to six weeks from order to delivery, set by the plant's schedule. A studio case should
add no more than two working days.