See what changed before the next service starts.

Follow reviewed invoice costs into the recipes and inventory context your manager needs before service. Available sources depend on the pilot setup.

See if Dynamic.ly fitsFollow the product flow

An illustrative service day · No customer result is shown

Illustrative restaurant day

A delivery at the back door, and a decision before the room fills.

  1. Delivery

    A delivery lands above the last reviewed cost.

    The invoice line stays in review with its vendor, pack size, unit, and source. Nothing else changes until the restaurant confirms it.

    Vendor
    Ocean Fresh
    Pack · unit
    18 lb · per lb
    Line cost
    $18.40 · was $17.10
    State
    In review
    Reviewed salmon line: 1 lb at $18.40, inventory item and source page attached. Invoice approval remains required.

  2. Prep

    Salmon Bowl economics showing a $14.20 configured internal price floor and a menu price above that floor.

    Two dishes moved with it.

    The new cost changes the ingredient history and the recipe economics. Dynamic.ly shows which recipe costs changed and keeps the configured floor visible without changing the menu.

    $18.00

    Menu price

    $14.20

    Configured price floor

    $3.80

    Price headroom

    Two dishes use this ingredient · both recosted · no menu price is changed here

  3. Manager review · the decision

    The manager sees one decision, not five disconnected reports.

    The recommendation arrives with the reason, service window, limits, source, and what remains estimated. The person running the shift decides what happens next.

    A proposed $15.50 offer for 5–7 PM, with a $14.20 floor and manager review required.
    Why now
    Cost up · Possible expiry exposure
    Service window
    5–7 PM · $15.50
    Limits
    $14.20 floor · cap 40
    Attached sources
    Invoice · recipe · lot
    Still estimated
    Impact · not measured

    Pending  →  recorded

    Decision history: revision 1 of the review plan, recorded by the General Manager. Not a measured outcome.

    Approve, edit, reject, or ignore. The choice is kept with its limits and sources, and the projected impact stays labelled as an estimate until the restaurant measures it.

    Review does not publish the offer or write to a provider

A different question for each person.

Owner or operator

Which reviewed changes deserve attention, and what evidence would make a pilot useful?

General manager

What needs a decision before service, within which limits, and who will carry it out?

Chef or kitchen lead

Which ingredient, pack, yield, or recipe assumption needs review?

Operations or finance

Which source, formula, baseline, and exclusions support the number?

Fit

Most of this depends on what the kitchen already writes down.

A useful fit

  • You have recent invoices and a current menu.
  • At least a few core recipes or counts can be reviewed.
  • A manager is willing to inspect what changed.
  • You want help deciding, not blind automation.

Probably not the right fit

  • You need guaranteed savings.
  • You want automatic price or provider changes.
  • You are looking for a replacement POS, scheduler, reservation system, or inventory platform.

Start with the records already in the restaurant.

Start with the records you have. Missing recipes, counts, or source mappings need review before they can support a decision.

  1. Recent vendor invoicesRequired
  2. Current menu and pricesRequired
  3. Core recipes or countsRequired
  4. A manager who knows the shiftRequired
  5. Read-only sales contextOptional

Bring recent invoices and a current menu.

That is enough to start the conversation. A pilot baseline itself uses 4–8 weeks of vendor invoices, so the comparison period is the restaurant’s own.

Dynamic.ly recommends. The manager decides.