Case study · Not documented
Tokyo Seta
The project moved well beyond Shopify theme work into the backend systems that actually run the business.
- Shopify
- Shopify APIs
- Node.js
- Database
- Discipline
- Custom Shopify app · Backend APIs · Database workflows
- Year
- Not documented
- Engagement
- Fixed scope
- Status
- Live

01Context
- Build custom Shopify functionality beyond theme limitations.
- Implement backend APIs and persistent data workflows.
- Deliver production-ready behavior with limited handholding from the client.
Tokyo Seta required functionality that could not be delivered through Liquid customization and off-the-shelf apps alone.
The engagement involved backend APIs, database-backed features, and custom Shopify application logic with detailed business requirements.
HeapByte handled both Shopify-facing implementation and the server-side systems supporting it.
02What was in the way
- 01
Cross-layer development
Storefront, Shopify APIs, backend services, and database logic all needed to work as one system.
- 02
Custom business requirements
Features could not simply be mapped to an existing Shopify app.
- 03
Implementation precision
The client expected complex behavior to be interpreted and delivered with minimal instruction.
03Architecture
What we built, and what we deliberately left alone.
- 01
Custom application layer
Business logic lives in an application rather than being forced into theme code.
- 02
API-driven Shopify integration
Shopify remains the commerce platform while server-side services manage additional workflows.
- 03
Persistent database
Non-Shopify application state is stored separately where appropriate.
Delivery
- Requirements mapping
- Backend architecture
- Shopify integration
- Feature development
- Production refinement
04Outcome
- Development layers
- Frontend + backend + database
- Custom logic
- Application-level
- Client response
- Strong testimonial
Full-stack implementation
Beyond standard Shopify theme capabilities
Praised execution with minimal instruction
“This man might be the best Website Developer on all of Upwork… Tokyo Seta required backend APIs, database work, custom Shopify app features, and extreme attention to detail. He nailed them all with minimal instruction.”
05Engineering notes
- API layer
- Custom services mediate between Shopify commerce data and application-specific business logic.
- Persistent state
- Database-backed features retain information that does not naturally belong in Shopify products or customers.
- Shopify integration
- Application behavior communicates through Shopify APIs rather than brittle storefront scraping.
- Production engineering
- The project combined UI behavior, API logic, and database consistency rather than isolated feature snippets.
What we took from it
- 01Shopify projects increasingly require traditional software engineering.
- 02Custom application state should not be shoehorned into theme settings.
- 03Backend ownership reduces dependence on combinations of third-party apps.
- 04Clear domain modeling matters more as Shopify customization becomes operational software.
Disciplines applied
Next case study
Online Stone Solutions
We developed custom Shopify shipping and rate-calculation logic for product and business rules that standard Shopify shipping configuration could not represent cleanly.
Similar problem?
We will tell you whether this approach fits.
Every store is different. Send us yours and we will say what we would actually do — including when the answer is less work, not more.