Equipment sales
Hypervision
Enquiry → quote → accepted order → delivery → completion
Products, multiple line items, stock, deposits, balance payments and warranty records.
Parklands Storage · Hypervision · Future offerings
One shared engine.
Separate business workflows.
Structure proposal · 21 September 2026 · No deploymentA new Sales & Rental Engine accessed through Virtual HQ, serving your businesses under their shared ABN and bank account.
Starting point
You confirmed that no sales or rental system is set up yet. The local VHQ source reviewed contains the office navigation, general records, notes, projects, files and a Master Key login. Its existing “Storage” record category is not a storage rental system.
Review boundary: local source only; no live database or deployed version was verified. No existing application files or live services have been changed.
Shared foundation
VHQ Sales & Rental Engine
One business entity • One customer directory • Shared invoices and payments • Shared administration • Combined and brand-specific reporting
Equipment hire
Hypervision
Enquiry → availability → agreement → dispatch → on hire → return
Individual assets, hire periods, extensions, condition reports, bonds and maintenance blocks.
Storage rentals
Parklands Storage
Enquiry → available unit → agreement → move-in → recurring rent → move-out
Sites and units, occupancy, billing dates, bonds, arrears, notice dates and closure.
What is shared, and what stays separate
| Customers | One customer record with contacts, addresses and a combined history. Each transaction retains its brand and workflow. Duplicate matches are reviewed before merging. |
|---|---|
| Branding | Each brand has its own logo, contact details, document templates and approved terms. Brand and workflow are separate settings, so future brands can offer any supported service. |
| Money | One payment register for the shared business. Allocate each receipt to the relevant invoice or invoices; track partial payments, unallocated receipts, refunds and bonds separately. Preserve brand reporting even when money reaches the same bank account. |
| Documents | Quotes, agreements, invoices and receipts retain the customer, branding, prices and terms used when issued. Later edits to a customer or price list must not rewrite historical documents. |
| Administration | One dashboard with All businesses / Hypervision / Parklands filters. Named staff accounts, permissions and a history of who changed what. |
| Availability | Sales stock, hire assets and storage units have different availability rules. Booking confirmation must prevent overlapping allocation, including simultaneous requests. |
Suggested VHQ navigation
Sales & Rentals → Dashboard · Customers · Sales · Equipment Hire · Storage Rentals · Invoices & Payments · Reports · Settings
Provide direct links from VHQ and its Administration area. Use a business selector within the engine. Keep the existing office experience available.
Proposed data structure
Shared: business entity, brands, customers, contacts, offerings, quotes and quote lines, invoices and invoice lines, payments and allocations, bonds, documents, staff permissions and audit history.
Workflow records: sales orders and stock movements; hire agreements, assets and reservations; storage sites, units, agreements and occupancy. Billing schedules link to agreements and produce traceable invoice periods without duplicates.
Technical direction: a dedicated business module and business database on the existing Cloudflare platform, with protected document storage. VHQ is the entry point. Keep commercial data separate from personal records and publicly shared desk files; do not copy the current broad public-read behaviour into this module. Named staff permissions are needed beyond the current single Master Key model.
Recommended first build
- Approve this structure. Confirm storage inventory, rental periods, current payment process and document requirements.
- Local demonstration. Shared customers, brand switching and a Parklands unit-to-agreement workflow using clearly labelled sample data.
- Shared billing. Invoices, manually recorded receipts, allocations and bonds; recurring rental billing with duplicate protection.
- Equipment workflows. Add sales and hire using the same customers, documents and payment foundation.
- Readiness review. Verify access controls, booking conflicts, billing dates, totals, backups and recovery. Obtain separate explicit approval before every deployment.
Decisions to settle before implementation
Parklands unit types and numbering; billing frequency and proration; bonds and notice rules; existing accounting/payment service, if any; staff access; approved prices, branding and agreement templates. These remain open rather than assumed.