SaaS & Infrastructure · Est. $18k – $20k
Larkfield Goods

E-commerce & retail ops

Coralsoft designed, built and shipped this product for the client.

BackendAutomationn8n (self-hosted)DockerPostgres
n8n-ecommerce-order-fulfillment.example / dashboard
Operations dashboard — orders across Shopify and three marketplaces
The situation

What was in place before we started.

Workflow automation on n8n (self-hosted), no LLM agent — deterministic process orchestration that replaced four disconnected order, inventory, fulfillment, and returns processes for a DTC home-goods brand selling across Shopify and three marketplaces.

The client sells through Shopify and three marketplaces simultaneously. Before the project, each channel lived in isolation: operators manually copied Etsy and Walmart orders into Shopify, inventory was reconciled in Google Sheets once a day, and returns were handled through email chains between support, the warehouse, and accounting. As volume grew past 600+ orders/day, the process started breaking down — selling stock that was no longer available, duplicate orders, and refund delays of 5–7 days.

The team had looked at Zapier, but the cost at that trigger volume (600+ orders × 4–6 steps each) blew past budget, and the conditional logic needed (different rules per marketplace) required custom branches that Zapier prices especially steeply.

Constraint

A budget constraint: the client needed something cheaper than Zapier/Make at scale, with full control over the logic and the option to self-host — so customer data never passed through a third-party SaaS.

Estimated Timeline
6 months
Estimated Team
5 people
Estimated Budget
$18k – $20k
Platforms
2
Stack
n8n (self-hosted)DockerPostgresRedisShopify Admin APIAmazon SP-APIEtsy APIWalmart Marketplace APIShippoStripeSlack API
Delivery story

Larkfield Goods: a product foundation built for reliable delivery

01

Challenge

Workflow automation on n8n (self-hosted), no LLM agent — deterministic process orchestration that replaced four disconnected order, inventory, fulfillment, and returns processes for a DTC home-goods brand selling across Shopify and three marketplaces. The main delivery challenge was to give users a maintainable interface and architecture that could absorb new requirements without slowing delivery, while keeping Order ingestion, Inventory sync, and Fulfillment routing consistent across the complete journey. We framed the engagement around the smallest production-worthy flow first, then expanded the scope without weakening the underlying component and data model.

02

How we built it

We first separated the core product rules from external services, then defined typed boundaries for every integration. The team delivered Order ingestion, Inventory sync, and Fulfillment routing as end-to-end flows, adding retries, idempotent operations, validation, and observable failure states before polishing the interface. This kept third-party behaviour from leaking into the product experience and made later integrations easier to add. The implementation was anchored by n8n (self-hosted), Docker, Postgres, and Redis, with shared TypeScript contracts across the frontend and service layer.

03

Delivery

The delivered scope brought Order ingestion, Inventory sync, Fulfillment routing, and Returns & refunds into one coherent production-ready product experience. The reusable component and data patterns leave a clear route for the next product iteration. For Larkfield Goods, the practical result is a product that communicates its value quickly while giving the team a maintainable base for continued delivery in saas & infrastructure.

Challenges

Each constraint, and what we did about it.

Constraint

A budget constraint: the client needed something cheaper than Zapier/Make at scale, with full control over the logic and the option to self-host — so customer data never passed through a third-party SaaS.

What we did

Triggers come from webhooks (Shopify, Amazon SP-API, Etsy, Walmart) plus cron triggers for periodic reconciliation and retries. The orchestration layer is n8n, self-hosted on Docker — 14 production workflows split into reusable sub-workflows for shared logic like order normalization, logging, and error handling. Postgres is the source of truth for orders and inventory, with Redis holding short-lived locks to prevent race conditions during parallel sales.

Results

Measured outcomes.

0
instances of overselling out-of-stock items in the 4 months after launch (down from ~12/week)
<30 sec
inventory sync time across all channels
~70%
savings on automation tooling versus the projected cost of Zapier at this volume
Showcase

How the system fits together.

3 of 3 views
n8n-ecommerce-order-fulfillment.example
Inventory sync — bidirectional stock updates across all channels
n8n-ecommerce-order-fulfillment.example
Returns and RMA flow with an automated refund trigger
n8n-ecommerce-order-fulfillment.example
n8n workflow architecture — triggers, orchestration, and integrations
Roadmap

Estimated delivery sequence.

6 months
Weeks 1–4

Discovery & architecture

Webhook intake from all 4 channels, normalized into a single schema, written to Postgres as the source of truth.

  • Order ingestion
Weeks 5–14

Core build

Bidirectional stock sync: any change on one channel (a sale, a manual adjustment) reflects across the other three plus the Shopify admin in under 30 seconds.

  • Inventory sync
Weeks 15–19

Integrations & data

Automatic order routing between the client's own warehouse and a 3PL partner based on rules (weight, shipping region, stock availability), with shipping labels generated via the Shippo API.

  • Fulfillment routing
Weeks 20–24

Hardening & QA

The customer initiates a return through a form — n8n creates an RMA, notifies the warehouse, and once receipt is confirmed, automatically triggers a refund via Stripe/marketplace APIs and updates the customer's status.

  • Returns & refunds
Weeks 25–26

Launch & handover

A Slack channel notifies an operator only about cases the workflow can't resolve on its own: data conflicts, API failures, negative inventory balances.

  • Exception alerts

More work like this.

Every case study covers a product Coralsoft designed, built, and shipped for a client.