# Custom Shopify app development for programs no public app supports.

> For ecommerce and engineering leads whose programs no public app supports, we build custom Shopify apps: loyalty programs, promotions, account tools and admin workflows. You own the code, and the Care tier of an Engineering Partnership can keep it current with Shopify’s API versions. Work starts with a three-week Architecture Review that settles build or buy first.

Custom apps and integrations · Custom Shopify apps

- **Starts with:** A three-week Architecture Review
- **Typical build:** Fixed-fee phases, each release tested and versioned
- **You own:** The app, its code and its documentation

## When is a custom Shopify app worth building?
- The program is core to how you sell, and no public app models it.
- Several public apps are stacked to approximate a program, and they conflict.
- App subscription costs keep rising with order volume or store count.
- Staff run the program from spreadsheets because the admin cannot hold it.
- The same program must run across several stores in a Plus organisation.

## How does a custom app build run?
1. **Decide build or buy** — Check public apps first; build only what is core or costly to rent.
2. **Write the program down** — Rules, roles, edge cases and data, agreed in writing before design starts.
3. **Design the surfaces** — Admin screens, checkout and account extensions, each on a supported extension point.
4. **Build and test** — Typed code, automated tests and a development store that mirrors yours.
5. **Release and hand over** — Versioned releases, monitoring, and documentation your team or ours can run.

## An app that belongs to you, not a vendor
- A build-or-buy decision for each requirement
- A written spec of rules, roles and data
- The app, in your repository, with automated tests
- Admin, checkout and account extensions where needed
- Monitoring and error alerts from the first release
- Documentation and a handover session for your team

## What usually goes wrong
- **Building what a public app already does** — Check the App Store first; build the difference only.
- **Treating launch as the finish line** — API versions change; plan upkeep before you build.
- **Storing program data outside Shopify by default** — Metafields and metaobjects keep data where Shopify can use it.
- **Letting the agency keep the code** — Keep the repository under your account from the start.

## Wholesale programs, built as custom Shopify apps

For a clinical skincare brand we built four B2B storefronts, each with its own buyers, prices, terms and rules, enforced at checkout by Shopify Functions and run alongside eleven store-aligned custom apps the brand owns.

## Questions
### Should we build a custom app or use a public one?

Public first. If an App Store app does the job, rent it. Build when the program is core to how you sell, when several apps are stacked to approximate it, or when subscription costs grow with the business. The Architecture Review makes that call per requirement.

### Who owns the code?

You do. The code lives in your repository from the start, with documentation and a handover. Where the app itself is registered is agreed in writing before we build. If you move the work in-house later, nothing needs to be rebuilt.

### What does a custom app cost to keep running?

The build is fixed-fee; the ongoing cost is upkeep. Shopify releases new API versions on a regular schedule, and apps have to move with them. The Care tier of our Engineering Partnership covers upkeep, API versions and fixes, so that work is planned and priced, not discovered.

### How long does a custom app take to build?

It depends on the program, so we do not quote a timeline before the scope is written. The Architecture Review produces that scope. The build is then split into phases, each with a fixed fee and a date agreed before it starts.

### Can a custom app run across all our stores?

Yes, within limits. A custom app can be installed on stores that belong to the same Shopify Plus organisation. Where stores need different behaviour, per-store settings handle it, so you maintain a single codebase, not a copy per store.

[Describe your requirement](https://www.studioantipodes.com/start-a-project)