When sourcing spices for food manufacturing, retail, private-label or export programmes, product evaluation involves more than comparing samples and prices.

Procurement and quality teams may need technical documents to understand what is being supplied, how the product is specified, and what information is available for evaluation.

Terms such as Product Specification, Certificate of Analysis (COA), Test Report and Technical Documentation are frequently used during spice sourcing. However, these documents serve different purposes and should not automatically be treated as interchangeable.

Understanding what to request — and when — can make supplier evaluation considerably more organised.

Why Is Documentation Important in Spice Sourcing?

Documentation creates a common technical reference between the buyer and supplier.

A buyer may need documents to:

• Evaluate a potential supplier
• Compare products from different sources
• Review technical parameters
• Complete internal quality approval
• Assess a sample or commercial batch
• Prepare a private-label programme
• Review packaging and labelling requirements
• Plan an export requirement
• Respond to customer or distributor documentation requests

The exact documentation required will depend on the product, application, buyer’s quality system and destination market.

This is why asking a supplier to simply “send all certificates” may not be the most effective approach.

A better approach is to identify what information your team actually needs for the stage of evaluation you are currently completing.

---

1. Product Specification Sheet

The Product Specification Sheet is usually one of the most useful documents during the initial technical evaluation of a spice or food ingredient.

It describes the expected characteristics and defined parameters of the product.

Depending on the spice and agreed specification, it may contain information relating to areas such as:

• Product name
• Product description
• Botanical information, where relevant
• Product format
• Appearance
• Colour
• Aroma
• Flavour
• Particle size or mesh
• Physical parameters
• Chemical parameters
• Microbiological parameters
• Packaging
• Storage conditions
• Shelf-life information

Not every specification will contain exactly the same parameters.

A whole spice, for example, may require different specifications from a finely ground spice, seasoning or dehydrated ingredient.

What is the specification used for?

Think of the specification as the technical definition of the product being discussed.

During sourcing, the buyer can review the specification and determine whether the proposed product is appropriate for the intended application.

It can therefore be useful relatively early in the evaluation process.

---

2. Certificate of Analysis (COA)

A Certificate of Analysis, commonly referred to as a COA, serves a different purpose.

While a product specification describes the parameters expected for a product, a COA generally reports results associated with a particular production batch or lot, depending on the testing and documentation system being used.

This distinction is important.

Product Specification

Defines the expected or agreed product parameters.

Certificate of Analysis

Reports applicable analytical information relating to a specific batch or lot.

A COA may include information such as:

• Product identification
• Batch or lot reference
• Date-related information
• Tested parameters
• Specification or reference limits
• Reported results

The exact parameters shown depend on the product, agreed requirements and testing programme.

Therefore, buyers should avoid assuming that every COA will contain the same tests.

---

3. Laboratory Test Reports

A laboratory test report provides results for tests conducted on a submitted sample.

Depending on the requirement, testing may relate to areas such as:

• Physical parameters
• Chemical parameters
• Microbiological parameters
• Residue-related parameters
• Contaminants
• Other buyer- or market-specific requirements

The tests required for one product or market may not necessarily be appropriate for another.

For example, requirements for a spice being evaluated for one destination market may differ from those for another country, customer or food application.

This makes context particularly important when requesting laboratory documentation.

Instead of asking:

“Please send your laboratory report.”

A more useful request would explain:

Product + required test parameters + intended market + purpose of the test report

This helps both parties understand what is actually being requested.

---

4. What Is the Difference Between a Specification, COA and Test Report?

These documents are related, but they should not automatically be considered the same.

Document	Primary Purpose
Product Specification	Defines the expected characteristics and parameters of the product
Certificate of Analysis (COA)	Reports applicable results associated with a particular batch or lot
Laboratory Test Report	Provides analytical results for tests performed on a submitted sample
Quality / Process Documentation	Provides supporting information about quality systems or processes
Packaging Information	Describes relevant packaging configuration and requirements

Understanding this distinction helps procurement and quality teams request the correct information at the correct stage.

---

5. Quality and Process Documentation

During supplier evaluation, buyers may also request information relating to the manufacturer’s quality systems, production processes or certifications.

The exact requirement varies significantly between organisations.

A procurement team may have a standard vendor qualification questionnaire, while a retailer or food manufacturer may have its own supplier approval checklist.

If your organisation already has such a checklist, it is usually better to share it with the supplier rather than sending multiple individual document requests.

This gives the supplier a clearer picture of the information required for approval.

---

6. Packaging and Labelling Information

Documentation requirements are not limited to the spice itself.

For private-label, retail and export programmes, buyers may also need information about packaging.

Depending on the project, discussions could include:

• Packaging format
• Pack size
• Outer packaging
• Product identification
• Batch coding
• Storage information
• Labelling requirements
• Shipping configuration
• Destination-market requirements

Packaging requirements should ideally be discussed together with the product and destination market.

This is particularly important for private-label projects where the packaging forms part of the finished commercial product.

---

7. Why the Destination Market Matters

One of the most important pieces of information to provide when requesting documentation is:

Where will the product be sold or used?

Requirements can differ between countries, customers and applications.

A supplier cannot necessarily determine the complete documentation requirement simply from the product name.

For example:

Product: Turmeric Powder
Destination: UAE
Application: Retail private-label product

provides considerably more useful context than:

“Please send turmeric documents.”

Similarly:

Product: Ground Cumin
Application: Industrial food manufacturing
Destination: European market
Requirement: Supplier technical evaluation

allows the supplier to understand the purpose of the request much more clearly.

---

8. Documentation for Private-Label Projects

Private-label projects often involve several layers of evaluation because the buyer is developing a finished product under its own brand.

Documentation discussions may therefore cover both:

Product Information

Specifications, product characteristics and applicable analytical information.

Packaging Information

Pack sizes, packaging format and relevant technical details.

Quality Information

Information required by the buyer’s quality or procurement team.

Market Requirements

Information relevant to the destination country or customer.

The earlier these requirements are communicated, the easier it becomes to incorporate them into the overall private-label development process.

---

9. Documentation for Export Orders

Export documentation deserves particular attention because commercial, product and destination requirements can intersect.

The documentation associated with an export shipment may depend on several factors, including:

• Product
• Destination country
• Buyer requirements
• Packaging
• Shipment terms
• Applicable regulatory requirements

For this reason, documentation should ideally be discussed before the commercial order is finalised, rather than after the product has already been prepared for dispatch.

If your importing team, customs consultant, distributor or customer has a specific documentation checklist, share it during the commercial discussion.

---

10. Avoid Requesting Documents Without Context

A common sourcing approach is to send a supplier a message such as:

“Please send all certificates and reports.”

The problem is that this does not explain what the buyer is evaluating.

A better documentation request should answer several basic questions.

Which product?

Whole cumin? Turmeric powder? Chilli powder? A spice blend?

What format?

Whole, ground, blended, seasoning or dehydrated?

What is the application?

Retail, private-label, food manufacturing or food service?

What is the destination?

Which country or market?

What stage are you at?

Initial supplier evaluation, sample approval, final commercial approval or shipment?

What does your team require?

Do you have a procurement or quality checklist?

These details make the request substantially clearer.

---

11. A Practical Documentation Request Checklist

Before contacting your supplier, prepare the following information:

Product
☐ Product name
☐ Product format
☐ Required specification, if already defined

Application
☐ Intended use
☐ Food manufacturing / retail / private label / distribution
☐ Any application-specific requirements

Market
☐ Destination country
☐ Customer-specific requirements
☐ Importer or distributor requirements, where applicable

Technical Evaluation
☐ Product specification required
☐ COA requirement
☐ Specific laboratory tests required
☐ Buyer quality checklist available

Packaging
☐ Bulk or retail packaging
☐ Required pack size
☐ Labelling requirements

Commercial Stage
☐ Supplier evaluation
☐ Sample evaluation
☐ Product approval
☐ Commercial order
☐ Shipment documentation

The more clearly these requirements are communicated, the easier it becomes for both procurement and supplier teams to work from the same information.

---

12. What Should Your Documentation Request Look Like?

A technical enquiry does not need to be complicated.

A structured request could look like this:

Product: Turmeric Powder
Format: Ground
Application: Private-label retail product
Pack Size: 100 g
Destination Market: [Country]
Estimated Requirement: [Quantity]
Current Stage: Product and supplier evaluation

Documents Required:

• Product specification
• Applicable analytical / COA information
• Packaging information
• Additional documents listed in our attached supplier checklist

This is much more actionable than simply requesting a catalogue of certificates.

---

Documentation Should Support the Buying Process

Technical documents are most useful when they support a clearly defined commercial requirement.

The sequence can be thought of as:

Product Requirement → Technical Evaluation → Sample Review → Documentation Review → Commercial Alignment → Final Supply Requirements

Documentation should not be treated as an isolated administrative exercise.

Instead, it should help the buyer and manufacturer establish a common understanding of the product, specification, quality expectations, packaging and intended market.

---

Evaluating Spices for Your Business?

Aditya Food Product works with food manufacturers, private-label brands, retailers, distributors and international buyers across whole spices, ground spices, spice blends, seasonings and dehydrated products.

When requesting technical documentation, share your product, intended application, packaging format, destination market and buyer-side documentation requirements.

This helps our team understand the context of your enquiry and provide information relevant to the stage of evaluation.

Aditya Food Product
Indian Spice Manufacturer | Private Label | Bulk & Export Supply