Software for retail and e-commerce operations
The shop front is rarely the problem. The work sits behind it: product data, stock, suppliers, orders and the systems that all need the same answer at the same time.
Typical problems
- Product data maintained separately for the webshop, the ERP and each marketplace.
- Stock levels that are accurate everywhere except where the customer is looking.
- Supplier feeds arriving in a different format from every supplier.
- Order and fulfilment status reconstructed manually across three tools.
What we build
- Product information systems that hold the master record and push it everywhere.
- Stock and pricing synchronisation between shops, ERP and marketplaces.
- Supplier feed processing: import, mapping, validation and error reporting.
- Order flows connecting payment, warehouse, shipping and returns.
- Internal tools for merchandising, promotions and reporting.
Constraints we design around
One source of truth
One system owns each field, and every other system receives it rather than editing it.
Failure handling
Feeds and integrations fail regularly. Retries, alerts and a visible queue are part of the design.
Peak load
Sized for campaign traffic, not for an average Tuesday.
No downtime
Changes deployed while the shop is trading, because there is no quiet window.
How the work runs
We map where each piece of data is currently created and edited. That map usually explains most of the recurring problems on its own.
Synchronisation is built one direction at a time and run alongside the current process until the numbers agree.
Integrations get monitoring from the first day, because a feed that silently stops is worse than one that fails loudly.
Questions we get
Do we have to replace our webshop platform?
Usually not. Most of this work sits behind the shop and connects to it through its API, whatever platform it runs on.
Can you connect our ERP?
If it has an API, yes. If it does not, we work through exports, files or the database, and we tell you early if it is not realistic.
How do you handle marketplace rules?
Each marketplace gets its own mapping and validation, so a rejected listing is a visible error with a reason rather than a silent gap.