PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Commerce engineering / Shopify

Shopify app development.
From storefront to store operations.

Public apps, custom merchant apps, Liquid themes and headless storefronts. Start with the surface that needs to change, then define distribution, platform limits, integration ownership and the evidence for release.

Discuss Shopify requirements โ†—
Contents ยท Shopify

Choose the surface before choosing the build.

A Shopify project can change the storefront, embedded administration, checkout, point of sale or the systems behind the store. A Liquid theme controls presentation; an app can own merchant settings, integrations and supported extensions; a headless front end has its own interface and release work. Those boundaries can overlap, so map each requirement instead of treating every change as an app.

The scope can suit merchants who have outgrown theme settings, brands moving from another store, and SaaS teams building a product for multiple merchants. Record the actual buyer journey, staff workflow, catalogue, markets and existing systems. A public app product and a single-merchant integration need different distribution, support, billing and data-isolation decisions.

Custom source and platform control are different things.

List the theme, app, extensions, Functions, headless front end, configuration, deployment instructions and documentation to be delivered. Agree repository control, account ownership, custom-code rights and third-party licences in writing. A transfer of custom source does not transfer Shopify itself or remove its platform, plan and distribution rules.

Name the owner of the store, developer account, listing, domains, hosting, merchant accounts and data. Set confidentiality, support boundaries, patch responsibility, change control and any ongoing service terms. Transfer secrets separately through an approved secure route.

Compare hosted commerce with an operated store.

Evaluate Shopify, WooCommerce and Magento against the same products, buyer roles, content, integrations and operational team. Do not replace that exercise with fastest, cheapest or most-customisable labels. Separate store infrastructure from the application services that your team still needs to run.

A WordPress-led site may warrant a WooCommerce comparison; a complex catalogue or multiple stores may warrant Magento or another commerce option. None is selected solely by catalogue size or an agency default.

Seven decisions before a Shopify project.

What does Shopify app development cover?

Separate public App Store apps, custom merchant apps, Liquid themes and headless storefronts. A theme can include sections merchants rearrange, product and collection templates, cart interactions and search. An app can provide admin screens, storefront blocks, integrations and supported checkout logic. Headless work includes front-end routing, data fetching and its own content-editing arrangements.

Migrations can involve WooCommerce, Magento, BigCommerce, OpenCart or a custom store. Define which capabilities already exist, which need configuration, which need a maintained app and which justify custom code. Do not purchase or build an app simply because a theme requirement was described as development.

Public distribution or custom distribution?

Shopify currently distinguishes public distribution for multiple merchants from custom distribution for a single store, stores in the same Plus organisation or development stores. Public distribution requires approval and App Store registration. Custom distribution cannot charge merchants through Shopify's app billing system. The distribution method cannot be changed after selection, so decide it on the production app before treating it as routine setup.

A public app is a supported product: installation, merchant isolation, billing, listing accuracy, privacy handling, version upgrades and merchant support all need owners. A custom app still needs authentication, permissions, data protection, deployment and recovery. The absence of listing review does not make an app unrestricted or safe by default.

Which developer tools belong in the scope?

Select the current Shopify CLI and supported app template for scaffolding and local development. An embedded app can involve Polaris and App Bridge; server services call the appropriate APIs; theme app extensions, checkout extensions and Functions have separate platform interfaces. Review current template and component versions rather than adopting an old Remix or React package assumption.

Keep Admin API credentials in trusted server-side services. Customer-facing Storefront API integration is a different boundary, not permission to expose administrative tokens. Record scopes, installation/session handling and the authenticated store context for every server request.

What needs preparation for App Store review?

Check current requirements at the start of the project and again before submission. Prepare installation and authentication, an accurate embedded experience where applicable, supported app billing, privacy-request handling, storefront impact evidence, a truthful listing, actual screenshots and a working support route. Define required protected-customer-data access and its approval separately.

Test install, reinstall, permission changes, cancellation, uninstall and data retention or deletion. A developer-store demonstration does not prove review acceptance or merchant eligibility. Shopify decides approval and timing; neither a source repository nor a submitted listing is approval.

What depends on Plus or another platform entitlement?

Current checkout UI documentation limits the information, shipping and payment-step UI extensions to Shopify Plus. A thank-you or order-status requirement must be checked against its own target and plan rules rather than treated as unrestricted checkout access. Checkout extensions run through supported APIs and components, not arbitrary access to checkout HTML or payment information.

Shopify's Functions overview distinguishes public App Store apps containing Functions from custom apps containing Functions, which require Plus. Individual Function capabilities can have additional restrictions. Verify the exact Function API, distribution model and store plan together. Company accounts, catalogues, payment terms, expansion stores, scheduled sales and any replacement for older Scripts or checkout.liquid work need their own current entitlement and migration checks.

When is a headless storefront worth its operating work?

Evaluate Hydrogen or another front end when a theme cannot meet the actual content, product configuration or multi-source experience. The scope includes routing, product and cart data, session handling, caching, search, analytics, preview, content editing and deployment. Compare Oxygen or another host against current eligibility, regions, runtime limits and commercial terms rather than assuming hosting is free or universally included.

A headless project does not automatically inherit a theme's editor workflow or every app-block integration. Identify app compatibility and editorial ownership before choosing it. Checkout constraints still need platform checks. Neither headless architecture nor a hosting label guarantees a speed score, sub-second load or lower operating cost.

How should cost and delivery be agreed?

Prepare a current written scope for the actual app audience, storefront surfaces, checkout rules, integrations, migration and operating work. Separate implementation from the Shopify plan, app subscriptions, backend hosting, search/CMS services, payment fees and maintenance. A public product also needs a current distribution, billing and commercial-policy check.

Dependencies include account access, plan eligibility, catalogue readiness, provider approval, privacy review and merchant feedback. Agree milestones, acceptance, change control and how blocked dependencies affect delivery. A separate catalogue platform's price or timeframe is not a Shopify quote.

Keep merchant UI, trusted services and extensions distinct.

Feature-first boundaries

A feature can own its embedded admin route, configuration, API queries, service logic and relevant extensions. Document how app versions, backend releases and theme changes fit together. Deploying extension code is not the same as deploying an app server: Shopify's checkout extension documentation explicitly distinguishes the hosted extension bundle from a backend that needs its own hosting.

Use separate development and production configuration. Keep permissions, store identity, data ownership and failure handling next to the feature, not hidden in a theme script. Pin supported versions and track dependency changes. A scaffold or CLI success is a starting point, not production readiness.

Webhooks, retries and reconciliation

For HTTPS delivery, verify the HMAC signature against the raw request body before trusting payload contents. Use the current official authentication helpers or a correctly implemented verifier. A shop parameter alone does not establish the authenticated tenant. Check each database query and queued job against that verified store context.

Duplicate deliveries can occur. Use idempotent operations and persistent delivery tracking; Shopify distinguishes the webhook delivery ID from an event ID that can correlate several deliveries. Design an atomic claim/processing state so concurrent retries cannot both create a shipment, charge or external order. Acknowledge only after the event has been durably accepted for the intended processing route.

Events are not guaranteed to arrive in order and delivery can be missed. Define timestamp/version conflict handling and reconciliation through supported APIs. Monitor failed deliveries, queued work and upstream errors. Test duplicate, delayed, invalid-signature, out-of-order and missing-event cases, not only a happy-path order creation.

Versioning and API work

Shopify's versioning guidance distinguishes versioned APIs from unversioned surfaces. Set supported API versions explicitly, review release notes and test changes before upgrading. Inspect the returned API-version header: an inaccessible requested version can fall forward to another supported version. A pinned URL alone does not prove the intended schema was served.

For integrations, plan pagination, supported bulk operations where appropriate, rate-limit handling, backoff and partial failures. Record which system owns product, stock, customer and order fields. A webhook can signal work; the reconciliation process must still detect missing or inconsistent data.

A low-stock badge is presentation, not inventory reservation

The original theme-app-extension example describes a merchant-placed badge with a configurable stock threshold. Retain that subject as a feature specification: identify the selected variant, inventory-management policy, availability rules and display threshold, then render only when the agreed condition holds.

App-block placement, dynamic variant updates and uninstall/data-retention behaviour need testing in the selected theme and app.

Performance and data isolation

Load app assets only where they are required, measure relevant templates before and after changes and test low-bandwidth mobile paths. Check cart, account and customer-specific cache boundaries. A storefront speed audit does not prove app-server reliability, webhook correctness or a secure tenant boundary.

Review authenticated shop scoping, permission changes, secret storage, escaping, redirects and externally supplied URLs. Keep fetched configuration as data rather than executable code. Test customer and merchant records from separate shops to expose cross-tenant access errors. Record evidence and limitations instead of declaring every platform-hosted element compliant.

Three engagement shapes, with separate acceptance.

Name the responsible engineering, QA and release roles. Agree review cadence, billing milestones, support scope and cancellation terms. No universal weekly delivery, staffing model or notice period is implied.

Six acceptance areas before handover.

Use development stores and authorised test-mode orders for testing. A test payment does not establish live merchant approval. Include agreed desktop/mobile browsers and accessibility checks. Request evidence for any accessibility or security standard rather than asserting certification from a checklist.

Choose each tool by its responsibility.

An option inventory, not an included bundle or evidence that every integration is configured.

Move records and buyer journeys, not just catalogue totals.

Inventory products, variants, collections, media, customers, orders, reviews, gift cards, discounts, subscriptions, content, blog posts and extension-specific fields. Establish export/import support and exclusions before promising transfer. Passwords, saved payment methods and recurring authorisations require provider-supported checks; an account invite is not a universal migration method.

Run a trial migration on a protected environment. Reconcile representative relationships and edge cases, not only record totals. Map old URLs, metadata, canonical pages and redirects; test search, cart, checkout and operator tasks. Redirects support continuity but cannot guarantee retained rankings.

Agree final sync, any order freeze, owner-authorised cutover, rollback and post-cutover reconciliation. Domain/DNS changes and live payments are separate authorised actions, not automatic consequences of approving a design.

From merchant brief to an operated release.

An App Store submission is not an approved listing. Domain setup, payment-provider eligibility, customer-data access and platform review can affect the plan. Agree those dependencies without promising a first-commit deadline or a fixed launch/support period.

What changes the Shopify estimate?

Obtain current one-time and recurring commercial terms separately. No sample price, platform app count or revenue-share figure is treated as a current quote. Custom source does not make platform or third-party services cost-free.

Shopify delivery review and handover.

Agree the implementation boundary, deliverables and acceptance checks in the project scope. Include the source and configuration to be handed over, third-party dependencies, account ownership and the receiving owner's installation and operating walkthrough. Review the selected work at the agreed milestones, with unresolved items recorded before release.

The delivery review can cover an authorised development-store demonstration, repeatable install/uninstall tests, cross-shop data-isolation checks, Function tests, migration reconciliation and a receiving-team release rehearsal. Confirm contracting identity and any source, support or confidentiality commitment directly. Unverified named testimonials, agency counts, badges and delivery guarantees are not reproduced as proof.

Turn sector labels into purchase and operating rules.

Questions to settle before Shopify work begins.

What is included in a theme delivery?

List actual product/collection pages, sections, search, cart drawer, quick-view behaviour, navigation and responsive states. Agree accessibility, product structured data, analytics/pixels and consent requirements as explicit scope, not an automatic standard-compliance or tracking promise. Checkout changes and app services need their own platform and hosting checks.

Can a custom app serve only our store?

Use the current custom-distribution requirements for the selected store or eligible Plus organisation. Verify the needed APIs, permissions and Function eligibility. Do not confuse custom distribution with the older admin-created custom-app route or assume it permits Shopify app billing.

Can a public app be published?

Prepare the current distribution, installation, billing, privacy, listing and storefront requirements. Assign the developer/listing account and support owner in the agreement. Shopify controls approval and timing. Launch planning should allow review and corrections without promising acceptance.

Who owns the app, theme and store?

Agree custom-code rights, repository and account control, third-party licences and export responsibilities in writing. Store hosting, checkout and administration remain governed by Shopify's platform terms. A handover must be demonstrated through setup, deployment and access tests, not a repository link alone.

Does headless mean faster?

No architecture guarantees speed. Compare a representative theme and headless implementation against the same content, devices and user journeys. Include editorial tools, app integration, cache/session boundaries and ongoing front-end operation in the decision.

What happens after launch?

Agree defect scope, updates, privacy-request handling, failed events, monitoring, support escalation and restoration responsibilities. Platform or feature changes can need separate work. Specify the actual support period, recurring fees and response expectations in the agreement.

What should an existing-store audit cover?

Review store and developer-account access, distribution method, app permissions, API versions, theme edits, extension compatibility, live billing, tokens, privacy handling, queues and reconciliation. Preserve the working state and recovery route before making changes. A pasted script or older integration is a fact to assess, not evidence of another provider's conduct.

Platform references used for technical checks.

Official documentation checked on 16 November 2026. Verify the selected version, distribution, plan and provider terms for the actual implementation.

Bring the storefront or operating task that no longer fits.

Describe what the buyer, merchant or integration needs to do and where the present flow breaks down. We can turn that into a scoped theme, app, extension, migration or headless discussion, with acceptance and responsibilities kept visible.

Discuss your Shopify scope โ†—