Recipe quantities and purchasing

Scale recipe quantities, apply explicit yields, combine equivalent ingredients and calculate whole packages with an auditable source trail.

Input

Result

The example scales four portions to ten. The two flour rows combine to 1500 g net and 1650 g including reserve, requiring two 1000 g packages with 350 g remaining. Carrots require 750 g net, 937.5 g after the supplied 80% yield, and 1031…

Recipe scaling needs more than a multiplication button. The same ingredient can appear in several preparation steps, supplied yields can change the purchasing amount, and package rounding can leave surplus. This tool keeps those stages separate and exposes their source records. The AI reviews the supplied ingredient notes for possible unit, yield, packaging or handling concerns; all numeric results are calculated independently.

Your texts, pages and images are processed on our own servers in the EU. Trust Center

Try it now Pricing

Who it is for

Kitchens, catering teams, small producers and recipe developers planning quantities from an existing documented recipe. Suitable for preparation and purchasing drafts, not nutrition analysis, allergen certification or food-safety approval.

Typical uses

Scale a recipe by a portion ratio or an explicit factor.
Account for ingredient-specific retained yields without inventing loss rates.
Combine explicit ingredient keys across recipe steps and normalize compatible units.
Compare net requirements, adjusted purchasing quantities, whole packages and surplus.
Keep uncertain package definitions visible instead of guessing a purchasing unit.

Example

Input

Recipe ingredients: id,ingredient_key,name,quantity,unit,yield_percent,pack_size,note I1,FLOUR,Flour,0.5,kg,100,1,Keep the flour type unchanged. I2,CARROT,Carrots,300,g,80,500,Yield includes the supplied trimming allowance. I3,FLOUR,Flour for dusting,100,g,100,1000,Same flour stock as I1. Base portions: 4 Target portions: 10 Scaling method: Portion ratio Explicit scaling factor: 2 Apply supplied yields: Enabled Reserve percentage: 10 Ingredient aggregation: Combine matching ingredient keys Displayed quantity units: g, ml and pcs Calculate whole packages: Enabled Displayed decimal places: 3 Display rounding: Round half upward Result order: Source order Show exact source notes: Enabled

Result

A fixed example, shortened. Real results are AI-generated: please check them.

Price and limits

Price: usually 1–3 credits
Available with: Free, With package
Input limit: One page with up to 160,000 characters of HTML

Privacy

Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.

In the API

Tool name: recipe_scaling. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.

curl -X POST https://do4u.eu/api/v1/jobs \
  -H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
  -d '{"tool": "recipe_scaling", "url": "https://example.com/"}'

Full API documentation →

Questions and answers

Are ingredient names matched automatically?

No. Only an explicitly shared ingredient_key creates an aggregation group. A name similarity is not sufficient evidence of equivalent ingredients.

Can volume be converted to mass?

No. The tool converts mg, g and kg within mass, and ml and L within volume. It does not invent density or a volume-to-count conversion.

Does scaling establish cooking times or allergen safety?

No. Cooking behavior, nutrition, allergens and food safety require separate verified procedures. AI notes are review suggestions tied to the supplied source.

Is my text stored?

Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).

Can I use the result right away?

Results are AI-generated. Please read them before you publish or send them.