Chapter 10 Supply Chain
Here is a thing about waitressing that no one tells you before you start doing it: it gives you a very particular kind of low-level cognitive engagement.
Not demanding enough to actually occupy you.
Demanding enough to prevent you from thinking about anything with real depth.
You are always just occupied — moving, carrying, calculating small sums, managing the emotional temperature of adjacent tables.
This is probably fine if you are a person whose default state is calm and uncomplicated.
I am a person whose brain runs continuous analysis in the background.
Always has. It ran analysis on Dominic for three years and I just didn't look at the output, which is its own lesson about what happens when you ignore your own data, but that's a matter for a different summer.
The point is: the analysis doesn't stop.
It just finds new things to analyse. On Kaliroi, for the first three weeks, those things had been: table numbers, order sequencing, carbon copy pad layers, recycling codes, herb names in Greek, the ferry timetable, and whether Barba-Nikos had a system for ignoring me or whether the ignoring was entirely intuitive.
(The answer, I had concluded, was: entirely intuitive. You couldn't systematise that level of serenity. It was a calling.)
By the first week of July, my brain had finished cataloguing everything it could catalogue about the operational logistics of Taverna Stavros and now it was doing what it always did when given slightly too much idle time: it was going back through everything it had observed and building a model.
The model was of the supply ordering system.
* * *
I noticed the pattern on a Wednesday at lunch.
We were at capacity — the high season was building, more tourists from the ferry now, two cruise ships had anchored offshore and sent their people in on tenders, which Elena had anticipated and the kitchen had absorbed, and the afternoon rush was real in a way the early June shifts hadn't been.
I was on the outdoor section, moving fast, and I was managing fine (I was managing well, actually, I was not going to say this aloud but I was moving well and I'd stopped having the table-number problem entirely and Theria had even said, on Tuesday, "good," which from Theria was the equivalent of a standing ovation), and we hit a point at around half one where three tables wanted the grilled vegetable dish at the same time.
Elena redirected two of them to the fish. They were happy. I was watching the pass-through.
The vegetable dish came through on a delay.
A real delay — not the kitchen running slow, but the kitchen working around something.
I'd been watching the kitchen long enough to know the difference.
Running slow had a particular sound: the pace of the prep, the frequency of the pass-through sliding open, the number of times Lex said something to Theria.
Working around something was quieter. More considered.
The sound of a person reconfiguring on the fly.
We ran out of courgettes at quarter past two.
This was a June courgette problem in the second week of July, which meant: we were running slightly behind on restocking the late-season order, probably because the delivery pattern had been set up for the slower early-summer volumes and hadn't adjusted for the high-season uptick.
I had worked on supply chain optimisation for several years.
I knew what this looked like. I had sat across from boards and explained this exact pattern to them using much more expensive consulting language.
I had built a framework — a very good framework, actually, one that had been adopted by seven regional food businesses across the Home Counties before everything went sideways — for exactly this kind of demand forecasting.
I started doing the arithmetic in my head while I was taking orders from table twelve.
I finished it on a napkin at the end of service.
* * *
The napkin had a table on it. Column one: item category.
Column two: estimated current reorder timing.
Column three: estimated high-season consumption rate (I'd been counting orders in my head; this was the background-analysis problem again — it just happens, I've stopped apologising for it).
Column four: recommended reorder schedule adjustment.
It was not a sophisticated model. It was a back-of-envelope calculation in the very literal sense of the word.
But it was correct, or close enough to correct that anyone who understood the patterns would see it immediately.
The courgette figure might be slightly off — I was working from observation rather than historical data — but the seasonal uptick shape was right and the reorder lag was obvious and any competent person looking at it would see the gap.
The question was whether to show it to anyone.
I sat with this for several minutes. On one hand: it was not my business.
I was the waitress. I carried plates. I had been here five weeks.
On the other hand: I had built a model for a sustainable fishing cooperative in 2023 on stronger information gaps than this and they'd used it for three years.
On the third, imaginary hand I was deploying to break the tie: Lex had been running this kitchen alone for four years and he was doing everything and the courgette problem had slowed the service and I could see the shape of it clearly and not saying something felt like its own kind of failure.
I showed it to Elena.
Elena looked at it. Her expression did not change. It very rarely did. She looked at me over the table with the contained assessment she brought to most things.
"You counted the orders," she said.
"During service."
"During service."
"I wasn't — I didn't mean to. It's a background thing."
She picked up the napkin, looked at it for another three seconds, and said, "One moment," and went into the kitchen.
There was a brief exchange. Then Lex came out.
* * *
He stood at the doorway with the napkin. He looked at it for a slightly longer moment than Elena had. Not longer in a way that suggested difficulty — longer in the way someone reads something a second time when they want to check they've understood it correctly.
"When did you do this?" he said.
"End of service. Just now."
"We were at capacity."
"I know."
He looked at me. Then at the napkin. "The column four figures."
"Estimated. Based on the order counts from the last three weeks — I don't have the historical data, obviously, so the model would be more accurate if—"
"The estimates are close," he said. He said it with no particular inflection. "The courgettes are slightly off — the delivery relationship is more flexible than you'd have a way of knowing — but the pattern is correct."
I nodded. "It'd be easy to adjust once you have the actual delivery parameters."
He didn't say anything. He was looking at the napkin.
"I can redo it properly," I said, "if you tell me the—"
"I'll need a few other figures." He folded the napkin carefully — the specific fold of someone who is keeping something, not dismissing it. "I'll come back to this."
He put the napkin in his apron pocket.
I stared at the apron pocket.
He went back inside.
* * *
I was thinking about what Lex had said, standing at the end of the table with the napkin.
The estimates are close.
He'd said it without flourish, the way he said things that were true.
What he hadn't said — and this was the gap I was sitting with — was how do you know.
He hadn't asked how I'd known what to estimate, or why I'd been paying attention to the supply side, or what I thought I was doing sitting at the pass-through during the lunch rush with a napkin and a column breakdown.
He'd simply read it, confirmed the numbers, and put it in his pocket.
A man who wanted to know why you'd done something would have asked. A man who already understood why you'd done it didn't need to.
I sat with this for a while. Then:
Elena brought me coffee — the better coffee, which I had by now understood was significant but didn't yet know exactly how — and sat down at her corner table, and I sat across from her because she sat in a way that suggested she expected company.
"You were a consultant," she said. It was not a question.
"Sustainability. Supply chain primarily." I looked at my coffee. "I was good at it."
"Yes," she said. "I can see that."
The harbour was doing the afternoon thing — the cruise tender making its second run out to the ships, the local boats settled at the dock, the light going long and yellow.
Somewhere behind us in the kitchen, Theria was doing the end-of-service cleanup to a soundtrack I'd started to identify as the playlist she kept on her phone, something Greek and rhythmic that occasionally came through the pass-through window.
"The business," Elena said, "has not always been run by someone who did mathematics at capacity."
I looked at her. She was looking at the harbour with the expression she kept for things she was going to say and then not elaborate on.
"Lex," I said. Not a question.
"He manages the food. The cooking, the sourcing, the kitchen.
He is very good." She picked up her coffee.
"The rest of the business — the things that need a spreadsheet, the things that need someone to look at patterns — he does them because they need doing.
Not because it is where he is strongest."
I thought about the napkin in his pocket. The way he'd read it twice.
"He's been doing the kitchen and the business administration," I said. "Both. Since he came back."
"Since Nikos was ill, yes."
There was a silence. Outside, the tender cut a white line across the Aegean.
The afternoon light had gone from yellow to something warmer, and the bougainvillea on the taverna wall had the particular over-saturated quality it got in the hour before sunset, the quality that had made my grandmother send a postcard and had made me take a photograph every evening for five weeks.
"The napkin," I said, because I needed to say something practical and the napkin was the practical thing.
"If it would be useful, I could put together a proper schedule.
For the high-season orders. It wouldn't take long — I'd just need to see the delivery contacts and the last two or three invoices. "
Elena looked at me. The expression was very slightly different from her usual expression.
Something in it that I couldn't yet read — something that might have been satisfaction or might have been recognition, or both, because on Kaliroi those things seemed to run together in ways that didn't require explanation.
"I'll get them for you," she said.
She set down her coffee cup with the deliberate quiet of someone concluding a negotiation they'd known would go this way.