> 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/start-here/last-mile-delivery.md). # Last-mile delivery #### What consumers actually see at checkout Last-mile delivery decisions are made at checkout. This is where consumers see delivery options, prices, providers, delivery times, and defaults. It is also where most delivery competition plays out - often invisibly, through positioning rather than explicit choice. Tembi captures the delivery choices consumers actually see in a webshop checkout:\ which carriers are shown, in what order, with which prices, methods, and branding. This matters because being present is not the same as being visible - and visibility drives volume.
#### From spot checks to market-wide visibility Looking at a handful of webshops does not reveal how a market works. Tembi monitors checkout setups across tens of thousands of webshops per market. At that scale, individual checkouts stop being anecdotes and start forming patterns: * How often providers appear in first position * Who competes with whom inside the same checkout * What delivery information is visible * How positioning changes over time This turns checkout data into a true market signal rather than isolated observations. #### Building a complete picture of the market Checkout data alone is powerful, but incomplete. Tembi connects checkout observations with additional layers of data for every webshop: * Company identifiers and ownership * Financial and organisational data * Product categories, price levels, size, and weight * Technical setup and integrations * Size, activity, and growth estimations This allows delivery performance to be analysed in context - not just by presence, but by the type of retailers, segments, and growth profiles involved. #### From data to intelligence The shift from data to intelligence is about answering questions, not just displaying metrics. By combining checkout behaviour with company, product, and growth data, Tembi supports: * Ideal Customer Profile (ICP) modelling based on real clients * Mapping competitors’ client portfolios and strengths * Detecting changes that signal opportunity or risk * Comparing markets and portfolios on a like-for-like basis Instead of asking “what happened?”, teams can ask “where should we focus next - and why?” #### Intelligence that supports commercial action Last-mile delivery intelligence only matters if it changes decisions. Tembi is used to: * Prepare key account reviews with concrete checkout evidence * Prioritise accounts where first position is realistic to win * Detect churn risk when positioning or setup changes * Support sales and KAM teams with timely, market-based signals The result is a shared, external view of the market that commercial, strategy, and leadership teams can act on - continuously, not once a year. --- # 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/start-here/last-mile-delivery.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.