diff --git a/qdrant-landing/content/documentation/guides/distributed_deployment.md b/qdrant-landing/content/documentation/guides/distributed_deployment.md
index 928cd1627..6431b5318 100644
--- a/qdrant-landing/content/documentation/guides/distributed_deployment.md
+++ b/qdrant-landing/content/documentation/guides/distributed_deployment.md
@@ -380,15 +380,19 @@ client
```
+
+* When using custom sharding, IDs are only enforced to be unique within a shard key. This means that you can have multiple points with the same ID, if they have different shard keys.
+This is a limitation of the current implementation, and is an anti-pattern that should be avoided because it can create scenarios of points with the same ID to have different contents. In the future, we plan to add a global ID uniqueness check.
+
Now you can target the operations to specific shard(s) by specifying the `shard_key` on any operation you do. Operations that do not specify the shard key will be executed on __all__ shards.
+Another use-case would be to have shards that track the data chronologically, so that you can do more complex itineraries like uploading live data in one shard and archiving it once a certain age has passed.
+
+
+
### Shard transfer method
*Available as of v1.7.0*
diff --git a/qdrant-landing/static/docs/sharding-per-day.png b/qdrant-landing/static/docs/sharding-per-day.png
new file mode 100644
index 000000000..05021c66a
Binary files /dev/null and b/qdrant-landing/static/docs/sharding-per-day.png differ