Feature Request: Integrate Underpanel as Subassembly within Upper Cabinet Product

Hi everyone,

There is currently an underpanel product available in the library, and we use it on nearly every job.

However, it must be manually inserted and positioned each time.

Given how commonly underpanels are used in upper cabinetry, it would be far more efficient if the underpanel were integrated directly into the upper cabinet product as a configurable subassembly.

Current Workflow

At the moment:

We place the upper cabinet.
We manually insert the underpanel product.
We manually position and size it.
Any cabinet size change requires manual adjustment of the underpanel.
Corner situations require additional manual handling.
There is no native corner underpanel with radiused front edge behaviour.

While this works, it introduces repetitive manual steps into something we use on nearly every project.

Why Integration Makes More Sense

If the underpanel were a subassembly within the upper cabinet product:

It would follow cabinet geometry automatically.
It would resize parametrically with cabinet changes.
It would remain structurally tied to the cabinet.
It would reduce the risk of missed or misaligned parts.
It would simplify drafting and training.

For high-volume environments, manually placing a structural component that is used on nearly every job adds unnecessary friction.

Corner and Radiused Requirement

In addition to integration, it would be valuable to include:

A corner underpanel configuration.
Configurable front edge radius.
Adjustable overhang and setback.
Full machining, nesting, and reporting integration.

Currently, corner radiused underpanels must be custom-built each time.

Business Impact

As workflows move toward greater automation and ERP integration, structural elements that require manual placement reduce reliability and scalability.

Given how standard underpanels are in modern cabinetry, integrating them as a configurable subassembly within the upper cabinet product would significantly improve efficiency and consistency.

NOTE: This post was drafted with the assistance of AI due to time constraints. The workflow issue and feature request reflect our genuine production experience. While I appreciate the transparency and community engagement Microvellum is encouraging, submitting feature requests via ticket was significantly faster from an operational standpoint.