fix: price levels admin page depends on PRO routes — needs Core-native API

[Blb3D]

Problem

The Price Levels admin page (AdminPriceLevels.jsx) calls /api/v1/pro/catalogs/price-levels which is a PRO-only route. If the PRO plugin is not installed, the page errors with a 404.

The price_levels table lives in Core's database — Core owns this data. But there is no Core API endpoint for it. The UI was built against the PRO endpoint, creating an invisible dependency.

Current State

price_levels table       → Core DB ✅
/api/v1/price-levels     → Does not exist ❌
/api/v1/pro/catalogs/... → PRO route (requires plugin)
AdminPriceLevels.jsx     → Calls PRO route ❌

Expected State

price_levels table       → Core DB ✅
/api/v1/price-levels     → Core CRUD endpoint ✅ (new)
/api/v1/pro/catalogs/... → PRO extends with customer assignment
AdminPriceLevels.jsx     → Calls Core API ✅

Scope

Backend (new Core endpoints)

• GET /api/v1/price-levels — list all price levels
• POST /api/v1/price-levels — create
• PATCH /api/v1/price-levels/{id} — update
• DELETE /api/v1/price-levels/{id} — deactivate

Frontend

• Update AdminPriceLevels.jsx to call Core endpoints for CRUD
• Customer assignment (the modal with assign/unassign) can stay on PRO routes — it uses pro_customer_price_levels which is genuinely a PRO table
• If PRO is not installed, the page should work for managing price levels, just without the customer assignment feature

Model

• Core already has price_levels table and model — no schema changes needed
• Add schema + service + endpoint files

Why This Matters

A Core-only user (open source, no PRO) cannot manage price levels at all right now. The page is inaccessible without the PRO plugin installed. This violates the principle that Core runs independently.

🤖 Generated with Claude Code

[coderabbitai]

🔗 Related PRs

#363 - feat: Phase 2 — PRO extension points for Core [merged]
#403 - feat: B2B Portal admin pages + sidebar lock icons (PRO-gated) [merged]
#412 - fix: consistent PRO upgrade card on Access Requests page [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Blb3D]

Triage (2026-03-30): Confirmed still open — sacred rule violation.

AdminPriceLevels.jsx hardcodes /api/v1/pro/catalogs/price-levels and /api/v1/pro/catalogs/available-customers routes. Also has a PRO feature gate that redirects to /pricing if PRO is not active.

Options:

1. Move price levels CRUD to Core API (/api/v1/catalogs/price-levels) since price levels are a Core concept (used by sales_order_service price auto-apply)
2. Move the admin page to the PRO repo if price levels are intended to be PRO-only

Either way, the current state violates the sacred rule: removing PRO breaks this Core admin page.