Merchant User Guide

Demo and Implementation Notes

Demo and Implementation Notes

Behaviours that are mock, simulated, or phase-1 only.

2 min read

The following features are currently implemented as demo/mock in the merchant portal. They represent planned functionality and demonstrate the intended user experience, but real backend processing is not yet live for these specific areas.

Mock/demo behaviours

Payments connection uses a simulated Stripe Connect-style flow (mock provider). Real payment onboarding will integrate with an actual payment processor.
Payouts ledger shows realistic data with correct fee structures, but no real fund movement occurs.
Driver management is functional in the UI but 'Mark Paid' is a bookkeeping action only — no real settlement occurs.
Online Shop orders are mock data. Real order processing will connect to the commerce backend.
MGVC batch creation and quota tracking is UI-functional but uses in-memory/localStorage persistence. Production will use a database.
POS API connection status is simulated. Real integrations will use actual OAuth flows with POS providers.
AI recommendations are pre-generated. Production will use live business data for personalised suggestions.
Customer data including segments, churn risk, and lifetime value are mock-generated. Production will derive these from real transaction history.
Invoice generation and billing are UI demonstrations. Production billing will connect to the accounting system.
ABN verification status is a UI indicator only. Production will integrate with ABN Lookup services.
Data persistence

Demo data is persisted in browser localStorage. Clearing your browser data or switching browsers will reset demo state. Production will use server-side persistence.

Merchant User Guide