POST-LAUNCH: Allow store-admin to create a new species leaf category in WooCommerce #13

New Issue

2026-09-01T22:56:01Z

Ty commented

2026-09-01 22:56:01 +00:00

Summary

Enable a store-admin capability to create a new species leaf category directly inside the WooCommerce server from the app, so the synced taxonomy stays the source of truth without requiring a separate Woo admin visit.

Context

Issue twelve locks the exclusivity rule: only WooCommerce-synced species are selectable in the UI and in Call 1's taxonomy, with no hardcoded or fallback lists.
This issue extends that rule for post-launch: when a genuinely new species appears in the real world, the admin should be able to create it in Woo rather than leaving the app.
Creation must be a leaf under the species parent category only — no free-form category creation, to prevent taxonomy drift.
After creation, trigger a re-sync so the new species appears in the price list and Call 1's taxonomy.
The new species still requires a price rule before it can be used in a listing, so creation and pricing remain two deliberate steps.

Scope

Post-launch / V1.5 or later. Not a POC gate.
Implementation: POST to /products/categories with the parent set to the species category, then re-sync.
UI: store-admin only, not a general user capability.

Acceptance criteria

Docs state that species creation is a store-admin capability, not available to general users.
Docs state creation is restricted to a leaf under the species parent; free-form creation is forbidden.
Docs state that creation triggers a re-sync and that a price rule is still required before the species can be used.
Docs note this is deferred to post-launch.

## Summary Enable a store-admin capability to create a new species leaf category directly inside the WooCommerce server from the app, so the synced taxonomy stays the source of truth without requiring a separate Woo admin visit. ## Context - Issue twelve locks the exclusivity rule: only WooCommerce-synced species are selectable in the UI and in Call 1's taxonomy, with no hardcoded or fallback lists. - This issue extends that rule for post-launch: when a genuinely new species appears in the real world, the admin should be able to create it in Woo rather than leaving the app. - Creation must be a leaf under the species parent category only — no free-form category creation, to prevent taxonomy drift. - After creation, trigger a re-sync so the new species appears in the price list and Call 1's taxonomy. - The new species still requires a price rule before it can be used in a listing, so creation and pricing remain two deliberate steps. ## Scope - Post-launch / V1.5 or later. Not a POC gate. - Implementation: POST to `/products/categories` with the parent set to the species category, then re-sync. - UI: store-admin only, not a general user capability. ## Acceptance criteria - [ ] Docs state that species creation is a store-admin capability, not available to general users. - [ ] Docs state creation is restricted to a leaf under the species parent; free-form creation is forbidden. - [ ] Docs state that creation triggers a re-sync and that a price rule is still required before the species can be used. - [ ] Docs note this is deferred to post-launch.

Ty added this to the V1 milestone 2026-09-01 23:49:45 +00:00

grokbot_ty added the post-launch label 2026-09-24 16:23:44 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Ty_Tech/SlabUploader#13