Shopify app development studio
Custom Shopify app development
We design and build Shopify apps and extensions for merchants who need more than off-the-shelf — internal workflows, bespoke admin tools, and integrations with ERP, CRM, PIM, subscriptions, and the rest of your stack.
Based in Copenhagen, working with Danish and international brands. English and Danish.
Discuss your appWhat we build
- Private and custom apps for internal workflows
- Custom admin tools and merchant-facing utilities
- Storefront and theme app extensions where it fits
- Checkout UI extensions and customer account extensions
- Integrations with ERP, CRM, PIM, subscriptions, and logistics
- Apps that replace manual work and reduce app-store bloat
Stack & platform
We ship with the same stack Shopify recommends for apps today — typed, maintainable, and ready for App Store review when you need it.
- Remix & React Router — Shopify’s app template foundation
- TypeScript end to end
- Shopify Admin API (GraphQL), webhooks, App Bridge
- Polaris and modern React patterns
Recent work
Public Shopify app
Product-page accessories with one-click add to cart — rules per product, collection, or the whole catalog. Built and listed by Globus.
View projectPartner tool
MRR, ARR, installs, and trials for every Shopify app you publish, synced from the Partner API so payouts are not your only revenue view.
View projectPublic Shopify app
A production app in the Shopify App Store — built and maintained by Globus. Real-world app architecture, merchant onboarding, and ongoing releases.
View projectDanish Shopify brand
Custom theme work and a polished storefront for a Danish living-design brand — multi-language, performance-focused, built for the Nordic market.
View projectHow we work
Discovery
We clarify the problem, constraints, and which Shopify surfaces (admin, checkout, storefront, APIs) are in scope.
Scope & build
We agree milestones, then implement, test in dev stores, and iterate with your team.
Launch & care
We help you ship safely — permissions, review if public, monitoring — and we can stay on for maintenance and new features.
Security & maintenance
Apps handle merchant and customer data: we follow least-privilege access, secure credential handling, and clear handover docs. After launch, we can agree on updates for API changes, new Shopify features, and bugfix windows.
Before you start
- Who owns the app?
- You do. The app, the repository, the store, and the data stay in your accounts. We hand over the code so you are not locked to us.
- How does a project start?
- We start with a conversation, write down the scope, and set milestones before we write code.
- What does it cost?
- An app does not have one price. It follows what the app has to do on day one. The guide shows how we think about the numbers: the platform, the apps, and the build, and where a cheap quote gets expensive later. Read what a Shopify store costs
Tell us what you need to automate or integrate
Whether you are in Denmark or abroad, we can help you turn a workflow into a proper Shopify app.
Get in touchWhen a Shopify app is the right build
A Shopify app is the right build when the logic has to run without someone sitting in the theme editor. A different product-page layout, a metafield that should be visible, a breadcrumb that can be drawn from the menu: that belongs in the theme or in a theme app extension. An app is for rules, sync, permissions, and something that has to happen on every order. If you are unsure, we start by saying which of the two it is. Building an app for a theme problem is the expensive mistake.
Private apps are most of the apps we make. They are not on the App Store. They are for your store or your organization: an admin tool, a connection to an ERP, CRM, or PIM, a checkout extension, something on the customer account. Public apps, like Smart Breadcrumbs and Product Accessories & Upsell, are a different discipline, because stores we do not know have to be able to install them, and because the listing, the privacy policy, and the terms have to make sense to a merchant who was not in the scope meeting.
We build with Remix, TypeScript, and Shopify’s current APIs. That means admin, checkout, customer accounts, and the webhooks and background jobs that belong when data has to move without anyone clicking. The scope says what the app reads, what it writes, who may use it, and how you turn it off. You see that boundary before the code starts. Along the way there are milestones, not an open queue of wishes that changes the app every time someone has an idea.
An integration is part of the app work when it has to be reliable. A nightly export into a spreadsheet is not an integration. An integration has a source, a target, an error you can see, and a way to run again when the warehouse or the ERP has had a bad night. We describe that before we connect the systems. Shopify does not become the master of data that already has a master somewhere else, unless you choose that on purpose.
Once the app is live, it is part of operations. Shopify moves APIs, checkout changes, and a webhook can fail without the storefront looking wrong. That is why watching the app, and agreeing who is allowed to change it, belongs in the work. You can come back with the next concrete change. It is scoped on its own. You should not maintain an app nobody can explain, and you should not keep putting business rules into a theme that cannot be updated afterwards.
Before we choose an app, we look at what Shopify already does. Discounts, markets, customer accounts, and Flow cover more than they did a few years ago. An app that repeats a built-in feature is an app you pay for and maintain without getting anything the theme or the admin did not already give you. We say so when that is the case. We build when the rule is yours: a calculation, a system outside Shopify, or a workflow the team cannot click through every day.
The documentation for a private app is short on purpose. What it does, which data it touches, how to turn it off, and who you write when an order gets stuck. That is hello@globus-dev.com, and it is the people who built it. You do not get a folder nobody reads. You get an app, a boundary, and a way to run it when Shopify or your ERP changes underneath it.
A private app has an owner on your side. That is the person allowed to ask for a change, and the person we write when Shopify moves an API. Without that owner the app becomes a place nobody dares to touch. Say who it is when you write. Also say whether the app may read orders, customers, or only products. That is scope, not paperwork for its own sake.
A public app and a private app are different projects, even when they look alike in the admin. A public app goes through Shopify’s review, needs permissions a stranger can understand, and needs support that holds when someone installs it without knowing you. A private app is your workflow: prices from an ERP, orders that must be split, a tool for customer service, a link to a PIM. It does not need the App Store to be finished. Smart Breadcrumbs and Product Accessories & Upsell are the public examples. AppDeck is the internal tool that reads the Partner API.
Three things should be said before a build. Who on your side owns the app when Shopify moves an API. Whether it may read orders, customers, or only products. And whether the display must survive a theme change, because then it is a theme app extension and not a copy of Liquid you have to remember. Put that in the first email to hello@globus-dev.com. We answer with the kind of job. We do not promise a review time Shopify has not given us, and we do not build an app when the theme can already do what you described.