Product Specification

A Buyer-Ready Bulk Matcha Specification Template

Create, approve and maintain one version-controlled product specification that connects bulk matcha identity, intended use, test methods, packaging, lot release, application acceptance and change control.

1 September 202616 minute readXIAO TEA Application & Commercial Team

Ten numbered control blocks in a buyer-ready bulk matcha product specification, from document identity through change control. — A complete specification connects the controlled document and product identity to application conditions, test methods, packaging, lot evidence and revalidation.

A workable bulk matcha specification is a controlled agreement, not a supplier brochure or a list of attractive numbers. It should identify the exact product and version; define destination, application and processing conditions; state each requirement with a method, unit, tolerance and decision rule; connect packaging, lot coding, sampling and COA evidence; record the approved application sample; and require review after material change. Keep legal limits destination-specific. The specification defines what must be met, while the COA reports results for one lot and application testing confirms performance in the buyer’s formula.

EDITABLE PROCUREMENT TOOL

Download the 8-language bulk matcha specification workbook (XLSX)

Open the editable field list, assign an owner to every OPEN item, preserve the source and method for each controlled requirement, and approve one revision before using it for purchase or lot release.

Download XLSX

USE THIS GUIDE IF

Procurement, quality and R&D teams converting an approved bulk matcha direction into a controlled B2B product specification.
Beverage, bakery, dessert, premix, retail and private-label buyers who need the supplier, laboratory and receiving team to use the same acceptance rules.
Importers and food manufacturers who need a versioned record connecting product identity, destination checks, lot evidence and change notification.

NOT THE RIGHT ROUTE IF

A universal legal-limit sheet that can be copied unchanged into every country, food category or end use.
A replacement for a lot-specific COA, buyer sampling, laboratory testing, application validation or qualified regulatory review.
A consumer tasting note, supplier qualification scorecard, commercial quotation or pre-project RFQ by itself.

PROJECT DECISIONS

Ten blocks to complete before approving a bulk matcha product specification

SituationDecisionReason

1. Document and version controlEnter the specification ID, revision, issue date, effective date, owner, approvers, superseded version and reason for change. Define which signed or electronically approved copy controls purchase and release decisions.Without one controlled version, purchasing, production, laboratories and receiving teams can judge the same lot against different requirements. A revision date alone is not enough if the changed field and approval route are not recorded.

2. Product identity and SKURecord the buyer and supplier product names, internal SKU, supplier code, ingredient declaration, physical form, flavor status, country-of-origin statement to be verified, and any reference sample code.A specification must attach to one identifiable product. Similar grades, development samples or private-label names can otherwise be confused with the commercial SKU, and evidence for another product may be accepted incorrectly.

3. Intended market, application and processState destination market, buyer type, finished-product category, usage rate range, dairy or plant base, hot or cold process, relevant heat, shear, hold and storage conditions, and whether the ingredient is consumed directly or further processed.Application conditions determine which sensory, dispersion, stability and compliance questions matter. A matcha accepted in water cannot automatically be assumed to perform in oat milk, bakery, ice cream or an RTD process.

4. Raw material and process statementSpecify the agreed tea identity, permitted ingredients, flavor declaration status, relevant origin or sourcing statement, key processing description and prohibited substitutions. Request enough information to assess change, without asking the supplier to disclose protected formula details.The buyer needs a stable product definition and change trigger, not a claim of access to the supplier’s confidential formulation. ISO 11287 concerns defined green-tea requirements and does not by itself create a universal specification for every powdered or further-processed matcha product.

5. Sensory, colour and physical requirementsFor each characteristic, enter the target or limit, test or preparation method, sample temperature, lighting or instrument conditions, unit, tolerance, reference sample and pass/hold/reject rule. Mark subjective targets separately from measured limits.Words such as bright green, fine or smooth are not reproducible unless the comparison conditions are fixed. Instrument readings also cannot be compared when equipment, preparation, sample presentation or calculation differs.

6. Chemical, microbiological and residue matrixList only the tests required for the real destination and use. For each item, record the source of the requirement, product or commodity mapping, limit or buyer target, method, unit, reporting or quantification limit where relevant, sampling frequency and decision owner.There is no single worldwide matcha limit table. Codex and EU pesticide databases organise limits by pesticide and commodity mapping, while national and buyer requirements may differ. The template must preserve the source and scope instead of inventing global limits.

7. Packaging, coding, storage and shelf-life basisDefine net weight and tolerance, food-contact pack structure, closure, oxygen or light protection where required, outer case, pallet rules, lot and date coding, non-retail label information, storage conditions, transport precautions and the evidence supporting the stated shelf life.Packaging is part of product control for a sensitive powder. CXS 346-2021 provides a Codex reference for non-retail-container information, but final labelling and language requirements must still be checked for the destination and transaction.

8. Lot COA, sampling, retained sample and releaseState which fields the COA must show, how product and lot are linked, who samples, which sampling plan applies, which laboratory performs each test, what is retained, how long records and samples are kept, and who has release authority.The specification sets the requirements; the COA reports results for one identified lot. CXG 50, CXG 27 and ISO/IEC 17025 support disciplined sampling and laboratory competence, but none makes an unrepresentative sample or unrelated report valid.

9. Approved application sample and acceptance conditionsRecord the approved sample code, formula, dosage, preparation sequence, water or base, equipment, time, temperature, sensory attributes and measurable application checks. Identify which results are critical and which are development preferences.A powder can meet compositional requirements yet fail in the finished product. An approved sample is meaningful only with the conditions that produced approval; it is not a substitute for commercial-scale or repeat-lot verification.

10. Change notice, deviations and revalidationDefine which changes require advance notice, the notice period agreed by the parties, temporary-deviation approval, investigation and retest rules, complaint evidence, corrective action, and triggers for a new sample, application test or revised specification.A specification becomes obsolete when material changes are made without review. Change control protects both buyer and supplier by distinguishing an approved revision from an undocumented substitution or an emergency deviation.

Bulk matcha lot-release chain linking the approved specification, representative sampling, laboratory result, COA, application reference and buyer release decision. — The specification defines the rule. Sampling, testing, the lot COA and application review provide separate evidence for the release decision.

Use the specification as a controlled decision document

A product specification has a different job from a supplier-evaluation framework. Supplier evaluation asks whether the legal entity, production site, quality system, traceability and execution evidence justify working with the supplier. Once that gate is passed, the specification controls one defined product: what the parties call it, where and how it will be used, which requirements apply, how conformity will be measured, which lot evidence is required, and what happens after a change or deviation. The document should therefore sit inside purchase, quality and release workflows rather than exist only as a sales attachment.

Separate three kinds of entries. A limit is a pass/fail boundary supported by a legal, safety, functional or contractual need. A target describes the desired operating centre and may carry an agreed tolerance. A reference is contextual information, such as an approved sample, typical result or observation, and should not silently become a release limit. For every controlled entry, add the source, method, unit, conditions and decision owner. If the team cannot say how a field will be verified or what happens when it is missed, that field is not yet an executable specification.

Lock identity, document control and intended use first

Start with document control and product identity because every later test and certificate depends on them. Give the specification a unique ID and revision, name the buyer SKU and supplier code, state whether the product is pure matcha or a flavored or blended preparation, list the agreed ingredient declaration and physical form, and connect it to the commercial reference sample. When a contract party, producer, packer or exporter differs, keep those entity relationships in the supplier file; do not overload the product name with unverified corporate or origin claims.

Next, define the destination and application. Record whether the ingredient will be used in a hot dairy latte, cold oat drink, bakery mix, frozen dessert, industrial RTD or retail powder; the intended use rate; relevant formula components; mixing, heat, shear and holding conditions; packaging format; and expected storage path. This application brief is not marketing decoration. It determines which physical and sensory fields matter, whether further processing changes the risk analysis, and which destination controls the buyer must confirm before final approval.

Translate quality language into reproducible methods

Sensory and appearance requirements fail when they rely on adjectives alone. If colour matters, specify whether the decision uses a controlled visual comparison, an instrument value or both; record sample preparation, layer depth, lighting, background, instrument settings and allowed tolerance. If particle behaviour matters, distinguish a particle-size method from dispersion in the finished formula. If aroma and taste matter, identify the reference sample, preparation ratio, water or milk base, temperature, evaluation time and defect rules. A supplier and buyer should be able to repeat the procedure without guessing.

Analytical fields require the same discipline. A number without a method, unit and sampling basis may not be comparable. Record whether the value is a legal limit, buyer limit, target or report-only item; identify the applicable method or validated laboratory procedure; include the reporting limit or limit of quantification when it affects interpretation; and define what triggers hold, investigation, retest or rejection. Do not paste every value from a generic data sheet into the controlled specification. Include a test only when it supports identity, safety, legality, process performance, stability or an agreed buyer decision.

Build destination controls without inventing a global matcha table

The chemical, microbiological and residue block should be a project matrix, not a universal claim. GB/T 34778-2017 is a Chinese recommended national standard titled Matcha, while ISO 11287:2011 addresses green tea definition and basic requirements and expressly has its own scope. Neither should be presented as automatic proof that a product complies with every destination or finished-food category. Use standards as cited inputs, then ask the importer or qualified adviser to confirm the current destination rule, commodity mapping, test scope and release responsibility.

The Codex pesticide database and the European Commission’s pesticide resources illustrate why mapping matters: searches are organised around particular pesticides and commodities, and the applicable result depends on the selected classification and jurisdiction. The FDA Foreign Supplier Verification Programs are another destination-specific example: responsibilities sit with covered U.S. importers and depend on the food, supplier and applicable requirements. This template does not decide those legal questions. It provides fields for the rule source, date checked, classification, test method, limit, laboratory and named decision owner so the buyer’s qualified resources can complete the review.

Connect packaging, traceability, sampling and the lot COA

Define the commercial pack as carefully as the powder. Record primary and secondary materials, closures, net content, case and pallet configuration, coding format, storage and transport conditions, and any agreed light, moisture or oxygen protection. For non-retail containers, CXS 346-2021 is a useful Codex reference, but the parties still need to determine the destination’s mandatory information, language, importer details and transaction-specific records. A specification should distinguish packaging performance requirements from unverified shelf-life claims and state the evidence basis for any agreed shelf life.

Then connect the product to the lot-release chain. CXG 60 explains traceability as a tool within food inspection and certification systems; it does not itself prove safety or origin. CXG 50 addresses sampling principles, while CXG 27 and ISO/IEC 17025 support assessment of laboratory competence. Apply those ideas practically: define the lot, identify who takes which sample under what plan, require the COA to name the exact product and lot, list methods and units, identify the laboratory, retain a representative sample where agreed, and record who may release, hold or reject the lot. A COA for another SKU or a composite sample with unclear linkage cannot satisfy this chain.

Keep application approval and change control attached

Product-document conformity is not the same as finished-application performance. Preserve an application approval record next to the specification: approved sample code, formula, dose, preparation sequence, equipment, temperature, hold time, colour and sensory references, physical stability checks and any processing conditions that affected the result. For flavored matcha, record the agreed flavor direction and balance without exposing protected formula detail. If the buyer changes milk base, sweetener, acidity, thermal process or serving conditions, the prior result may no longer predict performance.

Specify change and deviation rules before the first order. At minimum, consider changes to tea base or key raw materials, formulation, flavor status, production site, critical process, equipment, key supplier, packaging, test method and coding. Decide which change needs documents only and which needs a new sample, application test, pilot or first-lot review. Define temporary-deviation approval, investigation, retest and corrective-action expectations. The goal is not to freeze all improvement; it is to prevent an altered product from travelling under an unchanged specification without buyer review.

Approve the template, then use it as the project handrail

Complete the downloadable template jointly across procurement, quality and R&D. Procurement owns commercial identifiers and ordering alignment; quality owns controlled limits, methods, sampling, laboratory and release logic; R&D owns the application conditions and reference sample; regulatory or importing resources confirm destination requirements. The supplier confirms feasibility, test method alignment, coding, packaging and change-notice capability. Mark unknown fields as OPEN with an owner and due date rather than filling them with assumptions. Sign or electronically approve one revision and attach it to the purchase specification.

XIAO TEA operates here as a custom flavored matcha specialist and professional B2B supplier: translating the buyer’s market and application brief into matcha-base and flavor matching, testing in the intended matrix, adjusting sweetness and aroma balance, and carrying the approved direction into scale-up and repeat-order controls. This page does not assert that a particular XIAO TEA site, certificate or batch has been independently verified. For a custom project, the current route is USD 1,000 for up to five flavor directions, 50 g per flavor, international courier included and two adjustment rounds after sample receipt; after commercial cooperation, USD 500 may be credited to the goods payment. MOQ is one metric tonne per approved flavor. Download the template, complete the known fields, and send one controlled brief to start the review.

CONTROL BOUNDARY

The specification states the agreed rule; it does not create evidence that the rule was met.

This template helps buyers and suppliers define one product and its acceptance process. It does not establish a universal matcha standard, validate a named factory, approve a destination classification, or prove conformity of a commercial lot. A lot-specific COA, representative sampling, competent testing, application validation and qualified destination review remain separate evidence steps. Leave a destination limit open until its source, scope, method and decision owner are confirmed.

Author: XIAO TEA Application & Commercial Team
Published: 1 September 2026
Review trigger: Commercial terms, application evidence, regulatory sources or process scope changes

REFERENCE SOURCES

Official and primary references

Questions buyers ask next

What is the difference between a bulk matcha specification and a COA?

The specification is the approved, version-controlled agreement that defines requirements, methods, tolerances and decision rules for a product. A COA reports test results for one identified lot. A COA should reference the relevant specification, but it cannot replace it.

Can I copy one pesticide and microbiological table for every destination?

No. Requirements depend on jurisdiction, product or commodity mapping, finished-food category and intended use. Record the official source, date checked, applicable classification, limit, method and reviewer for the actual project.

Should sensory colour and flavor be written as numerical limits?

Only when a reproducible method and decision rule exist. Visual or sensory acceptance can use an approved reference and controlled preparation conditions. Instrument values need the instrument, method, sample preparation, unit and tolerance. Do not create false precision.

Does an approved 50-gram sample become the product specification?

No. The sample is a reference under recorded application conditions. The specification must separately define identity, methods, tolerances, packaging, lot evidence and change control, followed by scale-up and first-lot verification.

Who should approve a bulk matcha specification?

Approval usually requires the buyer’s quality owner, procurement owner and relevant R&D or application owner, with regulatory or importing review where destination rules are involved. The supplier should confirm feasibility and method alignment. Named roles are more useful than an unsigned data sheet.