Size code
Orange size 2, and how far it overlaps size 1
Size 2 shares three quarters of its band with size 1, the widest overlap between neighbouring codes anywhere on the orange scale. Every line in our catalogue reaches this code at the outer edge of its declared range, the three oranges on this table and the clementine on its own, and not one is packed in it by default.
The figures
| Size code | 2 |
|---|---|
| Diameter range | 84–96 mm |
| Varieties we pack in this size | None of ours is packed mainly in this size |
| Within the range of | Clementina Clemenules, Navel Foios, Navel Lane Late, Navelina |
| Millimetres shared with size 1 | 87–96 mm |
What it changes on an order
You are rejecting a load on size
Where two codes overlap this heavily, a fruit measured in the shared stretch satisfies both of them. A rejection has to rest on fruit outside the printed band, counted against the tolerance the standard allows, and not on an impression that the box looks wrong.
You are consolidating orders from two buyers
One buyer asking for this code and another asking for the code above can be served from the same pick across most of the band. Raise it as a packing question before either order is confirmed and you buy yourself a week.
You are setting an arrival check
Choose the gauge before the load arrives and write down which end of the band you care about. Checking against the middle of a range is how two people measure the same pallet and walk away disagreeing.
What this note does not settle
- A declared range says a variety reaches this code. It does not say a given week will produce enough of it to fill a pallet.
- The clementine in the table above is listed on the clementine table, where the same digit stands for a different diameter.
- How many fruit of this size fill a box is not settled here. That belongs to the format conversation and is still to be confirmed with the packer.
What an overlap this wide does to a claim
Codes on this scale were built to work on a packing line, not to exclude one another. Neighbouring bands share ground everywhere, and at this point they share more of it than anywhere else on the scale. A fruit sitting in the shared stretch is correctly described by either number, so a dispute about which one applies has no answer to reach.
The lesson is to stop arguing about the code and start counting fruit outside the printed band. That is the only test the standard supports, and the one an inspector runs. Everything else is a conversation about impressions, and impressions travel badly down a phone line.
Reaching a code and filling it
A declared range is the grower's statement about what the trees throw. The sizes packed week after week are a smaller set inside it, and this code falls outside that smaller set for every line we carry. Both facts sit in the table above, deliberately, because the gap between them is where most disappointments begin.
So the useful question is never whether we reach this code. It is how much of it a given week produces, and the pick answers that, not a page. Ask for the week and the volume together and you get a number to plan against.
Talk to the grower
Tell us the variety, the sizes and the delivery week you need. You get a delivered price and what we can commit to in writing, from the person who picks the fruit.
The grower handles enquiries. Response times are still to be confirmed.