The maintenance company replies, “The issue belongs to the app developer.” That diagnosis may be correct, yet the store still waits. Before buying monthly Shopify support, establish what you purchase when another supplier is needed: a prepared case, follow-up and verification, or simply a support address.
Separate activities before comparing hours
Investigating a cause, coordinating with an external developer and changing code controlled by the maintenance team are different activities. A proposal may include some and exclude others. “App support” alone identifies neither the worker, the retainer consumption nor the person who requests approval for additional costs.
In a fictional example, a party-supplies store uses an app to capture event details within a modified theme. Following a theme change, a field no longer appears as expected. No cause or completed experiment is claimed: send this same case to two suppliers to examine how each handles shared responsibility.
Who made the component, and who follows the issue?
Shopify links theme support to its maker and limits its assistance with external code and modifications. Its app documentation directs third-party app issues to their developers. These platform boundaries do not automatically define a separate maintenance supplier's contractual obligations.
Request one accountable role on the supplier's side, even when several parties perform the work. Accountability does not confer control of app code or guarantee a developer response. It identifies who assembles evidence, follows the next step and explains the remaining unresolved work to you.
A comparison sheet for the same case
Include the table in your request and ask suppliers to complete it for the same fictional issue. Compare included activities before comparing a ten-hour balance with another allowance. Keep the case description and written response with the proposal so their intended meaning remains available at renewal.
| Part | What to establish | Requested evidence |
|---|---|---|
| Initial diagnosis | Investigation boundary and further approval point | What was examined and remains uncertain |
| Coordination | Whether case preparation and follow-up consume hours | External reference and next-step owner |
| Waiting | How elapsed waiting differs from actual effort | A waiting state and reason, separate from worked hours |
| Solution verification | Who checks the result and modification scope | The agreed case outcome and remaining observations |
Preparing a useful message or reproducing a fault can require actual work, while a day of waiting may involve no activity on the case. Assume neither is free or billable: agree the policy. If coordination effort has a limit, establish what happens at that limit and who authorizes continuation.
Can the supplier prepare an understandable request?
Request the app name and version, expected and observed behavior, reproduction steps, onset and relevant changes. Shopify recommends these details when seeking help. Comparing proposals does not require sharing customer data or granting access to the live store.
For the fictional case, synthetic data can show the missing field and surrounding change. If a later investigation requires real logs or images, agree redactions, recipients and an allowed channel: some Function logs contain personal information. Passwords and keys do not belong in the issue card.
Read the follow-up update before month-end
A useful update identifies completed team work, the dependency on the developer, the latest response and the next follow-up owner. “Following up” without a reference or identified activity does not explain retainer consumption. An unanswered external request should remain visible in the monthly report.
Also distinguish an acceptable workaround, an app-developer fix and a custom change requiring separate scope. External support approval does not establish that every modification suits a customized theme. Verify the relevant case before treating it as finished under your agreement.
Review third-party dependencies and issue escalation scope to complete your questions. Bring this comparison sheet when requesting Shopify services from Nextwave to establish coordination effort and follow-up ownership without assuming free hours or guaranteed third-party responses.
References read
Shopify's theme support and app assistance documentation was read on 4 November 2026. Platform support benefits are not transferred into a private maintenance contract. Prepared with AI assistance and information and translation review.
