---
id: KB-CS-036
url: https://app.codecontract.io/help/use-cases-by-sector/farming-cooperatives
idioma: en
categoria: casos-por-sector
subcategoria: agroganadero
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CS-025, KB-AL-008]
citadoPor: [KB-CS-034]
---

# Farming cooperatives

_Many members contributing, one brand answering for it, and a season where everything happens at once._

**Responde a:** cooperative member documentation · traceability of member deliveries · farming cooperative season paperwork · member certifications

A cooperative has a documentary structure unlike a normal company's: the product is contributed by dozens or hundreds of members, each with their own holding and paperwork, and the one answering to the customer and to an inspector is the cooperative.

## The three layers to sustain

| Layer | Whose it is | What is asked for |
| --- | --- | --- |
| Each member's holding | The member's | Identification, treatments, certifications where applicable |
| Intake at the cooperative | The cooperative's | What each member delivered, when, and what was done with it |
| The product that leaves | The cooperative's | Which batch contains which deliveries and where it went |

> [!IMPORTANT]
> The middle layer joins the other two and decides whether the cooperative can answer at all. If intakes are recorded only to settle with the member — weight and quality for payment — it serves the accounts and not traceability: the link between that intake and the outgoing batch it ended up in is missing.

## The season's own problem

> [!WARNING]
> Everything arrives at once, from people who do not work at the cooperative. Asking a member mid-harvest to supply a certificate is the worst possible combination of timing and recipient. **Member documentation is renewed outside the season**, with months of margin, and during the season you only check that it is there — leave it until the trailer arrives and it will not come.

## What works with members

1. **An annual request, simple and by phone** — Most will never log into any system: they supply from the link and that is it.
2. **With spaced reminders and in their usual language** — And with document names they recognise, not administrative jargon.
3. **Checking before the season opens** — And a clear list of who is current and who is not.
4. **And a written decision for whoever is not** — You receive them anyway, segregate their product, or do not receive them. All three are options; deciding on the spot is not.

## What the cooperative's customers ask for

**En corto**

- Traceability to the holding, not to the cooperative.
- That members' certifications were valid on the delivery date.
- And a drill: they pick an outgoing batch and want to reach the plots.

That drill is the real test of the system, and it is answered in minutes or in days depending on what was recorded at the weighbridge during the season.

> [!NOTE]
> What documentation each member must hold and what the cooperative must keep depends on the product, the certification scheme and the region, and it gets updated. **Confirm that with your technical adviser or certifier**; this describes how to organise collection so that nobody has to be chased mid-season.

**What about members who do not use a phone?**

Collect on paper and have whoever attends at the cooperative upload it: what matters is that it links to the member.

**Must documentation of departing members be kept?**

Yes, for the period applicable to what they delivered while they were members.

**Can field technicians be given access?**

Yes, scoped; they are usually the fastest at spotting what is missing.

## Ejemplos

**A cooperative asks members for certificates once harvesting has already started.**

- Moves the documentation campaign to the preceding months
- Checks before opening and decides in writing what to do with those not current

→ The season is for receiving product, and the customer's traceability drill is answered in minutes.

**A cooperative with three hundred members starts the season not knowing whose field records are current.**

- Checks everyone's status before the first delivery
- Requests and chases automatically those who are missing
- Blocks intake only for those who genuinely cannot deliver

→ The season starts with most members current and the exceptions are handled by name.

**A member delivers and their documentation expired in March.**

- Records expiries per member

→ The warning arrives before collection.

**A client asks you to evidence a consignment's origin.**

- Checks which members made up that batch

→ You answer per consignment.

**Field records arrive on paper in five formats.**

- Requests specific documents to a single destination

→ What is received is comparable.

**Chasing three hundred members occupies two people.**

- Lets the reminder go out on its own

→ The two people review instead of nagging.

**A small member does not use email.**

- Sends them the link on the channel they do use

→ They deliver anyway and it is recorded.

**Deliveries from certified and uncertified members get mixed.**

- Records what went into each batch

→ You can say what came from where.