Written by: JJ Tan, Founder, Jelly
Key Takeaways
- Apicbase menu engineering requires accurate supplier pricing, portion-level recipe costing and a mapped POS before the four-quadrant matrix produces usable data.
- The module sits inside the Insights Hub and is gated by role-based permissions, with POS integrations limited by subscription tier and scope.
- Apicbase demands 20–80 hours of setup work plus one to three months of onboarding for multi-site groups, which suits operators with dedicated back-office resources.
- Jelly delivers live dish margins in the first week by scanning invoices automatically and connecting natively to Square, EPOS Now, Toast and Lightspeed in about five minutes.
- Jelly is the best menu engineering software for UK restaurants, pubs and boutique hotels that want live dish margins without a data project.
See Your Dish Margins In Week One
What Apicbase Menu Engineering Actually Measures
The four-quadrant framework of Stars, Plowhorses, Puzzles and Dogs is familiar to most operators, and Apicbase follows that structure. The key question is what the module measures and how it builds those quadrants.
Apicbase supports two measurement methods. The first is a revenue × profit margin approach, which weights dishes by the cash and margin they generate in total. That method helps when the priority is understanding which items drive the most financial impact on the P&L. The second is the Kasavana & Smith method, developed at Michigan State University in 1982, which classifies each dish on units sold (popularity index) against contribution margin, defined as selling price minus direct food cost. Kasavana himself argued that food cost percentage misleads as a menu decision tool because a dish with a higher food cost percentage can still put more money in the till per plate. Revenue-based analysis suits cash and margin impact at the business level. Kasavana & Smith suits volume-led menu decisions where you decide whether demand and per-dish contribution align, which drives repricing, repositioning or removal.
The module sits behind several gates that shape what you actually buy. Apicbase positions Menu Engineering as a distinct module within its platform, and its developer documentation confirms Menu Engineering is a separately tracked functional area alongside Sales and Insights Hub. Access is role-dependent, with detailed permission settings governing who sees what. The matrix sits inside the broader analytics and dashboards layer, and POS and supplier integrations are gated by plan and purchased scope. That gating matters because it changes what you are actually buying. The wider market comparison sits in a separate piece; first, here is how you reach the matrix inside Apicbase.
How To Access The Menu Engineering Matrix In Apicbase
The access path, based on Apicbase’s own documentation, follows this sequence.
- Log in to Apicbase and open the Insights Hub module.
- Navigate to Sales within the Insights Hub.
- Select Menu Engineering from the Sales section.
- Set your date range. Pull at least four weeks of sales so a single holiday week does not decide a dish’s verdict.
- Select the outlet you want to analyse.
- Apply filters by menu category to compare like with like, such as entrées against entrées.
Three data prerequisites must be in place before that matrix means anything. First, you need accurate supplier pricing. Apicbase updates ingredient prices automatically when suppliers integrate their catalogues, and where that integration is absent, teams must maintain prices manually. Second, you need portion-level recipe costing. Every dish must be built to a standardised recipe with correct yields, units and wastage percentages. Building ingredient libraries and mapping recipes commonly takes 20–80 hours before meaningful data flows. Third, you need a connected and mapped POS. Without clean item-level sales data, the popularity axis becomes guesswork. Data accuracy in the first 90 days is a major implementation risk, and recipe libraries, unit-of-measure mismatches and supplier catalogue errors corrupt data early.
For a time-poor kitchen team without a dedicated back-office resource, the setup work is what the module actually costs.
Does Apicbase Menu Engineering Need POS Integration?
Apicbase menu engineering depends on POS data. Apicbase’s own support documentation describes a POS as “the central hub of sales” and “essential to reach the true power of Apicbase.” Without item-level sales data flowing from a connected POS, the popularity axis of the matrix relies on manual sales imports or spreadsheet uploads, which Apicbase documents as a fallback. Output quality also depends on POS items being correctly mapped to recipes. A sale that cannot be linked to a recipe contributes nothing to the margin calculation.
Apicbase states that POS integration updates stock nightly, so the sales data feeding the menu engineering matrix reflects the prior day’s trading rather than the current moment. If you need margins as they happen, that lag is the constraint to weigh, and it is where Jelly’s approach diverges.
Jelly uses native real-time API integrations with its integration partners Square, EPOS Now, Toast and Lightspeed to deliver item-level sales data the moment a transaction completes. POS setup across these systems takes about five minutes. You open Jelly, click Integrations, sign in to the POS, grant permissions and select which categories to sync. POS-to-dish linking only surfaces items sold since the integration was connected, so mapping stays clean and free of legacy menu clutter. With sales and costs both current, the margin calculation runs itself. Invoices push to Xero in one click, and the manual reconciliation that used to take 2–5 hours a week disappears.
For a step-by-step guide to connecting inventory and POS data for menu engineering, see How To Build a Menu Engineering Inventory Integration.
The Faster Route To Live Dish Margins For UK Operators
Apicbase’s genuine strength is multi-outlet and multi-brand visibility. Apicbase’s GetApp listing states the platform is used across more than 1,000 sites by leading multi-outlet brands, and its own site reports over 4,000 sites globally. Underneath sits a recipe and supplier data model that holds standardised recipes with costing, allergen and nutrition data in one place. Guideflow’s 2026 restaurant BI comparison names Apicbase the best tool for food-cost and recipe profitability for finance teams that need recipe-to-actual reporting at the ingredient level. For a group with dedicated back-office resource, a data team and 5+ outlets, that depth earns its place.
Below that scale, the same depth becomes overhead, and the pricing structure reflects it. Apicbase’s Growth plan starts from five outlets and all pricing is quote-only, with no published per-location figure and a 15% surcharge for monthly billing. Onboarding is a scoped project: one to three months for up to 20 outlets. The setup effort and module gating are the real cost before a single dish margin appears on screen.
Jelly fits the £500k+ single-site or 2–5 site UK operator that wants live dish margins without a data team. Costs start with invoices. You photograph or email one and Jelly populates ingredient prices automatically, which makes everything downstream possible. Those prices feed Price Alert, so a supplier increase surfaces before it reaches a dish margin, and they feed the Cookbook, which builds standardised recipes with unit conversions and wastage already calculated. From there, Flash Report turns costs and POS sales into a gross profit view, and Sales Mix shows which dishes earn their place. The result is that costing a single menu item drops from 28 minutes to about 3. Onboarding generates initial value in the first week, and the flat rate is £129/month per location. Jelly users cut food costs by 3% on average in the first three months and add about 2 percentage points to gross margins.
Apicbase Menu Engineering Vs Jelly: What Actually Decides The Purchase
Everything above points to one question: how much setup can you absorb before you see a dish margin? Four factors decide that, and this section pulls them together side by side.
- Onboarding speed. Jelly generates initial value in the first week, with Price Alert and spending insights live as soon as suppliers send invoices to a dedicated email address or the kitchen photographs invoices into the app. Apicbase requires a data project first. Recipes, supplier catalogues and POS mappings must be clean before the menu engineering matrix is meaningful, and that earlier 20–80 hour setup estimate is the barrier.
- Invoice-to-cost automation. Jelly builds costs automatically from scanned invoices, updating every recipe and dish margin in real time when a new invoice arrives. Apicbase depends on maintained supplier pricing, either through integrated supplier catalogues or manual entry, and no OCR or scanning of a paper or PDF supplier invoice is described on any readable Apicbase page.
- POS breadth and setup. Jelly connects natively to its integration partners Square, EPOS Now, Toast and Lightspeed in about five minutes per integration, with real-time item-level data. Apicbase lists a broader range of POS integrations across its 42-system directory, though access is gated by plan and purchased scope. Its documentation says POS-driven stock updates run nightly for operational stability, while its CTO describes POS sales data feeding inventory, margin analysis and forecasting in real time.
- Pricing. Jelly charges a flat £129/month per location with no variable charge per user or feature. Apicbase is quote-only across all tiers, and module gating means the menu engineering capability may sit outside a base subscription.
For operators who have already read the general costing comparison, this piece focuses specifically on the menu engineering module and its access path. For the broader picture, see Apicbase Menu Costing: Why UK Operators Choose Jelly.
Conclusion: The Decision Checklist
Apicbase menu engineering is a genuinely deep module. It produces a live menu matrix combining actual food cost, sales volume and margin contribution per dish, supports multi-outlet comparison and integrates allergen and nutrition data in the same recipe model. For a larger group with dedicated back-office resource, it is the strongest recipe-to-actual reporting tool in its category.
The demands are equally clear. You need the Insights Hub and BI layer, dashboard permissions, accurate supplier pricing, portion-level recipe costing and a connected and mapped POS before the matrix produces a result worth acting on. The setup timeline is measured in months, and pricing is quote-only with a 15% surcharge for monthly billing.
Jelly is the best menu engineering software for UK restaurants, pubs and boutique hotels that want live dish margins without a data project because it builds costs automatically from scanned invoices, connects natively to Square, EPOS Now, Toast and Lightspeed, and costs a flat £129/month per location.
Before committing either way, answer these questions honestly:
- Do I have accurate supplier pricing and portion-level recipes in a usable format today?
- Is my POS connected and are menu items mapped to recipes?
- Do I need live margins this month, or can I absorb a multi-month data project first?
- Am I running five or more outlets with back-office support, or a growing 1–5 site group without a data team?
If the honest answer to the last question is the latter, Jelly is the faster, lower-friction route to the dish margins that protect your business. For a practical guide to using menu engineering software once you are live, see How To Use Menu Engineering Software: A UK Guide.
Talk Through Your Menu Engineering Options
Frequently Asked Questions
What Is Apicbase Menu Engineering?
Apicbase menu engineering is a cloud module that connects recipe costs, supplier prices and POS sales data to classify dishes by popularity and profitability using a four-quadrant matrix of Stars, Plowhorses, Puzzles and Dogs. It is a distinct module within the Apicbase platform, separately tracked and gated behind the Insights Hub and role-based dashboard permissions. The module supports both a revenue × profit margin method and the Kasavana & Smith contribution margin method.
Do You Need POS Integration For Apicbase Menu Engineering?
Yes. Apicbase’s own documentation describes a POS as essential to reach the true power of the platform. Without item-level sales data from a connected POS, the popularity axis of the menu engineering matrix relies on manual sales imports or spreadsheet uploads. The quality of the matrix output depends directly on POS items being correctly mapped to recipes and on the accuracy of the sales data flowing in.
Which Apicbase Module Includes The Menu Engineering Matrix?
Menu Engineering is a distinct module within Apicbase, listed alongside Insights Hub, Analytics, Menu Planning, Production Planning and others. Access requires the Insights Hub and appropriate dashboard permissions assigned at the user level. Apicbase’s developer audit-log documentation confirms Menu Engineering is a separately tracked functional area. POS and supplier integrations that feed the matrix are also gated by subscription plan and purchased scope.
What Is The Difference Between Revenue × Profit Margin And Kasavana & Smith?
The revenue × profit margin method weights dishes by the total cash and margin they generate, which helps you understand which items have the greatest financial impact on the P&L. The Kasavana & Smith method classifies each dish on units sold (popularity index) against contribution margin in pounds per plate, defined as selling price minus direct food cost. That method suits volume-led menu decisions such as repricing a Plowhorse, repositioning a Puzzle or removing a Dog. Kasavana argued that food cost percentage misleads as a decision tool because a dish with a higher percentage can still contribute more money per plate than one with a lower percentage.
Is There A Simpler Apicbase Menu Engineering Alternative For UK Restaurants?
Jelly is the primary alternative for UK restaurants, pubs and boutique hotels at the £500k+ single-site to 2–5 site stage. It builds costs automatically from scanned invoices, connects natively to its integration partners Square, EPOS Now, Toast and Lightspeed with about five-minute setup and shows which dishes are most popular and most profitable through its Sales Mix feature. Onboarding generates initial value in the first week, and the flat rate is £129/month per location. Jelly users cut food costs by 3% on average in the first three months.
How Quickly Can I Get Live Dish Margins?
With Jelly, live dish margins are available in the first week. Price Alert and spending insights go live as soon as suppliers send invoices to a dedicated email address or the kitchen photographs invoices into the app, and connecting a supported POS takes about five minutes. With Apicbase, the timeline depends on completing the data project first. Accurate supplier pricing, portion-level recipe costing and a mapped POS must all be in place before the menu engineering matrix produces a result worth acting on, and that same setup burden plus one to three months of onboarding is the timeline for a group of up to 20 outlets.
