When the Supplier Road Breaks: The Wet-Season Procurement Record MBG Needs

MBG Watch · 2026-09-05

The premise

A wet-season meal tray can look normal even when the procurement record behind it has changed.

The road to a local egg supplier may be blocked. Vegetables may still exist in the field but cannot be harvested safely or moved on time. A kitchen may spend more on LPG, water, ice, or transport. A shelter may suddenly need meals outside the school register. None of these conditions proves misconduct. But each one changes the accountability question.

BGN has already said the food-material component of MBG is Rp8,000 for younger children and Rp10,000 for older students and other eligible groups, with a separate Rp3,000 operating component for electricity, internet or telephone, gas, water, and SPPG worker incentives. In a separate Ramadan response, BGN said SPPGs should explain the Angka Kecukupan Gizi calculation and the price of each food ingredient in each menu, and that the food-material benchmark is at cost and may differ by regional cost index.

That is the right starting point. In the wet season, it is not enough to show that a meal was delivered and a payment was made. MBG needs a substitution record: a modest, kitchen-level ledger that shows what changed, why it changed, how the nutrition was preserved, whether food safety remained suitable, and how the public paid for the difference.

This builds on MBG Watch’s earlier wet-season work: the food-safety clock, climate baseline stress, route readiness, shelter-meal reimbursement, and commodity-to-tray supply-chain crossing. Rupiah Stability Watch’s Wet-Season MBG Kitchens and the Rupiah Operating Ledger added the sister question: when logistics, fuel, local prices, and fiscal opacity move together, public confidence depends on seeing the operating ledger before rumor fills the gap. This piece narrows that question to procurement substitution.

What the public record already supports

The public record supports a readiness standard. It does not yet support a broad claim that wet-season procurement substitution is already failing across MBG.

First, MBG is large enough that procurement changes cannot be treated as informal local exceptions. BGN reported in January 2026 that MBG had grown from about 570,000 beneficiaries and 190 SPPGs at the start of January 2025 to about 58.3 million beneficiaries and more than 19,000 SPPGs by early 2026. BGN also said each SPPG needs at least 15 suppliers across rice, oil, eggs, meat, chicken, milk, spices, vegetables, and other ingredients. A procurement failure at one supplier may be small nationally, but at kitchen scale it can alter thousands of trays quickly.

Second, BGN has already identified supplier concentration, mark-ups, and poor-quality ingredients as live governance risks. In a February 2026 release, BGN’s Nanik S. Deyang warned SPPG heads, finance supervisors, and nutrition supervisors not to cooperate with partners that mark up raw food prices or force kitchens to accept one or two selected suppliers, especially when quality is poor. The same release says SPPGs must use at least 15 food-ingredient suppliers and that a partner found marking up prices or narrowing suppliers could be suspended.

Third, wet-season disruption is not hypothetical in Indonesia’s operating environment. BNPB’s 8 May 2026 situation report recorded floods, landslides, and forest and land fires across several regions; it said moderate-to-heavy rain triggered flooding in Musi Rawas Utara, affecting 16 villages and one urban ward across two districts, while a landslide in North Tapanuli cut the Tarutung-Sipirok national road after material covered the route. BNPB’s 1 August report showed the same operating window can contain the opposite stress: 34 disaster events, including fires, drought, and extreme weather, with hot conditions and strong winds helping fire spread in several districts.

Fourth, weather can move food availability and price before it appears as a school-meal problem. RRI reported Bapanas’ February 2026 finding that high chili prices in producer areas were linked to harvest constraints from rain: crops existed, but farmers were not able or willing to pick safely during sustained rain, and distribution was constrained. Chili is not the whole MBG tray. It is a useful warning example: the procurement problem may be access, timing, quality, or safe harvest, not national scarcity.

Fifth, food safety cannot be separated from substitution. BGN has described NSPK operating guidance, layered supervision, routine training for food handlers, and cooperation with BPOM after poisoning incidents. A wet-season substitute is therefore not only a price event. It is also a suitability event: different ingredient, different supplier, different storage path, different delivery timing, sometimes different water or refrigeration condition.

What should be visible when procurement changes

A useful substitution record does not need to expose children, families, complainants, or small suppliers unnecessarily. It should show enough for public accountability and internal correction.

For each SPPG and service day, BGN should be able to publish or audit seven linked fields.

1. The planned tray. This is the original menu, portion logic, AKG basis, and planned ingredient list under the normal Rp8,000 or Rp10,000 food-material budget. It should identify the nutrition role of each ingredient: staple, animal protein, plant protein, vegetable, fruit, dairy, oil, or other.

2. The disruption reason. The reason code should be simple and inspectable: flood, landslide, road break, port or ferry disruption, heavy rain harvest delay, market closure, power outage, water disruption, refrigeration failure, shelter-feeding demand, supplier stockout, safety rejection, or price outlier. Free text can remain internal, but the public needs the category.

3. The substitute. The record should name the ingredient replaced, the substitute ingredient, the affected quantity, and the number of trays affected. If chicken becomes egg, fish becomes tempeh, fresh vegetables become a safer cooked alternative, or fruit is delayed and replaced the next service day, the nutrition effect should be visible rather than implied.

4. The nutrition check. Each substitution should show whether the menu still meets the intended nutrition standard for that beneficiary group. Where it does not, the record should state the correction: make-up item, next-day adjustment, reduced service, or meal held until safe ingredients arrive.

5. The food-safety check. The record should show whether the substitute passed receiving checks, temperature or storage requirements where relevant, water suitability, expiry or spoilage checks, and preparation-time limits. It should also record safety rejections, because a rejected ingredient is a control working, not a scandal by itself.

6. The payment line. The record should connect supplier identity, unit price, quantity, invoice, reason code, payment or reimbursement status, and whether the price exceeded the normal reference range. Emergency prices may be legitimate. Hidden emergency prices are where suspicion grows.

7. The correction and review. If the substitution caused a nutrition shortfall, price anomaly, late delivery, supplier concentration, or safety concern, the record should show who reviewed it, what was corrected, and whether the same issue recurred.

This is a small ledger, not a new bureaucracy for its own sake. Most of these fields should already exist somewhere in menu planning, receiving logs, invoices, supervisor checks, or incident follow-up. The missing control is the connection between them.

How the record should protect people while preserving accountability

The public version should not publish children’s names, family details, complainant identities, or personally identifying health information. It also need not expose the full commercial vulnerability of every small supplier.

A proportional design would publish aggregated SPPG-level and district-level data: number of substitution days, reason categories, ingredients most often replaced, number of trays affected, percent still meeting the nutrition standard, safety rejections, emergency-price bands, unresolved reimbursements, and repeated supplier concentration warnings. Supplier identities can be visible to auditors and procurement supervisors, with public disclosure reserved for sanctioned entities, material conflicts of interest, repeated monopoly patterns, or confirmed misconduct.

This distinction matters. Privacy should not become opacity. Openness should not become unnecessary exposure. The practical middle is a tiered record: public dashboard fields for pattern accountability, restricted audit fields for supplier and invoice verification, and protected complaint and child-health records for remedy.

What the evidence does not support

The evidence does not support saying that wet-season procurement disruption has already caused a specific national MBG nutrition failure unless a sourced incident shows it.

The evidence does not support treating every emergency price as corruption. Flooded roads, unsafe harvest conditions, port delays, fuel costs, water disruption, and substitute purchases can raise real costs. The test is whether the reason, price, supplier, and correction are recorded.

The evidence also does not support assuming local sourcing is always safer in disruption. Local supply can strengthen resilience in normal conditions, and BGN has framed MBG as a local economic program. But in a flood, nearby may mean inaccessible, unsafe, or temporarily overpriced. The accountability standard should protect the child’s tray first, then explain whether the kitchen used local, neighboring-district, provincial, or other backup supply.

Finally, the evidence does not support making a broad pause the default answer. A more proportionate control is a trigger: if an SPPG cannot document the substitute ingredient, nutrition effect, safety check, supplier identity, and payment reason, then that kitchen, supplier line, or menu should enter corrective review until the record is complete.

The least-harm path

BGN can make wet-season procurement substitution visible without turning every kitchen into a paperwork office.

The first step is a standard substitution form embedded into the existing menu, receiving, and payment workflow. It should be short enough to complete during operations and structured enough to audit later. No substitution should be accepted as “same as usual” if the supplier, ingredient, price, transport route, water condition, refrigeration condition, or beneficiary group changed.

The second step is a kitchen-level substitution threshold. A single small swap may need only ordinary supervisor review. Repeated substitutions, animal-protein replacement, emergency prices above a reference band, supplier concentration below the required diversity, rejected ingredients, water or power disruption, or shelter-feeding demand should trigger district review.

The third step is public monthly reporting before the wet-season peak: how many SPPGs used substitutions, what caused them, how many trays were affected, how many still met nutrition targets, how many safety rejections occurred, how many emergency-price lines were paid, and how many were corrected or denied. This would let BGN show the difference between adaptation, error, and abuse.

The fourth step is independent sampling. Auditors do not need to inspect every tray. They need to sample the linked chain: planned menu, changed ingredient, receiving log, AKG recalculation, invoice, payment, and corrective action. If those records agree, the system is learnable. If they do not, the problem is not only the wet season. It is the control chain.

What I am uncertain about

I could not verify from public sources how BGN currently records ingredient substitution at SPPG level during floods, road closures, port disruption, power or water disruption, or shelter-feeding demand.

I also could not verify whether the 15-supplier requirement is monitored as a daily operating condition, a registration condition, or a broader anti-monopoly rule. That distinction matters in a disruption: a kitchen may have 15 registered suppliers and still be functionally dependent on one available supplier during a flood week.

The most important missing public figure is not a national total. It is the denominator: how many SPPG service days involved menu, supplier, price, or beneficiary changes because of weather or disaster conditions, and how many of those changes still met nutrition and safety standards.

Until that is visible, the least-harm question remains simple: when the supplier road breaks, can MBG prove the tray did not quietly break with it?