Back to home

Software for collective catering

MEPO serves collective catering operators and self-managed operations in hospitals, factories, schools and other institutions. The Organization keeps the contract and the standard recipe sheets. Each Unit records its own stock, production and meal counts.

Demo steps
  1. Recipe sheet. The recipe sheet adds up the ingredient costs and shows the cost of each portion.
  2. Menu. The weekly menu uses the sheets and shows the expected cost of each day.
  3. Production. In production, MEPO reserves the ingredients and deducts them from the Unit's stock.
  4. Result. The contract result shows revenue, COGS, expenses and margin. Each value shows where it came from.

Collective catering means meals produced at scale for an institution, such as a hospital, factory or school. In Brazil, "alimentação coletiva" is the equivalent technical term used in the sector.

  • Operators with one or several Units
  • Self-managed operations in hospitals, factories and schools
  • Operations management and contract owners
  • Supply, stock and quality
  • Finance, billing and controllership
  1. What stays in the Organization and what stays in the Unit

    The Organization maintains catalogues, roles and standards. Each Unit records its own stock, production, meal counts and expenses. This way management follows the whole and knows in which Unit each event took place.

    • Access by person and Unit
    • Corporate recipe sheets and local versions
    • Indicators by Unit and accounting period
  2. Contract, rates and validity periods

    Services, sites, calendars, volumes, rates and validity periods in the contract feed the menu, meal counts and billing. An updated rate does not change a billing statement that has already been issued.

    • Services and modalities identified
    • Rates with a validity period
    • Contract origin preserved in billing
  3. Standard recipe sheet and local version

    Ingredients and recipe sheets stay in the Organization as the reference. When equipment, yield or composition differ in a Unit, it records its own version of the sheet, with its own period of use.

    • Corporate recipe sheet as the Organization's standard
    • Local version with its own period of use
    • Scope of the version identified
  4. Meal counts, billing statement and results

    The billable quantity comes from an explicit reconciliation. The billing statement uses that quantity and the valid rate. At closing, MEPO brings together revenue, cost of goods sold (COGS), waste and expenses, and reports when records are missing.

    • Operational quantities kept separate
    • Billing statement by contract and accounting period
    • Result by Unit with pending items visible

Example of management with several Units

Example: an operator has five Units and different contracts.

  1. 1. StandardizeThe Organization registers the ingredients and recipe sheets that every Unit uses.
  2. 2. AdaptA Unit creates a specific version when yield or composition really differ.
  3. 3. ExecuteEach Unit records its own purchasing, stock, production and meal counts.
  4. 4. CheckThe team reviews pending items and discrepancies before issuing billing statements.
  5. 5. CompareManagement compares costs and results only when the data for the accounting period is complete.

Frequently asked questions

Does MEPO allow Units to be compared?

Yes. The view by accounting period shows each Unit's numbers and warns when pending items could distort a comparison.

Does MEPO issue invoices?

No. MEPO issues the operational billing statement. The number and date of a tax document issued outside the system can be recorded.

How long does it take to get started?

Setup happens in the portal itself, with a first-steps checklist. The time depends on how many Units you register, how much of your records are ready and which routines you use first.

FREE EVALUATION

Try MEPO in your operation for 30 days.

Sign up in 1 minute. The evaluation includes one Unit and one user, with no card and no charge.