{ "schema_version": "1.0.0", "title": "See what each role can view and do", "canonical_url": "https://corecharge.cloud/en/software/features/", "language": "en", "last_reviewed": "2026-08-25", "product_scope": { "primary_product": "Shared power-bank rental software", "primary_audience": "Shared power-bank operators, agents, merchants, support, finance reviewers, local brand teams and buyer engineering teams", "public_positioning": "Developed through long-running, scaled shared-power-bank SaaS operations in China and adapted by market, provider, role and signed scope.", "secondary_extensibility_note": "Selected workflows may be adapted for charging cables, vending or other compatible hardware by signed scope. These are secondary extensions, not equal-weight product groups and not universal compatibility claims." }, "status_vocabulary": { "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." }, "role_catalog": [ { "id": "all", "label": "All roles" }, { "id": "platform_owner", "label": "Platform owner" }, { "id": "agent", "label": "Agent" }, { "id": "merchant", "label": "Merchant" }, { "id": "ops_support", "label": "Operations & support" }, { "id": "finance", "label": "Finance" }, { "id": "renter", "label": "Renter" } ], "role_functions": [ { "id": "FC-01", "module": "Overview & analytics", "roles": [ "Platform owner", "Agent", "Merchant", "Finance" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-10", "FM-14" ], "name": "Revenue overview", "view": "Revenue totals, order value and period trends within the assigned data scope.", "action": "Filter by date and assigned organization, then review permitted performance reports." }, { "id": "FC-02", "module": "Overview & analytics", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support", "Finance" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-03", "FM-10" ], "name": "Order overview", "view": "Order counts and completed, processing, failed, returned or refunded states.", "action": "Compare selected periods and open the related order list for follow-up." }, { "id": "FC-03", "module": "Overview & analytics", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-01", "FM-02", "FM-10" ], "name": "Device overview", "view": "Assigned stations, connectivity, slot inventory and visible anomaly counts.", "action": "Filter the fleet and move from a summary to the affected station or power bank." }, { "id": "FC-04", "module": "Overview & analytics", "roles": [ "Platform owner", "Agent", "Operations & support", "Finance" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-10", "FM-11", "FM-12", "FM-14" ], "name": "Agent and merchant overview", "view": "Assigned agent, merchant, station, order and performance summaries.", "action": "Drill into an authorized agent or merchant scope without exposing other organizations." }, { "id": "FC-05", "module": "Orders, payments & returns", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support", "Finance" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-03", "FM-08", "FM-09" ], "name": "Order search and status", "view": "Orders by permitted identifiers, dates, merchants, stations and business status.", "action": "Search, filter and open an order within the role’s assigned record scope." }, { "id": "FC-06", "module": "Orders, payments & returns", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support", "Finance" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-03", "FM-07", "FM-08" ], "name": "Order detail timeline", "view": "A timestamped chain from scan and payment through dispense, return and closure.", "action": "Trace the last confirmed event and route an exception to the responsible team." }, { "id": "FC-07", "module": "Orders, payments & returns", "roles": [ "Platform owner", "Operations & support", "Finance", "Renter" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-06", "FM-07" ], "name": "Payment and dispense state", "view": "Readable payment, callback, dispense command and station-confirmation states.", "action": "Distinguish payment success from physical dispense and follow the approved exception path." }, { "id": "FC-08", "module": "Orders, payments & returns", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support", "Renter" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-08" ], "name": "Return and order closure", "view": "Physical return, recognized return, billing stop and closed-order states as separate events.", "action": "Confirm the last recognized return event and investigate delayed closure." }, { "id": "FC-09", "module": "Orders, payments & returns", "roles": [ "Platform owner", "Operations & support", "Finance", "Renter" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-09", "FM-13" ], "name": "Refund and exception handling", "view": "Requested, under review, provider pending, completed or rejected refund states and related exceptions.", "action": "Review reason codes, references and ownership, then follow the approved manual or provider workflow." }, { "id": "FC-10", "module": "Devices & power banks", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-01" ], "name": "Station connectivity and details", "view": "Assigned station identifier, model context, connection or last-known state and last-seen time.", "action": "Search the fleet, open a station and identify stale or offline records." }, { "id": "FC-11", "module": "Devices & power banks", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-02" ], "name": "Slot and power bank inventory", "view": "Available, occupied, rented or visible fault state for slots and power banks.", "action": "Locate a slot or power bank and review the freshest source event before service action." }, { "id": "FC-12", "module": "Devices & power banks", "roles": [ "Platform owner", "Agent", "Operations & support" ], "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_ids": [ "FM-11", "FM-12", "FM-13" ], "name": "Device assignment and deployment scope", "view": "Which stations belong to each authorized agent, merchant or operating organization.", "action": "Assign or review device ownership within an approved hierarchy and audit trail." }, { "id": "FC-13", "module": "Devices & power banks", "roles": [ "Platform owner", "Agent", "Operations & support", "Renter" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-04", "FM-20" ], "name": "QR and station context", "view": "The station, market, language and environment context carried by a permitted QR entry.", "action": "Generate or validate approved station identifiers and open the correct H5 rental context." }, { "id": "FC-14", "module": "Devices & power banks", "roles": [ "Platform owner", "Agent", "Operations & support" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-02", "FM-07", "FM-13", "FM-20" ], "name": "Controlled device actions and service follow-up", "view": "Latest device state, command result, anomaly history and affected slot or power bank.", "action": "Run approved diagnostics, restart or eject actions when the model and protocol permit, then record follow-up." }, { "id": "FC-15", "module": "Agents & merchants", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-12" ], "name": "Merchant operating view", "view": "Only the merchant’s assigned stations, orders, exceptions and agreed report fields.", "action": "Review local performance and open support items without viewing other merchants’ records." }, { "id": "FC-16", "module": "Agents & merchants", "roles": [ "Platform owner", "Agent", "Operations & support", "Finance" ], "scope_status": "AVAILABLE_BY_SCOPE", "capability_ids": [ "FM-11" ], "name": "Agent hierarchy and assigned scope", "view": "The agent’s approved merchants, stations, orders, exceptions and report fields.", "action": "Operate within assigned records and escalate items requiring platform-level authority." }, { "id": "FC-17", "module": "Finance & controls", "roles": [ "Platform owner", "Agent", "Merchant", "Finance" ], "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_ids": [ "FM-14" ], "name": "Commission and settlement review", "view": "Expected and actual amounts, commission basis, period, owner and exception status.", "action": "Review differences and follow the approved settlement or correction workflow; this does not promise payout execution." }, { "id": "FC-18", "module": "Finance & controls", "roles": [ "Platform owner", "Operations & support", "Finance" ], "scope_status": "INTEGRATION_REQUIRED", "capability_ids": [ "FM-07", "FM-09", "FM-13", "FM-14" ], "name": "Exception audit and reconciliation", "view": "Payment, order, device, refund and settlement references with timestamps and ownership.", "action": "Compare linked states, identify the last confirmed event and assign a traceable follow-up." }, { "id": "FC-19", "module": "Configuration & delivery", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support", "Renter" ], "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_ids": [ "FM-05" ], "name": "Pricing, rental rules and support entry", "view": "Approved language, currency, pricing version, rental rules and support channel before confirmation.", "action": "Configure permitted market rules and publish the approved renter-facing version." }, { "id": "FC-20", "module": "Configuration & delivery", "roles": [ "Platform owner", "Operations & support", "Finance" ], "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_ids": [ "FM-11", "FM-12", "FM-21" ], "name": "Roles, records and data permissions", "view": "Which menus, fields and assigned records each approved role can access.", "action": "Apply the approved role model and verify backend authorization for every role." }, { "id": "FC-21", "module": "Configuration & delivery", "roles": [ "Platform owner", "Agent", "Merchant", "Operations & support", "Finance", "Renter" ], "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_ids": [ "FM-15", "FM-16", "FM-17", "FM-21" ], "name": "Brand, language and operating channels", "view": "Approved brand, languages and available H5, app or admin channel for the project.", "action": "Use the permitted renter or operator channel; platform owners can review scoped branding and localization." } ], "owner_routes": [ { "label": "H5 rental platform", "url": "https://corecharge.cloud/en/software/h5-shared-power-bank-rental-platform/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "H5 payment and refund UAT", "url": "https://corecharge.cloud/en/guides/h5-rental-flow-payment-refund-uat/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "Dashboard fields", "url": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "Overseas rental software", "url": "https://corecharge.cloud/en/software/overseas-shared-power-bank-rental-software/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "Singapore market guide", "url": "https://corecharge.cloud/en/markets/singapore/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "UAE market guide", "url": "https://corecharge.cloud/en/markets/united-arab-emirates/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "Malaysia market guide", "url": "https://corecharge.cloud/en/markets/malaysia/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "Verified deployments", "url": "https://corecharge.cloud/en/cases/", "public_state": "PUBLIC_200_SELF_CANONICAL" }, { "label": "Hardware protocol developer center", "url": "https://corecharge.cloud/developers/", "public_state": "PACKAGE_VALIDATED_DEPLOYMENT_PENDING", "release_gate": "Deploy the validated developer center package and verify a public 200 self-canonical response before marking the route live." } ], "capabilities": [ { "id": "FM-01", "module_group": "device-orders", "module": "Device operations", "capability": "Station connectivity and last-seen state", "buyer_question": "Can my operations team tell whether a station is current, stale or offline?", "operator_role": "Operator, agent, field service", "scope_status": "AVAILABLE_BY_SCOPE", "capability_boundary": "Show assigned station identity, connectivity or last-known state, last-seen time, timezone and an explicit stale/offline qualifier. A connectivity label does not prove venue performance or uptime.", "integration_deployment_dependency": "Compatible station protocol, heartbeat or device event, timezone rules, alert ownership and role scope.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" }, { "id": "FM-02", "module_group": "device-orders", "module": "Device operations", "capability": "Slot and power-bank inventory state", "buyer_question": "Can staff see available, occupied and fault states for the station and its power banks?", "operator_role": "Operator, agent, field service", "scope_status": "AVAILABLE_BY_SCOPE", "capability_boundary": "Use masked station, slot and power-bank references with source-event freshness. Battery-health conclusions require agreed telemetry and a test method.", "integration_deployment_dependency": "Model-specific telemetry, slot mapping, identifier masking and inventory-state definitions.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" }, { "id": "FM-03", "module_group": "device-orders", "module": "Orders", "capability": "Order, station, slot and device event chain", "buyer_question": "Can support trace a rental from scan through eject, return and closure?", "operator_role": "Operator, support, finance review", "scope_status": "AVAILABLE_BY_SCOPE", "capability_boundary": "Keep masked order, station, slot and device references plus event timestamps and exception codes. A visible order row does not prove every physical event succeeded.", "integration_deployment_dependency": "Consistent identifiers across renter, order, device and support systems; tested state-transition rules.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/guides/h5-rental-flow-payment-refund-uat/", "last_reviewed": "2026-08-24" }, { "id": "FM-04", "module_group": "renter-flow", "module": "H5 renter flow", "capability": "QR station context and browser entry", "buyer_question": "Can a renter scan a station QR and reach the intended market and station context?", "operator_role": "Renter, operator, support", "scope_status": "INTEGRATION_REQUIRED", "capability_boundary": "An H5 route can provide browser-first scan-to-rent entry. It must preserve station, language and environment context without exposing credentials or unrestricted identifiers.", "integration_deployment_dependency": "QR format, station identity, H5 route, session handling, supported browser and deployment environment.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/software/h5-shared-power-bank-rental-platform/", "last_reviewed": "2026-08-24" }, { "id": "FM-05", "module_group": "renter-flow", "module": "H5 renter flow", "capability": "Localized pricing, rental rules and support entry", "buyer_question": "Can the renter see the correct language, currency, pricing rule and support route before confirmation?", "operator_role": "Renter, operator, support", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "Selected language, currency, rental copy and support entry can be scoped. The page does not establish legal sufficiency, a universal pricing model or payment availability.", "integration_deployment_dependency": "Market, locale, pricing version, rental policy, support owner, legal review and configured payment route.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/guides/h5-rental-flow-payment-refund-uat/", "last_reviewed": "2026-08-24" }, { "id": "FM-06", "module_group": "payments-refunds", "module": "Payments", "capability": "Payment authorization or charge handoff", "buyer_question": "Can the rental flow hand off to the selected provider and record a readable result?", "operator_role": "Renter, support, finance review", "scope_status": "INTEGRATION_REQUIRED", "capability_boundary": "The workflow may store a masked provider reference, business state, amount, currency and callback classification. No provider approval, payment-method availability, settlement or production readiness is claimed.", "integration_deployment_dependency": "Selected provider, merchant onboarding, credentials, callback contract, idempotency, currency and market configuration.", "evidence_status": "PUBLIC_VALIDATION_METHOD_ONLY", "owner_canonical": "https://corecharge.cloud/en/guides/h5-rental-flow-payment-refund-uat/", "last_reviewed": "2026-08-24" }, { "id": "FM-07", "module_group": "payments-refunds", "module": "Payments and device control", "capability": "Payment-to-eject exception and idempotency handling", "buyer_question": "What happens if payment is readable but the station does not eject, or a callback is duplicated?", "operator_role": "Support, operator, engineering", "scope_status": "INTEGRATION_REQUIRED", "capability_boundary": "Payment result, dispense command, station acknowledgement and order state must remain separate. A failure should create a traceable exception rather than a false successful rental or automatic refund promise.", "integration_deployment_dependency": "Provider callback behavior, station protocol, timeout rules, duplicate-event handling and assigned support owner.", "evidence_status": "PUBLIC_VALIDATION_METHOD_ONLY", "owner_canonical": "https://corecharge.cloud/en/guides/h5-rental-flow-payment-refund-uat/", "last_reviewed": "2026-08-24" }, { "id": "FM-08", "module_group": "payments-refunds", "module": "Returns", "capability": "Return recognition, fee stop and order closure", "buyer_question": "Can the system distinguish physical insertion from a recognized return and closed rental?", "operator_role": "Renter, support, operator", "scope_status": "INTEGRATION_REQUIRED", "capability_boundary": "The event chain can distinguish return event, fee-stop event and order closure. A physical insertion alone is not sufficient when the system has not recognized the return.", "integration_deployment_dependency": "Station protocol, power-bank identity, return rules, delayed-event handling and order-closing logic.", "evidence_status": "PUBLIC_VALIDATION_METHOD_ONLY", "owner_canonical": "https://corecharge.cloud/en/guides/h5-rental-flow-payment-refund-uat/", "last_reviewed": "2026-08-24" }, { "id": "FM-09", "module_group": "payments-refunds", "module": "Refund support", "capability": "Refund or authorization-release review states", "buyer_question": "Can support tell whether an outcome is requested, under review, provider-pending, completed or declined?", "operator_role": "Support, finance review, operator", "scope_status": "INTEGRATION_REQUIRED", "capability_boundary": "Readable workflow states can be scoped when the provider integration supports them. CoreCharge does not guarantee provider approval, settlement, refund outcome or a universal completion time.", "integration_deployment_dependency": "Provider API and callback coverage, operator policy, reconciliation key, reason codes and manual follow-up ownership.", "evidence_status": "PUBLIC_VALIDATION_METHOD_ONLY", "owner_canonical": "https://corecharge.cloud/en/guides/h5-rental-flow-payment-refund-uat/", "last_reviewed": "2026-08-24" }, { "id": "FM-10", "module_group": "roles-reporting", "module": "Dashboard", "capability": "Field dictionary, data freshness and exception ownership", "buyer_question": "Will each dashboard field have a known source, timestamp, timezone and next action?", "operator_role": "Operator, agent, support, finance review", "scope_status": "AVAILABLE_BY_SCOPE", "capability_boundary": "Fields should be defined by meaning, source event, freshness, masking and permitted roles. Example dashboard values demonstrate structure only, not live performance.", "integration_deployment_dependency": "Field dictionary, source-system mapping, role policy, masking and acceptance tests.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" }, { "id": "FM-11", "module_group": "roles-reporting", "module": "Roles and permissions", "capability": "Agent-assigned operations scope", "buyer_question": "Can an agent work across assigned venues without seeing another agent's records?", "operator_role": "Platform owner, agent, support", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "Agent roles can be planned around assigned stations, merchants, exceptions and reports. Exact hierarchy, data access and settlement responsibility are not assumed.", "integration_deployment_dependency": "Organization hierarchy, permission model, assigned data domains, masking and backend enforcement.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" }, { "id": "FM-12", "module_group": "roles-reporting", "module": "Roles and permissions", "capability": "Merchant-limited operations view", "buyer_question": "Can a venue or merchant see only the local fields needed for support and operations?", "operator_role": "Platform owner, merchant, support", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "A merchant view may be limited to its assigned stations, orders and agreed report fields. It should not automatically expose another party's records or unrestricted logs.", "integration_deployment_dependency": "Merchant hierarchy, role-to-field policy, record ownership, masking and backend authorization tests.", "evidence_status": "PUBLIC_OWNER_CANONICAL_REVIEWED", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" }, { "id": "FM-13", "module_group": "roles-reporting", "module": "Support and audit", "capability": "Revenue leakage prevention, exception evidence and audit trail", "buyer_question": "Can the operator reconcile abnormal orders and reconstruct who reviewed an exception, which evidence was used and what decision followed?", "operator_role": "Support, operator, audit reviewer", "scope_status": "AVAILABLE_BY_SCOPE", "capability_boundary": "A scoped control set can include reconciliation keys, permission boundaries, exception cases, masked business references, evidence, owner, timestamps and disposition. It must not include deceptive, simulated or fabricated financial operations. Public material must exclude personal data, payment secrets and unrestricted logs.", "integration_deployment_dependency": "Order and payment event links, approved financial rules, role enforcement, audit retention, masking, access history and owner assignment.", "evidence_status": "PUBLIC_OWNER_CANONICAL_PLUS_BOUNDED_OWNER_SCOPE", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" }, { "id": "FM-14", "module_group": "roles-reporting", "module": "Settlement review", "capability": "Commission and settlement review fields", "buyer_question": "Can finance review the rule version, source orders, period and adjustments before approval?", "operator_role": "Finance review, platform owner, agent", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "Review fields may include scoped parties, period, source orders, adjustments, calculation time and known status. No accounting accuracy, payout, settlement timing or legal entitlement is promised.", "integration_deployment_dependency": "Approved commercial rules, source-order integrity, currency, period controls, review workflow and payout-provider scope.", "evidence_status": "PUBLIC_FIELD_MODEL_ONLY", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" }, { "id": "FM-15", "module_group": "deployment-evidence", "module": "Renter channels", "capability": "Browser H5 scan flow and optional native apps", "buyer_question": "Should renters use browser H5 with camera or QR entry, an optional native app, or both?", "operator_role": "Operator, local brand team, product owner", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "Browser H5 can support camera or QR entry without requiring an app install. Optional native apps can be prepared for Google Play and Apple App Store review. This does not claim feature parity, review approval, universal listing or availability in every store region.", "integration_deployment_dependency": "Camera and browser behavior, QR context, payment route, account model, store account and review process, target region, maintenance capacity and support plan.", "evidence_status": "PUBLIC_OWNER_CANONICAL_PLUS_BOUNDED_OWNER_SCOPE", "owner_canonical": "https://corecharge.cloud/en/software/h5-shared-power-bank-rental-platform/", "last_reviewed": "2026-08-24" }, { "id": "FM-16", "module_group": "deployment-evidence", "module": "White label", "capability": "Selected renter UI and operating-brand configuration", "buyer_question": "Which logos, colors, languages, support entries and operator assets can use my brand?", "operator_role": "Local brand team, operator, product owner", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "Selected H5 or App copy, station labels, packaging and operator-facing assets can be reviewed. White-label depth is not universal and depends on hardware, software, language and deployment scope.", "integration_deployment_dependency": "Approved brand assets, locale, hardware labeling, renter UI, App/store scope and acceptance review.", "evidence_status": "PUBLIC_OWNER_PLUS_AUTHORIZED_CASE_EVIDENCE", "owner_canonical": "https://corecharge.cloud/en/software/overseas-shared-power-bank-rental-software/", "last_reviewed": "2026-08-24" }, { "id": "FM-17", "module_group": "deployment-evidence", "module": "Deployment", "capability": "SaaS pilot and separately reviewed private deployment", "buyer_question": "Can we begin with SaaS and decide on private deployment after the operating model is proven?", "operator_role": "Operator, IT owner, product owner", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "A controlled SaaS pilot can precede a separately reviewed private-deployment discussion. Infrastructure, tenancy, operations, maintenance and migration commitments are not included by default.", "integration_deployment_dependency": "Security review, infrastructure ownership, tenancy, data boundaries, integrations, maintenance and migration plan.", "evidence_status": "PUBLIC_SCOPE_DESCRIPTION_ONLY", "owner_canonical": "https://corecharge.cloud/en/software/overseas-shared-power-bank-rental-software/", "last_reviewed": "2026-08-24" }, { "id": "FM-18", "module_group": "deployment-evidence", "module": "Country launch scope", "capability": "Market-specific software and operating checklist", "buyer_question": "Can the software plan be reviewed against the target country's language, provider and operating needs?", "operator_role": "Operator, local brand team, compliance and payment owners", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "Country pages organize launch questions for Singapore, the UAE, Malaysia and other markets. They do not prove regulatory approval, provider enablement, compliance completion or launch readiness.", "integration_deployment_dependency": "Country, city, locale, provider onboarding, support policy, legal review, station model and deployment owner.", "evidence_status": "PUBLIC_COUNTRY_PLANNING_CANONICALS", "owner_canonical": "https://corecharge.cloud/en/markets/", "last_reviewed": "2026-08-24" }, { "id": "FM-19", "module_group": "deployment-evidence", "module": "Delivery evidence", "capability": "Authorized named deployment references", "buyer_question": "Which public references can be used to review bounded CoreCharge delivery evidence?", "operator_role": "Buyer, procurement, product owner", "scope_status": "AVAILABLE_BY_SCOPE", "capability_boundary": "The Cases owner page may use authorized names, logos and bounded delivery descriptions. It does not establish revenue, volume, uptime, payment approval, certification, market leadership, endorsement or every feature in this matrix.", "integration_deployment_dependency": "Case authorization, public-link review, claim-by-claim scope and periodic evidence revalidation.", "evidence_status": "AUTHORIZED_PUBLIC_CASE_EVIDENCE", "owner_canonical": "https://corecharge.cloud/en/cases/", "last_reviewed": "2026-08-24" }, { "id": "FM-20", "module_group": "deployment-evidence", "module": "Hardware integration", "capability": "Public hardware protocol and independent software integration path", "buyer_question": "Can a hardware buyer review a safe protocol and evaluate an independent software integration?", "operator_role": "Buyer engineering, firmware, CoreCharge product owner", "scope_status": "INTEGRATION_REQUIRED", "capability_boundary": "The validated publication package exposes the complete v1.51 instruction syntax, upload and downlink parameters, CRC implementation, business flows and synthetic test vectors needed to evaluate an independent integration. It does not claim universal model or firmware compatibility and does not expose production endpoints, credentials or tenant access.", "integration_deployment_dependency": "Confirmed cabinet model and firmware, assigned endpoint and credentials, topic authorization, command safety review, version policy, middleware scope and end-to-end UAT.", "evidence_status": "PACKAGE_VALIDATED_DEPLOYMENT_PENDING", "owner_canonical": "https://corecharge.cloud/developers/", "last_reviewed": "2026-08-25" }, { "id": "FM-21", "module_group": "roles-reporting", "module": "Operator channels", "capability": "Desktop web admin, mobile H5 admin and optional admin app", "buyer_question": "Which operational channel and functions will each platform owner, agent, merchant, support or finance role receive?", "operator_role": "Platform owner, agent, merchant, support, finance review", "scope_status": "CONFIRM_FOR_DEPLOYMENT", "capability_boundary": "Desktop web admin and mobile H5 admin can be scoped, with an optional admin app. Role-based login and backend permissions expose different functions and records; channel presence does not imply identical features or unrestricted access.", "integration_deployment_dependency": "Approved role model, backend authorization, field-level visibility, mobile-browser support, optional app scope, store review and acceptance tests for every role.", "evidence_status": "OWNER_STATED_BOUNDED_SCOPE_WITH_PUBLIC_ROLE_FIELD_MODEL", "owner_canonical": "https://corecharge.cloud/en/software/agent-dashboard-field-guide/", "last_reviewed": "2026-08-24" } ] }