Custom software or SaaS: a defensible decision

For commerce teams choosing between an app, SaaS platform, custom application or combined architecture.

The first step is therefore not tool selection but a decision map. It separates essential processes from habits, names dependencies and shows which parts already sit inside Shopify's standard capabilities. Only the remaining gaps justify apps, middleware or custom development.

NICCOS considers a topic ready for delivery only when the objective, non-goals, owners and acceptance are documented. This prevents a concise page title from turning into an open-ended transformation programme whose effort nobody can explain reliably.

The decision is made per capability rather than for the whole stack. Commodity functions stay standard; differentiating logic sits in a small, decoupled application.

The architecture is shaped around change frequency, outage impact and team ownership. A process that runs every minute needs different guarantees from a nightly catalogue export. Editorial content requires different approvals from a price or an order.

We always plan an observable path: stable IDs, logged state transitions, repeatable processing and a dashboard for exceptions. Without that operating layer, a technically working connection is only a demo rather than a dependable commerce solution.

Portability, export formats, API access and deletion paths must be settled before signing. Data ownership without a practical export is only a clause.

For every relevant object we document source, destination, key, update frequency, conflict rule and error path. It sounds formal, but it removes the late loops caused when two systems hold the same field with different meanings.

Data is not merely migrated or synchronised; it is reconciled against business meaning. Samples must cover variants, taxes, markets, discounts, returns and historical exceptions. A successful import without business reconciliation proves only that files were read.

The delivery path is deliberately split into verifiable outcomes. Every phase ends with an artefact, a decision or test evidence. The team can change scope without losing the overall plan, and risks become visible before they block the critical path.

The order follows risk: data and processes first, then architecture and prototype, followed by implementation, migration, acceptance and staged rollout. Interfaces are not approved against sample data, and integrations are complete only after failure and recovery paths have been tested.

These risks need explicit controls in discovery, testing and monitoring. Before implementation, each one receives an owner, evidence requirement and fallback path.

SaaS lock-in becomes visible only when data or processes need to move.

Custom builds underestimate operations, security and staff turnover.

Feature lists hide the difference between essential process and habit.

We prefer standard products for interchangeable processes and custom development only where the process demonstrably differentiates. A hybrid answer is usually better than an ideological either-or.

We connect commerce decisions with SEO, data quality, analytics and operations. A solution is not complete when the happy path works. It must be discoverable, measurable, accessible, translatable and understandable to the team after the project.

We also document when the standard is the better decision. Not every requirement deserves custom software, not every data flow needs real-time processing, and not every historical exception should be carried into the target architecture.

Acceptance measures are set before implementation and tested with real data. Functional tests alone are insufficient: completeness, speed, fault tolerance and the team's ability to recognise and classify exceptions are what matter.