Your business has its own rules. So should your site.
Negotiated prices. Multiple vendors. Employee allowances. A buying journey that doesn’t fit a template.
Medusa is open-source software for products, orders and payments. We use it to build your specific buying rules and connect your store to the systems you already use.
You own your custom code and can keep developing it with another team. Hosting, maintenance and third-party services still have costs and their own terms.
Regular customer, own rules. Souk car park, midday.
The essentials. With your rules.
Commerce essentials
Products, pricing, carts and orders.
Your buying rules
The rules that make your operation yours.
Connected systems
Your store, stock, accounting and existing tools.
Selected work
Different businesses. Specific answers.
Online retail, a marketplace and wholesale. Each built around the people buying and the team running it.
Cap, olive, with employee tag. Public edition also available.
Public sales + employee programmeBelgium
An online store. An employee programme.
A merchandise store for a Belgian defence company, combining public sales with an employee purchase programme in one place.
Two properties, toy bricks. Supplies ordered separately.
Multi-vendor marketplaceUnited States
A multi-vendor marketplace.
Property managers buy supplies from several vendors in one marketplace. From finding the right product to tracking the order, the buying process stays connected.
Jewellery resellers order through a dedicated wholesale store, connected to the business’s existing Shopify consumer store. A self-service space built around how resellers buy.
Projects described anonymously. Product visuals are playful interpretations of their sectors.
How we work
A good site works. A better one is understood.
You should know what your site is made of, how it behaves, and what changes when it evolves.
We map the components and features, connect buying rules to customer journeys, and agree on tests before launch. You review the work in stages, then receive the code and documentation to run the site and plan its next changes.
The Souk approachServed by: Souk team
01Know what’s there.1×
Structure & components
Map the storefront’s components and features, and the relationships between them. Build a shared reference of what exists.
02Build and check it.1×
Buying rules & tests
Connect buying rules to customer journeys and agree on tests. Review the working site together in stages before approving the launch.
03Know what comes next.1×
Handover & future changes
Hand over the code and a map of how the site works. Compare future changes against that reference and the tests, so the next team has a starting point.
TotalKeep control.
Custom codeYours
Good things in store.
We’re developing internal tools to support this approach, alongside our engineering work.
Our services
Create your store. Or redesign it.
A new venture or channel
Create your e-commerce site.
Your first store, a marketplace or a new sales channel. We define a useful first version around your products and buying rules, from employee allowances to negotiated reseller prices, then design and build it with Medusa.
01
Souk /start
An agreed launch scope, tested buying journeys, and the code and documentation to keep developing your store.
When your platform’s limits or mounting app costs get in the way, we plan a redesign and a move to Medusa. Where your setup allows it, we test the new storefront on your existing system before changing the commerce software behind it.
02
Souk /replatform
A migration plan covering your data, connections and launch checks, with a rollback plan before the switch.
The buying rules, product information and connections your store needs.
Customer-specific prices, account tiers, purchase orders, purchase approvals and employee programmes. Buying rules designed around the people using them.
Your business. Your rules.
What’s the one thing your platform can’t do?
Tell us what you sell, how you operate, and what’s getting in the way.
The Souk approachServed by: Souk team