Dahu Composite

Server-driven configurable product kits for WooCommerce.

Developed and maintained by Hugo Vial-Jaime — Dahu-Concept.

What it does

Dahu Composite turns a WooCommerce product into a guided configurator. The customer walks through steps, picks an option at each one, and ends on a summary with a price and a weight that the server worked out.

That split is the point. Everything a shopper can change is revalidated server side before it reaches the cart, so a configuration that passed the configurator is a configuration the cart accepts. Nothing a client sends is trusted.

Architecture

A kit is a list of components. Each component offers products as options, and each option carries its own variation, quantity bounds, weight handling and display settings. Scenarios describe what happens to one component depending on what was chosen in another: hide options, keep only a subset, or stop the journey with a message.

The front end is a thin client. It calls one REST route on every customer action:

POST /wp-json/dahu-composite/v1/state
     { product_id, selections, quantity }
  -> corrected selections, validity, price, weight, lines — in one response

The server fixes selections invalidated by a scenario and cascades internally, with no further round trips. /validate and /quote remain as read-only routes for external headless clients; they take selections as given and never correct them.

REST routes

Price responses carry Cache-Control: no-store, private, because prices depend on the customer's role.

Features

• Step-by-step configurator with server-side validation
• Scenarios: conditional hiding, restriction to a subset, dead ends with a message
• Price and weight computed from the selected options
• Category sections with their own icons, colours and help bubbles
• Per-customer exceptions unlocking restricted options
• Saved configurations in My Account, with optional guest saving
• Admin simulator: test a configuration before saving the product
• JSON import and export of a kit's configuration
• Compatible with High-Performance Order Storage (HPOS)

Requirements

Optional integrations

The plugin works on its own. When they are present it also talks to Dahu Pricing (role-based price labels and tiers) and to a product bundle plugin (components offering a bundle as an option). Neither is required, and neither is bundled.

Theming

The configurator reads its palette from CSS custom properties, each with a light, neutral fallback, so it is readable on a stock WordPress page with no setup:

A theme imposes its own palette by defining these on :root; the theme's values always win over the fallbacks. For a dark theme, define the surface and text variables and the whole configurator follows:

:root {
    --color-surface-2: #2F2F2F;
    --color-on-surface: #F5F5F5;
}

For theme developers

Take over the configurator's styling:

add_filter( 'dahu_composite_theme_provides_styles', '__return_true' );

The plugin then enqueues only its functional stylesheet — drawer position, animation, scroll locking, column grid — and leaves the skin to you.

Render the detail tabs yourself:

add_filter( 'dahu_composite_product_tabs_callback', static function () {
    return 'my_theme_product_tabs'; // ( WC_Product $product, string[] $slugs )
} );

Hooks

Every filter the plugin exposes. None of them is required; the defaults are what the plugin does on its own.

Two of them carry wording rather than behaviour, and both are documented with a worked example in the source: dahu_composite_category_icons (Dahu_Composite_Frontend::category_icons()) and dahu_composite_includes_label (Dahu_Composite_Included::includes_label()).

Uninstalling

Deleting the plugin removes its settings and caches. Kit definitions and saved customer configurations are kept, because an uninstall is often just a step in reinstalling. To wipe everything, set dahu_composite_remove_data_on_uninstall to a truthy value before deleting.

External services

This plugin does not contact any external service.

License

MIT — see LICENSE.