Question 1

What is the minimum budget for a custom web shop?

Accepted Answer

A headless e-commerce store built with Medusa.js and Next.js 16 starts at approximately €5,000 for a standard setup including product catalogue, cart, payment integration, and admin panel. This covers design, development, and deployment on serverless infrastructure that handles traffic spikes without downtime. More complex builds with multi-currency support, ERP integration, or product configurators range from €8,000–€18,000. Every project receives a fixed quote before work begins.

Question 2

Which payment gateways do you support?

Accepted Answer

We integrate all major payment gateways across EU and global markets. For Croatia and the region: CorvusPay, Keks Pay, and T-Pay with full FINA fiscalisation. For EU and international transactions: Stripe, PayPal, Apple Pay, and Google Pay. Every integration includes PCI-compliant checkout, webhook-based order confirmation, and automated invoice generation. Multi-currency support is built in as standard, so your customers pay in their preferred currency with real-time exchange rate handling.

Question 3

Can the shop integrate with our existing ERP system?

Accepted Answer

Absolutely. We specialise in connecting Medusa.js with popular ERP systems. SAP Business One, Odoo, Microsoft Dynamics, or custom-built solutions, via REST API and n8n workflow automation. This enables real-time inventory synchronisation, automated order routing, and bidirectional stock updates that eliminate manual data entry. The integration runs continuously, so product availability on your webshop always matches your warehouse reality, reducing overselling incidents to near zero.

Question 4

Can we manage the shop ourselves after launch?

Accepted Answer

Yes, you receive a fully featured Medusa.js admin panel where your team can independently manage the entire catalogue: add products with variants and images, process orders, configure discount codes, and adjust pricing without writing a single line of code. We also provide a structured onboarding session and video documentation, so your team is confident from day one. The admin interface is responsive and accessible from any device, enabling order management even while away from the office.

Question 5

Will a new online store increase sales on its own?

Accepted Answer

Not by itself. A new store removes obstacles: faster loading, a clearer checkout, search that actually finds the product, and a mobile experience that does not break down. If visitors already reach you, that shows up in the share of them who complete a purchase. If there are no visitors, the store has nothing to convert and the problem sits in your channels, not in the shop. That is worth saying before the project, not after.

Question 6

Why not just use Shopify?

Accepted Answer

For many stores Shopify is the sensible choice, and we will tell you so. If you have a standard catalogue, standard shipping and a standard checkout, a hosted platform gets you to market faster and cheaper up front. Custom becomes worth it when the platform starts getting in the way: non-standard pricing or configurator logic, a deep link into an ERP or warehouse, local invoicing requirements, or transaction fees that become a serious cost at your volume. We make that call from your numbers, not from what we would rather build.

Question 7

Will a redesign fix abandoned carts?

Accepted Answer

Partly. Some abandonment comes from things a store controls: forced registration, shipping costs that only appear at the end, a slow checkout, too few payment methods. The rest comes from price, availability, or a shopper who was only comparing. We measure where people actually drop out first, then fix that step. Redesigning the whole store without that data is guesswork.

Question 8

How are invoicing and tax compliance handled?

Accepted Answer

Through an integration with the accounting or ERP system you already run, so invoices are created in one place. The store sends order data to the system that already issues your invoices instead of keeping a parallel record that drifts out of sync over time. Before we start we confirm which system you use and whether it exposes an API, because that determines how involved the integration is. If it has no API there are workarounds, but that needs to be known up front.

Question 9

Can we migrate existing orders, customers and search rankings from the old store?

Accepted Answer

Yes, and it is planned before the migration rather than after. Products, categories, customers and order history are moved by script from the old store's database. Search positions are protected by redirects: every old product and category URL gets a 301 to its new equivalent. Migrations that skip that step routinely lose organic traffic in the first weeks, and it is hard to win back.

Question 10

Who manages stock and pricing after launch?

Accepted Answer

You do, from the system you already use for it. If stock lives in an ERP or warehouse tool, the store reads from there and we do not ask you to enter the same numbers twice. If you have no such system, stock and prices are edited directly in the store admin. The goal is a single source of truth, because double entry always ends in the wrong quantity on the shelf.

Question 11

What if we have 10,000 products or more?

Accepted Answer

That is a question of architecture, not catalogue size. Large catalogues need search and filtering that stay fast, product pages generated without manual work, and careful canonical URL handling so that variants and filters do not create thousands of near-identical pages Google treats as duplicates. All three are planned up front. A catalogue that size is not a problem in itself; filters generating endless URL combinations are.

Question 12

Will we need our own developer after launch?

Accepted Answer

Not for day-to-day work. Products, prices, content, coupons and orders are all handled in the admin without touching code. A developer is needed for new features, upgrades and integrations, which are occasional jobs rather than a standing role. We offer maintenance, but the store does not stop working if you decline it: the code is yours and any team can pick it up.

E-Commerce That Grows Without Platform Lock-In in San Francisco