Scope. This page provides a controlled reader-run protocol and does not claim site-run measurements. For cooking, cooling, storage and reheating, follow the current official guidance linked on the page.
Poached pears are one of the few dishes where competent cooks routinely produce two opposite failures from the same recipe on consecutive attempts. The first time they come out chalky at the centre with a hard core of raw fruit. The second time the same pears, in the same pan, dissolve into the syrup somewhere between two checks.
Both outcomes come out of the same mechanism, and once you know what that mechanism is, the apparent absence of a middle stops being mysterious. Fruit is not behaving like a badly-timed vegetable. It is behaving like a different material, because it is one.
The two failure states
Vegetables mostly soften along a curve. You can push a knife into a potato at intervals and watch it get gradually easier, and if you go too far you get a soft potato rather than a destroyed one. There is a wide zone where the result is acceptable.
Fruit does not behave that way at the temperatures poaching uses. It holds its structure, holds it, holds it, and then goes. The transition can be short enough that the check before it and the check after it are on either side of a completely different dish, which is why cooks conclude there is no window. There is a window. It is narrower than the one they are used to, and it moves depending on the fruit, the liquid and the ripeness.
The reason is that the structural material doing the work is different, and it fails differently.
What pectin is doing as the temperature rises
Plant cells are glued together by pectin in the middle lamella, the layer between adjacent cell walls. Firmness in raw fruit is largely a matter of that glue holding and of the cells being turgid with water. Cooking attacks both.
Two processes matter here.
Cells lose turgor early. Heat damages the cell membranes, water moves out, and the fruit goes from crisp to yielding without anything structural having broken. This is the change you notice first and it is not the collapse.
Pectin breaks down later. Above some temperature the pectin between the cells degrades and the cells stop being held together. When that happens, the fruit no longer has a structure. It has a pile of loose cells suspended in syrup, which is exactly what mush is.
The second process is the one with the sharp character, and it is why the failure feels sudden. It is also strongly dependent on conditions in the liquid, which is where the useful control levers are.
This article publishes no universal pectin-degradation temperature. Compare different fruits and liquids at measured conditions, and record collapse as an observed endpoint for those samples.
Why acid firms fruit and alkalinity destroys it
The pH of the poaching liquid changes the rate of pectin breakdown substantially. Acidic conditions slow it. Neutral and alkaline conditions accelerate it, dramatically so at the alkaline end.
This is the same chemistry that makes an alkaline addition speed up the softening of onions, and it runs in the direction you would expect: whatever makes vegetables collapse faster makes fruit collapse faster.
The practical consequences are direct.
- A splash of acid in the poaching liquid buys you a wider window. It is not only there for flavour or to stop cut surfaces darkening. It is structural.
- Water composition may be a confounder. Record the water source and its measured pH rather than assuming “hard” means alkaline.
- Never add an alkaline ingredient to something you want to keep whole. It is a genuinely fast route to purée.
Calcium is included only as an optional controlled comparison. This page makes no calcium recommendation; a conclusion requires a matched test on the named fruit and conditions.
Why sugar in the poaching liquid is structural
This is the part most worth knowing, and the part that reads as an aesthetic choice in almost every recipe that mentions it.
Sugar in a poaching liquid is not there principally to sweeten the fruit. It is doing structural work, by at least two mechanisms.
It changes the water gradient. Fruit sitting in plain water has more dissolved material inside its cells than outside, so water moves inward and the tissue swells and weakens as it heats. Fruit sitting in a syrup faces a much smaller gradient, or none, so less water floods in. A syrup poach holds shape where a water poach does not.
It competes for water. Pectin degradation happens in water. Sugar binds a share of the available water, which slows the reactions that dissolve the fruit's structure. This is the same principle that makes heavily sweetened fruit preparations hold their pieces, though the preserving end of that spectrum is out of scope here and is safety-gated elsewhere.
No figure is stated for how syrup concentration moves the working window. The planned comparison measures that effect directly for the named fruit and syrup.
The practical upshot is a trade-off you can actually use. A light syrup gives you a lightly sweetened result and a narrower window. A heavier syrup gives you a wider, more forgiving window and a sweeter, denser result. A concentrated syrup will hold fruit together almost stubbornly, at the cost of a candied character and of penetration taking much longer, because the same gradient that keeps water in the fruit slows the syrup going in.
The version worth trying if you have only ever poached in water: start the fruit in a light syrup, and if you want it sweeter, reduce the liquid afterwards rather than starting stronger. You keep the wide window and get the concentrated result at the end.
The working band, and how to hold it
Everything above says the same thing. Fruit poaching wants a temperature high enough to soften the tissue and low enough that pectin degradation stays slow, held steadily, in a liquid whose acidity and sugar content you have chosen deliberately.
That is a below-the-boil technique in the most literal sense. A poaching liquid at a rolling boil is doing three unhelpful things at once: it is running the reactions faster, it is moving the fruit around and knocking pieces against each other, and it is making the temperature at the surface of the fruit impossible to control. Anything you have ever poached that arrived as fruit-shaped debris was probably boiled.
We give no working band and no failure temperature, meaning the point where structure is lost within the normal cooking time, for any fruit. Record both for each fruit you poach, with the date and the number of runs, and never infer one fruit's figures from a similar fruit.
Holding a steady band below the simmer is its own skill, and the equipment-independent version of it is covered in the heat work. Two things that help with fruit specifically:
- A cartouche, a disc of paper on the surface, keeps floating fruit submerged and reduces evaporation, so the liquid concentrates less and the temperature is steadier.
- Off-heat finishing. Bring the liquid to the band, add the fruit, and let the pan coast with the lid on. The temperature falls slowly rather than rising, so the process ends up on the safe side of the failure point by default. This is the same logic as pulling early to allow for carryover.
The related technique of stopping a cook deliberately, with cold, is covered in how to measure blanching and shocking, and it applies to fruit as directly as to vegetables.
Ripeness: the variable you cannot cook around
Here is the honest limit of everything above.
The pectin content and pectin state of a piece of fruit change continuously as it ripens. Ripening involves the fruit's own enzymes breaking down pectin, which is why a ripe pear is soft and an unripe one is not. So two pears from the same tree, a week apart, are different materials before you have done anything to them.
This means:
- A ripe piece of fruit will collapse sooner than an unripe one under identical conditions, and no adjustment to the liquid fully compensates.
- Firm and slightly under-ripe is usually the right buy for poaching, because the technique is going to soften it anyway and the extra structure is a margin you can spend.
- A published time for poaching any fruit is an estimate at best, since the writer's fruit was not your fruit. Times in fruit recipes should be read as a prompt to start checking, never as a duration.
- Check by feel, not by clock. A thin skewer into the thickest part, with light resistance still present, means stop, because carryover will continue in the hot syrup.
Record your results by fruit and by stated ripeness, described by a measurable proxy rather than by adjective, because "ripe" is not a specification. Which proxy predicts the result best is for your own notes to show.
In Plain English
What it means. Fruit holds its shape until the pectin holding its cells together breaks down, and then it stops holding its shape quite quickly. Acid slows that breakdown, sugar slows it, alkalinity speeds it up enormously, and ripeness sets the starting point before you touch anything.
Who it helps. Anyone whose poached fruit has come out raw at the centre or as a purée, and who assumed both results were timing errors.
When to use it. Whenever fruit meets heat and liquid: poaching, compotes, fruit in a tart, anything simmered.
What to do next. Next time, poach in a light syrup rather than water, add a little acid, keep the liquid below a simmer, and check by feel early. If your fruit was very ripe to start with, expect the window to be shorter than the recipe implies. The general framing of low-heat versus high-heat decisions is in sweating versus browning, and how to read the Temperature Ladder explains how a measured or cited entry is labelled.
Cook something with it
Poaching is the cheapest place to see this mechanism work, because the whole process is visible and reversible right up until it is not. Poach one fruit, record its working band and its failure point, and keep the log behind both.