Native capability
Use existing Shopify features when they meet the operating rules.
Identify the exact gap before adding another dependency.
Explore a custom Shopify integration or app only after the requirement, data access and maintenance commitment are understood.
Prices cover the listed scope. Additional work and external costs are quoted separately.
We start with the operational gap, the people using the workflow and the systems it touches. Custom development follows a clear comparison of the available routes.
Use existing Shopify features when they meet the operating rules.
Identify the exact gap before adding another dependency.
Assess a suitable app against the required features, costs and data access.
Test the important edge cases with representative records.
Build around a defined integration or behaviour that the other routes cannot reasonably provide.
Agree hosting, permissions, error handling and maintenance ownership.
| Route | Typical audience | What we establish |
|---|---|---|
| Custom distribution | A specific store or eligible Plus organisation. | Allowed installations, required access and the operating owner. |
| Public distribution | A product for multiple merchants. | App review, onboarding, billing needs and ongoing merchant support. |
We include checks for signed requests, minimum required permissions, duplicate events and failed deliveries. New public apps must use the GraphQL Admin API, and App Store approval remains a separate Shopify review.
Validate and build one Shopify app workflow with one backend integration and an explicit operating handover.
Compare native features and existing app options against the merchant’s workflow.
Record the gap, distribution needs and the agreed build/buy decision.
Define the authorised data, event flow, integration and failure behaviour.
Confirm required platform capabilities and keep access limited to the agreed purpose.
Implement the approved behaviour and run fifteen acceptance scenarios.
Cover authorised access, invalid input, duplicate actions and integration failures.
Document source, deployment, configuration and support ownership.
Check the release/rollback instructions and record the thirty-day defect correction window.
Requirements and permission map, fifteen-scenario test record, source/deployment handover and maintenance responsibilities.
Outside this scope: Guaranteed public-app approval, extensive billing systems, multi-tenant platform and unknown API work
6–10 weeks after feasibility review
Discovery $750 – $1,500; hosting/support separate
Distribution, permissions, hosting and integration requirements shape the quote. Agree a store-specific or multi-merchant application during discovery.
If the full scope is beyond your budget, we’ll prioritise the most useful work and agree a smaller first phase with you.
Share what is available. We’ll identify any missing access or inputs during scoping.
Published prices apply to the listed scope. Deliverables, timing, revisions and external costs are confirmed before work starts.
An illustrative delivery approach to help you review the scope. This is a planning example, not a client case study.
| Stage | Example work | Acceptance or decision |
|---|---|---|
| Core task | An authorised merchant starts the agreed store workflow. | Check role, required access and input validation. |
| Integration | Send the agreed fields to one external system and record the outcome. | Handle retries and duplicate requests safely. |
| Operations | Document configuration, deployment and support responsibilities. | Review access removal, logs and the release/rollback process. |
Illustrative platform screens show the type of work and reporting. These are not client results.
Inspect requests, responses and validation checks for a defined integration.
Make order rules, conditions and staff notifications explicit.
Inspect validation, duplicate checks, destinations and exception handling.
Organise product titles, stock, publication status and catalogue structure.
Explore eight illustrative projects, from the initial brief to delivery and acceptance. Businesses and data in these walkthroughs are fictional.
A considered storefront, from catalogue to checkout.
Illustrative project
Explore the walkthroughAn agreed theme, layouts and catalogue.
Custom sections or a separately scoped theme.
Data migration and feature replacement.
Begin by checking whether a native feature, suitable existing app or integration can meet the requirement. The proposed custom-app scope covers one workflow and one integration. A store-specific app and a product distributed to many merchants have different delivery and support needs; distribution must be decided during discovery.
Define source-code handover, hosting, secrets, permissions and the support owner in the agreement. The starting scope includes a thirty-day defect correction window; ongoing hosting and maintenance are additional.
A representative user can complete the workflow with the required permissions, errors are visible and repeat requests do not cause duplicate actions. Installation, access changes and removal should be considered for the chosen distribution model.
$5,000 – $12,000 / scoped custom app. Discovery $750 – $1,500; hosting/support separate These are published USD prices. The written quote must state the complete cost, payment schedule and applicable taxes.
6–10 weeks after feasibility review. To scope the work, prepare: Workflow gap; stores/users; existing app alternatives. The schedule starts after the required access, inputs and approvals are ready.
Use the listed deliverables and exclusions as the starting point. The quote must state acceptance checks, review rounds, payment stages, cancellation arrangements and any ongoing support. Requested additions need an agreed cost and schedule before implementation.
Tell us where you are, what needs to change, and what success would look like for your business.