Drone builder for FPV stores

Selection starts with the frame

The “Wizard” mode takes the customer from the frame through the propulsion system, flight control and FPV to power and add-ons. The chosen frame sets the limits: parts with the wrong mount or a propeller that is too large become unavailable. The builder explains why.

On a phone, selection also goes step by step. Each part’s card shows its specs, price and stock level, so the customer can assess a component before adding it to the build.

Compatibility is checked during selection

The Python core checks geometry, weight and center of gravity, power, protocols, UART ports and thrust-to-weight ratio. When a part is swapped, the specs are recalculated: the customer sees how the weight, current draw and estimated flight time change. Messages are split into errors, warnings and explanations. A blocking error disables adding the kit to the cart.

To calculate the center of gravity, each slot on the frame has defined mounting coordinates for its component. Thrust is calculated from the manufacturer’s measurements in the motor’s data table. If no suitable data is available, the result is marked as an estimate.

Catalog and rules without code

Store staff manage parts in the admin panel: they search by name and SKU, filter by category, and edit specs, prices and stock. Each category has its own form. The catalog can be imported from CSV or XLSX with a preview and column mapping.

A separate rule builder links properties of different categories. For example, it can limit propeller size for a certain frame class or battery voltage for the motors. The administrator sets the condition, message level and priority, and turns a rule on or off without changing the code.

Statistics show what gets in the way of a build

The admin panel collects checks, blocks, add-to-cart events and saved builds for a selected period. A funnel shows the path from check to cart, and a table of frequent errors shows staff which incompatibilities come up most often.

Embedding in the store’s website

The Preact widget supports the store’s colors and font. Shadow DOM isolates its styles from the site’s design. Partners’ data is separated into PostgreSQL schemas, and Redis caches the catalog and check results.

To pass the kit to the cart, we implemented a JavaScript event and a callback. The site receives the products, quantities and total based on its own catalog, then calculates discounts. The customer does not have to add each part again.

A guest build is saved in the browser’s local storage. A configuration can also be saved as a link and sent to a friend or a sales consultant. For a first look at the product, we prepared a browser demo: the Python core runs via Pyodide without a server API.