A 3D configurator demo is all front end. The version that ships for a real manufacturer is maybe one third front end. The rest is an admin the customer never sees, where someone maintains the products, the option rules, the prices, and the lead times, and reads the orders that come out. That back-office is where I spend most of the build, and I build it in Laravel with Filament.

What the back-office actually holds

For a manufacturer running a configurator, the admin needs at least:

  • Products and variants. Each product line, its 3D model, its valid options.
  • Option rules. Which choices exist, which combinations are valid, which option forces or forbids another.
  • Pricing rules. Base price, per-option surcharges, per-square-meter math. Editable by staff, not hardcoded by me.
  • Lead-time rules and a capacity input. The backlog field that makes a lead time real lives here.
  • Incoming quotes and orders. Each submitted configuration, its calculated price and lead time, its status.

The point: everything the configurator calculates has to be editable by the manufacturer without calling me. If a price changes and they cannot change it themselves, I built a brochure, not a tool.

Why Filament

Filament is an admin panel builder for Laravel. For this kind of internal tool it removes weeks of work:

  • Resource CRUD in minutes. A ProductResource with form and table is a single class. The twenty admin screens a configurator needs stop being twenty mini-projects.
  • Real validation and relationships. Option rules are relations between models. Filament renders the nested forms without me hand-building each one.
  • RBAC out of the box. The manufacturer's staff see orders and prices. They do not see system settings. Role-gated at the resource level.
  • It is still Laravel. The pricing calculator the configurator calls is the same code the admin uses to preview a price. One source of truth, used by both sides.

The shape that works

The configurator (Three.js) sends a raw config to a Laravel endpoint. Laravel calculates price and lead time, stores the quote, and the manufacturer sees it in Filament seconds later. Same models, same rules, two front ends: one public and visual, one internal and administrative.

That split is the whole architecture. The studio builds the visual half and this administrative half as one system, because a configurator that the manufacturer cannot run themselves is not finished.

I am Dominik Groński / GroDev, a studio in Poznan, Poland building custom 3D configurators and Laravel back-ends for manufacturers.