A white-label integration portal for every client you serve.
Build each integration once as a template, install it for every client, and let clients see their own runs and exceptions inside your product.
The problem
A fork of the same integration for every client.
3PLs, agencies, and logistics platforms rebuild the same order sync for each new client, with small differences nobody wrote down. When something breaks, the client emails to ask whether their orders came through, and someone digs through logs to answer.
At month end, usage per client lives in a spreadsheet, if anywhere. The integration is part of what the client pays for, but it is invisible to them and expensive to you.
How it works in Flows
Embedded iPaaS for 3PLs, in six parts.
Each client gets a real flow of their own, with their own connections and run history, while you keep one template to maintain.
- TemplateBuild the integration once
Publish a flow as a template and declare the settings each install needs as a JSON Schema, such as a carrier or a warehouse code. The install form is generated from that schema.
- InstallInstall it for each client
Install the template against the client's own connection, such as their store or WMS bridge. Params are checked at install, and the flow is fixed to that client from the moment it is created.
- IsolationKeep every client in its lane
A client flow touches only that client's connections, checked at publish, when a trigger matches, and again at every step. Order lookups, rate shops, label purchases, and claims fail on any record that is not the client's.
- Client pagesShow clients their own runs
Through the Orderly embed, each client sees their own flows, runs, and exceptions inside your product, under your brand. Where you allow it, they retry or ignore a failure themselves.
- Endpoint keysGive each client an endpoint
Publish an endpoint per client and issue keys that work only on that client's endpoint. If you turn it on, clients issue their own keys from their pages.
- MeteringBill what each client used
Runs and endpoint requests are counted per client, and the clients view shows each one's active flows, runs this period, and open exceptions.
When something goes wrong
Client failures your team and the client can both see.
A failed run opens an exception with the reason attached, visible to your team and, on the client's pages, to that client. Your alert channels hear about it by email, Slack, or signed webhook, and either side can retry from the failed step if you allowed it. One client's failing flow never touches another client's runs. The reliability page covers exceptions and alerts.
Where it fits
What 3PLs package first.
The usual first template is store order intake, as in the Shopify 3PL integration, followed by an endpoint clients call for rates and tracking, as in the unified shipping API. The partners page shows the template, install, and client page in detail. Read the partner docs ↗
Questions
White-label integration portal FAQ.
Do clients see or edit our flow definitions?
No. Clients see their own flows, runs, exceptions, and step results, and can take the actions you allowed at install, such as retrying a failure or starting a run. They never see or edit flow definitions and cannot create flows, so the integration stays your product.
Can we bill each client for their integration usage?
Yes. Runs and endpoint requests are metered per client, so usage passes straight through to your invoices without a reporting job. The Runs and Flows lists also filter by client when you need the detail behind a number.
How do we roll out a change to every client?
Publish the template again and its version goes up. Installed flows keep running their own copy and show that an update is available, and you choose when each client moves: upgrading checks that client's params against the new schema before it replaces the flow's draft.
Is the white-label portal an add-on?
No. Partner templates, white-label client pages, and per-client metering are included with Flows Pro and Flows Dedicated. Flows Launch covers your own integrations, without client templates or client pages.
Build it once
Run one integration for every client, under your brand.
Tell us the integration every new client needs and how you bill for it today. We will show you the template, the install, and the page your client sees.