Multi-merchant from day one

Build the web back office once. Feed every edge product into it.

This project is the operational and merchant control layer for edge. Terminal apps stay separate. Reporting, locations, permissions, and device allocation live here.

The right split from here

Keep the terminal apps separate. Keep the data contract shared. This project becomes the single source of truth for merchants, locations, roles, terminals, and reporting.

Merchant setup that stays simple

Create the customer, add locations, assign devices, and keep billing centred around the site instead of the terminal count.

One reporting layer for every product

edge Tap, edge go, and edge pos can feed the same merchant view later without changing how the business reads totals.

Built for fast, real-world use

Less text, stronger visual cues, and clear today-first reporting for merchants who just want to know what they have taken.

Build sequence

Start with setup and today-first reporting. Keep the UI visual, obvious, and light on words.

Route groups

/ops is for Edge staff. /merchant is for the merchant-facing portal. Shared data model underneath, separate permissions on top.

MVP path

Week 1: Edge ops setup and merchant dashboard showing today's total.Week 2: Locations, terminal allocation, and role permissions.Week 3: Transaction drill-down, refunds, and Xero prep.