diff --git a/docs/service-plans-a9d2d1b.md b/docs/service-plans-a9d2d1b.md
index 896efe4..c8e6c39 100644
--- a/docs/service-plans-a9d2d1b.md
+++ b/docs/service-plans-a9d2d1b.md
@@ -7,6 +7,9 @@ The SAP Cloud Logging service plans provide different ingestion and storage capa
 > ### Note:  
 > Updating service plans isn't supported. The recommended migration procedure involves running instances side-by-side during a transition.
 
+> ### Note:  
+> Service plans impact pricing. Pricing information is available via [Discovery Center](https://discovery-center.cloud.sap/serviceCatalog/cloud-logging?tab=service_plan) and [SAP Cloud Logging Capacity Unit Estimator](https://sap-cloud-logging-estimator.cfapps.us10.hana.ondemand.com/)
+
 > ### Caution:  
 > For production service plans, service instances scale automatically within the configured limits. To avoid disk overflow, there is time-based and disk-utilization-based data curation. If the disk usage watermark has been exceeded and the instance is scaled to its maximum, the system automatically deletes the oldest indices. The term `net storage capacity` used in service plan descriptions refers to the usable disk-size up to the watermark and has subtracted the disk space required for replicas. Service plans can handle peak load in relation to their storage volumes. However, service quality degradation can happen if the load exceeds the non-scaled disk capacity within one day.