# End user statements: collecting them without slowing sales | LandEdgeHQ

Source: https://landedgehq.com/blog/2026-10-25-end-user-statements-export-checks/

Cross-border operations guide · October 25, 2026


End user statements are essential export evidence and a notorious deal slower when handled badly. This guide shows how to ask for them early, keep them short, and reuse them properly, so compliance stops being the last minute obstacle in every controlled sale.

## Timing is the whole trick

Requested at dispatch, an end user statement holds a shipment hostage while a customer finds a signatory. Requested with the quotation, it is just paperwork in a process that already involves forms, credit checks, and terms. The document did not change; its position in the sales cycle did.

Sales teams resist early requests fearing friction, but customers judge friction against expectations. A statement requested up front reads as professionalism, especially in sectors where every serious supplier asks. The same request at the last minute reads as disorganisation, because that is what it is.

## Keep the form to what is actually needed

A good statement asks for the buyer and end user identity and address, a description of the goods, the intended end use in the buyer's own words, and a signature with a name, title, and date. Every extra page of legal language reduces completion rates without improving the evidence where it counts.

The end use answer must be specific enough to test against control concerns. Manufacturing components for agricultural machinery is usable. Commercial purposes is not. Train sales staff to spot the empty answer and ask once, politely, for the real one, while the deal is young and the customer is cooperative.

## Reuse with rules, not forever

For repeat customers, hold the statement on file and confirm it still applies on each order, with a refresh on a set cycle and immediately when anything material changes: new end user, new application, new destination, or a product with different control status. Reuse cuts friction where risk is genuinely low.

Log every order against the statement it relied on. In an audit, the link between shipment and statement is the evidence; a folder of statements with no order mapping proves the business collected paper, not that it checked anything.

## Refusals are information too

A customer who will not say what the goods are for, or who asks to route paperwork through an unrelated company, has told you something important. Treat refusal as a screening result, escalate it, and be willing to walk away. No margin on one order pays for an enforcement case.

Record refusals and odd requests in the same system as approvals. Patterns across enquiries, such as several new buyers asking for the same controlled item with vague uses, are exactly the intelligence that protects the business and that compliance teams are expected to notice.

Store statements where shipping can see them, with a flag on the customer record when a valid statement is missing or expired. A check that lives in a compliance inbox fails at 4pm on a Friday when the inbox owner is away. A flag on the order itself, visible at pick and pack, holds the shipment automatically and turns an individual's knowledge into a system property. That is the difference between a process and a person, and auditors price the difference exactly as you would expect.

Keep reading: [Export licence exceptions: when they do not apply](https://landedgehq.com/blog/2026-10-25-export-licence-exceptions-limits), [Sanctions screening for supplier lists: a practical routine for importers who are not lawyers](https://landedgehq.com/blog/2026-10-25-sanctions-screening-supplier-lists), and [Dual use goods and export screening basics for everyday importers and distributors](https://landedgehq.com/blog/2026-10-25-dual-use-goods-export-screening-basics) cover the nearby cases in this series.

## Frequently asked questions

## What is an end user statement for?

It is evidence of who will use controlled goods and for what purpose, used to test a sale against export control concerns and to support licence or exception decisions. It must be specific enough to actually test.

## When should the statement be requested?

At quotation stage, alongside credit and terms paperwork. Asked early it is routine; asked at dispatch it delays shipments and looks disorganised.

## Can one statement cover repeat orders?

Yes, held on file with an expiry and refresh triggers for any material change: new end user, application, destination, or differently controlled product. Each order should be logged against the statement it relied on.

## How should a refusal to provide one be handled?

As a screening result: escalate, ask once for the real end use, and be prepared to decline the sale. Vague uses and requests to route documents through third parties are recognised warning signs.