Furniture manufacturers who want "customers pick fabric, finish, and dimensions online, and the system generates the right BOM automatically" are describing configure-to-order (CTO), and Acumatica's answer to that is the Product Configurator module. It is real functionality, not vaporware, but it is also the single most implementation-heavy module in Manufacturing Edition, and I want to be direct about that before anyone budgets it as a quick add-on.
What the Configurator actually does
The Product Configurator lets you define a configurable item template with attributes (fabric, finish, dimensions, arm style) and rules — feature/option trees, formulas, and constraints — that generate a specific BOM and routing at order entry time based on the customer's selections, with calculated cost and price following automatically. A sales order line for a configurable sofa triggers a configuration session; the customer's picks resolve into a concrete BOM (a specific fabric SKU, a specific frame routing) before the order is confirmed.
Feature: Arm Style Options: [Track, Rolled, Tuxedo]
Feature: Fabric Grade Options: [Grade A, Grade B, Grade C, COM]
Rule: IF ArmStyle = 'Tuxedo' THEN RequireOption('Reinforced Frame')
Formula: FabricYardage = BaseYardage * SizeMultiplier[Dimension]
Result: Resolves to BOM# SOFA-STD--,
with Fabric component substituted per Fabric Grade selection The implementation cost is rule authoring, not licensing
Every feature, option, constraint, and formula is configuration work done by someone who understands both the product line and the Configurator's rule syntax — for a sofa line with 4 arm styles, 3 frame options, and COM (customer's-own-material) fabric handling, that is realistically weeks of rule-building and testing, not a checkbox in setup. Clients who come in expecting a drag-and-drop "just describe your products" experience are usually surprised by this. I scope Configurator projects with an explicit rule-count estimate up front so the effort is visible before the SOW is signed, not discovered mid-project.
The Configurator rewards starting with your highest-volume configurable product family, proving the rule structure works end-to-end (quote through production through costing), and expanding to the rest of the line afterward — not modeling every SKU family simultaneously. I have seen furniture Configurator projects stall when the team tried to model the entire catalog before validating the pattern on one product line.
Customer's-own-material (COM) is a real gap you'll hit
Furniture specifically has a common requirement the Configurator does not solve out of the box: COM, where the customer supplies their own fabric and the manufacturer needs to track yardage received, consumed, and remaining against that specific customer's order — essentially a mini lot-tracked inventory for material the company does not own. Acumatica has no native "customer-owned inventory" concept; the workaround is a non-stock or zero-cost inventory item scoped to the sales order with quantity tracked through standard issue transactions, which works but needs to be modeled deliberately, not assumed to exist.
Wrapping up
The Product Configurator genuinely delivers configure-to-order for furniture, but the deliverable is proportional to the rule-authoring effort invested — this is the module where "it's just configuration, not code" is technically true and still represents real weeks of work. Scope it honestly, start with one product family, and plan explicitly for COM material tracking since it is not a native concept.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.