Enterprise DNA

Instead of MarketMan

Stop renting MarketMan. Own your kitchen costing system.

We build your version around your kitchens, portions and supplier packs. We map your MarketMan exports, check the starting stock and run the system for you.

MarketMan lists Starter at US$249 a month and Growth at US$299 a month. The listed Starter rate is US$2,988 over a year. Source: MarketMan pricing, checked 28 September 2026.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription buys

The kitchen records are yours. The plan is recurring.

MarketMan already handles recipe costing and stock analysis. The choice here is whether to keep renting a packaged service or own a version built around your kitchens.

paid

Starter is a recurring bill

The public Starter price is US$249 monthly. Your actual agreement determines the final bill.

calendar_month

A year of Starter

Twelve payments at that listed rate total US$2,988. That is the subscription arithmetic, not a claimed saving.

restaurant

Ordering on Growth

Growth lists US$299 monthly and adds order-by-recipe and smart ordering.

query_stats

Enterprise reporting

Enterprise starts from US$449 and lists advanced reports. Confirm contract terms with the vendor.

extension

Data access can add cost

Read-only access for connecting other systems is listed at US$25 monthly for one to three locations. Enterprise includes it.

receipt_long

Scanning differs by plan

Starter has a monthly scan allowance. Growth lists unlimited invoice scanning. Review the capture work your kitchens need.

Your version

Follow the ingredient from supplier to plate

Recipe margins

Cost the portion you actually serve

Your quantities, preparation yields and supplier costs determine the answer.

  • check Calculate each portion from net ingredient quantity and preparation yield
  • check Compare food cost percentage with your chosen target
  • check Show contribution before labour and overhead
  • check Keep past sales usage intact when tomorrow's recipe changes

Stock and waste

Explain the gap between two counts

Separate recorded recipe usage, waste and stock still unexplained. Missing counts remain unknown.

  • check Compare opening count, accepted receipts and closing count
  • check Account for paired transfers between kitchens
  • check Keep held supplier deliveries out of available stock
  • check Read the quantity left unexplained after sales and recorded waste

Purchasing

Prepare the next supplier conversation

See pack quantities, outstanding orders and recorded cost changes in one place.

  • check Round a shortage to whole supplier packs
  • check Flag old stock counts before an order is reviewed
  • check Track partial deliveries and outstanding quantities
  • check Draft a supplier price discussion without sending it

Your records

Keep the working history in your database

Start with the free costing desk, then shape it around how your kitchen runs.

  • check Preview mapped exports before importing records
  • check Print recipe cards, stocktake sheets and receiving registers
  • check Review selected Australian receiving and supplier record gaps
  • check Add your own fields, approval steps and reports without waiting for a vendor release

Make it yours

Design your own MarketMan replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from MarketMan. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your MarketMan replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your MarketMan data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers captured from the fictional demo kitchens. Costs exclude tax. Missing counts remain unknown, and a person reviews every order proposal.

forum

Kitchen Costing for Claude Code

Connected to your own database

Which dishes miss our food cost target?

Harbour Kitchen

Currency
AUD
Dish
Lemon rice bowl
Portion cost
1.1000
Food cost %
9.17
Target %
30

Harbour Kitchen

Currency
AUD
Dish
Salmon plate
Portion cost
8.2000
Food cost %
34.17
Target %
30

Market Counter

Currency
AUD
Dish
Counter rice bowl
Portion cost
0.8000
Food cost %
8.00
Target %
30

Ask it anything

Questions to ask about your kitchen

These questions are answered by the free version today. MarketMan also offers costing and stock analysis. The difference is that you can change this system around your own records and rules.

chat_bubble Which dishes are above our chosen food cost target?
chat_bubble Which ingredients have usage left unexplained after recorded sales and waste?
chat_bubble Which kitchen has an old stock count behind its order proposal?
chat_bubble How many supplier packs cover the recorded shortage?
chat_bubble Which accepted receipt changed an ingredient cost?
chat_bubble Which orders are overdue with stock still outstanding?
chat_bubble Which waste entries have a recorded reason and operator?
chat_bubble Which suppliers have held deliveries and missing address records?
chat_bubble What portion of recorded sales went on the ingredients used?
chat_bubble What should each kitchen follow up this Monday?

Switching

How to switch from MarketMan

Moving off MarketMan means exporting what your account allows, mapping those columns to the new system, checking what the import flags, and running both systems side by side until the numbers agree, before you switch MarketMan off.

  1. 1

    Export what MarketMan will give you

    Export whatever your MarketMan plan allows, usually CSV or Excel. Check with MarketMan support on exactly what fields are available to pull. Get ingredients, suppliers, recipes, pack sizes and any stock or purchase history you want carried forward. Note the headings and pack sizes carefully, since MarketMan's export format is not standardised across accounts and needs review before anything is loaded into the new system.

  2. 2

    Run a test import first

    The import is a single guided step once your columns are mapped to the new system. Before touching real records, run it once as a trial so you can see how MarketMan's headings and units line up without changing anything live. Unknown columns fail until you deliberately map or ignore them, which is the safeguard doing its job, not a fault.

  3. 3

    Review everything the import flags

    After the trial run, go through what got flagged. Changed or unclear source columns stop for review rather than being guessed at. Historical recipes need a separate look too, since a backdated sale uses the recipe as it stood at the time, not today's version. Every original MarketMan column is kept on record, so nothing you exported is lost, even what you choose not to map yet.

  4. 4

    Run both systems side by side

    Keep MarketMan running as normal while you check the new numbers against it. Compare stock counts, recipe costs and a handful of purchase orders across both systems for a short stretch before committing to anything. Keep the existing capture process going, whatever staff use to enter counts and sales today, until the replacement has been tested end to end.

  5. 5

    Turn off MarketMan

    Once counts, recipe costs and orders line up and your team is working from the new desk without falling back to old habits, cancel MarketMan. Keep your exported files and a separate database backup regardless, since the export is a snapshot for moving records, not a substitute for your own backup routine.

construction

Where the real effort goes

The real work sits in the mapping, not in running the tool. Your MarketMan export will carry its own headings, pack sizes and supplier units, and someone has to decide how much recipe and stock history to bring across versus starting counts fresh. That review takes real attention. When Enterprise DNA installs and runs it for you, this mapping and reconciliation is handled as part of the setup.

Not ready for a call?

Get your MarketMan switch plan by email

We will send you the step-by-step plan for moving your business off MarketMan, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to make it yours

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free source

  1. 1 Clone the repo, run npm install and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and read AGENTS.md.
  3. 3 Map your MarketMan CSV headings and run an import preview.
  4. 4 Reconcile units, recipes, stock and history before switching.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your recipe yields, supplier packs, fields and approval rules
  • check Your MarketMan exports mapped and checked against a stocktake
  • check A web front end or phone counting process where your team needs one
  • check A different technology stack where your requirements call for it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your sales and supplier connections scoped and tested
  • check Access, backups and support agreed for your kitchens
  • check Ongoing changes as menus, suppliers and sites change
Book a call with Sam

Questions

Instead of MarketMan, answered

Can we bring our MarketMan records across? expand_more

Yes, after checking the actual exports. The free version imports exported records using a reviewed column map. Export headings, pack sizes and historical recipes need review first. It does not assume every MarketMan account produces the same export. We handle that mapping and reconciliation in your custom version.

Does this replace the phone app and invoice scanning? expand_more

The free version is a costing and purchasing desk with printable sheets and read-only reports. Enterprise DNA can build phone entry and connect sales or invoice capture in your version. We agree those workflows before the team switches.

Will it tell us our true food cost? expand_more

It calculates recipe cost from entered quantities and yields. Between stock counts it separates actual usage, recorded sales usage, waste and unexplained quantity. Missing counts and missing sales limit the answer. Figures exclude tax, and recipe contribution excludes labour and overhead.

Can we use it across several kitchens? expand_more

Yes. Each kitchen keeps its own stock, recipes and currency. Transfers record both sides together. Shared access, backups and the way staff capture counts need to be set up for your team. The free source has no per-seat licence charge.

What do we pay Enterprise DNA for? expand_more

One setup fee, then a retainer for the agreed service. We map the old records, customise the work, connect the systems and run it through Omni. The open-source version remains free to use yourself. Hosting and agent subscriptions are separate from the free source licence.

Bring the bill and one recipe that lost its margin

Spend 30 minutes with Sam. We look at your MarketMan bill, the records your chef uses and the work around each stocktake. Then we agree what your own version needs to do.

Book a call with Sam Get the free version

Kitchen Costing for Claude Code is free and open source, published by Enterprise DNA.

Done paying for MarketMan?

Get your version built