Custom franchise reporting software

One location, two reporting periods

Suppose a franchisee compares headquarters' report for the previous month with a report from their own sales system. The figures differ. They open the file they sent to headquarters and discover that the date range ended before the last day of the month. They prepare a corrected file covering the full month and need to get it to the person responsible for reporting.

In a portal, they could do that alongside their location's report: identify the incorrect period, attach the corrected file, and explain what happened. The person at headquarters could see which report the request concerns and open both the original source and its replacement. After checking the data, they would publish the corrected report. The franchisee could return to the same request to see whether the change had been included.

For this to work, people need to know what they are looking at. The location and reporting month should appear with the figures. They also need to know which source file was used and whether the submitted correction has been incorporated. Simply replacing one figure with another would make it harder to explain why an earlier report showed something different.

The portal cannot decide what your metrics mean. If locations interpret the same report item differently, the person responsible for reporting needs to settle its definition. In this example, the discrepancy comes from the file's date range. In another case, staff may need to ask what a location included in a figure. Keeping that explanation with the request gives them something to refer to next month.

Viewing a report and submitting a correction

A franchisee reading their location's results needs different access from an analyst building reports for the entire network. Submitting a correction is another requirement. A user can provide an explanation and a new source file while headquarters decides when to update the report. That arrangement lets the network collect local feedback while retaining a consistent way to calculate results.

This distinction also helps you review what the network pays for. If a location only needs to read a report, investigate the available viewing options. If staff at headquarters still search for the right report after every email and record corrections in a separate spreadsheet, a licensing change alone will leave that work in place.

Power BI supports direct report sharing, apps that package reports, and external guest access through Microsoft Entra B2B. Licensing depends on the sharing method and the infrastructure you purchase, which Microsoft calls capacity. Recipients can use a free license when both the report and its underlying data model are in capacity that meets Microsoft's requirements. Not every capacity option qualifies. Before comparing costs, ask your administrator to check the arrangement for your network (Microsoft's Power BI sharing documentation).

Each location needs access to its own data

In the example, the franchisee is explaining a discrepancy at their own location. Hiding other locations in a menu or setting a chart filter does not establish which data they can access. Microsoft states that hiding Power BI pages, columns, or visuals does not restrict access to the underlying data. Restrictions need to be defined in the data model, for example by limiting which rows a user can access (Power BI report and data access guidance).

The same concern applies when a report appears inside your own portal. A new login screen does not, by itself, change permissions in the reporting tool. When reviewing the proposed portal, use a franchisee account to open its report and download any available export. Files attached to a correction need the same access boundary. Headquarters may need to see the whole network; that does not mean every local user needs that view.

Keep the reports or rebuild them?

If your current tool produces useful reports, start with its features and terms for report viewers. A different sharing method or plan may be enough when the main problem is the cost of accounts used only occasionally. Include the work of managing invitations and helping people sign back in after a long absence.

When the reports work well but corrections arrive by email, an extension could focus on that gap. A portal could display an authenticated report from the existing tool alongside a form for explaining a discrepancy. This approach, known as embedding, needs to be checked against the available integrations, permissions, and licenses. Displaying a chart on another website does not remove the reporting vendor's terms.

Custom reporting is worth considering when the network needs a simple, repeatable view and the current product forces staff to do substantial work elsewhere or cannot handle the necessary corrections. The scope could be one location report and its change history. Headquarters could continue analyzing the full network in its existing tool. Recreating all of its analytical features would be a separate, much larger project.

This process does not require AI. A conventional application can display the right report and route a correction. Finding instructions that apply to a particular location is a different task, covered in our article on an AI knowledge base for franchise operations.

Who will look after the portal next year?

After launch, someone still has to add new locations, remove access when people leave the network, and respond when data transfers fail. Headquarters owns report definitions and approval of corrections. The application provider can maintain the software, but the scope of that support needs to be agreed. Comparing a subscription with development costs alone would leave out those ongoing responsibilities.

When changing systems, consider the history of reports and the explanations submitted with them. Decide what to migrate and what can remain in an accessible archive. Exports should preserve the connections between a report, its location, its period, and its corrections. For custom software, also discuss code ownership and what another provider would need to take over maintenance. Those arrangements help you assess your dependence on the provider before commissioning the work.

Syntalith builds custom applications. A possible first project is a view of one location report with space to explain a discrepancy and receive a response from headquarters. Start the conversation with the last correction someone sent by email: what did the franchisee notice, and what did headquarters have to do next? A description and the name of your current tool are enough to begin. You do not need a specification or confidential results. See Syntalith's pricing page for information about billing.