We build and run Shopware 6 stores for retailers, wholesalers and brands in Nigeria and West Africa, with the payments, SMS and delivery that commerce software written for other markets leaves out.
namespace KommandHub;
final class Studio implements Engineering, Operations
{
public function build(Brief $brief): System
{
return Commerce::onShopware($brief)
->payments(Paystack::class, Flutterwave::class)
->notifications(Sms::class)
->delivery(LastMile::withOtpHandover())
->covered(by: Tests::class)
->andWeKeepItRunning(); // the part most agencies skip
}
}Illustrative, not compilable. Everything it names is something we actually build and run.
The real code is on the plugins page See the plugin suite
Worth a look
A free Shopware theme
Monochrome by default, dark mode without a build step, and every brand decision a token rather than a component edit. Apache-2.0.
Read the storyDeliver from the nearest branch
Delivery priced from the branch that actually serves the customer, instead of one depot across the city. With proof at the door.
Read the storyCollection the counter knows about
Pickup locations, real opening hours and a thirty-minute slot in the checkout — so the branch is expecting them by name.
Read the storyWhat we do
Almost all of our work is Shopware commerce. The engineering practice exists to serve it: the integrations, internal tools and APIs a growing store ends up needing. The same people do both, which is why the integrations tend to hold.
Building, extending and migrating Shopware 6 stores — and writing the integrations merchants in our markets actually need: Paystack and Flutterwave payments, transactional SMS, click and collect, last-mile delivery with OTP handover.
SaaS platforms, internal tools and business applications on Laravel, Symfony and Vue. From the first release through to the version that carries real load.
Set up on hosting you own, then updates, monitoring and backups under a monthly care plan, in business hours.
Shopware plugins
Every client project in this region ran into the same missing pieces: local payment rails, SMS that customers actually read, delivery priced by the distance it actually covers. So we built them as Shopware 6 plugins. Most are in beta and in use on our own projects; the storefront theme is stable and open source.
See the full suiteHow we work
Every engagement starts with reading your actual store and data, not a requirements document. The audit is fixed-price: a written assessment of what we found, what we would change and what it costs, which you keep whether or not you hire us.
A migration that stalled, a store that falls over at peak, a build that needs to start. Describe it and we will tell you whether we are the right people.