Choose the smallest supported solution that meets the real workflow. Start with native Shopify features and theme capabilities, then compare an existing app or connector with a custom build. A custom app is justified by requirements and ownership, not by assuming that bespoke software is automatically better.
Map the workflow before choosing a tool
Write down the trigger, source system, destination, data fields, expected frequency and failure behaviour. For stock synchronization, “connect the ERP” is incomplete: which system owns available stock, what happens during an outage, and how are corrections reconciled?
| Option | Good fit to investigate | Question before committing |
|---|---|---|
| Native setting or theme configuration | Supported merchandising and storefront behaviour | Does the existing feature meet the exact requirement? |
| Theme development | Presentation and interactions using available store data | Is this actually a server-side or cross-system workflow? |
| Automation or existing app | Supported triggers, actions and repeatable business rules | Are permissions, plan requirements and exceptions covered? |
| Integration connector | Established systems with supported mappings | Who handles failed records, retries and reconciliation? |
| Custom integration or app | Material requirements unsupported by available options | Who owns hosting, security, API updates and support? |
A worked decision example
This is an illustrative workflow, not a client case. A merchant needs ERP stock updates in Shopify and Shopify orders sent back. Trial a connector with a normal order, cancellation, refund, partial fulfilment and duplicate message. Record which fields synchronize and how failures appear to staff.
If it covers the workflow and recovery process, configuration and testing may be the appropriate project. If it misses one business-critical exception, assess a targeted extension or integration rather than assuming the entire system needs rebuilding. If no supported route can handle the required data and error recovery, scope a custom solution.
Compare ownership and lifetime cost
For an app, include subscription fees, configuration, data export and the consequences of changing provider. For custom development, include hosting where needed, monitoring, incident response, access management, API changes and handover. Ask who fixes a failed order sync on a trading day.
Shopify’s app distribution terminology is not a shortcut for this commercial decision. Avoid old “private app” setup instructions; validate the current distribution and authentication model for the actual store and app. The merchant brief should describe the workflow first.
A useful implementation brief
List systems, record types, direction of sync, ownership, volume, timing, exception cases and acceptance tests. Add what you have already tried, including app names and the exact limitation. Separate essential behaviour from conveniences.
For Shopify integrations or app configuration, send that worksheet with your store URL. ZAGO can assess whether setup, theme work, an existing integration or custom development is the appropriate scope. For a storefront-only request, the theme customization checklist covers the information needed for an estimate.
Source: Shopify’s current app distribution models and deprecated app types.
