Building a commerce platform that stays lightweight when the business is small — and ready when it grows.

A small retailer shouldn't need enterprise infrastructure to sell online.

ShappX needed to support two worlds at the same time. There was the online storefront, where customers browse products, select variants, add items to a cart, and place orders. Then there was the physical store, where staff need to search products, process counter sales, manage inventory, and see orders without waiting for a complex backend stack to respond. The challenge was not simply building an ecommerce website. It was building the operating system behind a small retail business without introducing infrastructure costs and operational complexity that the business did not need.

Morphlix rebuilt the platform around the actual business: lightweight online commerce, physical retail, and conversational order confirmation.

Three experiences. One commerce system.

Morphlix separated ShappX into three independently deployed experiences while keeping them connected through a shared backend and data model.

Online orders and physical sales therefore operate against the same commerce state.

Replacing always-on infrastructure with an on-demand commerce stack.

The original ShappX backend used PostgreSQL and Amazon RDS.

Morphlix redesigned the architecture around the actual workload and moved the application to a fully serverless compute and data model.

The result is a significantly smaller operational footprint.

Moving from relational transactions to atomic serverless writes.

Moving from PostgreSQL to DynamoDB was not simply a database migration.

The data model had to change.

Three relational patterns were particularly important.

The migration was therefore not “Postgres replaced with DynamoDB.” It was a redesign around the way the application actually reads and writes data.

Checkout captures intent. WhatsApp closes the loop.

ShappX deliberately does not process online card payments.

Instead, checkout captures the customer's preferred payment method: Bank transfer, Pay on delivery and Card.

The order becomes the system record, while WhatsApp remains the primary customer confirmation channel.

This removes unnecessary payment infrastructure from the first version of the product while keeping the customer journey familiar.

WhatsApp is integrated throughout the experience: Floating WhatsApp contact, Footer contact, Order confirmation messaging and Direct customer communication.

The web creates the order. WhatsApp continues the conversation.

The till and storefront share the same stock.

Physical retail introduces a problem that many ecommerce implementations overlook.

A product can be sold online and at the counter within seconds of each other.

ShappX handles this at the data layer.

When a counter sale is completed, the order and inventory adjustment are performed atomically.

Each product's stock is checked against the quantity recorded at the time of sale.

If the stock has changed in the meantime, the transaction fails rather than allowing a second sale to create an invalid inventory state.

This makes the POS more than a separate screen.

It is another interface into the same commerce system.

The goal wasn't to make the architecture bigger. It was to make it appropriate.

The original architecture used infrastructure designed around a traditional web application.

That introduced a fixed database cost even when the business had little or no traffic.

Morphlix looked at the actual workload and redesigned the system around three principles.

The hard parts were not the AWS icons. They were the boundaries between them.

The migration exposed several problems that only appeared when the system was exercised end to end.

The image pipeline had to be redesigned around DynamoDB's item-size constraints. Uploaded images are now cropped and re-encoded to a controlled 900×900 JPEG output before storage.

The deployment process was hardened after environment configuration was found to be capable of overriding production values with development configuration.

The catalogue was also made safe to reseed without resurrecting deleted products.

The admin experience was separated from the customer storefront so the two applications could evolve and deploy independently.

The domain and DNS configuration was moved into Route 53, giving the platform a single managed DNS layer.

Testing was added from a previously empty test suite to approximately 50 Go tests alongside a 95-assertion end-to-end suite covering the deployed API and critical commerce flows.

The result wasn't simply a cheaper architecture. It was a more deliberate one.

A deliberately small AWS footprint.

A retail platform that scales down as naturally as it scales up.

Morphlix transformed ShappX from a conventional ecommerce application into a serverless commerce platform designed around the actual scale of the business.

The platform now supports three connected experiences — the online storefront, merchant back office, and physical-store till — through a single backend and data model.

The backend runs on Lambda, the data layer uses DynamoDB on demand, and the customer-facing applications are delivered through managed AWS services.

That means the platform does not need a fleet of servers or an always-running database waiting for the next customer.

When the store is quiet, the infrastructure can be quiet too.

At the same time, the architecture leaves room to grow: more products, more orders, more customers, and more traffic can increase consumption without requiring the team to redesign the application around a larger server footprint.

From ecommerce website to lightweight commerce infrastructure.

ShappX demonstrates a principle we apply across Morphlix builds:

Infrastructure should follow the business, not the other way around.

For a growing retailer, that meant replacing always-on infrastructure with an architecture that is: Serverless, On-demand, Operationally lightweight, Cost-conscious, Designed around real access patterns and Shared across online and physical commerce.

The result is not an over-engineered ecommerce platform.

It is a commerce system sized for the business today, with an architecture capable of growing with it tomorrow.