Platform Admin & Reseller Ops Console

Two control planes behind the storefront —
one for Qubere, one for every reseller.

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.

~100+
granular platform permission scopes, not an is_admin flag
60+
reference datasets, each with a real LIVE or NOT_YET_IMPLEMENTED status
0
reseller accounts able to see another reseller's data

The problem

Internal ops and reseller ops both run on spreadsheets and tribal knowledge.

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

Two consoles, one platform, real data underneath both.

  • Platform roles (PLATFORM_ADMIN, CUSTOMER_SUPPORT, BILLING_ADMIN, SECURITY_ADMIN) are a separate system from customer account roles — enforced on every route, not a hardcoded flag.
  • Support access is impersonation, not a backdoor: time-boxed, typed-reason, banner'd, and killable mid-session.
  • Every reference dataset carries a real status — an un-wired source returns a typed error, it never fakes a result.
  • A reseller gets its own console: provisioning, branding, billing, support and audit, scoped to only the accounts it owns.
  • Every action in either console writes an immutable audit entry — searchable, exportable, never silently overwritten.
Platform Admin Console

Audit, platform RBAC & impersonation

"Can your support team just look at our data?" Here's the proof either way.

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.

  • Every mutating action writes an AuditLog row — actor, entity, IP, user-agent, request-id, success/failure — a best-effort write that never blocks the underlying action
  • Impersonation sessions are typed-reason, banner'd on every screen, and can be killed instantly from the console
  • Platform roles gate ~100+ named scopes (admin.accounts.read, admin.audit.write, …) — a support agent's access is exactly what their role lists, nothing implicit
How to demo
Impersonation → start a session with a typed reason, show the persistent banner, then end it from the same screen. Then Audit Logs → filter to that session's actions.
Impersonation
MO
M. Okafor · Support
⚑ Impersonating Target Brokerage — reason: "Cust. request TCK-4471"
StatusACTIVE · started 12:41 · expires 13:11
Audit · this session
TimeActionEntityActor
12:42:03IMPERSONATION_STARTACC-TargetM. Okafor
12:44:17SHIPMENT_VIEWSHP-2026-000162M. Okafor (as Joe)
requestId on every rowbest-effort write · never blocks
Platform Admin Console

Data registry & HTS release lifecycle

"Which of your numbers are actually real?" We'll show you the matrix.

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.

  • 60+ reference datasets tracked with source, row count, and last successful refresh — status is LIVE or NOT_YET_IMPLEMENTED, never assumed
  • HTS tariff releases move DRAFT → human-reviewed → PUBLISHED before any duty math depends on them
  • A NOT_YET_IMPLEMENTED capability fails the request with a named reason, not a guessed number
  • Customs operations are visible too: the CBP Message Flow and Message Flow consoles show inbound queues, quarantined messages and flow timelines, with replay or discard, and ABI Credentials are managed in the console rather than by SQL
How to demo
Data Registry — point at a LIVE row and a NOT_YET_IMPLEMENTED row side by side. "Most vendors won't show you this table at all."
Data Registry
FR
Frank
DatasetStatusRowsLast refresh
HTSUS Tariff ScheduleLIVE19,2042026-08-26
OFAC SDN + ConsolidatedLIVE~20,0002026-09-22
PGA Requirements by HTSLIVE——
USITC Trade Remedy (AD/CVD Orders)NOT_YET_IMPLEMENTED——

Requesting a NOT_YET_IMPLEMENTED capability returns a typed error, not a fabricated value.

Platform Admin Console

AI operations & model governance

"Will your AI blow my budget, and can I see what it's doing?"

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.

  • AI quota and cost tracked per account, client, and model — with configurable cost-alert thresholds
  • Model routing can be pinned per account, client, or user, with durable precedence resolution and a transparent platform-fallback message when a pin isn't honored
  • Grounding abstention rate is tracked explicitly — how often the assistant says "I don't know" instead of guessing
  • Document-processing throughput and SLA are measured against real job completion times, not a marketing number
How to demo
AI Ops & Evals — open an account's quota panel, pin a model override, then show the fallback message that appears if that model isn't available.
AI Ops & Evals
FR
Frank
AI cost, this month
$1,842.60
Grounding abstention
6.2%
Doc SLA (p95)
41s
Model pin · Target Brokerage
Pinned modelgemini-2.5-pro
PrecedenceAccount pin > Client pin > Platform default
Fallback message"Pinned model unavailable; used platform default."
Platform Admin Console

Onboarding pipeline & cron control plane

A $2M deal moving from contract to live isn't tracked in someone's inbox.

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.

  • Onboarding projects track blocking stages and blockers explicitly — nothing silently stuck
  • Cron jobs are categorized (Data, Hygiene, Ops) with last-success timestamp and a manual re-trigger (single jobs or a bulk selection), so a stale HTS refresh or RPS sync is fixable in a click, not a support ticket
How to demo
Onboarding — open a project mid-pipeline, point at the blocking stage. Then Scheduled Jobs — show a job's last-success time and manually re-trigger it.
Scheduled Jobs
FR
Frank
Onboarding · Meridian Components GmbH
KYB compliance  · cleared
CBP Form 5106  · filed
Customs bond  · blocked: surety declined, resubmitting
JobCategoryLast success
HTS refreshData2026-09-22 03:00
RPS syncData2026-09-23 06:00
Reseller Ops Console

Multi-tenant provisioning & plan templates

Sell "Basic," "Professional," "Enterprise" — without a single line of code.

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.

  • New account provisioning picks a plan template; the template's entitlements and feature flags apply automatically
  • Every account is tagged to its owning reseller — tenant isolation is enforced at the query layer, not by convention
  • The account directory surfaces onboarding stage, 90-day shipment volume, open tickets, and billing exceptions in one row
How to demo
Accounts Management → New — pick a plan template, provision, then open the account detail to show onboarding stage and ticket/billing signals already populated.
Accounts Management
RP
Reseller Partner
AccountPlanOnboardingOpen tickets
Northline ImportsProfessionalLive0
Cascade Freight CoEnterpriseOnboarding2
Reseller Ops Console

Revenue attribution & billing exceptions

Margin leaks get flagged before the invoice goes out, not after.

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.

  • Cross-account revenue dashboard: accrued, unbilled, and outstanding AR, filterable to a single account
  • Billing-exceptions view detects manual work recorded with no corresponding usage charge — revenue leakage, surfaced automatically
  • Vendor pass-through bills (surety, drayage, exam fees, warehouse) are visible with match/variance status against customer invoices
How to demo
Revenue — show the rolled-up KPIs, then open Exceptions and point at a flagged unbilled work event. "This is the leak your controller usually finds a quarter late."
Revenue
RP
Reseller Partner
Accrued
$88,240
Unbilled
$6,120
Outstanding AR
$21,900
Open exceptions
3
Billing exceptions
Cascade Freight · document reviewwork recorded, no usage charge
Reseller Ops Console

Ops queue, alerts & team workload

Nobody finds out about a stalled onboarding from an angry phone call.

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 categories: onboarding blocker, SLA breach/at-risk, integration failure, billing exception, inactive account
  • Status workflow: OPEN → ACKNOWLEDGED → SNOOZED → RESOLVED, assignable to a specific team member
  • Team workload is computed fresh from real tables — accounts owned, alerts assigned, tickets assigned — never a guessed capacity number
How to demo
Alerts — assign an SLA-at-risk ticket to a team member. Then Team — show their workload counters update in real time.
Alerts
RP
Reseller Partner
AlertCategoryAccountStatus
Bond declinedonboarding_blockerCascade Freight CoOPEN
Ticket TCK-4471 due in 2hsla_at_riskNorthline ImportsACKNOWLEDGED
Team workload
D. Osei4 accounts · 2 alerts · 1 ticket
Reseller Ops Console

White-label branding & product-access licensing

Your customers see your brand. Qubere is invisible.

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.

  • Branding covers product name, logo, primary/accent color, and email from-name/from-address/support address, applied across the console and customer-facing email
  • Product-access matrix (Customs, TMS, Compliance, Client Portal, Billing) is per account/client, but every toggle is capped server-side by what Qubere has licensed that reseller — an unlicensed product cell is greyed out, not just hidden in the UI
How to demo
Branding — change the product name and logo, show it reflected instantly. Then Product Access — try to enable a product Qubere hasn't licensed and show it's greyed out, not just discouraged.
Product Access
RP
Reseller Partner
AccountCustomsTMSComplianceBilling
Northline ImportsONnot licensedONON

"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

Every hard question, answered directly.

"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

Run the platform with the same discipline you sell to your customers.

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.