Show where an existing app falls short
Suppose a merchant must approve an operations request before sending it to another system. Write down the required fields, who approves it and what happens if it fails. Ask every bidder to demonstrate that same example.
| Option | Evidence to request |
|---|---|
| Store configuration | The supported setting or workflow, its limits and the remaining manual steps. |
| Existing app | The exact plan or version, required permissions, exception behavior and continuing fees. |
| Custom app | The missing behavior, implementation boundary, acceptance cases and named operating responsibility. |
Record the fit gap in plain language. “The selected option cannot enforce the agreed reviewer rule” is a more useful brief than “we need a powerful app.” Keep later ideas in a separate list so they do not silently expand the first release.
Decide who will install it
An application for one merchant and a product for many merchants have different distribution choices. Shopify currently distinguishes custom and public distribution, and says the selected method cannot later be changed. Its distribution table also has specific limitations for each route. Review the intended audience before committing to a route. Shopify app distribution.
Ask the supplier to record the proposed route, relevant requirements and remaining review work. Development completion, installation and public distribution are separate acceptance events. A proposal should identify which of them it includes. An App Store listing or approval should be supported by its own evidence.
Request the permissions the task needs
List the store data the workflow reads or changes. For each item, record its purpose, source of truth and authorized actor. Ask why each permission is required and what the application does when the necessary permission is absent.
Shopify access scopes control what an app can read and write; a declared scope must be approved on the store before the app can use it. This makes the permission decision part of the workflow scope. Shopify access-scope guidance.
Use permitted synthetic examples during early discussions. Account credentials and private customer records belong in an agreed secure process when access is actually needed.
Plan for duplicate requests and failed transfers
Agree how a valid request is identified and which saved record confirms it. Check an invalid input, denied action, unavailable dependency and repeated submission. If a response is lost, the operator needs a way to find the existing operation before creating another one.
A local fixture can show a proposed rule. Evidence from the authorized store and actual interface is needed to establish platform behavior. Keep those states visible in the acceptance sheet so that a successful mock is not mistaken for an installed integration.
Compare maintenance and operating costs
Separate initial development from hosting, app subscriptions, provider charges and maintenance. Identify the owner of the source, app account and operating documentation. Ask how dependency changes, incidents and new requirements are handled after handover.
Agree support windows and review overlap with the actual merchant team. This applies to US, UK and Australian engagements without assuming an office or support arrangement in any country. Compare the same workflow and responsibility units across proposals; a country label does not establish fit or price.
Bring one workflow, the precise existing-app gap and the intended audience to a Shopify app scope discussion. If the requirement also changes the buying experience or catalogue, use a separate storefront scope with its shared dependencies identified.
