Financing a producers' platform and local food logistics with LEADER

What is this guide for?

A territorial food platform is not just a warehouse where products are stored. It is an organisation that makes it possible for a scattered agricultural supply to regularly meet buyers who expect reliable volumes, schedules, quality, traceability and invoicing. It can bring together collection, receiving, inspection, storage, order preparation, batch consolidation, delivery and order management. Depending on the territory, it can also organise commercial relationships between producers, processors, shops, restaurants, canteens, grocery stores, markets and consumers.

The project can address several difficulties: producers each delivering small quantities separately; buyers giving up on working locally because orders are too fragmented; long, under-filled delivery rounds; under-used storage equipment; or public procurement contracts that are hard for a single isolated farm to serve. But a platform does not automatically fix these problems. It also adds costs, organisation and responsibilities. The application must therefore prove that the collective service is useful, actually used and economically sustainable.

LEADER can be a possible source of funding when the project contributes to the local development strategy of the Local Action Group (LAG). However, it is neither a uniform national funding window nor an automatic right to a grant. Priorities, eligible applicants, expenses, rates, caps, timelines and obligations differ depending on the territory and the call for projects. This guide offers a design and verification method; it does not replace the LAG's action sheet (fiche-action) or the written instructions of the managing authority.

1. Define the service before choosing the building or the vehicle

Start by describing the logistics problem you want to solve. Avoid starting with a wish list of equipment — a cold room, a truck, software, a loading dock — without demonstrating the need. An equipment request is not a service strategy.

First formulate a simple statement: « We consolidate products from X producers to deliver to Y buyers in Z municipalities, at a defined frequency, with measurable service quality ». If you cannot fill in this sentence with realistic figures, the project is still at the idea stage.

Next, map the current flows: where the farms, storage sites, customers and points of sale are located; who currently collects products; how many kilometres are travelled; on which days and at which times; what volumes are available by season; which goods require controlled temperatures; and which products can be grouped together without losing quality. A map at the scale of the local living area is often more useful than a general presentation on local food.

Survey producers and buyers separately. Ask producers about the quantities they can actually sell, weeks of availability, packaging, harvest constraints, the minimum acceptable price and their capacity to prepare orders. Ask buyers about weekly volumes, receiving days, ordering rules, specifications, traceability requirements, target prices and the consequences of an incomplete delivery. An intention to support local agriculture is not the same as a purchasing commitment.

The deliverable of this first step is a flow diagnosis: participating producers, potential buyers, product families, volumes by period, distance, frequency, expected services and current difficulties. It should also identify flows that are not compatible: dry goods versus fresh products, goods requiring a cold chain, batches of different sizes, cleaning constraints or incompatible schedules.

2. Choose the right logistics model

There is no single model. Compare several scenarios before sizing the investment.

Scenario A — Coordination without a warehouse. An organisation centralises orders, availability, invoicing or scheduling, but products go directly from the farms to the buyers. This model limits capital investment and suits situations where volumes remain low or buyers accept direct deliveries. It requires a good information system and precise coordination, but avoids paying for premises and equipment that would be little used.

Scenario B — Lightweight consolidation point. Products are dropped off at a site at coordinated time slots, then picked up by buyers or grouped onto a delivery round. This could be an existing building, provided it is suitable for the products, the flows and the applicable rules. This model sometimes reduces kilometres but adds handling, receiving and inspection operations. Care must be taken that the consolidation point does not become just one more stop that increases costs without actually consolidating deliveries.

Scenario C — Platform with storage and order preparation. The organisation receives, stores, prepares orders, consolidates batches and organises dispatch. This service can improve reliability for buyers, but requires regular volumes, rigorous stock management, suitable equipment, hygiene procedures, staff and sufficient cash flow. Sizing must be based on seasonal peaks and troughs, not just the average annual volume.

Scenario D — Pooled logistics with a service provider. A transport company or a specialised operator carries out all or part of the collection and delivery. The collective retains the commercial relationship and coordination. This model turns some investment expenses into service expenses. It may be preferable if the delivery rounds are complex or if activity has not yet reached a stable volume. Compare the full cost of the service provider with that of an in-house fleet, including driver, maintenance, insurance, energy, capital investment, replacement and management time.

Scenario E — A platform attached to an existing facility. A slaughterhouse, a cooperative, a vegetable-processing unit, a transport company, an association or a public facility can sometimes provide part of the necessary functions. A service agreement can avoid building new infrastructure. However, check the availability of time slots, compatibility of products, liability in case of damage, and the operator's capacity to host several users.

To compare the scenarios, build a matrix with at least: initial investment, annual cost, cost per order, cost per kilogram or pallet, kilometres, fill rate, preparation time, losses, service level, staffing needs, regulatory risks and capacity to evolve. Make the assumptions and uncertainties explicit. A less spectacular but reversible scenario may be more robust than heavy, under-used equipment.

3. Size volumes and seasonality

The volume announced by partners must be translated into operational units. Distinguish between annual volume, average weekly volume, seasonal peak, volume per delivery round, and the volume actually confirmed by orders. Kilograms are not always enough: a pallet of dry goods, crates of fragile vegetables and fresh parcels do not take up the same space and do not require the same operations.

Build a calendar by product family. For each week or month, estimate the quantity available, the number of active producers, the buyers served, storage needs, delivery frequency and preparation constraints. Identify periods when the platform risks being empty and those when it will be saturated. Both situations have a cost: one spreads fixed costs over little volume, the other can cause delays, errors, losses and the need for emergency solutions.

Calculate a utilisation rate for each critical resource: square metres of storage, refrigeration capacity, preparation hours, vehicle capacity, dock slots. Do not size every resource for the absolute peak if it can be handled by a cheaper temporary solution. Conversely, do not forget cleaning, flow separation and circulation needs, which reduce theoretical capacity.

Formalise user commitments. A letter of interest can demonstrate that a need exists, but it does not secure volumes. For key partners, seek agreements or contracts specifying indicative volumes, ordering conditions, quality, prices or service fees, withdrawal terms, responsibilities and exit conditions. Do not present commercial projections as commitments that have already been signed.

4. Build an economic model that reveals the real costs

The operating statement must distinguish commercial revenue, service fees, any membership contributions, public contributions and one-off funding. An investment grant can help finance equipment; it does not guarantee that the organisation will be able to pay for staff, energy, fuel, maintenance and insurance every year.

List the fixed costs: rent or building charges, depreciation, insurance, software subscription, administrative costs, contracted maintenance, permanent salaries and compliance costs. Then estimate the variable costs: handling, packaging, consumables, fuel, volume-related energy, cleaning, breakage, losses, payment commissions, subcontracting and overtime during peak periods.

Allocate costs across services. On-farm collection, order preparation, cold storage, delivery and commercial management do not use the same resources. If all users pay a single commission with no cost analysis, costly activities may end up being unintentionally subsidised by the others. This situation can weaken the project and create conflicts among members.

Test several billing bases: a fee per order, a commission on turnover, a rate per crate or pallet, a price per kilometre, a buyer subscription, a producer membership fee, or a combination of these methods. Each formula has different effects. A commission on turnover can penalise low-margin products; a per-order price can be disproportionate for small orders; a per-kilometre rate does not always reflect handling time. Simulate costs for small, medium and large users.

Calculate the break-even point: the level of activity at which recurring revenue covers recurring costs. Build a cautious scenario, a central scenario and a favourable scenario. The cautious scenario must include volumes lower than forecast, start-up delays, rising transport costs and a slower ramp-up. If viability depends on an immediate, significant increase in volumes, explain how it will be achieved and what decisions will be made if it does not materialise.

Working capital needs are particularly important when the platform pays producers before being paid by buyers. Model payment terms, stock levels, deposits, disputes, credit notes and delays. Growth can worsen cash flow: more orders sometimes means more receivables and more stock before cash is collected. Plan for a reserve and customer credit rules; do not confuse accounting profitability with cash availability.

5. Define governance and the allocation of responsibilities

A multi-stakeholder platform must decide who makes commercial decisions, who owns the equipment, who hires staff, who invoices, who bears losses and who handles complaints. These questions must not be left implicit.

Compare the possible legal forms: a cooperative, a commercial company, an association, a social and solidarity economy structure, a local authority, or a contractual grouping. The choice depends on the nature of the activity, the role of producers, risk-sharing, investment needs and the relationship with buyers. There is no status that is automatically suited to every territorial food project. Seek advice from an accountant, a support network or a lawyer if the financial flows and responsibilities are complex.

Establish governance that gives users a voice while still allowing fast decisions. A steering committee can monitor strategy and indicators, while operational management handles orders, teams and incidents. Set admission rules, priority criteria for periods of limited capacity, dispute resolution, conflicts of interest and the conditions for a member's withdrawal.

Clarify ownership of commercial data: producer availability, prices, volumes, customer files, order history and traceability data. Users must know who can access it, for what purpose and under what rules. Trust is a condition for the platform to function; a platform that uses its members' data without clear rules risks losing the very producers it was meant to serve.

6. Hygiene, traceability and the cold chain: build in the obligations from the design stage

The applicable regime depends on the products, the operations actually carried out, the customers and the role of each operator. Storing packaged products, repackaging goods, preparing orders, transporting refrigerated products or processing raw materials do not raise exactly the same requirements. Do not assume a project is exempt just because it involves short food supply chains or small quantities.

Before renting or fitting out premises, describe the product flows and planned operations, then check the obligations with the relevant authorities and the health and safety contacts concerned. The rules may include procedures based on HACCP principles, requirements for cleaning, temperature control, pest control, separation of activities, traceability, allergen information and, depending on the case, registration or approval procedures. The details depend on the specific situation; they must be confirmed for the actual project.

Map out the circulation routes: receiving, inspection, storage, preparation, dispatch, container returns, waste and cleaning. Avoid crossovers that could contaminate products or cause errors. Define responsibilities in the event of a cold-chain break, a damaged parcel, a refused delivery or a batch recall. A contract should specify who decides on withdrawal, who contacts customers, who keeps the records and who bears the costs.

For refrigerated or frozen products, choose equipment based on the products and volumes, then document temperature monitoring, alarms, maintenance and backup solutions in case of breakdown. A refrigeration unit alone is not enough to guarantee control of the cold chain: procedures, trained staff in charge and recorded evidence are also needed.

Traceability must link the supplier, the batch, the quantities, the dates, storage, preparation and the recipient. Run a traceability exercise before launch: can you quickly identify all the customers who received a specific batch? Software can help, but only if users enter reliable data and follow shared procedures.

7. Choose digital tools based on operations

Order management software, an ERP, a traceability tool or a delivery-round app should not be purchased before the processes have been defined. Start by mapping the full cycle: published availability, order, confirmation, preparation, dispatch, proof of delivery, invoice, payment and complaint handling.

Check which functions are actually needed: a catalogue with seasonality, recurring orders, management of units and packaging, stock by batch, dates, prices per customer, document generation, accounting integration, temperature tracking where relevant, preparation by delivery round and data export. Ask for a demonstration based on a real case from the territory, not just a sales presentation.

Evaluate the total cost over three to five years: licence, configuration, data migration, training, hardware, support, updates and any per-transaction fees. Check reversibility: can you retrieve the data in a usable format if the provider changes its prices or stops its service? A simple solution that is used well is often better than a sophisticated tool that producers and buyers work around.

Plan a pilot period with a limited number of producers, buyers and product references. Measure the error rate, data-entry time, incomplete orders and administrative workload. Do not switch over the whole operation until the essential processes have been tested.

8. Design genuinely efficient delivery rounds

A delivery round should not be judged solely on the number of kilometres. Loading times, delivery windows, waiting times, empty return trips, traffic constraints and product specifics must all be factored in. A very long round serving many customers may seem efficient but can generate delays and excessive use of working time.

Group deliveries by compatible zones and time slots, without promising a frequency that volume does not justify. Set cut-off times for orders and changes. Late orders disrupt preparation and can generate extra kilometres. Buyers must know the rules and the consequences of exceptional orders.

Measure the vehicle fill rate, cost per stop, cost per crate or kilogram delivered, empty kilometres, adherence to time slots and the number of incomplete deliveries. Compare delivery rounds with each other, taking into account density and the nature of the products. For remote areas, a relay point or a different frequency may be more realistic than daily delivery.

Pooling resources does not mean that every producer must use every service. A remote producer with a small volume can be served by a local partner or a dedicated delivery day, while large volumes follow a different circuit. The rule must be transparent to prevent a small number of customers from absorbing capacity to the detriment of others.

9. Prepare a credible LEADER application

The first step is to contact the LAG covering the project's territory. Present a short note: the problem observed, beneficiaries, area served, envisaged logistics model, volumes, partners, indicative budget, timeline and expected results. Ask whether the project matches a priority of the local strategy and which action sheet (fiche-action) might be relevant.

Ask for an explicit answer on the following points: can the intended applicant submit a project? Are the type of activity and the beneficiaries compatible with the call for projects? Are equipment, works, services, studies, staff costs or communication expenses eligible? From what date can expenses start? What supporting documents and competitive tendering rules apply? Are there thresholds, caps, rates or co-financing obligations? How will the project be selected and on what criteria?

Do not transpose to your own territory a rate announced by another LAG. Rules can vary depending on the local strategy, the call for projects, the category of beneficiary, the applicable aid scheme and the nature of the expense. Confirmation must be obtained from the competent authority and kept in the file.

The application must explain the territorial usefulness beyond the purchase of equipment. Show who will be served, what collective problem will be solved, how producers and buyers will participate, what results will be measured and how the service will continue after the grant. A more convincing application compares solutions, acknowledges risks and presents evidence of use rather than promising undocumented growth.

Prepare a budget separating studies, works, equipment, digital tools, services, operating costs and recurring expenses. For each item, state the need, the calculation method, the quote, the date, the amount excluding or including tax depending on the applicable treatment, and any associated revenue or contributions. VAT rules, recovery and budget presentation must be checked according to the applicant's status.

10. Combine LEADER with other funding without counting the same expense twice

Depending on the nature of the project and the calls for projects open, it may be worth looking at regional schemes, aid for agricultural or agri-food investments, cooperation programmes, calls related to sustainable food, local authority funding, or FranceAgriMer tools. ADEME may also be relevant for certain environmental topics, such as waste reduction or energy efficiency, but only if the scheme and the project match its criteria.

Build a funding matrix indicating, for each funder, the purpose, the eligible beneficiary, the targeted expenses, the submission date, the authorised start date, the published rate or cap, the required documents and the status of the application. Do not list a grant as secured until it has actually been awarded. Distinguish between confirmed, requested, planned and purely exploratory funding.

The same expense cannot be funded beyond its eligible cost, nor declared in incompatible ways to several funders. Rules on combining aid, State aid, public co-financing, publicity obligations and controls depend on the situation. Ask funders how to present a combined financing plan and keep their answers. Do not artificially split an invoice to get around the rules.

Plan a fallback scenario if co-financing is not obtained: reducing capacity, leasing rather than buying, pooling with existing equipment, starting with a pilot, or postponing certain investments. It is better to present a scalable and sustainable project than a structure whose balance depends on uncertain funding.

11. Measure useful results, not just expenses

Indicators must be used to steer the activity. Counting the equipment purchased or the meetings held does not demonstrate that the service works. Choose a maximum of about ten indicators, each with a definition, a source, a frequency and an owner.

Possible operational indicators: number of active producers, number of regular buyers, volume delivered by product family, share of complete orders, adherence to time slots, fill rate, average cost per order, kilometres per unit delivered, loss rate, complaint rate and average payment time. Possible territorial indicators: number of municipalities served, share of small farms using the service, outlets created or maintained, volume of local products in partners' purchases, and documented reduction in redundant trips.

Establish a baseline before launch. If you want to claim that the platform reduces kilometres or emissions, compare actual delivery rounds before and after, specifying the assumptions and the scope. An increase in volume delivered can increase total kilometres while reducing kilometres per kilogram: both measures must be interpreted correctly.

Set realistic targets for the first six months, then for the second year. Launch often involves adjustments; distinguish ramp-up indicators from steady-state targets. If results fall short of expectations, the steering committee must decide on concrete actions: change time slots, review pricing, cut certain delivery rounds, recruit an additional buyer, or suspend a loss-making activity.

12. Common risks and concrete responses

Overestimated volumes. Partners express interest but order little. Response: test volumes over a pilot period, request detailed letters of commitment, and set volume thresholds that trigger investments.

Too much equipment too soon. The cold room, truck or building is sized on an optimistic assumption. Response: compare leasing, subcontracting and pooled equipment; phase purchases; plan a scale-up decision based on observed results.

Underestimated delivery cost. Calculations overlook waiting times, returns, small orders and management costs. Response: time pilot delivery rounds and calculate a full cost per service.

Dependence on a major buyer. Losing a single contract puts the whole activity at risk. Response: measure revenue concentration, gradually diversify outlets, and plan scenarios in case of termination.

Health and safety rules discovered too late. The chosen building or flow requires costly adaptations. Response: validate operations and requirements before signing a lease or starting works.

Insufficient cash flow. Producers must be paid before customers settle their invoices. Response: model payment terms, plan appropriate advances or credit lines, limit delays, and set up a payment-reminder procedure.

Unclear governance. Members dispute pricing or delivery priorities. Response: adopt written rules, a decision-making mechanism and a complaints procedure before start-up.

Unsuitable digital tool. Users keep sending orders through scattered messages. Response: simplify the process, train users, test the tool and appoint someone responsible for data quality.

13. 90-day action plan

Days 1 to 15 — scope the need. Identify a project leader and a small group of producers and buyers. Map current flows, gather volumes, availability periods, delivery constraints and the most costly problems. Produce a two- to four-page diagnostic note, with explicit data and limitations.

Days 16 to 30 — test demand. Survey buyers using a shared questionnaire. Obtain forecasts by product family, schedules and receiving conditions. Ask producers for realistic volumes and gradual commitments. Identify partners who can provide warehousing, transport or preparation functions without new investment.

Days 31 to 45 — compare scenarios. Build at least three models: coordination only, lightweight consolidation, and an equipped platform. Compare full cost, service quality, risks, capacity and flexibility. Organise a pilot delivery round or an order simulation to measure actual preparation, loading and delivery times.

Days 46 to 60 — secure the model. Choose the governance, billing rules, responsibilities, ordering procedures, quality criteria and payment terms. Check health and safety obligations, premises needs, insurance, security and applicable authorisations. Build the operating and cash flow forecast with cautious, central and favourable scenarios.

Days 61 to 75 — verify funding. Present the project to the LAG before any irreversible commitment. Obtain the action sheet, the list of required documents and the rules on when the operation may start. Identify any other possible funders, check combination rules, request comparable quotes, and distinguish investment expenses from recurring costs. Do not record hoped-for aid as certain.

Days 76 to 90 — decide and document. Finalise the financing plan, partner agreements, timeline and indicators. Carry out a risk review with named owners. Explicitly decide whether the project should be submitted, tested for longer, resized or abandoned. The right outcome of the 90 days is not necessarily an investment: it is an informed, documented decision.

14. Checklist before submitting

• The logistics need is described using identifiable data and interviews.
• Producers and buyers are categorised into contacts, interested partners and formalised commitments.
• Volumes are detailed by period, product and type of packaging.
• Several logistics scenarios have been compared, including a solution without heavy investment.
• The full cost of services and the break-even point have been calculated.
• Working capital needs and payment terms have been modelled.
• Governance, equipment ownership and responsibilities are documented in writing.
• Health and safety rules, traceability and the cold chain have been checked for the planned operations.
• The LAG has been contacted and the local conditions have been obtained in writing.
• Expenses, quotes, start-of-operation rules and co-financing are documented.
• Indicators have a baseline and an owner.
• A fallback scenario exists in case volumes or co-financing do not materialise.

Conclusion

A producers' platform succeeds when it makes exchanges simpler and more reliable without creating a structure that is too costly for the volume it serves. The right starting point is therefore organising the flows and proving demand, not buying a truck or building a warehouse. The model can be digital coordination, a consolidation point, a partnership with a service provider, or an equipped platform; the choice must follow from observed usage.

LEADER can contribute to financing if the project fits within the LAG's strategy and meets the conditions of the call for projects. Preparation must nonetheless demonstrate territorial usefulness, viability after the grant, user participation and risk management. The best next action is to gather flow data, run a pilot delivery round, and submit a concise note to the LAG before incurring any irreversible expense.

Practical reference points

Action plan

Territorial diagnosis → documented need → compared scenarios → LAG validation → budget and cash flow → partners and authorisations → submission → results monitoring.

Eligibility conditions

To be confirmed in the local strategy and the LAG's call for projects: territory, type of applicant, expenses, eligibility period, thresholds, rates, caps, co-financing, start-of-operation rules and any State aid.

Funding and instruments

LEADER to be examined according to the local strategy; other sectoral or territorial aid to be identified separately. No universal rate or cap is assumed.

Access and procedures

Contact the LAG before any commitment; request the call sheet and the list of required documents; document quotes, co-financing, authorisations, cash flow and indicators.

Points of caution

insufficient volumes, delivery rounds that are too long, under-use of refrigeration equipment, poorly allocated delivery costs, seasonality and health and safety responsibilities. Also check the rules on when the operation may start, competitive tendering, combining aid, publicity and keeping supporting documents.

Official sources

• https://reseau-pac.agriculture.gouv.fr/quest-ce-que-leader
• https://eu-cap-network.ec.europa.eu/networking/leader/lag-directory_en
• https://agriculture.gouv.fr/circuits-courts-exigences-sanitaires-et-flexibilite-pour-les-petites-entreprises
• https://www.franceagrimer.fr/aides
• https://agriculture.ec.europa.eu/cap-my-country/rural-development_en