Typed flow templates
Declare the settings each install needs as a JSON Schema, such as a carrier or a warehouse code. The install form is generated from it, and params are checked at install and again at every upgrade.
White-label integrations for every client you serve.
Package a flow as a template with typed params, install it for each client, and run every copy under your brand, metered per client.
How it fits together
Embedded iPaaS for 3PLs, agencies, and platforms.
It replaces maintaining a fork of the same integration for every customer. Each install touches only that client's connections, shipments, and inventory. Clients see their own flows, runs, and exceptions on white-label pages inside your product, and every run is metered per client, so usage passes straight through to your invoices.
Template · Order sync v3
carrierenum · requiredwarehouse_codestring · requirednotify_urluri · optional
Installed for
- Client A
fedex · WH-EASTv3 - Client B
ups · WH-WESTv3 - Client C
usps · WH-EASTv2 · upgrade
Your brandClient A
- Order synccompleted
- Tracking updatewaiting
- Order syncfailed · Retry
Metered per client · this month
- Client Aruns
- Client Bruns
- Client Cruns
Templates
Integration templates with typed params and versioned upgrades.
Upgrades on your schedule
Each publish raises the template version. Installed flows keep running their own copy, and you choose when each client moves to the new version.
The client's own connections
A template that listens for order or shipment events is installed against the client's own bridge, never your organization's, so each copy hears only that client's events.
Client pages
White-label client pages inside your product.
Their flows, runs, and exceptions
Through the Orderly embed, clients see their own flows, runs, and exceptions inside your product, with each run's input, output, and step results.
Self-service where you allow it
Clients can retry or ignore a failure, start the runs you allowed at install, and, if you turn it on, issue their own endpoint keys.
Definitions stay yours
Clients never see or edit flow definitions and cannot create flows. The integration remains your product.
Client-scoped data
Client isolation enforced at every layer.
A client flow touches only that client's connections, checked at publish, when a trigger matches, and again at every step. Every query is scoped to your organization, and endpoint keys issued for a client work only on that client's endpoints.
- At publish. A client flow that uses a bridge belonging to anyone else is refused.
- When a trigger matches. Only the client's own events can start the client's flows.
- At every step. Order lookups, rate shops, label purchases, and claims fail on any record that is not the client's.
- In the client pages. Every list and action is filtered to the signed-in client. Another client's run simply does not exist to them.
Metering
Per-client metering you can bill through.
Runs and endpoint requests are counted per client, so you can bill usage through without building a reporting job. The clients view shows each client's active flows, runs this period, and open exceptions, and the Runs and Flows lists filter by client.
Agencies and platforms
Partner-managed client onboarding
Package your standard integration as a template with typed params, such as a carrier and a warehouse code, and install it for each new client. Every install runs in that client's lane, appears on their pages under your brand, and is metered per client.
template v3params checkedinstall per clientmetered per client
Partner features are included with Flows Pro and Dedicated; see Flows pricing. Read the partner docs ↗
Questions
White-label integrations FAQ.
Can one client see another client's flows or data?
No. A client flow touches only that client's connections, checked at publish, when a trigger matches, and again at every step. In the white-label pages every list and action is filtered to the signed-in client, and an endpoint key issued for one client cannot be used on another client's endpoint.
How do template upgrades reach our clients?
Publishing a template creates a new version, and flows installed from an older version show that an update is available. Upgrading checks the client's params against the current schema and replaces the flow's draft; the client keeps running the published version until you publish again.
Which plans include partner features?
Partner templates, white-label client pages, and per-client metering are included with Flows Pro and Flows Dedicated, as are X12 EDI and trading partner connections. Flows Launch covers your own integrations.
Build it once
Stop maintaining a fork of the same integration for every client.
Tell us the integration every new client needs. We will show you the template, the install, and the page your client sees.