Technical compatibility packages
A historical License Plan (BC-POL Plan) binds a catalog Product to a Policy for technical packaging. It remains during the compatibility period, but it is not the customer-facing tariff model.
Keep the three levels separate
| Level | Meaning |
|---|---|
| PlatformPlan / PlatformSubscription | The vendor pays for the MyHoreca platform |
| Product tariff / version / customer subscription | A customer buys the vendor Product |
| Policy / compatibility Plan / FeatureLimit | Runtime rules, entitlements and limits |
Configure customer price, billing period and immutable versions under Product → Tariffs. Existing customer subscriptions stay pinned to the version they bought until an explicit migration is authorized.
Compatibility route
The Vendor Console keeps /plans as an Advanced compatibility route. It is no
longer a top-level commercial navigation item.
| Entry | Path |
|---|---|
| From a Product technical flow | Product → Policy → create the required technical package → /plans?productId={catalogProductId} |
| Direct support access | /plans |
The compatibility create dialog still accepts code, display name, Policy, and catalog Product. There is no Plan edit/PATCH in Console. These fields do not define customer price or subscription terms.
Technical Policy rules stay under Operations → Policies (/policies). Do
not treat a compatibility Plan as a Product tariff or a PlatformPlan.
Related
- Products · Policies · Entitlements · Trials
- Licensing Models · Core Concepts
- Beginner path: Vendor: first hour
- API Reference
Next steps
- Getting Started
- Keys: License Keys
- Payments for platform SaaS: Checkout and payments