POS systems, delivery apps, card processors and suppliers each tell you part of the story. SpanFlow puts it together per branch, every night, and flags what doesn’t add up.
Each manager prints the POS report, logs into two or three delivery portals and the processor, and types totals into a sheet.
Cash and card variances are caught the night they happen, per location, not at month end.
See it working: Restaurant nightly close (POS vs card settlement)
Invoices arrive as files and PDFs; someone re-types them and checks prices by eye.
Each invoice line is matched to the agreed price list. Only the exceptions reach a person.
See it working: Supplier invoice against the contract price
A price change means editing the POS, then each delivery app, then the website — and something is always missed.
Change it once. It is validated, then delivered to every channel; anything invalid is quarantined.
See it working: One menu change, pushed to every channel
Runnable today — create them in your workspace and press run.
The smallest useful notification: read something, email somebody about it, attach it. The email node is a side channel — the payload passes…
Messaging channels, identities and campaigns, walkable without an appThe E26 channel end to end with no messaging account and nothing running but this API. An `echochat` connection is a loopback app: outbound…
Per-location totals joined to settlement, variances emailedWhat every area manager does by hand after service: take the POS sales for each location, take what the card processor actually settled, and find…
File in, cleansed, joined to a price list, exceptions emailedA supplier's invoice arrives as a file, the way it actually does. It is written to SFTP, read back, cleansed — quantities and prices arrive from a…
Validate once, deliver to two channels, quarantine the restA 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…
Rendered documentsA landscape certificate for everyone who completed a course, rendered as a PNG image. This time the fan-out is the graph's: a foreach node runs…
Start free with three projects, or talk to us about running it across your organisation.