Marketplace, Shops & Employment
Manage marketplace, shop, product, job and employment reference values.
Parent Marketplace Categories
Preserve the existing top-level marketplace hierarchy and its relationships to shops, products and listings.
| Category name | Description | Status | Actions |
|---|---|---|---|
| ExampleFuneral products | Goods used for funeral arrangements | Demo only |
Shop Categories
Classify shops or storefronts, not individual products. Connect each value to its parent marketplace category where applicable.
Name | Description | Actions |
|---|
Job Categories
Group employment opportunities by occupational or service area.
Name | Description | Actions |
|---|
Job Type Categories
Check whether these records describe employment terms or another hierarchy before connecting them alongside Employment Types.
Name | Description | Actions |
|---|
Marketplace Types
Describe distinct marketplace contexts only when they change navigation, access or listing behaviour.
| Marketplace type | Description | Status | Actions |
|---|---|---|---|
| ExampleProducts marketplace | Physical and made-to-order goods | Demo only |
Product Categories
Classify individual products. Do not use Product Categories as a substitute for Shop Categories.
Category Name | Description | Actions |
|---|
Employment Types
Use for employment terms such as permanent, fixed-term, temporary, casual, internship or volunteer.
| Employment type | Description | Status | Actions |
|---|---|---|---|
| ExampleFixed-term | Employment for an agreed period | Demo only |
Work Arrangement Types
Use for on-site, remote, hybrid, shift-based, travel-based or similar working arrangements.
| Arrangement | Description | Status | Actions |
|---|---|---|---|
| ExampleOn-site | Work performed at the employer location | Demo only |
Experience Levels
Use a clear ordered scale without excluding candidates through vague or inflated requirements.
| Experience level | Description | Status | Actions |
|---|---|---|---|
| ExampleEntry level | Limited prior experience required | Demo only |
Job Application Statuses
Control the job-application lifecycle separately from job publication, moderation and account status.
| Status | Description | Status | Actions |
|---|---|---|---|
| ExampleSubmitted | Application received for review | Demo only |
DrapCode connection notes
- Create or duplicate a restricted admin page at the route shown above and add this Bootstrap 5 layout.
- Bind every accordion table and Add/Edit action to the existing collection named by its heading. Verify technical names and relationships first.
- Preserve Parent Marketplace Category → Shop Category for storefront classification and Parent Marketplace Category → Product Category for goods classification.
- Compare Job Type Categories with Employment Types. If both mean permanent, temporary, contract and similar terms, keep one canonical collection and reconnect dependent forms.
- Keep shops, products, job advertisements, applications, employers and candidates in their operational collections rather than these reference tables.
- Restrict write access to authorised admins. Record material changes in Audit Logs and notify the responsible administrator when active listings or applications may be affected.
- After changes, test shop registration, product listing, marketplace filtering, job creation, job search and application workflows.