> For the complete documentation index, see [llms.txt](https://tembi.gitbook.io/tembi-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tembi.gitbook.io/tembi-knowledge-base/product-how-to/checkout-score.md).
# Checkout score
The checkout score measures how clearly your delivery brand and services are presented to consumers at checkout.
It is designed to turn qualitative checkout setups into a simple, comparable signal that teams can track, benchmark, and act on - across individual clients and the wider market.
#### What the checkout score measures
The checkout score is built from a set of observable elements in the checkout flow. Each webshop is assessed on whether key information is clearly presented to the shopper.
The score currently covers:
* **Brand visibility** - whether the delivery provider is clearly named
* **Delivery method clarity** - whether delivery methods are understandable to the shopper
* **Delivery time** - whether expected delivery time is displayed
* **Environment friendly (optional)** - whether environmentally friendly delivery is surfaced when sorting
Each webshop receives a simple score (for example 1/3, 2/3) and a qualitative label (low, medium, high), making it easy to interpret at a glance.
#### Why this matters
Being present in checkout is not enough.
If your brand is unclear, delivery methods are vague, or delivery time is missing, consumers are less likely to choose your option - even if you are technically available. And this becomes especially important with agentic commerce.
The checkout score makes these issues visible and measurable, so teams can move from assumptions to evidence.
#### How teams use the checkout score
**Key Account Management**
* Monitor how your brand is presented to consumers
* Detect changes that could impact volume or compliance
* Target clients with low scores to build brand
**Sales**
* Identify prospects where delivery presentation is weak
* Build pitches based on concrete checkout gaps
* Prioritise accounts where small setup changes can improve conversion
**Leadership**
* Benchmark checkout quality across markets and portfolios
* Track structural differences between countries or segments
* Understand how delivery visibility supports - or limits - market position
#### Designed for monitoring, not one-off checks
Checkout setups change frequently.
The checkout score is calculated continuously and shown alongside historical data, allowing teams to:
* Track improvements or deterioration over time
* Set up monitoring and alerts
* Compare performance consistently across clients and competitors
As checkout decisions become increasingly automated and agent-driven, clear and correct delivery presentation becomes critical. The checkout score makes that clarity measurable.
If you want, next we can add a short **“How to act on a low score”** section with concrete examples for Sales and KAM teams.
*Get a simple overview inside the Tembi platform.*
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://tembi.gitbook.io/tembi-knowledge-base/product-how-to/checkout-score.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.