Website & Payment Portal Design - Wordpress

Hello Calum,
Before scoping, I need to confirm how the points system will be treated legally and financially, since selling prepaid credits for services can carry different obligations than standard product sales. Please clarify whether points expire, whether unused balances are refundable, and how VAT is handled at the point of purchase versus the point of redemption. These affect how the system is built and what you will need to state in your terms.

The proposed stack (WooCommerce, myCred and a payment gateway) can handle points purchases and balances, but per-property balances, photo uploads on completed jobs, a job request workflow, and role-based dashboards for landlords, tenants and staff would require custom development or additional plugins. Please confirm whether points belong to the landlord or letting agent account and are allocated to properties, or whether each property holds its own balance, and whether tenants can request work without spending points. Also confirm who approves a request before points are deducted, how you price jobs in points, and whether the "Revive Tokens" step in your outline refers to a specific plugin or service, as I am not familiar with it as a standard component and would want to confirm it before quoting.

-/ Should tokens belong to the landlord/agent's overall account and then be allocated between their properties, or should every property maintain its own separate token wallet?

-/ When a tenant submits a job, should the landlord/agent approve it before it reaches your team, or should it enter your back-office queue immediately?

-/ Will each service have a predefined token cost, such as plumbing = X tokens and electrical = Y tokens, or do you want your team to assess each request and manually assign/deduct the required tokens?

Hi Calum,

To ensure complete alignment before kickoff, we would appreciate a little more information:

1. Should purchased token balances belong strictly to a primary Landlord account (shared across all their properties), or should tokens be explicitly locked to individual properties at the time of purchase?

2. Will token deductions be based on fixed/predefined job templates (e.g., Oven Replacement = 30 Tokens), or will your team manually enter a custom token deduction amount when marking a job complete?

3. Should tenants log in via standard user accounts to submit requests, or will they submit requests through a public, property-verified web form?

4. Do you already have custom UI/UX design mockups or wireframes prepared, or would you like us to handle the full UI/UX design phase?

Happy to discuss.

Best Regards.

One thing I’d like to clarify: should landlords be able to *move tokens between their own properties*, or should tokens remain locked to the property they were purchased for?

1/ How will the points system work when customers purchase a package, for example, fixed packages such as 100, 250, or 500 points?

2/ Can one landlord/letting agent have multiple properties under the same account, and should each property have its own separate point balance?

3/ When a landlord or tenant submits a maintenance request, what information should be required, property, issue category, description, priority, photos, preferred date/time, etc.?

4/ When your team completes a job, should the system automatically deduct the predefined points, or should an admin enter the actual points used before marking the job as complete?