Blueprint and governance
Every service in the target architecture is named, then the enterprise architect and the e-commerce lead sign it off with the product type model and the message formats between systems, before the first API call is written.
Platform implementation
commercetools
We build composable commerce on commercetools, connecting its APIs to the front end, search, content and payments you choose, so each part can change without replatforming the rest.
Projects on commercetools start with architecture: which front end, search, content management and payment services sit around the commerce APIs, and who owns each. That freedom helps in the Gulf, where an Arabic front end, a payment orchestrator that supports mada and Apple Pay, and local delivery partners can each be chosen on their merits. The hosting region for the commerce APIs is checked against your data residency policy early.
The commerce core is modelled through product types, categories, stores and channels, and changed through the HTTP and GraphQL APIs. Logic that must run inside an API call goes into API Extensions; events leave through Subscriptions to a message queue, where integration services pick them up. The front end can be commercetools Frontend or your own Next.js application.
commercetools and related product names may be trademarks of their respective owners.
How we implement commercetools
From blueprint to go-live and beyond: configuration, integration and support from one accountable team.
Product type modelling
Product types and attributes designed for Arabic and English values, variants and search facets, so the catalogue does not need rework later.
Checkout and payment orchestration
A checkout built on the carts and orders APIs, wired to a payment service that covers mada, Apple Pay, cards and cash on delivery.
Merchant Center for business users
Merchant Center set up with roles and custom views, so merchandisers manage prices, promotions and stores without developers.
Hypercare and managed support
commercetools evolves the platform continuously behind a stable API, so our ongoing work is in the services around it: dependency updates, monitoring API latency and error rates, and new extensions as the business asks for them.
Signs you are ready for composable commerce
It is built for organisations with an engineering team that wants to own the architecture, several brands or channels to serve, and a clear reason the all-in-one suites do not fit.
- An in-house or retained engineering team that runs cloud services
- Several brands, countries or channels on one commerce core
- Budget for separate search, content and front-end products
- An architect who owns the integration contracts
Plan commercetools with Hosn Al Tomoh
Tell us what the platform needs to do and when. We will propose a first phase with scope, team and an itemised quotation.