Case Study · Retail & E-Commerce
NRG Alternatives: Out of QuickBooks, Onto Shopify
Neckles IO · Engagement 2026 · Belleville, Ontario
- Client
- NRG Alternatives, lighting retailer, Belleville, Ontario
- Engagement
- E-commerce catalogue migration, QuickBooks to Shopify
- Stack
- Shopify, QuickBooks Online, isolated API gateway, n8n
NRG Alternatives sells lighting. Their product catalogue (every SKU, price, and variant) lived in QuickBooks, where it served accounting well and commerce not at all. Getting a real online store meant getting that catalogue into Shopify, and the obvious paths were both bad: weeks of manual retyping, or a one-shot CSV import that fails halfway through and leaves the store half-populated with no way to tell which half.
A migration built like infrastructure, not a chore
We built the migration as a resumable pipeline. Products move in small batches, and progress is checkpointed after every batch. If anything interrupts the run, it resumes exactly where it stopped rather than starting over or double-creating products. Variants carry their options, prices, SKUs, and compare-at pricing. Collections are created once, remembered, and reused, so re-running the pipeline is safe by design.
That last property, idempotence, is the difference between a script and a tool. The pipeline can run again tomorrow against an updated export and converge on the right answer instead of duplicating the store.
Every API call through an isolated gateway
All writes to the client's store were routed through the same architecture we use on every engagement: a per-client security gateway holding NRG's credentials server-side, scoped to NRG's domains only, with write permissions capped at exactly what the migration needed. The automation never held the keys, and no other client's systems were reachable from the session doing the work.
Demo before build
With the catalogue live, the obvious next question was inventory intelligence: what to reorder, when, from which supplier. Rather than scope a build on speculation, we shipped a private, access-gated concept demo: a supplier-grouped replenishment forecast dashboard with illustrative figures, for the owner to react to before any production tool is commissioned. It cost a fraction of a discovery engagement and answered the same question better.
The outcome
The full catalogue is live on Shopify, migrated once and migrated correctly, on foundations built to support whatever the store needs next.
By the numbers
- • Full product catalogue migrated: products, variants, options, collections
- • Batched and checkpointed: interruptions resume, never restart
- • Idempotent re-runs: safe to execute again without duplicating the store
- • All API writes through an isolated, credential-scoped client gateway
- • Replenishment-forecast concept demo shipped before any production build
Related reading: Your CRM Data Is Dirty Because of How Leads Enter It.
Catalogue trapped in your accounting system?
Tell us where your product data lives today. We will let you know if we can help.
Discuss Your Infrastructure