Skip to content
Retail & e-commerce

Every channel, in step.

Web store, marketplaces, POS and warehouse — each needs the same prices, stock and orders. SpanFlow keeps them in step and gives you the forms and APIs on top.

1

Order intake from several marketplaces

Today

Orders from each marketplace are downloaded and re-entered into the order system.

With SpanFlow

Each marketplace webhook maps into one order format; validate → reserve stock → notify runs as one unit.

  1. 1Marketplace webhooks
  2. 2Map to house format
  3. 3Validate
  4. 4Reserve stock
  5. 5Notify

See it working: Three pipelines run as one unit (sequence)

2

A public order form

Today

Trade customers email orders that someone types in.

With SpanFlow

A hosted order form on your domain calls the order pipeline directly, with the rules checked twice.

  1. 1Customer fills the form
  2. 2Rules checked in the browser
  3. 3Pipeline validates again
  4. 4Order saved

See it working: A public order form (hosted page)

Templates for retail & e-commerce

Runnable today — create them in your workspace and press run.

Webhook trigger

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 —…

PostgreSQL
Sequence of pipelines

Three 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…

PostgreSQLSequence
Published app

One 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…

PostgreSQLPublished app
Per-location totals joined to settlement, variances emailed

Restaurant nightly close (POS vs card settlement)

What every area manager does by hand after service: take the POS sales for each location, take what the card processor actually settled, and find…

PostgreSQLEmail
Validate once, deliver to two channels, quarantine the rest

One menu change, pushed to every channel

A price change edited once and delivered everywhere it has to land. The menu is validated against the group's own rules first — nothing without a…

PostgreSQLAmazon S3Email
A hosted page: a public form in front of a pipeline, with its rules enforced twice

A public order form (hosted page)

A form anyone can open — no account, no API key — that places an order into the demo Postgres. The page is generated from the endpoint's own…

PostgreSQLPublished appFront end
A designed UI: every action kind on one screen, list → detail with a read that sends state, computed totals and a deprecated binding with its successor

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,…

SQLitePublished appFront end6 pipelines
Rendered documents

Invoice from order lines (PDF)

An invoice is a header and a variable number of lines. The query returns one row per line with the invoice's own details and totals alongside…

SQLiteLocal filesRendered documents
Web scraping (webfetch)

Scrape a news page into rows

Reads the demo newspaper's front page and turns each story into a row: its headline, its link made absolute, its date as ISO-8601 and its section.…

HTTP API
Pipeline calling a pipeline (callPipeline)

One pipeline called like a function from others (callPipeline)

Build a job once and call it wherever it is needed. "High-value orders" keeps the orders worth 100 or more and puts the biggest first. The main…

3 pipelines
AI cost control (routing, prompt + response caching)

The same AI workload, before and after routing + caching

Twelve customer reviews, one sentiment label each, run twice over. The baseline sends every review to the connection's big model (gpt-5). The…

PostgreSQLAI model2 pipelines

Stop moving data by hand.

Start free with three projects, or talk to us about running it across your organisation.