SFD
100,000+
app downloads
100,000+ downloads, a 4.9 App Store rating, and a Mobile Trends Awards 2025 nomination in Commerce.
We develop apps and online shops when technology starts holding sales back.
Reviews, recognition and our libraries
Rated 5.0 out of 5 on Google17 client reviews on GoogleSee client case studiesSee our work for SFDCommerce nomination, Mobile Trends Awards 2025Read about the nominationCheck the code of our librariesPublic repositories and documentationSee the librariesAgree the scope and a fixed priceAfter workshops, before work on the agreed scope beginsHow we agree scope
Buying feels simple. Behind the scenes, the systems work together.
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.
Skincare serum
€21.00
Pick a part of the shop to see an example flow.
Underneath
The steps and responsibilities depend on the company’s systems and business rules.
- 232ERPorders, documents
- 31Warehousestock, picking
- 12Paymentsone-off, recurring
- 42Couriersshipments, tracking
- 21Physical storesavailability, pickup
- 14Loyalty programmepoints, rewards
- 133Customer accountdetails, order history
- 43Notificationsemail, push, SMS
- 1The payment provider confirms the payment.
- 2The paid order goes into processing.
- 3The warehouse prepares the products for shipping.
- 4The customer gets an order confirmation.
- 1The customer picks a delivery cycle and agrees to recurring payments.
- 2On the agreed date the system requests the next payment.
- 3Once it is confirmed, an order is created for fulfilment.
- 4The carrier receives the details of the prepared shipment.
- 1The programme awards points for a confirmed qualifying purchase.
- 2Physical stores use the same programme.
- 3The customer account shows the confirmed points balance.
- 1The store confirms the selected products are available.
- 2The order system records the confirmed reservation.
- 3Once the order is ready, the customer gets a notification.
- 4The programme checks how points were recorded, without awarding points twice for the same purchase.
- 1The warehouse picks the order.
- 2The carrier provides the shipment number and status.
- 3The customer account shows the delivery details.
02Selected companies we have worked with
Onet
Project context: Campaign sites and tailored landing pages for major-brand marketing programs.
See the apps and systems we have built.
See all our workŚwiat Książki
100,000+
app downloads
“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.”
Grzegorz BiedakOperations Director, Księgarnie Świat Książki bookstore chainTranslated from Polish.
Your app or online shop is already taking orders, but something is holding back its growth.
We start by reviewing the system and choosing the problem to solve. We compare the cost and risk of repairing, extending or rebuilding it.
- Releases
A new app version waits weeks to be published.
We sort out how versions are built and released.
- Payments
Customers drop off between basket and order confirmation.
We check the whole path from basket to order.
- Loyalty
Points and discounts differ between the app and the store.
We agree the rules and data sources for points and discounts.
- Integrations
The ERP or warehouse cannot keep up with online sales.
We start with the connection that gets in the way most.
- Changing vendor
The previous team is leaving, and the system knowledge with it.
We take over the code, access and documentation.
From the first blocker to continued development.
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.
Knowledge base
Have questions?
We have answers.
We've gathered the most frequently asked questions about cooperation, costs, and technology.
Will you take over an app or shop from another vendor?
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.
Does the system have to be rewritten from scratch?
We do not assume so up front. After the diagnosis we compare fixing, extending and rebuilding by cost and risk.
Which systems do you connect shops and apps with?
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.
How much does taking over and developing a system cost?
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.
Can we get a fixed price?
Yes. We agree a fixed price after workshops and scope definition. Changes to the scope require a separate agreement.
Do you provide support after launch?
We agree maintenance, updates and issue handling in the contract.
Will we own the code?
We define code ownership and the handover of repositories, access and documentation in the contract.