ECOMMERCE WITH WOOCOMMERCE
Unit 5: Catalog Structure, Attributes and Variations
Unit purpose
Organize products for discovery, then model reusable attributes and complete purchasable variation data.
Safe practice boundary
Use a staging or practice site for learning tasks. Keep credentials, customer details, payment data and API secrets out of handouts and screenshots. Confirm current tax, privacy, consumer, accessibility and payment obligations with appropriately qualified professionals for the store's jurisdiction.
Catalog Organization for Customer Discovery
Topic: Product organization
Subtopic: Categories, subcategories, tags, slugs, navigation and catalog governance
Catalog organization helps customers browse and helps administrators maintain consistent product records. Categories create a hierarchy, tags connect items through flexible descriptors, and a naming standard reduces duplication and confusion as the catalog grows.
Source-context note: The lesson focuses on avoiding product confusion. Current WooCommerce documentation describes categories as hierarchical, tags as flexible non-hierarchical descriptors, and attributes as structured product characteristics.
Definitions and meanings
| Term | Meaning | My example or question |
|---|---|---|
| Category | A hierarchical product grouping that can contain parent and child sections. | |
| Tag | A non-hierarchical descriptor that connects products sharing a characteristic. | |
| Taxonomy | A system for classifying and organizing content. | |
| Slug | The URL-friendly text used to identify a page, product or taxonomy term. |
Learning outcomes
- Distinguish categories, subcategories and tags.
- Design a small catalog hierarchy around customer tasks.
- Create naming rules that prevent duplicate terms.
Illustration task
Draw a category tree for a six-product shop. Add tags as cross-links rather than extra branches, and show the route a customer follows to one product.
Applied activity
Organize twelve fictional products into a maximum of four top-level categories. Add only useful subcategories and tags, then test whether another learner can locate three named items.
Assessment evidence and criteria
A catalog tree, naming standard and findability test record.
- ☐ Hierarchy stays understandable
- ☐ Tags are not used as duplicate categories
- ☐ Names and slugs are consistent
- ☐ Navigation is tested with a user task
Attributes, Variations and Product Choice
Topic: Product attributes
Subtopic: Global and custom attributes, terms, variable products, variation data and selection testing
An attribute describes a structured product characteristic such as color or size. Attributes can support filtering and can define variations, while each purchasable variation may need its own price, stock, SKU, image or shipping information.
Source-context note: The supplied example uses product colors. The current curriculum broadens the concept to global reuse, filtering and variation-level operational data.
Definitions and meanings
| Term | Meaning | My example or question |
|---|---|---|
| Attribute | A structured characteristic assigned to a product, such as size or color. | |
| Term | One permitted value within an attribute, such as Blue within Color. | |
| Variation | A purchasable combination of attributes within a variable product. | |
| Global attribute | An attribute defined once for consistent reuse across multiple products. |
Learning outcomes
- Separate descriptive attributes from purchasable variations.
- Choose between global and product-specific attributes.
- Test whether every valid variation can be selected and fulfilled.
Illustration task
Create a variation matrix with Color on one axis and Size on the other. Mark valid combinations and attach SKU, price and stock fields to each purchasable cell.
Applied activity
Build a specification for a fictional variable product with two attributes. Remove impossible combinations, assign unique SKUs and write tests for selection, stock, price and image changes.
Assessment evidence and criteria
A completed variation matrix and four acceptance tests.
- ☐ Attribute names and terms are consistent
- ☐ Every purchasable variation has required data
- ☐ Impossible combinations are controlled
- ☐ Customer selection is tested
Unit knowledge check
1. Which product grouping is hierarchical?
☐ Category
☐ Tag
☐ Webhook
2. What is a term within an attribute?
☐ A permitted value such as Blue
☐ A product order
☐ A payment gateway
3. What should every purchasable variation have when required?
☐ Complete price, stock and SKU data
☐ A duplicate category
☐ An unrelated tag
Store-build reflection
What did I understand? Which setting or workflow still needs current documentation? What will I test on staging before using it on a live store?
