HyperBridge Platformhyperbridge.digital ↗
QuantumOS
Book a demo
QuantumOS Route · Partner

Invite, onboard and revoke retailers and dealers

An admin tool to invite, onboard, suspend and revoke retailers and dealers. There is no partner-facing app yet.

4 lifecycle states
invited to revoked
4 product-access levels
none, all products, categories or SKUs
Written reasons
required to suspend, reinstate or revoke
About

What QuantumOS Partner is

Partner is the thinnest of the six modules, and this page describes it at that size. What exists is an admin workspace with two tabs, Overview and Partners, that manages a retailer or dealer relationship from start to end: an invitation with agreement terms and a product-access scope, an admin recording acceptance, and later suspension or revocation. The tagline, "One app for every retailer relationship", describes the direction. The partner-facing app, the portal and the multi-seller basket are planned only.

At a glance

What is available and what is not

3 capabilities: 1 available, 0 built and tested, 2 on the roadmap.

  • Available

    In production and usable in the QuantumOS admin workspace by customers who have the module.

  • Built and tested

    Built and tested, but not yet a finished feature. It may not be in production on its own, or may have no workspace screen yet. The description says which.

  • Roadmap

    Planned only. Nothing runs yet.

Capabilities

What Partner actually does

Each entry says where to find it in the product. Where a capability stops short of what its name suggests, the detail says so.

01

Partner lifecycle administration

Available

Invite a retailer or dealer, record acceptance of an agreement, set product access, suspend or revoke.

Inviting a partner adds the retailer or dealer to your channel network and creates a partner record with contact details, agreement terms (version, payment terms in days, credit limit) and a product-access scope, and issues an invitation token. There is no partner-facing portal yet, so an admin records acceptance. That is allowed only from the invited state and only for the agreement version the partner holds. Once accepted, the agreement cannot be changed; the API can set a new version only on an agreement that has not been accepted, and the workspace form does not offer that. Suspension can be reversed; revocation is final and clears the product access. Suspend, reinstate and revoke each need a written reason, and every change goes into the audit trail.

  • Lifecycle states: invited, onboarded, suspended, revoked
  • Product-access levels: none, all products, categories, SKUs
  • Suspend, reinstate and revoke each require a written reason of at least three characters
  • The invitation token is generated, but the module does not email it; an admin can reveal it in the workspace
  • The access level is stored and shown, but nothing enforces it yet because partners cannot order yet

Where to find it: Partner workspace, Partners tab

02

Multi-seller basket

Roadmap

A basket across several sellers that splits into separate orders, invoices and settlements for each seller is planned only.

The plan includes a way for sellers to share a basket and a rule that no business can read another's data. Nothing runs yet.

  • Planned only
  • The design allows no reading of another business's data
03

Partner self-service

Roadmap

Catalogue, orders, statements, credit notes, returns and notifications for the partner are planned only.

This would reuse the B2B portal workflows where they exist. The partner mobile app and the portal are not built.

  • Planned only
  • Partner mobile app and portal: not built
Workflows

How the work moves

Partner lifecycle

The steps the system allows.

  1. 01Invite — adds the retailer or dealer to the network and creates the partner record in the invited state
  2. 02Onboard — an admin records acceptance of the agreement version the partner holds
  3. 03Suspend — can be reversed, with a reason
  4. 04Reinstate — back to onboarded, with a reason
  5. 05Revoke — final, allowed from any state except revoked, clears product access
Connections

How it connects to the other modules

These are the hand-offs that work today. They are optional, so you can use one module without the others.

Partners are Channel members

A partner is a retailer or dealer in the network with a lifecycle record, so it appears in Channel.

Credit terms are recorded, not applied

The agreement stores payment terms and a credit limit. Channel credit limits are set separately in Purchases.

Boundaries

What is not built, and where it stops

Roadmap

Not built yet

  • A partner-facing app or portal, and any way for a partner to use the invitation token
  • Sending the invitation by email or message
  • Enforcing the product-access level when a partner orders
  • The partner mobile app
Limits

Worth knowing

  • This is an administration tool, not a partner-facing product.
  • One small workspace; treat it as a foundation.