CASE STUDY / 03 · FURNITURE MANUFACTURING · CLIENT BUILD · PRE-LAUNCH

From multi-channel orders to one coordinated operating system.

A post-order operating system built for a custom furniture manufacturer, connecting multi-channel orders with production, customer communication, fulfillment, and exception handling.

n8nShopify · Etsy · SquareGoogle SheetsGmailShipStation
See the real build ↓
Post-order operations architecture: two rails from paid orders to production and from shipments to the customer, with exceptions routed to a person.
System architecture · click image to inspect full size
The challenge

Orders arriving through Shopify, Etsy, and Square can create fragmented data, repetitive updates, and manual coordination across production, customer communication, shipping, and exception handling. I built this system so those moving parts operate as one connected system rather than a collection of separate tasks.

The architecture

The system captures and standardizes incoming orders, creates a centralized production record, coordinates customer updates and fulfillment, and routes exceptions for human review. Automation handles repeatable execution while people remain responsible for decisions that require judgment—creating an operational structure designed to be more consistent, visible, and scalable.

Shopify · Etsy · Square → Production → Communication → Fulfillment → Human Review
The build in n8n

Cropped straight from the editor it was built in. Click any canvas to inspect it full size.

n8n canvas showing the Shopify, Etsy and Square intake lanes with signature verification and routing
01

Three sales channels, verified before anything moves.

Shopify, Etsy and Square each arrive through their own lane. Signatures are verified and each platform gets an immediate response. A cancellation or refund puts the order on hold and holds any unsent emails, without touching the columns the team owns.

n8n canvas showing order claim, production records, estimated ship date and confirmation email states
02

One canonical order, processed exactly once.

Every channel converges on the same path: business rules from a config sheet, validation, then a claim so a repeated event can't be processed twice. Production rows and an estimated ship date are created, and the confirmation email moves through Pending, Sending and Sent. A message left in Sending is flagged for review, never re-sent automatically.

n8n canvas showing the ShipStation shipment rail and the central error handling path
03

Shipments matched to orders; failures routed to people.

ShipStation notifications are matched to the right order, never by customer name, and logged per shipment, including partial and multi-package shipments. Expected failures are tagged where they happen, logged to an errors sheet, and released. Temporary errors retry automatically; business errors go straight to manual review.

n8n canvas showing installation rules and the one-email-per-shipment send states
04

Installation rules decide what the customer hears.

Before a shipping email goes out, installation and hardware rules are applied. Each shipment gets exactly one email, tracked through the same send states as order confirmations.

Stage: Client build · Pre-launch. Built for a custom furniture manufacturer and not yet live. Outcomes represent design objectives rather than measured results.

← PREVIOUS SYSTEM START A CONVERSATION → NEXT SYSTEM →