Sixlinked

Demos / Order run

Sixlinked demoAutomation and IT

An order entered once. Seven steps follow, or it stops for a person.

A workflow for a wholesaler's trade orders. Each order from the website is taken through stock, the account check, the picking slip, the carrier booking, the invoice and the customer notice with nobody retyping it. A failed step is tried again. An order that needs a decision stops and waits for operations.

Made-up business
Harbour Lane Provisions
Staff in the film
Ben Castell, Operations
Recorded
21 November 2026
The 33 second film, 0:33

What we measured.

267 of 270orders with nothing to decide finished start to finish with nobody retyping
57 of 60runs that hit an injected carrier or accounts fault recovered on their own
0 of 300orders were booked or invoiced twice, counted in the carrier and accounts tables. With the guards switched off, it happened to 23 of 300
30 of 30orders that needed a decision were held for a person
0 of 30held orders went through without a person pressing a choice
0 of 154runs in flight were lost when the worker was killed and restarted, 3 times

Where it missed.

3 orders did not finish on their own: HL-24102, HL-24308 and HL-24339. Each was planned to finish untouched but met a carrier outage we planned to outlast all four tries. Each stopped, waited for a person to press Try again, and then finished. They are the 3 missing from 267 of 270 and from 57 of 60.

These figures are from the third scored run. The first two each found a bug: stock reserved twice for one order, and a crash when four threads drew picking slip images at once. Both were fixed and the whole plan of 300 orders was run again.

What it does not show

  • No AI model is used. This demo is plain code.
  • The website, carrier and accounts system are local stand-ins written for this test, not n8n, Zapier, Make, Power Automate or a live system.
  • Faults were injected on a seeded plan; real outages are less tidy.
  • One machine, one scored run (after two earlier runs that found bugs, reported in the README). Orders, customers and addresses are invented sample data.

What staff see.

Screens from the recording. Scroll sideways, or use the arrow keys.

  1. The Order run board with three orders, each with a track of seven steps. One is done, one is raising its invoice, and one is waiting to try the carrier again after it did not answer.
    1The carrier does not answer. The run tries again by itself.
  2. The run board with four orders. Three are done. The order for The Little Pantry has stopped at the stock step and is marked Needs Ben, out of stock.
    2An item is out of stock. The run stops and waits for Ben.
  3. The Needs Ben screen. Order HL-24129 for The Little Pantry asked for 10 Cold brew concentrate 1L and 4 are on the shelf. Two buttons: Substitute Chai concentrate 1L, and Cancel order.
    3Ben reads why and presses one control.
  4. The run board with eight orders. Seven are done, including The Little Pantry marked Ben decided. One is waiting to try the accounts system again.
    4The run carries on from the same step.
  5. The detail of one finished run: seven steps listed with what each did, the picking slip as a document, and the delivery booking, invoice and confirmation references.
    5Every finished run keeps its picking slip and references.

How it was built and tested.

  1. Each order becomes a run of seven durable steps kept in Postgres. A separate worker process claims runs with a short lease, so a killed worker's runs carry on from the step they were on.
  2. Every step has an idempotency key. Technical failures (time-out, 500, a reply lost after the request was accepted) are retried with doubling waits, four tries in all. Business exceptions (out of stock, credit hold, outside the delivery zones) are never retried: the run stops at Needs Ben with the reason and the choices.
  3. A frozen plan of 300 invented orders (30 webhooks delivered twice, injected faults on 60 runs, the worker killed 3 times, 30 business exceptions) was committed before scoring. Figures are counted from the carrier and accounts stand-ins' own tables, the database and the outbox folder.
  4. Two earlier scored runs exposed two bugs (a double stock reservation, and a crash when four threads rendered slip images at once). Both were fixed and the whole plan was re-run; all three runs are reported in the README.

About this recording

The film shows the recorded session at its real speed with a camera that zooms and a results card made from results.json. Ben's presses were scripted; every step, retry, hold, booking, invoice and slip is what the software did in that run. Stand-in replies were slowed to about half a second so the steps can be seen.

Recorded
21 November 2026
Model
None. This demo is plain code.
Real time of the session
33 seconds over 8 steps

Talk about a job like thisAbout this job

Let's talk

Want an Automation and IT job like this?

Tell us what the work is today, who does it, and who should decide when something is doubtful.

You will get a reply by email from Matthew, the engineer who would do the work.

Your enquiry goes straight to our inbox. We use your details only to reply to you. Privacy

Send an enquiry

Sending an enquiry needs JavaScript. You can also email hello@sixlinked.com.