Reference
Shopify Custom App Discovery examines actors, workflows, decisions, exceptions, data, and acceptance criteria as a store-specific workflow. Discovery should model decisions and exceptions, not collect a feature wishlist. Define the user decision, Shopify surface, app-owned state, failure model, and maintenance. The decision is Which real operator or customer process should the app improve?
Red flags
The primary risk is using a feature list as a substitute for workflow discovery.
Findings
This guidance applies directly to actors, workflows, decisions, exceptions, data, and acceptance criteria.
For shopify custom app discovery, keep the interface centered on the staff or customer decision. Embedded admin screens should preserve Shopify context, make permission and loading states clear, and avoid turning an operational task into a generic dashboard.
Use Functions for supported deterministic commerce logic, Flow for visible automation, APIs for Shopify resources, and app infrastructure for stateful external work. Observe actors, triggers, data, permissions, frequency, handoffs, errors, workarounds, and acceptance outcomes.
Verify webhooks, deduplicate, queue long work, use safe retries, retain attempt history, and reconcile state. A screen list can conceal conflicting workflows and undefined source data. An app must explain what an operator does when automatic recovery stops.
Budget hosting, monitoring, support, incidents, security, API version changes, dependency upgrades, and feature evolution. Validate the mapped workflow with operators using realistic scenarios before architecture.
Investigation
The sequence follows the actual operating model for this subject.
Compare native Shopify capability, configuration, existing apps, and process changes against actors, workflows, decisions, exceptions, data, and acceptance criteria. Record why the remaining gap deserves custom ownership.
Map actors, permissions, decisions, exceptions, loading, errors, confirmation, and reversal. The central decision is Which real operator or customer process should the app improve?
Place deterministic commerce logic, admin UX, storefront behavior, automation, and stateful services in their supported Shopify boundaries. Observe actors, triggers, data, permissions, frequency, handoffs, errors, workarounds, and acceptance outcomes.
Test installation, scope denial, duplicate events, jobs, dependency outages, migrations, rollout, rollback, and offboarding. The route risk is using a feature list as a substitute for workflow discovery. A screen list can conceal conflicting workflows and undefined source data.
Ship observability, runbooks, support boundaries, API-version review, dependency updates, backups, and succession guidance. Validate the mapped workflow with operators using realistic scenarios before architecture.
Case frame
Which real operator or customer process should the app improve? The lenses below are specific to actors, workflows, decisions, exceptions, data, and acceptance criteria.
Describe the staff or customer workflow behind shopify custom app discovery, its frequency, current failure cost, exceptions, and decision owner. A feature list does not prove custom software is the right answer.
Choose where actors, workflows, decisions, exceptions, data, and acceptance criteria belongs: embedded admin, Admin API, Storefront API, webhook processing, Flow, Function, app proxy, theme extension, or app infrastructure. Observe actors, triggers, data, permissions, frequency, handoffs, errors, workarounds, and acceptance outcomes.
Name what the app must store, what remains authoritative in Shopify, retention and deletion behavior, and how schema changes migrate. Avoid copying platform data without a product reason.
Assign hosting, deployments, incidents, security, API upgrades, documentation, support, and roadmap decisions. Validate the mapped workflow with operators using realistic scenarios before architecture.
Exhibits
| Layer | What to preserve | When |
|---|---|---|
| Gap record | Native, configured, existing-app, and process alternatives compared against the exact workflow. | Discovery |
| Product fixture | Realistic store, actor, data, permission, exception, and acceptance scenarios for actors, workflows, decisions, exceptions, data, and acceptance criteria. | Design |
| Lifecycle proof | Install, denied access, duplicate, timeout, migration, rollout, rollback, and recovery evidence. A screen list can conceal conflicting workflows and undefined source data. | Pre-release |
| Ownership file | Named operational owner, dashboards, runbook, API-version schedule, support path, and cost boundary. Validate the mapped workflow with operators using realistic scenarios before architecture. | Handoff |
Disposition
Interview notes
It is justified when actors, workflows, decisions, exceptions, data, and acceptance criteria represents a valuable, store-specific workflow that native features, configuration, established apps, or a process change cannot meet reliably—and when someone will own the resulting product. Discovery should model decisions and exceptions, not collect a feature wishlist.
Depending on the workflow, an app can use Admin or Storefront APIs, embedded admin UI, webhooks, Flow extensions, Functions, theme extensions, app proxies, checkout or customer-account extensions, and app-hosted services. Choose by execution, trust, and state requirements.
Discovery, hosting, queues, observability, backups, security, support, API upgrades, dependency maintenance, data migration, rollout, rollback, and succession are often omitted. They are part of owning the product.
Use realistic store fixtures, denied permissions, duplicate and delayed events, dependency outages, migration tests, monitoring, rollback, and operator recovery. Validate the mapped workflow with operators using realistic scenarios before architecture.
Devuchi
Devuchi is a subscription Shopify development service for ecommerce brands and agencies that need reliable recurring development capacity.
actors, workflows, decisions, exceptions, data, and acceptance criteria can be planned against the frameworks and checks in this reference.