Platform Admin & Reseller Ops Console
The Platform Admin Console runs Qubere itself: tenancy, audit, data health, AI cost and onboarding. The Reseller Ops Console lets a partner provision, brand, bill, and support their own customers — without ever touching Qubere's internals or another reseller's data.
The problem
What platform teams and reselling partners will tell you today:
"When support looks at a customer's account, is that logged anywhere? Can I prove no one just poked around?"
Unaudited vendor access
"We don't actually know which of our data feeds are real and which are quietly stubbed out until a customer hits the gap."
Silent fabrication risk
"Our reseller wants to sell this under their own name, provision accounts themselves, and see their own margin — without opening a ticket with us every time."
No self-serve reseller layer
"An onboarding stalls on a KYB step or a bond, and nobody notices until the customer calls angry."
Invisible ops queues
How Qubere addresses it
Audit, platform RBAC & impersonation
Platform staff roles are enforced by a real permission catalogue, not an environment flag. When support needs to see a customer's workspace, it's a logged, time-boxed impersonation session — never a silent login-as.
| Time | Action | Entity | Actor |
|---|---|---|---|
| 12:42:03 | IMPERSONATION_START | ACC-Target | M. Okafor |
| 12:44:17 | SHIPMENT_VIEW | SHP-2026-000162 | M. Okafor (as Joe) |
Data registry & HTS release lifecycle
Every reference dataset the platform depends on — tariffs, sanctions lists, PGA rules — has one honest status. An un-wired source returns a typed error at request time. It never quietly fabricates a result.
| Dataset | Status | Rows | Last refresh |
|---|---|---|---|
| HTSUS Tariff Schedule | LIVE | 19,204 | 2026-08-26 |
| OFAC SDN + Consolidated | LIVE | ~20,000 | 2026-09-22 |
| PGA Requirements by HTS | LIVE | — | — |
| USITC Trade Remedy (AD/CVD Orders) | NOT_YET_IMPLEMENTED | — | — |
Requesting a NOT_YET_IMPLEMENTED capability returns a typed error, not a fabricated value.
AI operations & model governance
Every AI call the platform makes is metered, attributable, and pinnable. Quota, cost, and grounding-abstention rate are queried from real usage records, not estimated.
Onboarding pipeline & cron control plane
Customer onboarding is a stage-gated project: KYB, legal-entity screening, CBP Form 5106, Customs Power of Attorney, continuous bond, platform configuration, sign-offs, then live activation. And the scheduled jobs that keep reference data fresh are visible and re-triggerable, not a black box.
| Job | Category | Last success | |
|---|---|---|---|
| HTS refresh | Data | 2026-09-22 03:00 | |
| RPS sync | Data | 2026-09-23 06:00 |
Multi-tenant provisioning & plan templates
A reseller provisions customer accounts on demand, each a fully isolated workspace. Plan templates bundle product entitlements and feature flags into a sellable tier, so onboarding a new customer is a form, not an engagement.
| Account | Plan | Onboarding | Open tickets |
|---|---|---|---|
| Northline Imports | Professional | Live | 0 |
| Cascade Freight Co | Enterprise | Onboarding | 2 |
Revenue attribution & billing exceptions
Every operational action across every managed account emits a rated usage record against that account's rate card. The reseller sees accrued charges, unbilled charges, and outstanding AR rolled up — and gets flagged when work happened with no matching charge.
Ops queue, alerts & team workload
Alerts are materialized from real data — onboarding blockers, SLA breaches and at-risk tickets, integration failures, billing exceptions, and inactive accounts — not a synthetic health score. Each is assignable and moves through a real status lifecycle.
| Alert | Category | Account | Status |
|---|---|---|---|
| Bond declined | onboarding_blocker | Cascade Freight Co | OPEN |
| Ticket TCK-4471 due in 2h | sla_at_risk | Northline Imports | ACKNOWLEDGED |
White-label branding & product-access licensing
A reseller can rebrand the entire console and every customer email — product name, logo, colors, from-name and support address — and can only ever grant access to the products Qubere has actually licensed to them.
| Account | Customs | TMS | Compliance | Billing |
|---|---|---|---|---|
| Northline Imports | ON | not licensed | ON | ON |
"TMS" is greyed out because Qubere hasn't licensed it to this reseller — enforced server-side on every toggle, not a UI hint.
Objection handling
| "Can your staff see our data without us knowing?" | Only through a typed-reason, time-boxed, banner'd impersonation session — killable instantly, and every action inside it is audit-logged the same as any other action. |
| "If we resell this, can our customers tell it's Qubere underneath?" | Not unless you want them to. Product name, logo, colors, and every customer-facing email address are reseller-branded across the console and outbound email. |
| "Can one reseller see another reseller's accounts or data?" | No. Every account is tagged to exactly one owning reseller, and access is enforced at the query layer — not a filter that a bug could bypass. |
| "How do we know a data feed you show us is actually real?" | The Data Registry names every dataset's real status. A NOT_YET_IMPLEMENTED capability returns a typed error, never a guessed number dressed up as data. |
The close
Immutable audit, honest data status, and real tenant isolation aren't just customer-facing promises — they're how Qubere runs its own operations, and how a reseller runs theirs on top of it.
Next step: open a live Impersonation session, show the audit trail it produces, then provision a reseller test account end to end — branded, licensed, and billed — in the same meeting.