Requests & Offers
Manage request classification, provider responses, offer decisions, budgets and fulfilment reference values.
Request Types
Use the established request types: product, service, transport, accommodation, venue, catering, emergency, support/donation, equipment hire and other.
Name | Description | Actions |
|---|
Request Categories
Classify requests for filtering and provider matching. Reuse an existing shared category only when its meaning and relationships are identical.
Name of Category | Description | Actions |
|---|
Requested Item Types
Used by Request Required Service or required-item records to identify what the family needs.
| Item type | Description | Status | Actions |
|---|---|---|---|
| ExampleHearse service | Service required | Demo only |
Urgency Levels
Use a small ordered scale with clear operational meaning; urgent values must not promise unavailable emergency response.
Name | Description | Actions |
|---|
Response Types
Describe the provider response, such as offer, quote, information request or decline.
Name | Description | Actions |
|---|
Offer Types
Classify offers without duplicating Response Type. Use only when it drives a distinct workflow or presentation.
| Offer type | Description | Status | Actions |
|---|---|---|---|
| ExampleFixed quotation | One proposed total | Demo only |
Offer Statuses
Preserve stable lifecycle values used by request offers, decision controls, notifications and audit records.
Description | Name | Slug | Sort Order | System Code | Actions |
|---|
Offer Withdrawal Reasons
Use the existing Reason for Withdrawal of Offer collection or migrate it carefully; retain the provider explanation on the offer record.
Active | Description | Name | Sort Order | Actions |
|---|
Rejection Reasons
Scope these values to request or offer decisions. Do not mix them with moderation, verification or suspension reasons unless one contextual collection is deliberately used.
| Reason | Applies to | Status | Actions |
|---|---|---|---|
| ExampleRequirements not met | Offer decision | Demo only |
Budget Types
Support fixed budget, range, negotiable, quote requested, no budget specified and similar request-pricing choices.
Name | Description | Actions |
|---|
Fulfilment Statuses
Track delivery or completion of the requested need separately from request status, offer status and booking status.
| Status | Description | Status | Actions |
|---|---|---|---|
| ExampleIn progress | Accepted work is underway | Demo only |
DrapCode connection notes
- Create or duplicate a restricted admin page at the route shown above; add this layout with Bootstrap 5 components.
- Bind every accordion table and its Add/Edit actions to the existing collection named by the heading. Confirm technical names and fields first.
- Connect Request Categories to the applicable Request Type, and connect Requested Item Types to Request Required Service or the existing required-item child collection.
- Keep Request Status, Offer Status and Fulfilment Status distinct. Each represents a different record and lifecycle.
- Scope rejection reasons to their context. Use Offer Withdrawal Reasons only for provider-initiated withdrawal and record the selected reason on the offer before its status changes.
- Restrict write access to authorized admins. Record actor, timestamp and before/after values in Audit Logs; send relevant user/admin notifications for material status changes.
- After changes, test create request, submit offer, accept/reject/withdraw offer, booking creation, messaging and notification workflows.