Draft pending review by counsel — not yet in force
Order Authorisation Acknowledgement
Version 2026-10-16.1 · Effective · Not yet reviewed by counsel · Markdown
In short
- Bridge to Brands uses your own dealer logins to stage orders and, where you enable it, submit them to the brand.
- A submitted order is a real purchase order. It is binding and it costs money.
- You set the caps, the confirmation rule and which keys and agents may submit. You are responsible for orders placed with them.
- If we cannot tell whether a submit went through, we do not retry. We check the portal and tell you.
This summary is for convenience. The full text below governs.
You accept this acknowledgement when you first accept the Terms of Service, again when you turn on submitting for a brand, and again when you create an API key that can submit orders. Capitalised words have the meanings in the Terms.
1. What we do with your dealer accounts
1.1 Bridge to Brands signs in to your Dealer Portals with the Portal Credentials you gave us. It reads catalog, availability, prices and order history, and it places orders into your accounts.
1.2 By default an Order is Staged: it sits in the portal as an unsubmitted basket or draft until someone submits it.
1.3 Where you have enabled it for a Brand, and only for Brands whose submit path we have verified on a live account, Bridge to Brands Submits the Order: it presses the portal’s order button for you.
1.4 Orders can be started by your Users in the app, by your software through an API Key, or by AI Agents you connected. All of them act for you.
2. Submitted orders are binding
2.1 A Submitted Order is a purchase order from you to the Brand. The Brand may ship it and invoice you under your dealer terms, including freight, minimums and any cancellation or restocking fees.
2.2 Some portals allow cancellation for a short time after submitting; many do not. Where a Brand allows it, the order shows its cancel window. Otherwise you must contact the Brand.
2.3 RunOps is not a party to the Order and does not pay for, guarantee or cancel it.
3. You control the limits
3.1 You choose, per Brand: stage only, submit with confirmation (a person clicks Confirm in the app for every Order) or submit.
3.2 You set the Caps (units, lines and dollars per Order and per day). Orders over a Cap are refused before anything reaches the portal. Default Caps apply until you change them.
3.3 You decide which API Keys carry the orders:submit scope and which AI Agents you connect. REST and MCP submits also require an explicit confirm: true on each request.
3.4 You are responsible for every Order placed with your sessions, keys, credentials and agents, including Orders an AI Agent placed without a person reviewing them.
4. When the outcome is unknown
4.1 Sometimes a portal times out or answers ambiguously after a submit. We then mark the Order submit unknown.
4.2 We never retry it automatically. We check the portal’s order history several times over the following hour. If we find the Order, it becomes submitted with the Brand’s order number. If we do not, it becomes submit failed and we give you the basket link; a person decides what happens next.
4.3 Until then, treat the Order as possibly placed and do not re-order the same goods through another route.
5. Safety switches
5.1 You can turn submitting off for a Brand or for the whole Account at any time. We can also turn it off for a Brand or an Account; when we do, Orders in progress fall back to Staged.
Change log
| Version | Effective | Change |
|---|---|---|
| 2026-10-16.1 | 2026-10-16 | First engineering draft, pending review by counsel. |