You are scoping a kitchen planner app, and you have probably tried the IKEA one, so you already know the bar. A founder or a retail brand wants a tool where a customer draws their kitchen, drops in cabinets, swaps doors and worktops, and watches a price update as they go. The real question is what that takes to build, and where the cost hides. The short answer: the hard part is not the 3D. It is the parametric catalogue, the cabinets in fixed sizes that snap together with doors, worktops and appliances as priced options, sitting on a layout that respects walls and plumbing.
One thing up front. IKEA is a reference brand in this post, not an appico client, and appico did not build the IKEA planner. Every fact about the IKEA planner below comes from IKEA's own pages, linked at the point it is used. Anything described as a general mechanism is written as "a kitchen planner like this needs", to keep IKEA's stated facts apart from engineering opinion.
What is a kitchen planner app, in plain terms?
A kitchen planner app is a design tool where a customer lays out a kitchen to scale, fits real cabinets and appliances into it, and gets a plan, a parts list and a price. It is closer to a product configurator than to a drawing app. The furniture is not decoration you place freely. It is a catalogue of buyable items with sizes and rules.
IKEA describes its own kitchen planner as a tool that "works online, so you don't need to download a program", and calls it a 3D kitchen planner (IKEA kitchen planner page). On its planners hub, IKEA says its room planners let you "create a detailed technical plan of your space, including windows, outlets and pipes" (IKEA planners hub). Those two facts, web-based and constraint-aware down to pipes and outlets, tell you most of what you need to know about the shape of the problem.
If your product is a general furniture placer rather than a kitchen tool, the build is different and lighter. Read our guide to building a 3D room planner app for that path. This post is about the harder kitchen case, where the catalogue and the pricing carry the weight.
Why is a kitchen planner harder than a room planner?
A room planner lets you drop furniture of a fixed size anywhere. A kitchen planner has to configure and cost real products. Cabinets come in set widths, snap into continuous runs and corners, sit at fixed worktop heights, and expose doors, worktops, handles and appliances as options. Each option changes the shape and the price. That configuration layer is the extra work.
The picture below shows the gap at a glance. Everything on the right side is engineering a room planner never touches.
Read down the right column and you can see why teams underestimate this. "Cabinets in fixed sizes" sounds simple until you realise the app must know every allowed width, refuse the ones that do not exist, and fill an awkward gap with a filler panel the way a real fitter would. "Live price and parts list" sounds like a footer number until you realise it has to agree with your checkout to the cent. None of this exists in a place-a-sofa room planner.
The parametric catalogue: the part worth owning
The parametric catalogue is the core of a kitchen planner, and it is where most of the budget and most of the risk sit. Parametric means each cabinet is stored as a rule, not as one fixed model. A base cabinet family knows its allowed widths, its depth, its height, its carcass, and where its door, drawers and shelves go. One definition then produces every valid size on demand.
Why does this matter so much? Because the alternative does not scale. If you model every cabinet in every width as a separate object, a modest range explodes into thousands of hand-built models that all have to be priced, textured and kept in sync. A parametric family collapses that into one rule plus a list of allowed sizes. It is the difference between a catalogue you can maintain and one that owns you.
How cabinets snap together
Snapping is the behaviour that makes a kitchen feel real. A base unit dropped next to another should align to the same depth, share a worktop line, and butt up with no gap. At a corner, the app has to insert a corner unit or a filler, not overlap two cabinets. Wall units snap to a fixed height above the worktop. Tall units break the worktop line and need their own rules.
This is the single biggest sink of engineering time, and it is why the flow below puts the layout engine and the rules before the 3D view. Get snapping and constraints wrong and every plan a customer makes is subtly impossible to actually build.
Doors, worktops and appliances as options
On top of the carcass sit the choices. A door front is an option with its own price and finish. A worktop is a run that spans several cabinets and is priced by length and material. An appliance is a unit with a fixed cut-out that the surrounding cabinets must accommodate. In a parametric model these are attachments, not new cabinets, so a customer can swap a matt door for a gloss one without the layout changing, while the price and the render both update.
The 3D assets for all of this are their own project. Producing clean, reusable models for cabinets, fronts and appliances, at a size that loads fast on the web, is covered in our guides on making 3D models for furniture apps and building a 3D model catalogue at scale. Treat the asset pipeline as a parallel track from day one, not a task for the end.
The 2D layout with wall and plumbing constraints
Most of the intelligence lives in 2D. The plan view holds the wall lengths, the ceiling height, the positions of windows and doors, and the runs for water and waste. Cabinets snap onto that plan. The 3D view then reads the same plan and renders it as a room. IKEA's own description of a technical plan "including windows, outlets and pipes" is exactly this layer.
Plumbing and services are the constraints that separate a toy from a tool. A sink base has to sit where the waste pipe can reach. A hob or oven needs the right supply. A dishwasher needs both water and drainage. A planner that ignores these will happily draw a kitchen that no plumber can install. You do not have to model pipes perfectly, but the app needs to let a user mark where services are and warn when a fixture lands somewhere it cannot be served.
Accurate measurement underpins all of it. If your app captures a room with a phone camera rather than typed dimensions, the scale has to be right, because a cabinet run that is two centimetres too long will not fit the wall. Apple's room-scanning framework is one route to a measured plan, explained in our piece on what Apple RoomPlan is and where it fits.
What are the build phases for a kitchen planner app?
Build in this order: scope the catalogue and its rules, build the 2D layout engine with snapping and constraints, model the parts as parametric families, wire the pricing engine, then ship the plan and buy list. The 3D view slots in once the 2D plan is trustworthy. Building the 3D view first is the most common way these projects stall.
The reason the phases run this way is dependency, not preference. The layout engine needs the catalogue rules to know what can snap where. The pricing engine needs the catalogue to know what each part costs. The 3D view needs the plan to know what to render. Skip ahead and you build on rules that are not settled yet, then rework everything when they change. If you are turning a rough concept into a first scoped version, our guide on turning an idea into an app covers how to cut the first version down to something buildable.
The modules you are actually building
It helps to see the whole thing as a set of modules, each with a clear job and a clear risk. The table below is the honest map of a kitchen planner. Read the build-note column closely, because that is where the effort and the mistakes live.
| Module | What it does | Build note |
|---|---|---|
| Catalogue engine | Holds cabinets, fronts, worktops and appliances as parametric parts | The moat. Model a family once, size it many ways |
| Layout canvas (2D) | Draws walls, windows, doors and pipe runs to scale | Constraints live here, not in the 3D view |
| 3D view | Renders the same plan as a room you can look around | Reuses the 2D parts. It is a viewer, not the truth |
| Snapping and rules | Clicks units into runs, corners and fixed heights | Where the most engineering time goes |
| Configurator | Swaps fronts, worktops, handles and appliances | Each choice changes both the price and the geometry |
| Pricing engine | Adds every chosen part into a running total | Has to match your real store prices to the cent |
| Export and buy list | Outputs the plan, the parts list and the price | The commercial payoff, and often an afterthought |
Two modules in that table are underestimated in almost every quote. The pricing engine looks trivial and is not, because it has to stay in step with your real store prices, promotions and stock. The export and buy list looks like a formatting task and is not, because it is the point where a design becomes an order, and any mismatch there is a mismatch a customer sees at checkout.
Tell us what you have in mind. We turn AI prototypes and fresh ideas into shipped, scalable products, from India, for the US and UK.
What does it cost to build a kitchen planner app?
Cost tracks catalogue depth more than screen count. A focused first version, with a small cabinet range and 2D pricing, sits in appico MVP territory, from about $10,000. A native mobile app starts from about $12,000. A full planner, with 3D, a wide configurable catalogue and live store integration, is a larger build that can run up to about $150,000. A simpler web front for browsing designs can start from about $1,000, and ongoing upkeep is a separate monthly plan.
The drivers behind those numbers are worth naming, because they are where a quote grows or shrinks:
- Catalogue size. Each cabinet family, finish and appliance is more parametric work and more pricing rules to test. Ten families is a different project from a hundred.
- 3D asset production. Modelling, texturing and web-optimising every part is a real line item that often runs alongside the software. The two model guides linked above explain why this can be a large share of the total.
- Pricing accuracy and integration. Reading live prices and stock from your store or ERP is more work than typing prices into the app, but it is the only way the planner stays correct.
- Constraint depth. Basic snapping is cheaper than full corner logic, filler panels and plumbing warnings. Decide how far into fitter-grade rules you need to go.
- Platform. A web planner, a native app, or both changes the number. Detailed planning suits a big screen, which is why many planners are web-first.
For a like-for-like comparison against a general 3D planner, see our breakdown of the cost to build a 3D room planner app, and put your own numbers through the project cost calculator before you commit. If a kitchen planner is one part of a bigger retail AR product, the full guide to building an app like IKEA Place sets the wider scope.
When a kitchen planner app is not worth it
A full planner is not always the right build, and an honest answer saves you money. It is probably not worth it if your range is small, your prices move often, or most customers still want a designer to visit and measure. In those cases a clean product gallery and a booking form deliver most of the value for a fraction of the cost, and they do not carry a catalogue you have to keep in sync.
It also disappoints when the catalogue behind it is thin. The IKEA planner feels powerful partly because it sits on a huge, well-structured product range. A planner with twenty cabinets and three finishes will feel empty no matter how good the 3D looks, and the effort is better spent widening the range first. A planner is a way to sell a deep catalogue, not a substitute for having one.
And it is the wrong first move if you are still testing whether customers want to self-serve at all. Ship the lighter tool, watch whether people design and save kitchens, and only then invest in the full engine. On monetisation, the patterns that actually pay back are covered in how room planner apps make money.
Our take
We build these as a senior team out of India for US, UK and global brands, with fixed scope and prices agreed up front, and you own the code and the catalogue from day one. The lesson from every planner we have scoped is the same: the win is in the boring middle, the catalogue rules and the pricing, not the 3D that everyone demos first. Get the parts, the snapping and the prices right, and the visible layers fall into place. Get them wrong, and no amount of polish hides a kitchen that cannot be built or a price that does not match the till.
If you want a scoped plan and a fixed number for a kitchen planner, talk to us through our app development service. Bring your product range and your current price list, and the first conversation is about the catalogue, because that is the project. When you are ready to build, our product and app development team can take it from scope to launch.
Frequently asked questions
How much does it cost to build a kitchen planner app like IKEA?
It depends on how deep the catalogue goes. A focused first version with a small cabinet range and 2D pricing can start in appico MVP territory, from about $10,000. A native mobile app starts from about $12,000. A full planner with 3D, a wide configurable catalogue and store integration is a larger build that can run up to about $150,000. The catalogue and 3D assets drive most of the cost.
What is a parametric catalogue in a kitchen planner app?
A parametric catalogue stores each cabinet as a rule, not as one fixed model. A base cabinet family knows its allowed widths, its height, its depth and where its door and shelves go, so one definition produces every size variant on demand. Doors, worktops, handles and appliances attach as options. This is what lets a planner offer thousands of combinations without modelling each one by hand.
Do I need 3D for a kitchen planner app, or is 2D enough?
Most of the real work happens in 2D. The plan view holds the measurements, the wall lengths, the window and door positions and the pipe runs, and it is where cabinets snap into place. A 3D view helps customers picture the result and raises confidence, but it reads from the same 2D plan. Start with an accurate 2D engine, then add 3D once the layout and pricing are solid.
How long does it take to build a kitchen planner app?
A scoped first version with a limited catalogue and 2D layout can take a few months. A full planner with 3D, a wide configurable range and live store pricing takes longer because the catalogue and 3D assets are produced in parallel with the software. The honest driver is catalogue size, not the app screens. More cabinet families and more finishes mean more modelling and more pricing rules to test.
What is the hardest part of building a kitchen planner app?
The parametric catalogue and the layout rules, not the graphics. Cabinets come in fixed sizes that must snap together into runs and corners, doors and worktops attach as options, and every choice has to change both the shape and the price at once. Layered on top are wall, window and plumbing constraints. Getting that engine right is deeper than anything a generic room planner needs.
Can a kitchen planner app show a live price as the customer designs?
Yes, and it should. Each part in the catalogue carries a price, so as a customer swaps a door front, extends a run or adds an appliance, the planner adds the changed parts into a running total. The engineering catch is that the total has to match your real store prices exactly. A planner price that differs from the checkout price destroys trust faster than any missing feature.
Should a kitchen planner app be web-based or a native mobile app?
Detailed kitchen planning suits a large screen, so many planners are web-based and used on a desktop or laptop. A native mobile app fits quick browsing, saved designs and a store visit, and can add camera-based measuring. A common answer is a web planner for the full design work plus a lighter mobile companion. Match the platform to how your customers actually plan a kitchen.
How is a kitchen planner different from a generic room planner?
A room planner lets you place furniture of a fixed size anywhere in a space. A kitchen planner has to configure and cost real products. Cabinets come in set sizes, snap into continuous runs, obey worktop heights and corner rules, and expose doors, worktops and appliances as priced options. It also has to respect walls and plumbing. That configuration and pricing layer is the extra work.
Can a kitchen planner connect to my existing product catalogue or ERP?
It can, and for a retailer it should. The planner needs current sizes, finishes, stock and prices, so it reads from the same source your store uses rather than a separate copy that drifts out of date. Plan the integration early. Mapping a real product range into parametric parts with correct pricing rules is usually a bigger job than the visual planner itself.
Is a kitchen planner app worth building for a small kitchen brand?
Not always. If your range is small, your prices change often and most customers still want a designer visit, a simple product gallery plus a booking form may serve you better and cost far less. A full planner earns its keep when a wide, configurable range and self-serve pricing genuinely reduce sales effort or returns. Match the tool to the size of the catalogue and the buying habit.
“Disciplined, committed, over-delivers. Three years in, I would re-hire any day.”
“A factory of ideas.”
“A fantastic-looking and performing website.”
Talk to the team, we reply within 24 hours, and the first consultation is free.
Start a conversation →