Buyer Due Diligence Checklist: Answer It Once, Not Every Time

Every buyer sends a version of the same buyer due diligence checklist: company registration, product origin, licences, and proof that the goods are legal and traceable. Exporters often treat each request as a fresh project, digging up the same documents for every new customer. That is slow, and it signals disorganisation to buyers who are themselves under pressure to prove their own supply chains are clean.

This guide explains what a due diligence request is actually used for downstream, what Ghanaian exporters need on file to answer it, and how to build one answer pack you can reuse instead of starting over each time.

What the buyer actually does with your answer

A buyer's due diligence request is rarely idle paperwork. If your buyer sells into the EU, they are likely an operator under the EU Deforestation Regulation (EUDR). Under that regulation, operators must submit a due diligence statement with key product information to the EUDR's online Information System once their own due diligence is complete and any risk of non-compliance is negligible ^[1]. They can only place the product on the EU market, or export it, after that statement has been accepted in the system ^[2].

That means your paperwork becomes part of someone else's regulatory filing. Once the statement is accepted, the operator passes the statement number down to their own direct downstream buyers, so the number travels with the shipment as a traceability reference ^[3]. If your documents are incomplete or inconsistent, your buyer's filing stalls, and so does your shipment. This is the same underlying discipline covered in Audit Trail vs Emailed Certificates: What a Buyer Needs — a buyer wants a record they can point to later, not a one-off email attachment.

What Ghanaian exporters need on file

Before any buyer request lands, a Ghanaian exporter should already have its own export registration sorted. To register as an exporting company with the Ghana Export Promotion Authority, a business must submit the completed GEPA Registration Form together with photocopies of its registered business certificates ^[4]. This is a baseline document, not a buyer-specific one, so it belongs in every answer pack regardless of destination market.

Beyond registration, what a buyer asks for depends on the product and destination. Origin and preferential-trade documents matter if you're shipping under AfCFTA Rules of Origin: How Ghanaian Exporters Qualify. EU-bound shipments of commodities covered by deforestation rules will eventually need to trace back to an accepted due diligence statement and its reference number, as described above.

Build one answer pack, reuse it

Instead of answering each buyer from scratch, build a single reference pack: company registration, product specifications, origin evidence, and any statement numbers or reference IDs you've already received from buyers or systems. Update it as documents renew, and send the same pack to every new buyer, trimmed to what they actually asked for.

This is the same idea behind a supplier onboarding checklist that larger buyers run internally — a fixed, repeatable set of documents rather than an ad hoc email thread. Exporters working with several buyers, or with cooperative members, increasingly use due diligence software or supplier due diligence software to keep one shared file up to date rather than tracking versions in email. The tool matters less than the habit: one current pack, reused, beats a new search every time someone asks.

Worked example: a cashew exporter's first EU buyer request

A Ghanaian cashew exporter receives a due diligence request from a new EU buyer. The buyer explains, in plain terms, that they are an operator under the EU Deforestation Regulation and cannot bring the shipment into the EU market until their own due diligence statement is accepted in the EUDR's Information System ^[2].

The exporter already holds its GEPA registration, filed with the completed registration form and business certificate photocopies ^[4], so that part of the pack is ready immediately. What's missing is origin and traceability detail specific to this buyer's filing. The exporter gathers it, sends the pack, and soon after the buyer confirms their due diligence statement has been accepted and passes back the statement number generated by the Information System ^[3]. The exporter files that number alongside the shipment record — it's now part of the traceability chain for any downstream buyer who asks the same questions later. On the next order from a different EU buyer, the exporter reuses the same pack, adding only the new statement number once it arrives, rather than rebuilding the file from zero.

Answer-every-time vs answer-once