Skip to main content
BuildHow-to· Updated October 30, 2026

How to build and deploy your first flow

When you deploy a flow in Flow Studio, you choose an update policy — inactivity (auto-updates after 3 minutes idle), scheduled (a specific local hour), or force (immediate). Stations then update automatically without any manual steps at each device.

How to build and deploy your first flow

Flow Studio is where you describe the checkout experience you want and turn it into a working point of sale. This guide walks you from a blank chat to a live flow running on your stations.

What you'll need

  • A Final POS account

  • At least one Station set up under Run in Final Manage

  • A rough idea of how you want your checkout to work

Step 1: Open Flow Studio

From Final Manage, open Flow Studio. If this is your first flow, you'll land on a blank chat. If you have existing flows, select New flow from the top of the chat list.

Step 2: Describe your checkout

Type a description of the checkout experience you want. Be as specific as you like — mention your product types, how staff take orders, whether you need modifiers, split payments, or anything else specific to your business.

Flow Studio builds a live preview as you chat. You can keep refining it by sending more messages.

Tip: Use Plan mode if you want Flow Studio to draft an approach for your approval before making any changes. Use Ask mode if you just have a question and don't want anything modified.

Step 3: Test your flow

Switch to the Test view to run your flow through its paces before going live. Flow Studio runs an auto-derived test suite and flags any issues in the Issue inbox. Fix anything that needs attention, then come back to Build mode.

Step 4: Deploy your flow

When you're happy with the flow, click Deploy in the top bar. Flow Studio runs a pre-flight review, then opens the publish modal.

You'll set a version label and choose how your stations receive the update:

Update timing options

Between orders (recommended for most deployments) Stations apply the update automatically after 3 minutes of inactivity. Active sessions are not interrupted — operators see a toast notification with an Update Now button if they want to apply it sooner.

Scheduled Pick a specific hour and the update applies at that time on each station's local clock. Useful for rolling out changes overnight or between shifts.

Force update Pushes the new version to all stations immediately, even if a session is in progress. Because this can interrupt an active sale, you'll need to read and acknowledge a warning before this option becomes available. Use it for urgent fixes only.

Once you confirm, Flow Studio deploys the flow and your stations will update according to the policy you chose.

Step 5: Confirm the update on your stations

On each station, Station Home shows the active flow and its version. After the update applies, the version shown will match the one you just deployed.

If a station was offline when you deployed, it will evaluate the pending update as soon as it reconnects.

Updating your flow later

Every time you make changes and deploy again, you'll go through the same publish modal and choose an update policy. If you deploy multiple builds before a station updates, it will jump straight to the latest version.

You can also switch flow versions manually from Station Home at any time — see How to switch flows and manage shifts from Station Home for details.

Frequently asked questions

Can I roll back to an older version if something goes wrong? Yes — from Station Home, open the version picker next to the active flow and choose a previous version. Automatic rollback on load failure is not currently supported.

What if I want to notify staff before the update applies? The Notify live session option in the publish modal sends a toast notification to active stations so operators know an update is coming and can apply it when convenient.

How many flows can I deploy? Every account supports unlimited deployed flows at no monthly fee.

Step by step

  1. 1

    Describe the flow you want

    On the Flow Studio home ("What will you build?"), describe the checkout experience you want in the prompt box. Optionally choose your hardware, industry, and style, add your logo and colors, or drop in a screenshot as a design reference.

  2. 2

    Click Start

    Select Start. Flow Studio names your flow and starts building it right away, so clicking Start kicks off the build and there's no separate approval step. You'll see a summary of what Flow Studio is creating (your request plus any branding you added). Prefer to build with your own AI tool? Choose "Connect your own AI (MCP)" instead.

  3. 3

    Watch the live preview

    Flow Studio generates your flow and opens the workspace with a live, interactive preview. It appears as soon as your flow is serving, so you can click through it to try your flow as it takes shape.

  4. 4

    Refine by chatting

    In the composer, stay in Build mode to make changes (it writes and edits the code for you). Switch modes with Shift + Tab: Plan proposes an approach and waits for you to click Approve & Build before it edits anything, and Ask answers questions read-only. Describe what you want and the preview updates.

  5. 5

    Deploy your flow

    When it's ready, click Deploy in the top bar. Flow Studio runs a quick pre-flight review, so you can fix any flagged issues or choose Deploy anyway, then set a version number and an optional changelog (or Draft with AI) and deploy. When it's live you'll see "You're live!"

Frequently asked questions

Do I need to know how to code to build a flow?

No. You describe the checkout experience you want in plain language and Flow Studio creates it. You refine it by chatting, with no coding required.

Why is the Deploy button unavailable?

Deploy turns on once your flow has finished building. Until then it shows "Build your app first" or "Hang tight" while the flow is still generating.

Can I change my flow after Flow Studio creates it?

Yes. Keep chatting in Build mode to change it. Plan mode drafts an approach without touching anything, and Ask mode answers questions read-only.

What happens when I deploy?

Flow Studio runs a pre-flight review of your flow, then you set a version number and an optional changelog. Flow Studio compiles, uploads, and activates it so it goes live on your stations.

Can I undo a change?

Yes. Every change is saved as a restorable checkpoint, and deploys are versioned, so you can roll back to an earlier point.