diff --git a/components/esp_matter_rainmaker/esp_matter_rainmaker.cpp b/components/esp_matter_rainmaker/esp_matter_rainmaker.cpp
index c092783c0..06d2c0e5b 100644
--- a/components/esp_matter_rainmaker/esp_matter_rainmaker.cpp
+++ b/components/esp_matter_rainmaker/esp_matter_rainmaker.cpp
@@ -32,7 +32,8 @@ namespace cluster {
 namespace rainmaker {
 static constexpr chip::EndpointId endpoint_id = 0x00000000; /* Same as root node endpoint. This will always be
                                                             endpoint_id 0. */
-static constexpr chip::ClusterId Id = 0x131B0000; /* 0x131B == manufacturer code */
+static constexpr chip::ClusterId Id = 0x131BFC00; /* 0x131B == manufacturer code.
+                                                     0xFCOO == start of manufacturer specific cluster_id */
 
 namespace attribute {
 namespace status {
diff --git a/docs/en/developing.rst b/docs/en/developing.rst
index d7e84295b..0a387efe4 100644
--- a/docs/en/developing.rst
+++ b/docs/en/developing.rst
@@ -528,7 +528,7 @@ Non-Standard/Custom clusters can also be created:
 
    ::
       
-      uint32_t custom_cluster_id = 0x131b0000;
+      uint32_t custom_cluster_id = 0x131bfc00;
       cluster_t *cluster = cluster::create(endpoint, custom_cluster_id, CLUSTER_FLAG_SERVER);
 
 2.4.3.3 Attributes and Commands
diff --git a/examples/rainmaker_light/README.md b/examples/rainmaker_light/README.md
index b090081eb..be09d2e4a 100644
--- a/examples/rainmaker_light/README.md
+++ b/examples/rainmaker_light/README.md
@@ -44,10 +44,10 @@ rainmaker.py claim --addr 0x3E0000 $ESPPORT
 This needs to be done after commissioning.
 
 Check if the device already has user node association done, using the
-custom RainMaker cluster (cluster_id: 0x131b0000):
+custom RainMaker cluster (cluster_id: 0x131bfc00):
 
 ```
-chip-tool any read-by-id 0x131b0000 0x0 0x7283 0x0
+chip-tool any read-by-id 0x131bfc00 0x0 0x7283 0x0
 ```
 
 -   If the above custom status attribute (attribute_id: 0x0) returns
@@ -59,7 +59,7 @@ chip-tool any read-by-id 0x131b0000 0x0 0x7283 0x0
 Get the RainMaker node id (attribute_id: 0x1):
 
 ```
-chip-tool any read-by-id 0x131b0000 0x1 0x7283 0x0
+chip-tool any read-by-id 0x131bfc00 0x1 0x7283 0x0
 ```
 
 RainMaker CLI:
@@ -83,7 +83,7 @@ Now use the payload to run the RainMaker configuration command from
 chip-tool:
 
 ```
-chip-tool any command-by-id 0x131b0000 0x0 '"<user-id>::<secret-key>"' 0x7283 0x0
+chip-tool any command-by-id 0x131bfc00 0x0 '"<user-id>::<secret-key>"' 0x7283 0x0
 ```
 
 The device/node should now be associated with the user.
@@ -132,7 +132,7 @@ User Node association is failing on my device:
 -   If the device prints "This command has reached a limit", reboot the
     device to run the command again.
 -   Read the status attribute:
-    `chip-tool any read-by-id 0x131b0000 0x0 0x7283 0x0`. If this custom
+    `chip-tool any read-by-id 0x131bfc00 0x0 0x7283 0x0`. If this custom
     status attribute (attribute_id: 0x0) returns true, the association
     has already been done.
 -   If you are still facing issues, reproduce the issue on the default