Anonymous product configuration case study

Building a multilingual online product configurator

A software provider needed two coordinated modules that would let customers design and book a configurable windscreen online while administrators managed multilingual page content and email templates.

  • Product Configurator
  • E-commerce
  • Multilingual Content
  • .NET

The situation

A step-by-step designer and its navigation module had to behave like one product.

The primary design module needed to guide users through size, color, logos, text, description, preview, and booking. A separate step-menu module needed to save progress, switch stages, and display a summary for each step.

The broader scope also included scheduling, email, data access, order generation, e-commerce, and multilingual content—making module coordination and dynamic language settings the central technical challenges.

Illustrative online product design studio with size, color, artwork, preview, order, and safe-area controls.
Illustrative configurator concept based on the documented design steps; not a production screenshot.

The product challenge

Coordinate modular software across a continuous design, preview, and order journey.

The experience needed the flexibility of independent platform modules without exposing that separation to customers or administrators.

01

Interaction between modules

The step menu had to trigger saving and navigation in the primary design module without creating brittle flow control.

02

Dynamic multilingual content

Administrator-managed page copy and email templates could not rely on static source-language resources.

03

A wide transaction scope

Design, booking, scheduling, email, data access, e-commerce, and order generation all had to contribute to one coherent path.

The solution

Two DotNetNuke modules were coordinated through simple client-side behavior and shared multilingual administration.

The primary module handled design and booking while the step module managed stage switching and summaries. The implementation used generated .NET callbacks to coordinate saves and navigation without complex flow control.

  1. 01

    Guide the configuration

    Break size, color, artwork, text, description, preview, and booking into understandable steps.

  2. 02

    Coordinate independent modules

    Use lightweight client-side scripts and .NET callbacks for saving and stage changes.

  3. 03

    Localize dynamic content

    Give administrators language controls for page documents and email templates that could not be translated through static code alone.

Illustrative multilingual order review with design summary, language controls, email template, and order preview.
Illustrative multilingual order-review concept; not a production screenshot.

How we worked

Treat module boundaries as an implementation detail, not a user journey boundary.

The team mapped the design and booking flow across the step menu and primary module before selecting a simple coordination approach.

Development covered the wider DotNetNuke ecosystem, including scheduling, email, the data-access layer, product design, order management, and e-commerce behavior.

Alpha testing and defect correction verified how the separate modules and multilingual settings behaved as one end-to-end product.

01Configure

Capture size, color, artwork, text, and description.

02Coordinate

Save and navigate across the two modules.

03Localize

Manage dynamic content and email by language.

04Complete

Preview, book, schedule, and generate the order.

The result

The module suite supported a complete multilingual path from product design to order preparation.

The implemented modules connected step-by-step configuration, persistent summaries, preview, booking, scheduling, email, e-commerce, order generation, and administrator-managed multilingual content.

Two coordinated modulesfor navigation, design, and booking
Multilingual administrationfor dynamic page content and email templates
End-to-end product flowfrom configuration through order generation

A guided design experience

Customers could define product attributes step by step and preview the configuration as it evolved.

Module separation without journey breaks

Client-side coordination let the step menu and design module behave as a unified product.

Localization beyond static labels

Administrators could manage language-specific documents and email templates as dynamic content.

Case taxonomy

Searchable by industry, technology, product, and business need.

Industry and product

  • Product Configurator
  • Manufacturing
  • E-commerce
  • Online Design
  • Booking

Technology and delivery

  • DotNetNuke
  • .NET
  • IIS
  • SQL Server
  • Module Integration
  • Alpha Testing

Business need

  • Multilingual Content
  • Order Generation
  • Email Templates
  • Scheduling
  • Product Preview

Turn configuration into a complete journey

Need a modular product configurator that still feels like one continuous experience?

Talk to our team

Get in touch

Ready to build software that fits your business?

Tell us what you need to build, modernize, automate, or augment with AI. We can start with a focused discussion or a no-risk 1-week trial.

“A fantastic company to work with.” After the initial rapid development project, American Shipping Co. kept two Shinetech developers embedded for nearly four years, supporting internal and external tools and new AI initiatives.
Marc Greenberg testimonial portrait Marc GreenbergCEO, American Shipping Co. - 5-star Google Review

Response within 1 business day.