A service product type for WooCommerce turns a collection of service pages into a consistent sales and delivery workflow. Editors get one reusable structure, while customers get the scope, duration, delivery, and preparation information they need before purchasing.
This guide builds a Website Performance Audit with Custom Product Type for WooCommerce.
Define the service promise and data
The product description should sell the outcome. Structured fields should carry the facts repeated across services.
| Information | Recommended layer |
|---|---|
| Audit outcome and value | Product description |
| Delivery time and method | Service Details fields |
| Included checks and revisions | Service Details fields |
| Customer website and goals | Customer input |
| Supporting files | Customer file upload |
| Optional appointment date | Booking-oriented input |
Write the service model in one sentence
A Website Performance Audit is a virtual service with a defined scope, delivery time, preparation process, report format, and follow-up.
This definition separates the reusable model from one audit’s title or campaign copy. Every field should support the sentence or the customer decision.
Step 1: Create the Service type
- Go to WooCommerce > Product Types > Add New.
- Enter Service and Services as the labels.
- Select an available product-page layout, or keep the default WooCommerce layout.
- Use Custom Taxonomy for service families when useful.
- Set Display In Shop according to the store navigation.
- Add a concise Service badge when it improves listing clarity.
Step 2: Build the Service Details tab
Enable Back-end Fields > Admin Fields and set Admin Fields Tab Label to Service Details.
| Field | Type | Example |
|---|---|---|
| Delivery Time | Text | Five business days |
| Delivery Method | Select | PDF report and video call |
| Included Checks | Number | 30 |
| Follow-up Included | Checkbox | Yes |
| Communication Channel | Radio | |
| Preparation Requirements | Textarea | Provide the URL and analytics access |
Step 3: Show the details that reduce purchase friction
Enable Show In Front for delivery time, method, included checks, follow-up, and preparation. Select a Position In Front before or after Add to Cart, around Product Meta, or inside the Single Product Summary.
Keep the page focused: promise first, essential specifications second, purchase action third.
Build a conversion-focused service page
- Lead with the problem the audit solves.
- Explain the deliverable and expected outcome.
- Show delivery time, method, included checks, and follow-up.
- Present the price and purchase action.
- Collect the website URL, goals, and supporting files.
Do not use the structured fields as a substitute for persuasive service copy. The description creates demand; Service Details reduce uncertainty.
Step 4: Add customer input only where needed
The Website Performance Audit may require:
- Website URL.
- Primary business goal.
- Known performance concern.
- Supporting report or screenshot.
- Preferred follow-up date when the offer includes a session.
These values belong to the individual purchase. Keep them separate from the stable Service Details model.
Decide whether the service needs booking
A performance audit delivered asynchronously may only need customer text and file upload. An audit with a live review session may also need a preferred date. Add booking input only when it is part of the customer journey.
For a full service model plus customer booking choices, keep the stable offer in Custom Product Type and the reservation values in the buyer-input layer.
Step 5: Create the first service product
- Add a title centered on the result.
- Explain who the audit is for and what it delivers.
- Add the price and product image.
- Mark the service Virtual when shipping is not required.
- Select Service as the product type.
- Complete Service Details.
- Preview the page and customer inputs on mobile and desktop.
Use the model as a service publishing standard
- Outcome and target customer are clear.
- Scope and included work are visible.
- Delivery time and method are explicit.
- Preparation requirements are understandable.
- Customer inputs are limited to necessary information.
- The purchase action is easy to find.
This checklist reduces pre-sale questions and lets the content team create the next service without rebuilding the page structure.
Document it for every editor.
Test service operations, not only layout
- An editor can create the next audit from the same model.
- The public fields match the actual service scope.
- The customer form provides enough preparation information.
- Optional fields remain clean when empty.
- The mobile page keeps the purchase action easy to find.
For customer booking and upload requirements, compare Custom Product Type vs Product Add-Ons. For the complete creation workflow, use the custom product type guide.
Frequently asked questions
Can WooCommerce sell services as a dedicated product type?
Yes. Create Service and Services labels, then configure the admin fields, layout, storefront output, and customer options required by the model.
Which service fields should appear publicly?
Show delivery, scope, preparation, and included-value fields that support the buying decision.
Should customer project details be backend fields?
No. Information supplied for one purchase belongs in the customer-input layer.
Can services be hidden from the main shop?
Yes. Use Display In Shop when services have a separate landing or collection path.
