How to Write a Produce Purchase Specification Buyers and Suppliers Can Check

A produce purchase specification should make one question easy to answer at receiving: does this delivered lot match what the buyer and supplier agreed?

That requires more than a product name and a general request for “good quality.” A usable specification turns the purchase request into a shared checking record. It identifies the product, defines the relevant acceptance criteria, states how the lot will be checked, and gives both sides a way to record exceptions before a disagreement becomes difficult to reconstruct.

The aim is not to impose one universal grade, pack or inspection method. Requirements depend on the commodity, intended use, route to market, contract and applicable local rules. For China-focused transactions, overseas procurement guides can help structure a document, but they do not establish Chinese grading, labelling, food-safety or contractual requirements.

Start with the product and the intended transaction

Begin by defining what is being purchased before defining whether it is acceptable. “Tomatoes,” “leafy vegetables” or “apples” may not be sufficiently precise where variety, maturity, processing state or delivery form affects the transaction.

A product identification section can include:

• Commodity name.
• Variety, type or cultivar where relevant to the buyer’s use.
• Intended use, such as retail sale, foodservice preparation, processing or redistribution.
• Delivery form: loose, pre-packed, whole, trimmed, washed, chilled or another clearly described form.
• Origin or growing-area requirement, if this is a contractual requirement rather than a preference.
• Purchase order number, contract reference and specification version.
• Delivery date, delivery location and agreed delivery window.

The value of these fields is operational. They allow warehouse staff, quality staff, procurement teams and supplier dispatch staff to confirm they are working from the same request.

A South Carolina guide to procuring local produce provides a useful example of specification fields such as product name, description or variety, size, grade, pack size and ripeness. Its form should not be treated as a mandatory model outside its original context. The practical lesson is that the product description must resolve the decisions that affect acceptance.

ACA working principle: if a receiving team could reasonably ask “which type?” or “in what form?”, the specification is not yet complete enough to check.

Turn quality expectations into checkable acceptance criteria

Quality language works best when it distinguishes product attributes from acceptance thresholds. An attribute is what the parties are looking at: size, colour, maturity, external condition, internal condition, cleanliness or defect type. A threshold states what is acceptable for that attribute.

For example, “high quality onions” is an expectation but not a checking rule. A more usable entry might identify the relevant observable criteria and state the agreed reference, range or limit. The actual threshold should be negotiated for the product and transaction rather than copied from an unrelated trade.

Separate the following fields where they matter:

Guidance from North Carolina State University on fresh-produce product specifications distinguishes sorting by size and colour from grading based on defects. That distinction is useful because it prevents a document from treating all quality terms as interchangeable. A lot can meet a size requirement while failing a condition requirement, or meet a grade reference while arriving in a pack configuration that the buyer cannot use.

If the parties use a formal grade or commodity standard, name it accurately and attach or link the applicable version in the commercial records. Do not assume that a standard applies merely because it is common in another market. A buyer standard, a local trade practice and a regulatory requirement may overlap, but they are not automatically the same thing.

Specify units, pack configuration and handling requirements

The right product can still fail the transaction if it arrives in the wrong unit or container. The specification should make the ordered quantity and usable delivery format clear enough for dispatch, transport and receiving teams.

Record the purchase unit first: kilograms, cartons, pieces, bunches, trays or another agreed unit. If a pack has both a nominal weight and a count, state which measure controls the transaction if they differ. Avoid leaving staff to infer whether a “case” means a fixed net weight, a variable-weight carton or a particular item count.

Then define the pack and delivery configuration:

• Net weight, gross weight or count basis, as applicable.
• Number of inner packs and units per inner pack.
• Outer container type and condition requirement.
• Label information needed for receiving and traceability.
• Pallet arrangement, stacking limit or delivery configuration where it affects safe handling.
• Temperature or handling instruction where both sides have a practical way to verify it.

The Illinois farm-to-school procurement guide notes that specifications can designate packaged-product size or weight and that container manageability should be considered. This is a sound operational prompt: the lowest-cost pack is not necessarily the most usable pack if it cannot be safely received, stored or moved.

Official purchasing documents can also address containers and packing. For example, the USDA AMS bulk-products specification includes packing provisions for its own procurement context. It is not a general rule for fresh-produce transactions, but it illustrates why packing details belong in a specification rather than in an informal message after the order is placed.

Agree how inspection will be carried out

A quality target without an inspection method leaves too much room for retrospective interpretation. The specification should state how compliance will be assessed, at least at a level proportionate to the value and risk of the transaction.

Set out the following points:

1. Inspection point and timing. State whether the check occurs before loading, at dispatch, on delivery, after unloading or at another agreed stage.
2. Lot definition. Identify what constitutes one lot for the purpose of checking: a delivery, pallet, vehicle load, production batch or another stated unit.
3. Sample selection approach. Describe how samples will be selected. The approach might be simple for a small routine delivery and more structured for a higher-risk or high-value purchase.
4. Checks performed. Match each check to the criteria in the specification: pack count, weight, labelling, visible condition, temperature record or another agreed measure.
5. Authorised people. Name the role, not necessarily an individual, authorised to accept, conditionally accept, hold or escalate a lot.
6. Records. State what will be retained: receiving record, delivery note, photographs, measurement sheet, temperature record or written exception notice.

A California commodity-standard document refers to inspection, condition and packaging details in its own purchasing setting. See STD. 12. The broader lesson is that condition and packaging need a method of verification, not just a statement of intent.

Photographs can help show visible conditions, but they do not prove every issue. Their usefulness depends on lighting, timing, the defect and whether the image can be connected clearly to the lot. Similarly, visual checks may be suitable for some arrival conditions but not for every internal or later-developing issue. The parties should agree what the chosen check can establish and what it cannot.

ACA recommendation: use a sampling plan that your team can actually perform and record. Do not describe it as a legally required method unless an applicable rule has been verified for the product and jurisdiction.

Document exceptions, disputes and changes to the order

An exception record is not a blame document. It is the handover record for a lot that does not fully match the original specification, or for an order that has changed after confirmation.

For each exception, record:

• Purchase order and specification version.
• Lot, pallet, carton or delivery identification.
• Date, location and person making the observation.
• Observed issue stated in neutral terms.
• Quantity or proportion affected only where it was actually measured or counted.
• Supporting evidence, such as photographs or receiving records, where useful.
• Immediate handling decision: accept, conditionally accept, segregate, return, replace or escalate, as agreed by the parties.
• Decision-maker and time of decision.
• Follow-up action and revised document reference if the order changes.

Keep substitutions and changes under version control. If a buyer agrees to a different variety, pack, maturity stage or delivery date, record the new agreement in writing and identify which specification version governs the revised lot. This protects both parties from later disagreement about whether a variation was approved or merely discussed.

This framework does not determine legal rejection rights, payment deductions, liability or dispute outcomes. Those matters depend on the contract and applicable law. The useful operational step is to preserve a clear factual record before commercial or legal discussions begin.

Use a one-page specification and pre-delivery check

For routine trade, a one-page specification can be more useful than a long document that no one consults at dispatch or receiving. Attach additional pages only where the product or transaction needs them, such as defect definitions, diagrams, approved labels or detailed sampling instructions.

A practical one-page layout can include:

1. Product identity and intended use.
2. Purchase order, version and delivery details.
3. Grade, size, maturity, condition and defect criteria.
4. Unit of purchase and pack configuration.
5. Labelling, handling and delivery requirements.
6. Inspection point, method, responsible role and record.
7. Exception, substitution and change-control process.
8. Buyer and supplier confirmation fields.

Before dispatch and before receiving, both teams can use the same short check:

• Does every requirement have a unit, threshold or named reference?
• Does every stated quality criterion have a practical way to inspect it?
• Is the delivery unit and pack configuration unambiguous?
• Are the correct specification version and purchase order shown on the records?
• Does the team know who may accept, hold or escalate a non-conforming lot?
• Is there a clear record path for exceptions and agreed changes?

The next step is to pilot the specification on one recurring product and one supplier relationship. Compare the document against the questions that arise at dispatch and receiving, then revise only the fields that caused uncertainty. A specification is working when it supports a calm, traceable decision at the point of handover—not when it merely looks complete.