All elements

Element 07·Foundation·State engine

Workflows you edit, not workflows you escape.

Orders, waves, returns, inbound receipts, onboarding, performance reviews — every long-lived process is a flow on the same engine. States, transitions, guards, side effects. Edit a step in the UI, version it, replay history. When your floor changes, the software changes with it.

Start free for 14 daysWhat's inside

No credit card·Your workspace in three minutes

Element 07 of 23: State engine, symbol Se, group Foundation07FOUNDATIONSeState engineONE OF 23 · ONE DATABASE

fig. 07·underneath all of it

01/What's inside

Three things Advanced State Engine actually does.

Editable flows for orders, waves, returns, onboarding — versioned, replayable.

  1. 01

    Every flow is a graph

    States, transitions, guards (who can advance), side effects (what happens when you do). The same engine runs an order, a wave, a return, an onboarding — drawn the same way, edited the same way.

  2. 02

    Edit in the UI, versioned automatically

    Add a step to your returns flow. Add a guard so only managers can refund over $500. Change the side effect to ping #ops in Slack instead of email. Every change is versioned and signed by the editor.

  3. 03

    Replay, audit, fork

    Replay any flow run to see exactly what happened. Fork a flow to test a change without disrupting live runs. Audit every transition: who, when, why. Sebastien can propose new flows from a description.

02/In practice

A returns flow, drawn the way you edit it.

Received, inspected, a disposition with three outcomes, and a reject lane. Every transition names its trigger — a scan, a decision, a timer — and any of them can carry a guard. Change a step in the interface and the engine versions it for you.

A returns flow — received, inspected, disposition — ending in refunded, restocked or destroyed, with a reject lane for intake rejections and SLA breachesRETURNS · STATES · TRANSITIONS · GUARDSVERSIONED · REPLAYABLEscan · webhookdecide · manualrefund · autorestock · manualdestroy · manualreject at intake · manualSLA breach · timerReceivedInspectedSLA 4HDispositionGUARDEDRefundedRestockedDestroyedRejectedMANUAL · AUTOWEBHOOKTIMEREDIT A STEP · SAVED AS A NEW VERSION · REPLAY ANY RUN

03/Bonds

What Advanced State Engine already knows.

Every element writes to the same database. Advanced State Engine shares its records with Commerce, Integrations + API and Fulfillment, so reports, flows and Sebastien see across all of them — no syncs, no exports, no duplicates.

  1. Cm01
    Commerce
    Catalog, orders, carts, payments.
    Revenue
  2. Ig08
    Integrations + API
    QuickBooks, Stripe, Shopify, API.
    Foundation
  3. Fu16
    Fulfillment
    Inbound, waves, pick · pack · QC, dock.
    Operations

In your workspace·/settings

See it in your workspace

Advanced State Engine·Free for fourteen days

Se.

Fourteen days free. No card. Your workspace in three minutes — switch on Advanced State Engine the moment you're in, and the other 22 elements stay out of the way until you need them.

Start freeSee pricing
Relmz.

One system for realizing a vision.

Commerce · CRM · Telephony · CMS · Scheduling · Fulfillment · Projects · HR

Product
  • Why Relmz
  • Features
  • Solutions
  • Pricing
  • Samples
  • What's new
Resources
  • Blog
  • Changelog
  • Contact
Company
  • About
  • Talk to sales
Legal
  • Terms
  • Privacy
  • DPA
  • Security
  • Cookies
© 2026 RelmzBuilt for a team of one and a company of a thousand.
Relmz.
  • Why
  • Features
  • Solutions
  • Pricing
  • Samples
Sign inStart free trial
Menu
  • Why
  • Features
  • Solutions
  • Pricing
  • Samples
  • Sign in