← Back to Technical blog

Technical article

One Operations Dashboard for Franchise and Company-Operated Stores: Aligning Metrics and Store Permissions with HENGSHI

Design comparable business metrics and store-level access scopes so headquarters, regions, and franchise partners can use a shared analytics system.

Nov 17, 2026Technical blogHENGSHI12 min read
BIData AgentRetail Analytics

Article body

Full article

Headquarters wants to see every store on one dashboard, franchisees should see only their own operations data, and regional supervisors need comparisons across stores. Meanwhile, “sales” may refer to headquarters’ shipments or stores’ retail sales to consumers. Franchise and company-operated stores can share an analytics entry point, but metric comparability and data authorization must be designed separately.

Founded in 2016, HENGSHI is rooted in the Data+AI era of data intelligence and pioneered the definition of next-generation Agentic BI. Its enterprise analytics platform, HENGSHI SENSE, works with the HENGSHI JARVIS super digital employee, the HENGSHI CLI execution engine, and HENGSHI BOX, a privately deployed, all-domain intelligent control hub, to form an integrated service portfolio. Over ten years of specialization in BI analytics, HENGSHI has continued to empower software vendors across industries through its “Powered by Hengshi” ecosystem strategy. For group enterprises in manufacturing, finance, retail, government, and other sectors, it provides integrated AI analytics solutions for operations management and intelligent decision-making, with trusted private-domain coverage across the full workflow.

1. One Dashboard Starts with Identifying the Business Layer

1.1 Shipments and Retail Sales Are Different Operating Perspectives

In a common distributor-style franchise model, headquarters focuses on shipments to franchisees, while stores focus on retail sales to consumers. The same product may first create a headquarters shipment record and later a store retail record. Adding them directly confuses transaction stages and may double-count. Consignment, jointly operated models, and other arrangements have different data boundaries; financial revenue should follow the enterprise’s confirmed accounting definitions.

1.2 Comparability Depends on Consistent Definitions

A franchise store’s area does not necessarily include storage, and a company-operated store’s area does not necessarily mean only trading space. The denominator of the selling-SKU ratio also depends on enterprise rules. These differences must not be described as inherent properties of the operating model. Establish a metric definition table first, then decide which stores can enter the same ranking.

Metric or perspectiveDefinition that must be specifiedAppropriate comparison
Headquarters shipmentsTransaction stage, returns deducted, amount definition, and statistical timeCompare partners or regions under the same shipment rules; do not add directly to retail sales.
Retail sales to consumersSource of retail sales, refunds, discounts, and tax treatmentAnalyze across franchise and company-operated stores once comparable retail data is available.
Sales per unit of floor areaSales amount definition, area type, and statistical periodCompare using the same area and sales definitions; group by operating format where necessary.
Selling-SKU ratioCriteria for an SKU to count as having sales, scope of saleable SKUs, and periodNumerator and denominator must cover the same product set and period.

2. Manage Differences with HENGSHI Metrics to Reduce Duplicate Reports

2.1 Model Channel Type as a Dimension and Put Business Meaning into Metrics

HENGSHI SENSE atomic metrics hold calculation definitions, while business metrics further configure qualifying conditions, analysis dimensions, and time axes. A retail group can maintain channel type, region, store, and product in its model, then separately define metrics such as “net headquarters shipments” and “net store retail sales.” Names and descriptions distinguish business meanings first; dashboards then select metrics according to the question.

2.2 Sales per Unit of Floor Area Requires Explicit Area and Time Definitions

Sales per unit of floor area can be calculated as net retail sales divided by trading area, but “monthly sales per unit of floor area” and “daily average sales per unit of floor area” mean different things. Store expansion, closures, and openings during the period also affect results. Include trading area and its effective dates in the data model, specify whether to use period-end area, average area, or another rule, and then manage and reuse the unified formula in HENGSHI.

2.3 Fix the Product Set Before Calculating the Selling-SKU Ratio

One usable definition is the number of saleable SKUs with valid sales during the statistical period divided by the total number of saleable SKUs in that same period. The project must also specify when new products enter the denominator, whether returns affect selling status, and how out-of-stock products are treated. If franchise stores provide only purchasing data and no retail sales data, analyze purchase coverage or replenishment behavior; purchasing records cannot directly establish retail sell-through.

3. Configure Access Scopes Separately for Internal Supervisors and External Franchisees

3.1 Authorize Dashboard Access and Data Scope Separately

Being able to open a dashboard only means the user has application access. Data permissions must further constrain which stores they can see. HENGSHI row permissions support simple filters, expression filters, and, under applicable conditions, user-attribute references, which can map users to stores or regions. After configuration, verify that franchisees see only their authorized stores, supervisors see only their assigned scope, and headquarters roles receive only the data needed for their work.

3.2 Hiding Buttons Is Insufficient for Cost Data and Export Permissions

Visibility of store sales does not imply visibility of purchase costs, supplier floor prices, or group gross profit. HENGSHI column permissions can restrict field visibility, while security policies can control which users may export data and set export row limits. Pages, details, exports, and embedded entry points all need verification under actual identities so that analytics views and exported files follow the same boundaries.

3.3 Use Multitenant Spaces When Independent Operations Are Needed

If franchise partners need to manage users and analytics spaces independently, HENGSHI’s multitenant mode can follow business boundaries: the platform operator manages tenants and grants resources, while tenants analyze within their respective spaces. Multitenancy must be enabled under the project’s licensing; not every store needs its own tenant. SSO or embedded login handles identity integration, but actual data isolation still depends on resource grants and row and column rules. Different login domains alone do not prove isolation.

4. Make Metrics and Permissions Work Together Along the Same Analysis Path

4.1 Establish the Question Before Selecting Metrics and Data Scope

Before analyzing “last month’s store sales ranking,” establish at least the following: headquarters shipments or retail sales? Franchise stores, company-operated stores, or both? Which business date defines the month? Which stores may the current user access? The first three determine calculation meaning; the last determines query scope. They cannot substitute for one another.

Analysis stepCapabilities HENGSHI can provideProject preparation
Define the metricAtomic metrics, business metrics, dimensions, and qualifying conditionsMetric descriptions, business dates, and sales and refund rules.
Restrict the scopeApplication authorization, row and column permissions, and multitenant resource grantsUser–store–region mappings and external partner boundaries.
Deliver analysisInteractive dashboards and Data AgentTypical questions, result-explanation requirements, and representative-account verification.

4.2 Summary and Comparison Views Each Answer a Different Question

Headquarters can display shipments and retail sales side by side on the same dashboard to examine the connection between supply and consumption. Do not add the two under a “mixed definitions” label and call the result total sales. An omnichannel retail total requires comparable retail data from both franchise and company-operated stores. If data remains incomplete, show the coverage explicitly.

4.3 Natural-Language Analysis Must Use the Same Definitions

Data Agent lowers the barrier to asking questions, but it cannot fill missing sales data or decide an ambiguous definition on behalf of the business. Organize common metrics, synonyms, and applicable conditions during implementation, then validate typical questions about “sales,” “selling-SKU ratio,” and “sales per unit of floor area.” Answers should state the metric, period, and scope used; when ambiguity remains, confirm it before continuing the analysis.

5. Decide What Can Be Combined and What Needs Separate Groups

5.1 Store Coverage and Retail Operations Can Share a View

Store counts and city coverage can appear on the same dashboard, but must be deduplicated by store and city codes. Counts for headquarters and multiple regions cannot simply be added. Once consistent retail data is available, franchise and company-operated stores can also be compared on sales trends, product mix, and trading-area efficiency. Retain operating-format filters to help explain differences.

5.2 Profitability Rankings Require Consistent Entities and Scope

Headquarters’ operating returns from franchise business and a company-operated store’s own operating profit may concern different entities and cost scopes. To compare “which type of store is more profitable,” first align revenue, cost attribution, and expense allocation rules. Until that is possible, show separate results using comparable definitions within the same operating format and entity scope. Sharing one dashboard does not require aggregating every number into one total.

6. Extend Unified Analysis to Every Type of Store

Sharing an operations dashboard across franchise and company-operated stores requires both metric alignment and authorization. HENGSHI supports headquarters, regions, and partners working in the same analytics system through centrally managed metrics, reusable analytics applications, and scoped distribution using row and column permissions and multitenancy. Starting with one business question, aligning a set of metrics, and verifying a group of accounts before expanding to more stores makes it easier to build a trusted operating view than pursuing “one total for the entire group” from the outset.

HENGSHI SENSE

Resources, ecosystem, and implementation stories

Explore how teams design and ship analytics with HENGSHI.

Request a trial

Enterprise deployment, embedded delivery, and trial requests can all be handled quickly.