All guides
Operations6 min read

The Karu Inbox: One Intake Flow for Invoices, Recipes, Menus, and Sales

How a single document inbox turns PDFs, photos, spreadsheets, and pasted text into structured drafts ready for review.

July 15, 2026Updated July 15, 2026By Karu EditorialReviewed by Karu Product Team

Margin systems fail when every document type needs its own upload ritual. Karu's Inbox is the intake center for the files a food business already has: supplier invoices, recipe sheets, menus, price lists, sales exports, photos, PDFs, and pasted text.

One front door for messy inputs

Owners should not need to guess whether a file is an invoice job, a recipe job, or a menu job before uploading. The inbox accepts the mess and routes it into the right draft type.

That keeps the first session lightweight: drop files, review drafts, approve truth.

Parsing is the start, not the finish

After upload, Karu extracts structured candidates: supplier lines, ingredients, products, units, prices, and confidence scores.

Those candidates land in the Review Center. Official recipes, supplier prices, and product links only update after approval.

The inbox connects to margin action

Once approved data exists, the same intake history explains why a margin moved: new invoice, recipe change, sales upload, or packaging update.

That is how Karu turns document intake into decisions — fix, push, or reprice — instead of another archive folder.

Operator checklist

Upload invoices, recipes, menus, and sales through the same intake flow.

Review extracted drafts before they affect official costs.

Keep source files tied to approved price and recipe changes.

Use approved data to rank margin actions, not just store files.

Sources

Related guides