See what each role can view and do

One operating system, multiple approved channels

The primary product is shared power bank rental. Channel, store, provider, role and market availability are confirmed per deployment.

Renter journey

Browser H5 and optional apps

Camera or QR entry can open the renter flow in a supported browser. Native renter apps can be prepared for Apple or Google review where included.

Operator workspace

Desktop web, mobile H5 and optional app

Platform, operator, agent, merchant, support and finance roles receive approved functions and data through backend authorization.

Operating depth

Mature workflows adapted for overseas delivery

Long-running, scaled shared power bank SaaS operations in China inform exception handling, reconciliation and revenue-leakage controls, adapted by market and signed scope.

Choose your operating role

The list updates to show the functions normally relevant to that role. Final fields and permissions are enforced by the approved project scope.

Software function list

Start with what the role can see and what it can do. Open the evidence note only when delivery conditions or technical proof are needed.

21 functions shown

01 / 06

Overview & analytics

4

Function	What you can view	What you can do	Delivery scope
Revenue overview Platform ownerAgentMerchantFinance Evidence and delivery conditions Backed by reviewed capability records: FM-10Field dictionary, data freshness and exception ownership FM-14Commission and settlement review fields	Revenue totals, order value and period trends within the assigned data scope.	Filter by date and assigned organization, then review permitted performance reports.	Available by scope
Order overview Platform ownerAgentMerchantOperations & supportFinance Evidence and delivery conditions Backed by reviewed capability records: FM-03Order, station, slot and device event chain FM-10Field dictionary, data freshness and exception ownership	Order counts and completed, processing, failed, returned or refunded states.	Compare selected periods and open the related order list for follow-up.	Available by scope
Device overview Platform ownerAgentMerchantOperations & support Evidence and delivery conditions Backed by reviewed capability records: FM-01Station connectivity and last-seen state FM-02Slot and power-bank inventory state FM-10Field dictionary, data freshness and exception ownership	Assigned stations, connectivity, slot inventory and visible anomaly counts.	Filter the fleet and move from a summary to the affected station or power bank.	Available by scope
Agent and merchant overview Platform ownerAgentOperations & supportFinance Evidence and delivery conditions Backed by reviewed capability records: FM-10Field dictionary, data freshness and exception ownership FM-11Agent-assigned operations scope FM-12Merchant-limited operations view FM-14Commission and settlement review fields	Assigned agent, merchant, station, order and performance summaries.	Drill into an authorized agent or merchant scope without exposing other organizations.	Available by scope

02 / 06

Orders, payments & returns

5

Function	What you can view	What you can do	Delivery scope
Order search and status Platform ownerAgentMerchantOperations & supportFinance Evidence and delivery conditions Backed by reviewed capability records: FM-03Order, station, slot and device event chain FM-08Return recognition, fee stop and order closure FM-09Refund or authorization-release review states	Orders by permitted identifiers, dates, merchants, stations and business status.	Search, filter and open an order within the role’s assigned record scope.	Available by scope
Order detail timeline Platform ownerAgentMerchantOperations & supportFinance Evidence and delivery conditions Backed by reviewed capability records: FM-03Order, station, slot and device event chain FM-07Payment-to-eject exception and idempotency handling FM-08Return recognition, fee stop and order closure	A timestamped chain from scan and payment through dispense, return and closure.	Trace the last confirmed event and route an exception to the responsible team.	Available by scope
Payment and dispense state Platform ownerOperations & supportFinanceRenter Evidence and delivery conditions Backed by reviewed capability records: FM-06Payment authorization or charge handoff FM-07Payment-to-eject exception and idempotency handling	Readable payment, callback, dispense command and station-confirmation states.	Distinguish payment success from physical dispense and follow the approved exception path.	Integration required
Return and order closure Platform ownerAgentMerchantOperations & supportRenter Evidence and delivery conditions Backed by reviewed capability records: FM-08Return recognition, fee stop and order closure	Physical return, recognized return, billing stop and closed-order states as separate events.	Confirm the last recognized return event and investigate delayed closure.	Integration required
Refund and exception handling Platform ownerOperations & supportFinanceRenter Evidence and delivery conditions Backed by reviewed capability records: FM-09Refund or authorization-release review states FM-13Revenue leakage prevention, exception evidence and audit trail	Requested, under review, provider pending, completed or rejected refund states and related exceptions.	Review reason codes, references and ownership, then follow the approved manual or provider workflow.	Integration required

03 / 06

Devices & power banks

5

Function	What you can view	What you can do	Delivery scope
Station connectivity and details Platform ownerAgentMerchantOperations & support Evidence and delivery conditions Backed by reviewed capability records: FM-01Station connectivity and last-seen state	Assigned station identifier, model context, connection or last-known state and last-seen time.	Search the fleet, open a station and identify stale or offline records.	Integration required
Slot and power bank inventory Platform ownerAgentMerchantOperations & support Evidence and delivery conditions Backed by reviewed capability records: FM-02Slot and power-bank inventory state	Available, occupied, rented or visible fault state for slots and power banks.	Locate a slot or power bank and review the freshest source event before service action.	Integration required
Device assignment and deployment scope Platform ownerAgentOperations & support Evidence and delivery conditions Backed by reviewed capability records: FM-11Agent-assigned operations scope FM-12Merchant-limited operations view FM-13Revenue leakage prevention, exception evidence and audit trail	Which stations belong to each authorized agent, merchant or operating organization.	Assign or review device ownership within an approved hierarchy and audit trail.	Confirm for deployment
QR and station context Platform ownerAgentOperations & supportRenter Evidence and delivery conditions Backed by reviewed capability records: FM-04QR station context and browser entry FM-20Public hardware protocol and independent software integration path	The station, market, language and environment context carried by a permitted QR entry.	Generate or validate approved station identifiers and open the correct H5 rental context.	Integration required
Controlled device actions and service follow-up Platform ownerAgentOperations & support Evidence and delivery conditions Backed by reviewed capability records: FM-02Slot and power-bank inventory state FM-07Payment-to-eject exception and idempotency handling FM-13Revenue leakage prevention, exception evidence and audit trail FM-20Public hardware protocol and independent software integration path	Latest device state, command result, anomaly history and affected slot or power bank.	Run approved diagnostics, restart or eject actions when the model and protocol permit, then record follow-up.	Integration required

04 / 06

Agents & merchants

2

Function	What you can view	What you can do	Delivery scope
Merchant operating view Platform ownerAgentMerchantOperations & support Evidence and delivery conditions Backed by reviewed capability records: FM-12Merchant-limited operations view	Only the merchant’s assigned stations, orders, exceptions and agreed report fields.	Review local performance and open support items without viewing other merchants’ records.	Available by scope
Agent hierarchy and assigned scope Platform ownerAgentOperations & supportFinance Evidence and delivery conditions Backed by reviewed capability records: FM-11Agent-assigned operations scope	The agent’s approved merchants, stations, orders, exceptions and report fields.	Operate within assigned records and escalate items requiring platform-level authority.	Available by scope

05 / 06

Finance & controls

2

Function	What you can view	What you can do	Delivery scope
Commission and settlement review Platform ownerAgentMerchantFinance Evidence and delivery conditions Backed by reviewed capability records: FM-14Commission and settlement review fields	Expected and actual amounts, commission basis, period, owner and exception status.	Review differences and follow the approved settlement or correction workflow; this does not promise payout execution.	Confirm for deployment
Exception audit and reconciliation Platform ownerOperations & supportFinance Evidence and delivery conditions Backed by reviewed capability records: FM-07Payment-to-eject exception and idempotency handling FM-09Refund or authorization-release review states FM-13Revenue leakage prevention, exception evidence and audit trail FM-14Commission and settlement review fields	Payment, order, device, refund and settlement references with timestamps and ownership.	Compare linked states, identify the last confirmed event and assign a traceable follow-up.	Integration required

06 / 06

Configuration & delivery

3

Function	What you can view	What you can do	Delivery scope
Pricing, rental rules and support entry Platform ownerAgentMerchantOperations & supportRenter Evidence and delivery conditions Backed by reviewed capability records: FM-05Localized pricing, rental rules and support entry	Approved language, currency, pricing version, rental rules and support channel before confirmation.	Configure permitted market rules and publish the approved renter-facing version.	Confirm for deployment
Roles, records and data permissions Platform ownerOperations & supportFinance Evidence and delivery conditions Backed by reviewed capability records: FM-11Agent-assigned operations scope FM-12Merchant-limited operations view FM-21Desktop web admin, mobile H5 admin and optional admin app	Which menus, fields and assigned records each approved role can access.	Apply the approved role model and verify backend authorization for every role.	Confirm for deployment
Brand, language and operating channels Platform ownerAgentMerchantOperations & supportFinanceRenter Evidence and delivery conditions Backed by reviewed capability records: FM-15Browser H5 scan flow and optional native apps FM-16Selected renter UI and operating-brand configuration FM-17SaaS pilot and separately reviewed private deployment FM-21Desktop web admin, mobile H5 admin and optional admin app	Approved brand, languages and available H5, app or admin channel for the project.	Use the permitted renter or operator channel; platform owners can review scoped branding and localization.	Confirm for deployment

Delivery formats and integration options

These options shape how the operating functions are delivered; they are not extra business modules.

Confirm for deployment

Browser H5 scan flow and optional native apps

Should renters use browser H5 with camera or QR entry, an optional native app, or both?

Owner canonical

Confirm for deployment

Selected renter UI and operating-brand configuration

Which logos, colors, languages, support entries and operator assets can use my brand?

Owner canonical

Confirm for deployment

SaaS pilot and separately reviewed private deployment

Can we begin with SaaS and decide on private deployment after the operating model is proven?

Owner canonical

Confirm for deployment

Market-specific software and operating checklist

Can the software plan be reviewed against the target country's language, provider and operating needs?

Owner canonical

Available by scope

Authorized named deployment references

Which public references can be used to review bounded CoreCharge delivery evidence?

Owner canonical

Integration required

Public hardware protocol and independent software integration path

Can a hardware buyer review a safe protocol and evaluate an independent software integration?

Owner canonical

Confirm for deployment

Desktop web admin, mobile H5 admin and optional admin app

Which operational channel and functions will each platform owner, agent, merchant, support or finance role receive?

Owner canonical

How to read capability status

Documentation, integration, deployment and production acceptance are separate evidence states.

Available by scope

The capability is represented in reviewed CoreCharge owner content, but its fields, roles and configuration must be included in the signed project scope.

Integration required

The result depends on a device, provider, callback, protocol or other external integration and must be validated end to end.

Confirm for deployment

The capability may be planned, but the exact deployment, role, market, language or infrastructure configuration must be confirmed before launch.

Unknown

Current public and local evidence is insufficient for an availability claim. Product-owner evidence is required.

Owner evidence routes

Use the page that owns each buyer question. A public URL is not proof of a specific tenant, provider, store listing or hardware release.