A browser-based operational platform that connects complex product configuration, live technical drawings, documents and manufacturer ordering.
TechGeni designed and built the solution from the ground up for a European window sales business. The platform replaces fragmented spreadsheets, sketches and manual handoffs with one governed workflow—from reusable product definitions to validated manufacturer-ready orders.
Client and product details have been anonymized.
Industry: Window sales and manufacturing Engagement: Greenfield custom platform Status: Operational and evolving
Role-based access is enforced at the API layer. Major records retain created-by, updated-by and deleted-by audit fields. Soft deletion, project versioning, request validation, required-field checks and dependency checks protect data integrity throughout the workflow.
Industry: Window sales and manufacturing Engagement: Greenfield custom platform Status: Operational and evolving
The business challenge
A window is not a simple stock item. Each sale can involve dimensions, sash layouts, opening directions, frame extensions, glass options, colours, accessories, technical drawings, document templates and a manufacturer-specific order format. When this information is distributed across spreadsheets, sketches, catalogues and partner files, every handoff creates delay and another opportunity for error. The client needed a system that could capture product knowledge once and reuse it throughout the commercial and operational process.What had to change
- Fragmented product knowledge: Rules and options were difficult to maintain consistently across separate tools.
- Repeated manual entry: Dimensions and selections could be retyped for drawings, documents and orders.
- Complex technical products: Multi-sash layouts and accessories required structured, position-specific configuration.
- Partner-specific output: Each manufacturer could require different fields, codes, payloads or file formats.
- Limited traceability: Offer revisions, configuration changes and order activity needed a reliable history.
A single connected workflow
TechGeni designed the platform around one shared data model. Product definitions drive the configurator, configured project data drives documents, and the same validated data is transformed for the selected manufacturer.- Catalogue and rules — reusable product structures, attributes and options.
- Project and version — customer-specific configurations with revision history.
- Visual configuration — guided data entry with a live technical drawing.
- Documents and validation — consistent output generated from current project data.
- Manufacturer dispatch — partner-specific data prepared for API, XML or file-based delivery.
An attribute-driven product foundation
Rather than building a fixed form for every product, TechGeni created an attribute-driven platform. Administrators define reusable attributes, option sets, product categories, build types, sub-products, document fields and manufacturer mappings. Sales users then work with a focused interface generated from those definitions.One model, multiple outputs
- Central product catalogue: Categories, SKUs, media, build types, manufacturers and related sub-products are maintained in one place.
- Reusable attributes: Text, numeric, selection and file fields can be assigned to categories and reused across products.
- Flexible mappings: Whole-window and per-sash attributes connect catalogue data to visual and integration fields.
- Configuration templates: Preset values speed up repeated project setup while keeping the underlying data structured.
Visual product configuration
The flagship configurator turns complex technical selections into a guided sales workflow. As dimensions and options change, a live SVG drawing updates with sash geometry, opening symbols, frame extensions and millimetre measurements. The interface adapts to the build type selected for the product.Build types encode product structure
Ten supported layouts cover common single-wing, multi-wing, stacked, grid, T-shaped and L-shaped structures. Each build type defines which sashes exist and how the preview behaves. Product structure is therefore controlled by reusable configuration rather than duplicated interface logic.Documents generated from live project data
Configured project data does not stop at the drawing. The platform reuses the same source data to generate consistent customer and internal documents, validate manufacturer requirements, build partner-specific payloads and record order activity.Configurable document templates
Administrators choose which customer, project, product and configuration fields appear in grid-based output. PDF and multi-sheet Excel exports are generated from current data, so documents remain aligned with the project configuration. This approach provides three operational advantages:- One source of truth: Documents reflect the same configuration that users reviewed on screen.
- Flexible layout control: Teams can tailor headers, columns and compact sub-product presentation by document.
- Consistent exports: Current project data flows into PDF and Excel output without rebuilding the order by hand.
Validated manufacturer ordering
Manufacturer mappings can use attributes, fixed values, calculated values or product categories. Required fields are checked before dispatch. The integration layer supports authenticated API payloads, OpenTrans XML and Excel output, with logging, retry and timeout handling where applicable.A controlled handoff to production
- Clear status: Each line item shows the selected manufacturer and current order state.
- Consistent review: Teams can preview the generated grid before sharing or dispatching the order.
- Flexible delivery: The same workflow supports integrated and file-based manufacturing partners.
- Traceable operations: Validation results, user actions and order activity remain connected to the project history.
How TechGeni implemented the platform
TechGeni built the solution from the ground up using a modular, API-first architecture. The engineering approach focused on modelling the client’s product knowledge before automating individual screens, allowing the same rules and attributes to serve sales, operations, documents and integrations.- Domain modelling: Product categories, attributes, build types, projects, versions, sub-products, manufacturers and orders were defined as connected business entities.
- API-first backend: Business logic, validation, exports and integrations are exposed through a RESTful Laravel API.
- Responsive user experience: A Vue 3 single-page application gives sales users and administrators focused browser workflows.
- Visual rules engine: SVG-based drawings translate structured selections into an immediate technical representation.
- Integration layer: Configurable mappings transform internal product data into manufacturer-specific API, XML or spreadsheet output.
- Controlled deployment: Docker, nginx, SSL and environment-specific configuration support maintainable releases.
Technology foundation
| Layer | Technology | Role in the platform |
|---|---|---|
| Backend | Laravel 12 and PHP 8.4 | Business rules, validation, exports and integrations |
| Frontend | Vue 3 and Quasar | Responsive browser workflows for sales and administration |
| Data | MySQL | Relational product, project, configuration and order data |
| Security | Sanctum and role permissions | Token authentication and granular access control |
| Deployment | Docker, nginx and SSL | Repeatable, environment-aware releases |
Operational results
The operational platform has improved three areas that matter directly to the client’s sales and fulfilment teams. Public baseline figures have not been approved, so the outcomes are described qualitatively.- Faster configuration and quotation preparation: Structured fields, reusable templates and an immediate technical preview shorten the path from customer requirements to a reviewable configuration.
- Fewer errors and less rework: A shared attribute model, required-field checks, version history and manufacturer mappings reduce duplicate entry and identify inconsistent data earlier.
- Faster document and order handling: PDF, Excel, API and XML outputs are generated from the same live project data instead of being reconstructed for each delivery channel.
Why this project matters
This case study demonstrates TechGeni’s ability to translate specialist product knowledge and operational rules into a maintainable business platform. The result is not a collection of isolated screens. It is a connected product, sales, document and integration foundation that can evolve as the client adds options, layouts, users and manufacturing partners.- Complex domain rules made usable: Technical product logic is presented through a guided browser experience.
- Administrative flexibility built in: Attributes, templates, mappings and product structures can evolve without hard-coding every variation.
- External partners connected safely: Validation and transformation sit between internal product data and manufacturer-specific interfaces.
- Long-term maintainability considered: The modular API-first architecture supports continued development and additional channels.