Frequently Asked Questions

We design, build and operate eCommerce systems. That covers the storefront customers see, the commerce services behind it, the integrations to ERP, PIM, warehouse and payment systems, the infrastructure it all runs on, and the support that keeps it online. One team owns all of it.

Send a brief through the contact page or email us directly. A principal architect reads it and replies within one working day. If there is a fit, the next step is almost always a two week technical assessment at a fixed fee, which ends with a written report and a fixed price for whatever comes next.

Usually not, and we will say so early. Our engagements start around 60,000 EUR because they involve senior engineers working on systems that carry real revenue. If your platform is a standard Shopify store with light customisation, a specialist Shopify partner will serve you better and cost less.

London and Belgrade. Delivery teams work in Central European Time with a minimum four hour overlap with your working day, and we travel for discovery workshops, gate reviews and go live.

All delivery, documentation and code review is in English. We also work day to day in Serbian and German where a client team prefers it.

Storefronts in Next.js and React. Commerce engines including commercetools, Shopify Plus and Adobe Commerce, or custom services in TypeScript, Go or .NET where no product fits. Search on Algolia, Elasticsearch or Typesense. Content in Contentful, Storyblok, Sanity or headless WordPress. Payments through Adyen, Stripe, Mollie and Klarna. The full list is on the technology page.

No. Headless costs more to operate and only pays back when the roadmap needs independent release cadence, multi brand reuse or an exit from a vendor that is blocking the business. When none of those apply, a well built suite with a custom storefront is the cheaper correct answer and we will recommend it.

Yes, and it is often the better option. A large share of our work is fixing what exists: rebuilding checkout, repairing an integration nobody trusts, or getting performance under control without touching the commerce engine.

We build them where they earn their cost: search relevance and semantic ranking, product data enrichment from supplier feeds, support deflection on order status, and merchandising suggestions. We do not add a chat interface to a storefront because it is fashionable, and we measure every feature against the conversion or cost metric it was meant to move.

A focused storefront rebuild on an existing commerce engine runs eight to twelve weeks. A full replatform with ERP, PIM and payment integration runs sixteen to twenty four weeks. Multi market or multi ERP B2B programmes run twenty four to thirty two weeks. Discovery gives you a specific number before you commit.

Named senior engineers, introduced by name before you sign. Median experience across the team is eleven years in commerce engineering. We do not staff a pyramid, and we do not swap people out mid programme without agreeing it with you first.

You get a live delivery board you can open at any time, a demo of working software every two weeks, and a written increment report that lists what shipped, what moved and why. If something is slipping you will know in week three, not week fifteen.

Peer reviewed and merged, automated tests written and green, performance budget respected, accessibility checks passed, documentation and run book updated, and deployed to staging. A ticket that meets five of those six is not done.

Yes, and it is a defined work package with its own owner and acceptance criteria. We crawl the live site, build a complete URL map, keep parity on titles, structured data and internal links, ship redirects in the same release as the cutover, then monitor index coverage and rankings daily for eight weeks. Across our last five migrations the median ranking change at week eight was zero.

No. Traffic moves incrementally, by market or by route, and the old platform stays warm behind a routing switch that takes about four minutes to reverse. Nobody is asked to approve an irreversible cutover late at night.

They are migrated with reconciliation reports that account for every record, and any record that cannot be migrated cleanly is listed with the reason rather than quietly dropped. Customers keep their accounts and their history. Passwords are rehashed on first login rather than reset, unless your security policy requires otherwise.

Technical assessment is 8,500 EUR and is deducted from the build. Storefront rebuilds start around 60,000 EUR. Full replatforming programmes start around 120,000 EUR. Dedicated pods start at 34,000 EUR per month. Managed run services start at 4,500 EUR per month. Detail is on the pricing page.

You do, from the first commit. Work happens in your version control where possible, or transfers at the first milestone. There is no proprietary framework to licence, no code held back, and no clause that makes leaving expensive.

No. We are not a reseller for any commerce engine, CMS, search product or payment provider, and we take no margin on licences. That is what lets us recommend the cheaper option when the cheaper option is right.

24/7 monitoring of business and infrastructure metrics, incident response against a defined SLA, security patching, dependency upgrades, a monthly engineering budget for improvements, a quarterly platform review and an annual peak readiness programme before your trading season.

Fifteen minutes for priority one, twenty four hours a day, with a workaround target of two hours. Priority one means customers cannot buy or data is at risk. Every priority one gets a written blameless review inside five working days with actions tracked to closure.

Yes, and we prepare for it in September rather than November. That means building a load model from your own traffic data, testing at three times the previous peak, fixing what breaks, rehearsing the incident process, and agreeing a code freeze window with the business.

That is a normal and reasonable outcome, and we plan for it. Run books, architecture decision records and infrastructure code exist so your team can take over. We run a structured handover and stay available on a reduced retainer while your team builds confidence.