The Challenge

Buying a custom number plate involves more decisions than it initially appears.

A customer may need to choose:

• Their registration

• Front, rear or a pair

• Plate dimensions

• Printed, 3D or 4D lettering

• Lettering finish

• Identifier band

• Border

• Fixing kit

• Delivery method

But not every combination can be manufactured.

Some plate formats are rear-only.

Certain finishes are unavailable on specific sizes.

Badges are only compatible with particular formats.

Short plates physically cannot accommodate every registration.

On top of that, UK road-legal number plates cannot simply be manufactured and dispatched without the required proof of identity and entitlement.

That means the website has to do much more than take payment.

It has to guide the customer through a complicated configuration process, prevent invalid orders, securely collect sensitive documents and give the Plate Studio team a reliable way to verify and manage everything afterwards.

A Plate Builder Customers Can Trust

The centrepiece of Plate Studio is its interactive plate builder.

Customers enter their registration and immediately see it rendered on screen.

As they change the:

• Plate size

• Lettering style

• Finish

• Badge

• Border

• Fixings

…the preview changes instantly.

There is no waiting for the server to generate an image and no need to reload the page.

More importantly, the preview is based on the real physical dimensions of the product.

A 340mm short plate therefore genuinely appears shorter than a standard 520mm plate.

Character proportions, margins, spacing and plate dimensions are calculated from the measurements used in the physical product.

The intention is simple:

what the customer approves on screen should closely represent what they receive.

The Plate Is Rendered Rather Than Photographed

One of the technically unusual parts of the project is that the live plate preview is not based on a library of pre-generated images.

The registration itself is rendered dynamically in the browser.

That means the platform does not need thousands of image combinations covering every registration, finish, size and plate shape.

Instead, the customer's own registration is rendered immediately in the selected configuration.

This provides several benefits:

• Instant updates

• Sharp rendering at any screen size

• Accurate differences between plate dimensions

• Easier introduction of new styles

• No delay while preview images are generated

• No requirement to maintain huge libraries of rendered plate images

Product photography still sits alongside the builder so customers can see how the real materials look in practice.

The live builder and real photography therefore perform different jobs:

the builder shows the customer's plate; the photography shows the physical finish.

Making Premium Finishes Easy to Understand

Plate Studio sells a number of different lettering finishes.

For the customer, the difference between 3D gel, 4D acrylic and 4D gel needs to be obvious before they spend more money on an upgraded product.

The builder therefore visually changes the registration itself.

It can represent finishes including:

• Printed lettering

• 3D gel

• 4D acrylic

• 4D gel

• Retro bevel

• Specialist treatments for selected formats

This is important commercially.

The customer is not simply presented with a list of product names and prices.

They can see how their own registration changes as they move through the available options.

Different Plate Formats, Properly Represented

The platform supports multiple physical formats, including:

• Standard road plates

• Short plates

• Oversized plates

• Hex plates

• Import and JDM plates

• Motorcycle plates

Some formats are available in different widths depending on the customer's registration.

Import and motorcycle plates use two-line registration layouts.

Hex plates have their own physical shape rather than simply appearing as a rectangular plate carrying a different label.

The builder therefore reflects the product itself, not just a generic approximation.

Preventing Invalid Orders Before They Happen

One of the most important parts of the platform is the rules engine operating behind the builder.

The system understands which combinations Plate Studio can actually manufacture.

For example:

• Some plate sizes are rear-only

• Some finishes are unavailable on particular formats

• Identifier bands are restricted to compatible plates

• Certain border options do not apply to particular shapes

• Short plate sizes have registration-length restrictions

The customer interface removes or disables options that are not available.

But the protection does not stop there.

When the order reaches the server, those rules are checked again independently.

The system never relies solely on information submitted by the customer's browser.

This is particularly important for pricing.

Pricing Is Recalculated by the Platform

The final price can depend on several factors:

• Plate style

• Plate dimensions

• Front, rear or pair

• Finish

• Badge

• Border

• Fixing kit

The visible price updates immediately while the customer builds their plate.

However, the platform never blindly accepts that price when the order is submitted.

Before an order is created, the server recalculates the entire configuration using Plate Studio's own pricing rules.

This protects the business against pricing errors and prevents a manipulated browser request from changing what an order should cost.

Secure DVLA Document Handling

This is one of the most important parts of the platform.

For road-legal number plates, Plate Studio must obtain evidence of the customer's identity and their entitlement to use the registration.

That can include sensitive documents such as:

• V5C log books

• Photo identification

• Insurance documentation

• Other proof-of-entitlement documents

This is highly sensitive personal information.

I therefore designed the document system so these files are treated very differently from ordinary website images.

They are not uploaded into a public website folder.

They are not stored directly inside the application database.

And they are never exposed through a publicly accessible file URL.

Instead, production documents are stored privately in Amazon Web Services S3.

Why I Used AWS S3

AWS S3 is an object-storage service designed for reliably storing files independently of the application server running the website.

That separation matters.

If customer documents were simply stored on the web server, the application itself would become responsible for keeping those files safe.

That creates several problems.

A server migration, container replacement or infrastructure failure could potentially affect both the application and the documents stored alongside it.

It would also make it harder to run multiple application servers or move the platform between infrastructure providers.

By storing documents separately in AWS, the application server can effectively remain disposable.

The website can be updated, rebuilt or moved without moving the customer's sensitive files with it.

For a growing platform, that is an important architectural distinction.

Private Means Private

Simply putting documents into cloud storage does not automatically make a system secure.

The way those files are accessed matters just as much.

Plate Studio's customer documents are stored as private objects.

There are no public links directly to the files.

A customer's browser does not communicate directly with the storage bucket.

Instead, every request passes through the Plate Studio application first.

The application checks:

• Who the user is

• Whether they are logged in

• Which order the document belongs to

• Whether they own that order

• Whether they are authorised to view that particular file

Only then is the appropriate file returned.

For administrators, the original document can be made available for verification.

Customers are handled differently.

Customers Do Not Receive Their Original Identity Documents Back

A deliberate security decision was made around customer previews.

Customers need to be able to confirm that they uploaded the correct document.

They do not need the platform to hand the original passport, driving licence or V5C file back to their browser every time they view the order.

For that reason, the platform creates a separate low-resolution preview after upload.

The process works like this:

1. The customer uploads their document.

2. The platform validates the file.

3. The original is stored privately.

4. A smaller preview image is automatically created.

5. That preview is stored separately.

6. The customer's account displays the preview rather than the original.

The original therefore remains available to authorised administrators for compliance checks without unnecessarily exposing the full-resolution identity document to the customer-facing interface.

It is a small detail technically, but an important example of designing around the sensitivity of the data being handled.

Separate Storage for Website Imagery

The same storage system can also hold ordinary Plate Studio product photography.

However, public product imagery and private customer documents are treated as completely different classes of information.

The platform separates them by storage location and access rules.

Customer documentation remains protected.

Product photography can be safely served to the public website.

That allows Plate Studio to benefit from one reliable storage architecture without accidentally creating a path between public website assets and sensitive customer records.

Encryption and UK-Based Storage

The production storage system is configured so files are encrypted at rest.

The AWS infrastructure can also be located in the London region, keeping UK customer identity information within UK-based AWS infrastructure.

The underlying storage architecture can support features such as:

• Encryption

• Versioning

• Access logging

• Lifecycle policies

• Automated retention rules

• Highly durable file storage

This is significantly stronger than simply placing customer documents into an uploads directory on the web server.

It also gives the platform a sensible foundation for future data-retention policies.

For example, document lifecycle rules could be used to remove sensitive identity information automatically once it no longer needs to be retained.

File Names Cannot Be Used to Guess Other Documents

Another important part of the design is how files are named.

The system does not simply accept the customer's original filename and use it as the storage address.

Storage keys are generated by the platform.

This prevents predictable filenames, avoids accidental collisions and makes it far more difficult for one file location to reveal anything about another customer's documents.

Again, these are details customers should never have to think about.

But they matter enormously in systems handling sensitive information.

Safe Development Without Touching Live Customer Data

The storage system has also been designed with development in mind.

When AWS is configured in production, files are stored in S3.

In a development environment, the exact same application can use a protected local storage directory instead.

The rest of the platform does not need to know which storage system is being used.

This means a developer can clone and run the application without needing access to Plate Studio's production AWS credentials or accidentally putting test files into the live customer document store.

That separation improves both security and maintainability.

Document Upload Validation

The platform also validates documents before accepting them.

Checks include:

• Authentication

• Order ownership

• Maximum file size

• Approved file types

Supported document formats include common image formats and PDFs.

Only after those checks pass does the platform store the file and create the appropriate database record.

The database itself stores information about the document — such as its filename, type, verification status and storage reference — rather than storing the large file itself.

This keeps operational data and binary document storage separate.

An Audit Trail for Compliance

Once a document has been uploaded, Plate Studio staff can verify it from the administration system.

The platform records information including:

• Which document was supplied

• Which order it belongs to

• Whether it has been verified

• Who verified it

• When it was verified

Orders that are still missing the required documentation can also trigger reminder communications.

The result is a structured compliance workflow rather than a collection of documents being passed around through email.

Stripe and PayPal Checkout

Customers can pay using:

• Debit or credit card through Stripe

• PayPal

Both payment services feed into the same order-management system.

The payment process has also been designed so that an order does not depend entirely on the customer's browser returning successfully after payment.

If the customer pays and closes the tab at the wrong moment, the platform can still recognise the successful payment and finalise the order.

That reduces manual intervention and prevents successful payments becoming incomplete orders.

Complete Customer Accounts

Customers have access to their own account area where they can:

• Review current orders

• View previous orders

• Check order status

• Upload compliance documents

• Confirm document previews

• Manage account information

• Manage delivery details

• Reset their password

• Settle outstanding orders

Guest checkout is also supported.

The platform can create the underlying account automatically without forcing the customer through an unnecessary registration process before buying.

Order Management From Enquiry to Completion

The platform manages the full order lifecycle.

Orders can move through stages including:

• Enquiry

• Pending

• Confirmed

• Paid

• Processing

• Dispatched

• Completed

• Cancelled

The administration dashboard gives staff visibility and control over those stages.

Customers see the relevant status information through their own account.

A Purpose-Built Administration System

The back office gives Plate Studio control over the day-to-day running of the platform.

Staff can manage:

• Orders

• Customers

• Customer documentation

• Document verification

• Product imagery

• Product content

• Plate options

• Payment settings

• Email templates

• Delivery information

• Website notifications

• WhatsApp settings

The objective is to keep routine operational changes in the hands of the business.

A developer should not be required every time a product image, email message or configuration setting needs changing.

Mobile-First by Design

The plate-building process is too important to simply shrink a desktop layout onto a phone.

The mobile journey was designed around the order in which customers actually make decisions:

Registration → Preview → Size → Style → Options → Final Preview → Price

The preview is brought back into view at the points where changes matter, so customers can immediately see the impact of their selections.

This makes a relatively complex configuration process manageable even on a small screen.

Search Visibility Built Into the Platform

Plate Studio also has a full content and SEO structure rather than relying entirely on the configurator.

The site includes:

• Product pages

• Category pages

• Individual plate-style pages

• DVLA compliance information

• FAQ content

• Supporting service pages

• Policy pages

• Search metadata

• XML sitemap

• Structured product information

• Structured FAQ data

• Organisation and service information

That gives search engines substantially more context than a single generic plate-builder page.

The Result

Plate Studio is not simply an e-commerce website with a clever product preview.

It is a complete digital operating platform for a business selling a highly configurable and legally regulated product.

For the customer, the experience remains simple:

enter a registration, choose a plate, see it instantly and place the order.

Behind that simplicity, the platform manages:

• Accurate real-time plate rendering

• Product configuration rules

• Manufacturing restrictions

• Server-controlled pricing

• Stripe and PayPal payments

• Customer accounts

• Secure AWS S3 document storage

• Private identity-document handling

• Document previews

• DVLA verification

• Compliance audit trails

• Order management

• Transactional email

• Product content

• Shipping

• WhatsApp communications

• Search optimisation

The AWS document architecture is an important part of that result.

Sensitive customer identity records are kept separate from the application itself, stored privately, accessed only through controlled routes and handled differently from ordinary website assets.

That means the technology is not only designed around what Plate Studio sells.

It is designed around the responsibilities that come with selling it.

That is what bespoke development should do: take the complexity, risk and operational requirements of a business and turn them into a system that feels simple to use.

Technical Stack

For those interested in the technology behind the project:

Next.js 16, React 19, TypeScript, Tailwind CSS 4, CSS Container Queries, MongoDB, Mongoose, AWS S3, Stripe, PayPal, Sharp, Nodemailer, reCAPTCHA v3 and Node.js.