# CBX — Features > What CBX can do, at a glance. This track is the showcase: each section makes the case for one capability area the way you would to a prospect or a decision-m… Source: CBX documentation, version 3.x (released). Canonical page: https://docs.configbox.at/docs/features/. Last updated 2026-08-25. --- **What CBX can do, at a glance.** This track is the showcase: each section makes the case for one capability area the way you would to a prospect or a decision-maker — and then backs every claim with links into the documentation that describes it in full. If a claim here has no link, treat that as a bug in this track. **Audience:** people evaluating CBX — shop owners, agencies, integrators scoping a project — and anyone who needs the "why", not yet the "how". For the how: the [Admin Guide](https://docs.configbox.at/docs/admin-guide/) (running a store), [functional/](https://docs.configbox.at/docs/functional/evaluation) (exhaustive behavior), [technical/](https://docs.configbox.at/docs/technical/) (the code), and [customization/](https://docs.configbox.at/docs/customization/) (extending it). > **Already know CBX and want to know what changed?** > **→ [Latest features](https://docs.configbox.at/docs/features/latest/)** — what has landed since the 4.0 line opened, area by area: > [configurator & storefront](https://docs.configbox.at/docs/features/latest/configurator-and-storefront) · > [the admin](https://docs.configbox.at/docs/features/latest/admin-experience) · [the HTTP API](https://docs.configbox.at/docs/features/latest/http-api) · > [the CLI](https://docs.configbox.at/docs/features/latest/cli) · [the MCP server](https://docs.configbox.at/docs/features/latest/mcp-server) · > [the AI assistant](https://docs.configbox.at/docs/features/latest/ai-assistant) · > [payments & commerce](https://docs.configbox.at/docs/features/latest/payments-and-commerce) · > [catalog operations](https://docs.configbox.at/docs/features/latest/catalog-operations) · > [platform & extensibility](https://docs.configbox.at/docs/features/latest/platform-and-extensibility). > (For the CBX 2/3 → CBX 4 *upgrade* story instead, see > [migration-to-cb4/](https://docs.configbox.at/docs/migration-to-cb4/).) --- ## A real product configurator, not a form builder Customers compose products step by step — pages, questions, answers — with a **live price** at every click, conditional show/hide logic, quantity and text inputs, image uploads, and optional **2D/3D visualization** (including ShapeDiver-backed parametric 3D). Configurations are first-class objects: they can be saved, re-edited from the cart, and they freeze into the order exactly as configured. - [Building a product: Product → Pages → Questions → Answers](https://docs.configbox.at/docs/functional/configurator_building) - [What end-customers can do, as user stories](https://docs.configbox.at/docs/functional/user_stories) - [Admin Guide: create your first product](https://docs.configbox.at/docs/admin-guide/) ## Pricing and logic without a developer Store admins author **conditional rules** ("show the motor question only for the cargo frame") and **calculations** (formula, code, or matrix — e.g. price by width × height lookup) in the admin UI. The rule and calculation engines evaluate live in the configurator and again server-side, so the price the customer sees is the price the order stores. - [How admins author rules](https://docs.configbox.at/docs/functional/rule_authoring) · [the engine underneath](https://docs.configbox.at/docs/technical/rule_engine) - [How admins author calculations](https://docs.configbox.at/docs/functional/calculation_authoring) · [the engine underneath](https://docs.configbox.at/docs/technical/calculation_engine) ## Commerce built in — or your platform's CBX ships a complete flow around the configurator: cart, checkout, customer accounts, quotations, invoices, order processing, transactional e-mails, taxes, shipping and payment methods (extensible PSP connectors). On Magento 2, CBX instead plugs its configurator into Magento's own cart/checkout/orders — you choose the commerce brain per platform. - [Commerce setup: groups, currencies, taxes, shipping, payment](https://docs.configbox.at/docs/functional/commerce_setup) - [Running the shop: orders, customers, notifications](https://docs.configbox.at/docs/functional/operations) - [Admin Guide: commerce](https://docs.configbox.at/docs/admin-guide/) · [CBX on Magento 2](https://docs.configbox.at/docs/admin-guide/magento2/) ## One application, three host platforms The same CBX application runs inside **Joomla**, **WordPress** and **Magento 2** — same admin screens, same data model, same release. Your team's platform choice doesn't fork the product, and a store can migrate hosts without rebuilding its catalog. A platform-abstraction layer (Kenedo) keeps behavior identical; each host gets a native integration (menus/SEF on Joomla, shortcodes and hidden post types on WordPress, catalog integration on Magento 2). - Platform guides: [Joomla](https://docs.configbox.at/docs/platform/joomla/joomla_platform_guide) · [WordPress](https://docs.configbox.at/docs/platform/wordpress/wordpress_platform_guide) · [Magento 2](https://docs.configbox.at/docs/platform/magento2/magento2_platform_guide) ## Multi-language, multi-currency, B2B-ready Every customer-facing text — product names, questions, answers, URL segments — is translatable in-place (flag icons next to each field), with per-language SEF URLs. Currencies, tax classes and geography-aware rates are built in. Customer **groups** are the B2B policy hub: per-group discounts and tax mode, whether a group sees prices at all, per-group shipping methods, and quotation (RFQ) workflows alongside direct orders. - [Configuration & settings, per option](https://docs.configbox.at/docs/functional/configuration) - [Commerce setup: groups, currencies, tax, geography](https://docs.configbox.at/docs/functional/commerce_setup) ## Operations tooling that respects your deploy pipeline A full CLI suite ships on every platform (`wp configbox …`, `php cli/joomla.php configbox:…`, `bin/magento configbox:…`): cache clearing, **deploy-gate migration status** (non-zero exit while work is pending), guided recovery from failed migrations, settings read/write with UI-grade validation, and `run-task` to exercise any endpoint headlessly. Schema updates are versioned, idempotent scripts with an explicit freeze-on-failure design. There is even an **MCP server**, so an AI assistant can read your catalog through typed tools. - [The CLI command suite](https://docs.configbox.at/docs/technical/cli_commands) - [Database migrations](https://docs.configbox.at/docs/technical/migrations) - [The MCP server](https://docs.configbox.at/docs/technical/mcp_server) ## Move a product between installs, logic and all A configured product is not one record — it is pages, questions, answers, detail panes, the rules wired through all of it, every calculation any of it uses, and the images hanging off any of those. **Product transfer** packages the whole graph as a zip and imports it into another CBX install: build on staging and push to live, or lift a product from one client's site to another. References are **re-aimed on arrival** — a rule that named answer 412 on the source names the right answer here — while things that belong to the target, like tax classes and customer groups, are matched by name and never invented. The import is **checked before anything is written**: blockers stop it, warnings are shown for the operator to acknowledge, and a package can be imported either as fresh products or under the original IDs to overwrite what is there. Both halves have a command-line equivalent, so it drops into a deploy script. - [Admin Guide: move products between sites](https://docs.configbox.at/docs/admin-guide/products/move-products-between-sites) - [Product transfer: the package format, both import modes, and what is validated](https://docs.configbox.at/docs/technical/product_transfer) ## Smaller things that make the admin's day easier Not headline capabilities — the everyday friction that gets filed down release by release. - **Images straight into any rich-text field.** Drag a photo onto a product description, paste one from the clipboard, or pick it in the editor's image dialog. It is stored where an extension update will not touch it, scaled down to a sensible web size, and converted to **WebP** — so a 6000-pixel camera original does not become a several-megabyte product page. Uploading the same picture twice reuses the first one rather than filling the disk with copies. - [Editor image upload: what happens to the file and where it lands](https://docs.configbox.at/docs/technical/editor_image_upload) ## The customization layer — extend it without forking it Agencies and in-house developers get a **supported, upgrade-safe extension layer**: override templates, add fields to stock models, write event observers, payment connectors, custom rule conditions, custom admin field types, frontend JS/CSS modules — and even **site-specific CLI commands** — all in one directory that updates never touch. This is the feature that keeps customized CBX stores updatable for years. **→ [The customization layer, in full](https://docs.configbox.at/docs/features/customization-layer)** (this track's deep-dive section) ## What has changed lately The sections above describe CBX as it stands. **[Latest features](https://docs.configbox.at/docs/features/latest/)** is the other cut of the same product: what has landed since the 4.0 line opened — across the storefront, the admin, the HTTP API, the CLI, the MCP server, the AI assistant, payments, catalog operations and the extension layer — one child article per area, same linking rule. **→ [Latest features](https://docs.configbox.at/docs/features/latest/)** (this track's what's-new section) --- *Every capability above is documented in depth — start at the [documentation index](https://docs.configbox.at/docs/). Found a claim without a link, or a capability without a section? Extend this track; it is maintained with the product.*