For partners

A shopping list that knows what it cannot order.

RecipeMirror turns a cooking video or a recipe page into steps somebody cooks along to. The shopping list falls out of that — and unlike every other list, it knows which lines the recipe never gave an amount for, and declines to invent one.

1. Step 1

   A cook saves a video and cooks from it

   RecipeMirror reads the video into ingredients and steps. Amounts it states are used; amounts it never gave stay blank rather than being guessed.

2. Step 2

   The list, sorted for a shop

   4 ready to send. 2 need an amount first — nobody sells “some”, so RecipeMirror will not guess one.

   • chicken thighs800 g
   • basmati rice500 g
   • double cream200 ml
   • tinned tomatoes400 g
   • vegetable oilno amount given

     “a good glug of oil”

   • garlicno amount given

     “a bit more garlic if you like it”

3. Step 3

   What you receive, once the cook decides

   Names, amounts, units. No dish titles, no cook, no household, no account — a partner integration is where personal data leaves, so there is nothing here about a person.

   {
     "items": [
       {
         "name": "chicken thighs",
         "amount": 800,
         "unit": "g"
       },
       {
         "name": "basmati rice",
         "amount": 500,
         "unit": "g"
       },
       {
         "name": "double cream",
         "amount": 200,
         "unit": "ml"
       },
       {
         "name": "tinned tomatoes",
         "amount": 400,
         "unit": "g"
       }
     ],
     "note": "2 ingredients left off: the recipe never gave an amount."
   }

4. And this is the point

   We ask the cook first.

   Two lines never got an amount, so they are not in the basket. Every other recipe app sends “1 unit” — which is how somebody receives one clove of garlic for a curry, and how you receive a refund request. RecipeMirror asks the cook to set those amounts, and only then are they orderable.