KT-1048: input
sku: KB-TOTE-S; qty: "2x"; shipTo.postcode: "06420"; zone: Z3.
Studio concept · n8n automation
Kutu
Kutu: an order exception workflow you can run in the browser
A Studio concept for a small online shop. Eight demo orders pass intake, validation, deduplication and a stock check. Orders that cannot ship wait in an exception queue with their reason, and the team gets one summary alert preview. It is a local workflow prototype modelled on an n8n flow, with no live connection.
Studio concept
The brief
Order problems such as a missing postcode, an invalid quantity, a repeated order or an empty shelf usually surface late and one at a time. The concept had to show how an automated flow can stop each case at the right station, keep the reason attached and give the team one clear summary instead of scattered messages.
Our approach
The page is the prototype itself: a warehouse-style conveyor in ink navy and teal with six stations and hazard-striped exception chutes, eight original shipping labels, a step inspector showing the input, rule and output JSON recorded by the state machine, a demo stock table, a run log, an exception queue with retry, demo fix and review actions, and an alert preview built from the current queue. Without JavaScript the page shows the documented result of one full run.
What we made
- Workflow and decision rules
- Working prototype with demonstration data
- Error and retry states
- Execution trace and status tracking
One order, held and retried
Validation hold
reason: invalid_qty; station: validate. The order stays in the exception queue; no stock is reserved.
Correction and retry
After the full batch finishes, choose Fix qty and retry to change "2x" to 2. Validate passes, deduplicate records a new key, stock changes from 4 to 2 and the order reaches Ready.
Workflow beside the trace
Read the workflow
Intake > Validate > Deduplicate > Stock > Ready. Each failed check branches to Exception; Retry resumes at the holding station. A repeated email + SKU + quantity is held as duplicate. A timed-out stock lookup tries twice before entering the queue.
Inspect the recorded payload
Open the demo, run the batch, choose KT-1048 and select Validate. Input, Rule and Output show the recorded state. After correction and retry, inspect Stock for requested: 2, available: 4, availableAfter: 2.
Implementation status
Running: browser JavaScript, in-memory stock table, validation, deduplication, retry and alert preview. Proposed n8n build: Webhook, Code validation, IF branches, Data Table dedupe, HTTP Request stock lookup, Wait/retry and team notification. No n8n workflow or external integrations are running in this concept.