An order desk (designed UI)
A front end drawn on the UI designer rather than scaffolded: one screen that loads its orders when it opens, totals them with computed values, takes a new order and refreshes itself, opens an order's detail page by clicking its row (carrying its id, which the detail page sends to load the order), and hands the visitor off to another site. A report page still calls a deprecated endpoint, so Check everything has something to say and the editor offers the one-click swap. Everything lives in a local SQLite file.
Connects to
- SQLite
Also includes
- Published app
- Front end
- 6 pipelines
How you know it worked
Open the desk and press 'Load / reset sample orders': the tiles show 4 orders and their total. Take an order — the list refreshes, the tiles move and the confirmation appears. Click a row and the order page opens: it is handed only the order's id, loads the order itself (a read that sends the id), and 'Mark shipped' sends the same id and reloads it. The Report page shows totals by status. In the admin UI (Apps → Order desk → Pages → Report), press Check everything: it warns that loadTotals calls the deprecated totals-v1 and offers totals; switch totals-v1 off and the report still loads, through its fallback.
Try this templateUsed in: Retail & e-commerce
Related templates
Webhook → database
A pipeline that starts when something posts to it. The webhook's JSON body is the run's starting payload, so the first node already has the data —…
Sequence of pipelinesThree pipelines run as one unit (sequence)
A sequence is orchestration above the run machinery: it runs pipelines you already have, in order, feeding each one's output to the next. This one…
Published appOne app, one URL namespace (published app)
A published app groups things you have already published under a single URL — /apps/demo-shop/v1/… — with its own OpenAPI document. This one binds…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.