SFD
100,000+ downloads, a 4.9 App Store rating, and a Mobile Trends Awards 2025 nomination in Commerce.
We improve online shops and apps that already take orders. We connect them to ERP and warehouse systems, payment providers and logistics, starting with what makes order processing difficult.
Shop
Chooses a serumThen places an order in the app or online shop.
Pays for the orderUsing the chosen payment method.
Gets an updateThe order is being prepared.
Collects in storeOption: store collection.
Or receives delivery at homeAlternative option: courier delivery.
Back office
The order comes inERP records the order; the customer account shows its status.
Payment and pickingAfter payment confirmation, the warehouse picks the products.
Packing and labelThe warehouse packs the products. The customer receives an update about order preparation.
In-store collectionA member of staff confirms collection and records the handover.
Handover to the courierThe carrier provides the shipment status. The customer account shows delivery information.
Onet
Project context: Campaign sites and tailored landing pages for major-brand marketing programs.
100,000+ downloads, a 4.9 App Store rating, and a Mobile Trends Awards 2025 nomination in Commerce.
“From the start of our collaboration, we could count on strong commitment, efficient communication, and openness to our ideas. The team understands our needs well and responds quickly to questions and challenges as they arise.”
We start by reviewing the system and choosing the problem to solve. We compare the cost and risk of repairing, extending or rebuilding it.
A new app version waits weeks to be published.
We sort out how versions are built and released.
Customers drop off between basket and order confirmation.
We check the whole path from basket to order.
Points and discounts differ between the app and the store.
We agree the rules and data sources for points and discounts.
The ERP or warehouse cannot keep up with online sales.
We start with the connection that gets in the way most.
The previous team is leaving, and the system knowledge with it.
We take over the code, access and documentation.




We start with what is blocking releases or sales today.
We take over the code, access and knowledge of the app.
We review the code, release process, payments and integrations.
We decide what to fix, what to modernise and what to rewrite.
We agree the first scope of work and how it will be priced.
We fix the checkout path, payments and integrations.
We test the critical paths: sign-in, basket and payment.
We sort out the release process and publish to the app stores.
We maintain the app and keep building new features.
We've gathered the most frequently asked questions about cooperation, costs, and technology.
Yes. We start with the handover of code, access and documentation, then review the state of the system. We agree further work after this diagnosis.
We do not assume so up front. After the diagnosis we compare fixing, extending and rebuilding by cost and risk.
Integrations can cover ERP and warehouse systems, payments, couriers, loyalty programmes and physical store systems. We agree the scope based on your company’s needs and the systems you use.
The price depends on the state of the code, the number of integrations and the scope of work. After the diagnosis we prepare an estimate for the first scope.
Yes. We agree a fixed price after workshops and scope definition. Changes to the scope require a separate agreement.
We agree maintenance, updates and issue handling in the contract.
We define code ownership and the handover of repositories, access and documentation in the contract.