When Shopify has to talk to the rest of your systems
Most requests that arrive with the word Shopify are not development requests. A theme that is slow because of twelve apps gets fixed by removing apps. We are worth hiring when the store has to talk to something else: an ERP, a stock system, a pricing rule, a payment flow, a move off another platform.
Most Shopify problems are not development problems
A slow storefront, a checkout that loses people, an admin that crawls: in most cases the cause is years of accumulated apps, three of which do the same thing and two of which nobody uses. The fix is removing apps, not writing code. It is less impressive and it costs far less.
So we look at what is actually running on the store before proposing anything. If the answer is to uninstall six apps and fix how images load, that is what you will hear, even when it costs us the engagement.
What engineers are actually for
Shopify does everything standard very well. Engineering starts where the platform stops: when the store has to exchange with an ERP, reflect real stock held somewhere else, apply a price grid per customer or per volume, handle an unusual payment journey, or when you have to leave another platform without breaking URLs or order history.
Those are integration problems: APIs, queues, error recovery, state to reconcile on both sides. It is what we do every day outside commerce and it transfers directly.
We have built payment flows with iDEAL, Bancontact and Stripe, and integrations with ERP systems. The hard part is never the API call. It is what happens when the call half fails.
Migrating onto Shopify, or off it
A platform migration is decided by what nobody sees: redirects, customer identifiers, order history, credit notes, live subscriptions, tax per country. The visual side is the fastest to redo and the least risky.
We treat a migration as a data migration before it is a store project: inventory of what exists, a cutover plan, a set of checks before and after, and a rollback window that stays open until the numbers match.
Where we are the wrong answer
If what you need is a storefront redesign, hire a specialist Shopify agency or buy a good theme. They will do it better, faster and cheaper than we will, and it is a real craft that we do not practise. We are not a Shopify partner agency and we will not pretend to be one.
The same goes for straightforward retail: simple catalogue, standard payment, standard shipping. Shopify already covers that, and putting engineers on it is money wasted. Come back when stock lives in another system and two people are retyping orders by hand.
We also do not do acquisition, advertising or product SEO. We can make a store fast and consistent with the rest of your systems. We do not bring you traffic.
The shape of a Shopify engagement here. None of them start with a theme.
- ERP or stock integrationNode, .NET, Shopify Admin APIProducts, stock and orders kept in sync, with error recovery and a log of what failed.
- Pricing rules and B2BShopify Functions, NodePrice per customer or per volume, order conditions, cart validation.
- Payment flowsStripe, iDEAL, BancontactUnusual payment journeys and reconciliation of settlements with the accounts.
- Platform migrationPostgreSQL, migration scriptsCatalogue, customers and history moved over, redirects and checks before cutover.
- Performance and app debtAudit, theme, LiquidOften the shortest engagement: find what slows the store down and remove what is dead.
Common questions
- Do you build custom themes?
- We do when it goes with an integration, for instance a product page that has to show stock or a price coming from another system. For a purely visual redesign, a Shopify agency will do better than us.
- Our store is slow. Is that a development project?
- Rarely. Start with the list of installed apps and with the images. We can run that diagnosis in a few days and tell you whether there is real engineering work left behind it.
- Can you connect Shopify to our ERP?
- Yes, that is the core of what we do. The useful question is not which ERP, it is which system is the source of truth: who decides stock, who decides price, and what happens when the two disagree. That is where we start.
- How long does a migration take?
- Almost entirely down to how clean the source data is and how many commercial exceptions exist. We estimate after an inventory, not before. A simple catalogue and a healthy customer base is not the same project as ten years of history full of special cases.
- Are you ISO 27001 certified?
- Not today. Our practices follow ISO/IEC 27001 principles and are mapped against CyberFundamentals from the Belgian Centre for Cybersecurity, with the Stage 2 audit planned with a BELAC-accredited body in 2027. Encryption, enforced MFA, least privilege and access review at project close are in place now.
- Where is the team and who do we contract with?
- Engineering is in Rabat and Casablanca at UTC+1, so the same working day as Brussels, Paris and Amsterdam. Contracting is through JADEV GROUP SARL in Belgium, in euros, under Belgian law.
Tell us what Shopify has to reach outside itself
Describe the system the store has to talk to and what breaks today. The scoping assistant asks the questions an engineer would ask, then returns an estimate with a scope and a start date.
Scope an integration- Custom booking platform cost, block by blockFive technical blocks, a published day-rate grid from 150 to 450 EUR, and worked examples from booking platforms we operate in production.
- Payment idempotency for iDEAL and BancontactOne replayed webhook is enough to charge the same traveler twice. We explain the idempotency key design that makes it impossible, drawn from booking platforms we run in production with iDEAL and Bancontact.
- Industrial IoT data ingestion on Azure: the patternThe pattern that makes machine data ingestion into Azure survive real plant conditions: a queue between the shop floor and the cloud, priced in engineering days on our public rates.
- Zero downtime data migration: dual write to cutoverThe new system shadows the old one in silence, the copies are proven to match, and the rollback lever stays live until the end. The full playbook, priced, limits included.
- IT staff augmentationNamed engineers inside your existing team, on a European working day, contracted through Belgium.
- Nearshore vs offshoreA straight comparison for European teams who already offshore and are weighing a move closer.
- Nearshore development teamA dedicated group that owns delivery end to end, from architecture through production support.
- CTO as a servicePart-time senior technical leadership, to arbitrate without a full-time hire.
- Managed IT and cloudCloud, pipelines, domains, mail and access, held by the team that also knows the code.
- Cloud migrationInventory, batched cutovers and a tested rollback, so the move does not depend on luck.
- Infrastructure as codeEnvironments described in code, reviewed and rebuildable, instead of configured by hand once and never again.
- AI and chatbot engineeringModels integrated into software that has to run, with a straight answer on what will not work.
- Data engineeringWarehouse, pipelines and reconciliation, so the numbers can be trusted.