One platform. Every part of the business.
From the first WhatsApp order to a growing multi-branch operation, businesses need more than a storefront: a way to manage products, stock, orders, customers, payments and finances without running the business across disconnected tools. Mercado is a commerce operating system built by Morphlix for African businesses, giving developers the infrastructure to build on and business owners a simpler way to run their operations. Morphlix is building it as both a product and a long-term technology venture, with product engineering, cloud infrastructure and operations under one roof.
- AWS
- Commerce
- Fintech
- Cloud Infrastructure
- Platform Engineering
- Multi-Tenant SaaS
- Industry
- Commerce Infrastructure
- Engagement
- Studio build
Results
19
operational modules in one console
A connected merchant control plane covering the major operational areas of a commerce business, with 121 console routes.
44
granular permission actions
A role-based permission model that scopes who can perform particular business and administrative actions.
99.8%
resource-tag coverage
At the 14 October 2026 audit, 432 of 433 resources carried the required partner revenue measurement tag.
0
infrastructure drift
The audited Terraform plan for the shared environment reported 0 to change and 0 to destroy: the declared configuration matched the resources evaluated.
8 of 8
load-balancer target groups healthy
All eight Application Load Balancer target groups were healthy during the audit. A point-in-time result, not a claim of uninterrupted availability or a service-level agreement.
38
CloudWatch alarms
None was in the ALARM state at audit time, and notifications go through Amazon SNS email to the operations owner.
The challenge
Businesses shouldn't have to outgrow their tools to grow
Across African markets, commerce often begins with familiar tools. A seller takes orders on WhatsApp, tracks stock in a notebook or spreadsheet, records sales separately and takes payments through different providers. That works at the start, but as a business adds products, staff, channels or locations, keeping everything aligned gets harder.
Stock that doesn't match
A stock count in one system may not match another, and multi-branch businesses lose sight of what is actually available.
Orders lost in conversation
An order received through chat may never reach the accounting records.
Payments left unreconciled
A payment can arrive without being matched against the original sale.
Growth on fragile foundations
For a business expanding from one shop to several branches, these gaps affect daily decisions, customer experience, financial visibility and the ability to grow with confidence.
The tools that helped a business get started can become the same tools that hold it back.
The solution
Everything behind the sale, connected
Mercado brings the core operations of a commerce business into one platform. Instead of treating the storefront, inventory, orders, payments and accounting as separate products, it connects them through a shared operating layer.
Sell wherever customers are
For many businesses the conversation begins in WhatsApp, continues through a product enquiry and ends with a payment. Mercado is designed to bring conversational ordering into the wider workflow, connecting customer conversations with orders, inventory and payments, so merchants meet customers in familiar channels without losing control behind the scenes.
Inventory that stays connected
Stock management by location, adjustments, transfers and stock alerts. High-volume storefront reads are kept apart from merchant operations that need fresher data, so product pages are optimised for browsing while stock is managed against transactional records.
Orders and customers together
The order lifecycle is connected with customer profiles, promotions and operational records: order tracking, returns, split payments, customer segments, wholesale relationships and loyalty in the same environment.
Finance at the heart of commerce
A double-entry accounting foundation connects commercial activity with financial records and reporting, narrowing the gap between making a sale and understanding what it means financially.
Control without engineers
Developers get APIs, integrations, permissions and infrastructure; operators get practical screens for products, orders, stock, teams and finances. The merchant control plane spans 19 operational modules and 121 console routes.
Room for different businesses
Shared SaaS infrastructure for businesses that want a managed experience, with a path towards isolated deployments for enterprises that need more control over their cloud environment.
Not another storefront or isolated business application, but the operating infrastructure that connects the whole commerce journey.
Built for African Businesses
From a single seller to a growing retail operation
Mercado is designed around different stages of business growth. These are the operating models it is designed to support; the availability of individual capabilities depends on the current release and deployment status.
Starter
For independent sellers, market traders and small businesses beginning with a product catalogue and customer conversations: organising products, receiving orders and establishing consistent operations.
Growth
For established shops, boutiques, restaurants and service-led businesses that need better inventory management, customer records, sales visibility and financial workflows in one connected environment.
Scale
For multi-location businesses that need shared inventory visibility, location-specific access, coordinated sales and financial reporting across branches, without rebuilding their systems every time they grow.
Enterprise
For larger businesses that need more control over infrastructure, security boundaries, identity and deployment. Mercado's architectural direction includes Bring Your Own Cloud, in which qualifying enterprise deployments run within the customer's own AWS environment.
How Morphlix Built It
Product thinking backed by engineering discipline
Mercado is a Morphlix venture, built through the studio model that combines product development with cloud architecture and operating support. The objective isn't simply to ship features, but to build a platform where they work together and evolve without each new capability becoming another disconnected system.
Organised around business functions
The backend is organised around distinct commerce domains: accounts, catalogues, locations, inventory, orders, customers, promotions, finance, AI and notifications. Each has clear responsibilities and API boundaries, so one capability can be improved or extended without treating the platform as a single, indivisible application.
Different data paths for different needs
A shopper browsing the catalogue and a merchant updating stock have different needs. Shopper-facing catalogue data is served from a DynamoDB-backed read path, while merchant operations use PostgreSQL for transactional records.
Permissions built around real roles
The merchant console serves different people doing different jobs: managing products, handling orders, reviewing finances or administering the account. 44 granular actions let access be scoped by role and responsibility.
The AI layer
A foundation for intelligent commerce
Mercado's product direction includes AI-assisted commerce workflows, such as interpreting conversational orders and making business information more useful within existing operations.
Working with the data
Intelligence should work with the underlying commerce data, rather than sit apart as a disconnected chatbot.
Governed before it goes live
AI deployment is a separate milestone from the core platform. At the 14 October 2026 audit, the AI service was deliberately held at zero tasks pending governance sign-off.
Architecture
Built to be operated, not just demonstrated
Mercado runs on AWS, with infrastructure managed in Terraform and application services deployed through controlled environments.
Application
Amazon ECS on AWS Fargate behind an Application Load Balancer, with images in Amazon ECR and AWS Lambda for supporting functions.
Data
Amazon RDS for PostgreSQL for transactional records, Amazon ElastiCache for Redis for caching, Amazon DynamoDB for the catalogue read path and Amazon S3 for storage.
Events
Event-driven messaging through Amazon SQS, Amazon SNS and Amazon EventBridge.
Edge and security
Amazon Route 53, AWS Certificate Manager and AWS WAF at the edge, with AWS Secrets Manager and AWS KMS protecting secrets and data.
Governance
Audit logging, configuration monitoring, threat detection, infrastructure tagging, controlled infrastructure changes and cost alerts, with Amazon CloudWatch for operational monitoring. Security, reliability and cost management evolve with the product rather than waiting until after growth.
Technology stack
AWS services, managed as code
Compute
- Amazon ECS on AWS Fargate
- AWS Lambda
- Application Load Balancer
- Amazon ECR
Data
- Amazon RDS for PostgreSQL
- Amazon ElastiCache for Redis
- Amazon DynamoDB
- Amazon S3
Messaging
- Amazon SQS
- Amazon SNS
- Amazon EventBridge
Edge and security
- Amazon Route 53
- AWS Certificate Manager
- AWS WAF
- AWS Secrets Manager
- AWS KMS
Operations and tooling
- Amazon CloudWatch
- Terraform
Outcome
A working platform with a measurable engineering foundation
These measures show engineering and governance progress. They are not evidence of payment volume, merchant growth, reconciliation improvements or commercial savings, none of which has been established yet.
Where Mercado Stands
A working beta, with a roadmap towards greater scale
Mercado's current environment is a beta deployment with live application infrastructure. At the 14 October 2026 audit, eight of nine ECS service workloads were running at their configured task count; the ninth, the AI service, was deliberately held at zero pending governance sign-off.
The database is Amazon RDS for PostgreSQL in a single Availability Zone. A Multi-AZ database, additional Redis capacity and cross-region disaster recovery are planned improvements for general availability, not features of the beta.
That distinction matters. A platform can have a working application and a strong governance foundation while important production-readiness work is still ahead. Morphlix treats these as deliberate stages: establish the core platform, verify the operational controls, address the remaining risks, then expand resilience for broader production use.
What's Next
From a connected platform to a commerce ecosystem
The objective is to turn a strong engineering foundation into evidence of practical value for merchants and partners.
Complete production readiness
Tighten deployment-role permissions, strengthen preventive controls at the organisation level, rotate outstanding secrets and validate database recovery through documented restore testing.
Strengthen resilience
Move to the planned Multi-AZ database and additional recovery protections, with recovery objectives validated by testing rather than design estimates.
Bring intelligence into commerce
Complete the governance and implementation work to bring AI workflows into operation, with clear boundaries on what AI components can access and do.
Expand the integrations
Continue developing payment orchestration and the integrations that connect orders, payment providers, settlement and financial records.
Measure business outcomes
As real transactions flow, measure reconciliation turnaround, transaction outcomes, service availability and the operational effort needed to run the platform.
The Bigger Picture
Not another storefront. The infrastructure underneath it.
African businesses shouldn't have to assemble their entire operation from disconnected products just to sell, manage stock, receive payments and understand their finances. Morphlix is building Mercado to connect those capabilities through one commerce operating layer, one that can serve a seller starting on WhatsApp and grow with them into more sophisticated retail. The work goes beyond the application: it includes the cloud infrastructure, engineering discipline, governance and operational practice needed to build the platform responsibly.
Mercado is the commerce operating system for Africa: built by Morphlix, designed around the market and developed for the businesses that will grow with it.
Mercado is not another storefront. It is the infrastructure underneath the storefront — giving technical teams the rails to build on and business operators the control plane to run their commerce.
More from the library.
All case studiesAI · Productivity
Building Seshira: an AI-native project management platform
Replacing fragmented project workflows with one cloud-native workspace where the agent and the team call the same tools.
Fintech & Payments
Governing the cloud behind a payments platform
Audit trail, threat detection, alerting and reviewed Terraform changes for a payments platform heading to production.
Work with the studio
Ready to future-proof
your infrastructure?
Tell us what you are building and where the current stack is holding you back. We will come back with an architecture and a plan.