Institutional fresh produce supplyProcurement guide

Fresh Produce Procurement for CSR Nutrition Programmes

Fresh-produce procurement works best when programme teams separate programme objectives from the supply brief. FPS supplies produce; programme design remains with the organisation.

Fresh fruit arranged for institutional produce procurement
Quick overview

Start with a usable brief.

  • Separate programme goals from the supplier’s deliverable.
  • Compare quotations using the same products, quantities and packing basis.
  • Keep seasonal alternatives open for review rather than assuming availability.
  • Record responsibilities, approvals and handover details before ordering.
01

Define the procurement scope

Begin by stating exactly what is being procured: fresh fruit, vegetables or a combination of fresh produce. Add the proposed location, date or frequency, approximate quantity and packing need. This gives potential suppliers a comparable starting point and keeps the conversation centred on an operational requirement.

The programme team may have wider nutrition or social objectives, but those objectives should not be presented as supplier deliverables unless they genuinely are. FPS supplies fresh produce and can discuss requirement-based assortments. Programme design, beneficiary management, nutritional assessment, catering, cooked meals and impact measurement remain outside this supply service.

  • Produce category and preferred items
  • Proposed location and supply pattern
  • Approximate quantity and packing context
  • Named procurement and receiving contacts
Planning note

A short, precise scope is more useful than a broad request that combines supply, programme design and distribution responsibilities.

02

Write specifications that allow a fair review

A useful specification distinguishes mandatory conditions from preferences. If certain products are essential, list them. If the organisation can review seasonal alternatives, state the limits of that flexibility. Ask suppliers to identify what they are quoting rather than using a broad phrase such as assorted fruit without further explanation.

Domestic & Imported Produce Options may be discussed where relevant, but origin, variety and availability should not be assumed. The same principle applies to packing. Describe the outcome needed—grouped supply, loose produce or another presentation requirement—then ask what can be offered for the stated quantity and schedule.

  • Required products versus preferred options
  • Acceptable substitution process
  • Packing outcome the programme needs
  • Information suppliers should include in their response
Planning note

Specifications should support comparison without forcing an arrangement that has not been checked for availability or feasibility.

03

Compare quotations on the same basis

A price can only be understood alongside scope. Compare the products or assortment basis, quantity, packing, delivery location, schedule and stated commercial terms together. A lower figure for a different product mix or packing method is not a like-for-like comparison.

Create a simple comparison sheet using the requirements in the brief. Record clarifications beside the relevant item rather than relying on separate message threads. If a quotation permits substitutions, note who approves them and when. Procurement teams can then review the complete offer without turning unverified assumptions into commitments.

  • Quoted assortment or product list
  • Quantity and unit basis
  • Packing and delivery inclusion
  • Validity, payment and change terms stated by the supplier
Planning note

FPS confirms commercial terms for the reviewed requirement; website examples should not be treated as a quotation.

04

Plan for season and availability

Fresh produce is not a fixed manufactured inventory. Season, market availability, condition and the requested schedule can affect suitable options. A procurement process should allow the supplier to flag unavailable items and propose alternatives for approval instead of silently changing the assortment.

This does not mean the brief should be vague. State the programme’s priorities, such as required produce categories or products that cannot be substituted, and define where flexibility is possible. Requirement-Based Assortments are most useful when the decision process is explicit and the final mix is confirmed before supply.

  • Items that must remain unchanged
  • Categories where alternatives may be reviewed
  • Who can approve a substitution
  • How the confirmed assortment will be recorded
Planning note

Never communicate an alternative as approved until the authorised programme or procurement contact has accepted it.

05

Set clear roles from approval to handover

Procurement approval is only one part of a successful supply. Identify who sends the final order, who receives the produce, who checks the handover and who responds if a question arises. Where a CSR team works with an implementing organisation, both sides should understand which contact owns each step.

The receiving location also needs practical information: proposed timing, access instructions and a contact who will be available. If the programme will distribute produce onward, that handling belongs to the organisation unless a different service has been explicitly agreed. Fresh-produce supply should not be described as catering, ration-kit delivery or end-to-end programme operation.

  • Authorised approver and ordering contact
  • Receiving person and location instructions
  • Handover checking responsibility
  • Organisation’s plan after receipt
Planning note

Multi-party programmes benefit from one confirmed version of the requirement rather than separate instructions from different teams.

06

Document the final supply decision

Before issuing approval, ensure the final record contains the accepted products or assortment basis, quantity, packing, location, proposed schedule and commercial terms. Note any permitted alternatives and the process for approving changes. This creates a clear reference for procurement, programme and receiving teams.

Recurring programmes should also define how future requirements are reviewed. Quantities, locations or preferred products may change, so avoid treating the first discussion as a permanent guarantee. A fresh confirmation process keeps later supplies connected to the organisation’s current requirement and the supplier’s reviewed availability.

  • Accepted scope matches the latest brief
  • Approvals are recorded by the responsible team
  • Receiving information is current
  • Future changes have a clear communication path
Planning note

Each supply remains subject to the requirement, availability, location and terms confirmed for it.

Before supply is confirmed

A practical confirmation checklist.

  • Scope covers produce, quantity, packing and location
  • Programme services are separated from produce supply
  • Mandatory and preferred items are distinguished
  • Quotation comparisons use the same basis
  • Substitution approval is defined
  • Procurement and receiving contacts are named
  • Final scope and commercial terms are recorded
  • Recurring requirements include a review process
Continue reading

Related institutional guides

Plan with FPS

Discuss an institutional produce requirement.

Request a supply quote