diff --git a/doc/service_design/catalogs.md b/doc/service_design/catalogs.md
index b34701caef6638c277f43d3257a2e4f8c509cdd9..9464877f5f50fddffcc336f02c36946aaf16393a 100644
--- a/doc/service_design/catalogs.md
+++ b/doc/service_design/catalogs.md
@@ -1,6 +1,6 @@
 # Catalogs and Templates
 
-The OpenSlice Service Catalogue (accessible through the API or Services portal) contains the representation of Service Specifications, either created from the provider defining service attributes, or by supporting the GSMA Generic Slice Templates (GST) as well as the VINNI Service Blueprint. The following scenarios are supported by the OpenSlice Service Catalogue.
+The OpenSlice Service Catalogue (accessible through the API or Services portal) contains the representation of Service Specifications, either created from the provider defining service attributes, or by supporting the GSMA Generic Slice Template (GST). The following scenarios are supported by the OpenSlice Service Catalogue.
 
 
 ## Create/Design a Service Specification
@@ -91,6 +91,9 @@ See more on [Consuming Services From External Partner Organizations]( ../getting
 
 ## Probe further
 
-[Design Kubernetes-based Service Specifications](./kubernetes/exposing_kubernetes_resources.md/)
+Design and expose services based on:
 
-[Design NFV/OSM-based Service Specifications](./nfv/design_nfv_services.md)
+* [Containerized resources via the Kubernetes Operator pattern](./kubernetes/exposing_kubernetes_resources.md)
+* [NFV artifacts](./nfv/design_nfv_services.md)
+* [Monitoring sources](./monitoring/design_monitoring_services.md)
+* [Generic, developer-owned controllers](./generic/design_generic_services.md)
diff --git a/doc/service_design/intro.md b/doc/service_design/intro.md
index 140c814639d6ed88eff06dfb17034240f06794b0..8916706ab4486add2b538d3ac28d640daf49f1e8 100644
--- a/doc/service_design/intro.md
+++ b/doc/service_design/intro.md
@@ -3,17 +3,10 @@
 **Intended Audience: OpenSlice Service Designers**
 
 
-This section offers details on how to design Service Specifications and expose them in Service Catalogs
+This section offers details on how to design Service Specifications and expose them in Service Catalogs.
 
-Service Designers create detailed service specifications, which are then managed and exposed in service catalogs. These services are integrated into OpenSlice E2E service orchestration framework to automate and optimize the delivery of network services.
-
-
-OpenSlice can be used to design service specifications for various services, even not networking related services. Here we cover how service designers can expose services related to the NFV world and the containerized world.
-
-## Probe further
-
-* [Design and expose services based on containerized resources via the Kubernetes Operator pattern](./kubernetes/exposing_kubernetes_resources.md)
-* [Design and expose services based on NFV artifacts](./nfv/design_nfv_services.md)
+Service Designers create detailed Service Specifications, which are then managed and exposed in Service Catalogs. These services are integrated into OpenSlice end-to-end service orchestration framework to automate and optimize the delivery of network services.
 
+OpenSlice can be used to design Service Specifications for various services, even not networking related ones. Here we cover how Service Designers can expose services, related to the cloud world (containerized/Kubernetes and NFV), monitoring domain, or even generic developer-owned ones.
 
 
diff --git a/doc/service_ordering/images/service_marketplace.png b/doc/service_ordering/images/service_marketplace.png
new file mode 100644
index 0000000000000000000000000000000000000000..c590119c86f899b157021b666411c3b1aabb3459
Binary files /dev/null and b/doc/service_ordering/images/service_marketplace.png differ
diff --git a/doc/service_ordering/images/service_order_checkout.png b/doc/service_ordering/images/service_order_checkout.png
new file mode 100644
index 0000000000000000000000000000000000000000..744dc9fe561d6b9076ff6eb2c7bc1a5672a86913
Binary files /dev/null and b/doc/service_ordering/images/service_order_checkout.png differ
diff --git a/doc/service_ordering/images/service_order_preview.png b/doc/service_ordering/images/service_order_preview.png
new file mode 100644
index 0000000000000000000000000000000000000000..300c4c224d4296263117cbbb4eed353794a07f1c
Binary files /dev/null and b/doc/service_ordering/images/service_order_preview.png differ
diff --git a/doc/service_ordering/images/service_order_preview_completed.png b/doc/service_ordering/images/service_order_preview_completed.png
new file mode 100644
index 0000000000000000000000000000000000000000..0c94363959f48f50c58f876dc858c4be4fa446b9
Binary files /dev/null and b/doc/service_ordering/images/service_order_preview_completed.png differ
diff --git a/doc/service_ordering/images/service_preview.png b/doc/service_ordering/images/service_preview.png
new file mode 100644
index 0000000000000000000000000000000000000000..5e1fd9426f476517eac8f6a4feef45ecc3f65401
Binary files /dev/null and b/doc/service_ordering/images/service_preview.png differ
diff --git a/doc/service_ordering/ordering_services.md b/doc/service_ordering/ordering_services.md
index c88edca3e4f5f42a7bd560b66722a8bffed78876..57f95211b6ee66091c61dc926c2ec6e0334e1d38 100644
--- a/doc/service_ordering/ordering_services.md
+++ b/doc/service_ordering/ordering_services.md
@@ -2,4 +2,38 @@
 
 **Intended Audience: OpenSlice Users**
 
-_This section is WIP._
\ No newline at end of file
+Having covered how OpenSlice can facilitate the Service Design and exposure, this section introduces the process of ordering the designed Service Specifications and their fulfillment process.
+
+To that extend, we assume that the OpenSlice Service Designers have already created the designated, detailed Service Specifications that are willing to expose to the OpenSlice users, or to potential Communication Service Customers (CSCs). Furthermore, the designed Service Specifications are categorized in the respective Service Categories and Catalogs.
+
+## Service Marketplace
+
+The OpenSlice User can browse the Services Marketplace for available services. There is a designated Service Catalog Explorer that goes through all the available Catalogs and the respective Categories, as seen in the following figure.
+
+![Service Marketplace](./images/service_marketplace.png)
+
+The User can filter offered services within a Category, and when needed, preview a desired service for more information, as well as configurable/non-configurable characteristics.
+
+![Service Preview](./images/service_preview.png)
+
+Once satisfied, the User may place the selected service(s) in the Order List. An icon at the top-right part of the navbar presents the number of services in the Order List. Clicking that icon, the flow is navigated to the Service Order Checkout page.
+
+## Service Order Checkout
+
+Here, the User can see the Order List in detail and configure each Order Item. Specifically, all the configurable characteristics (if any) of a service can be altered and customized, as well as some general preferences, i.e. notes and Service Order duration.
+
+> The ultimate duration may differ from the one requested by the User, as it has to be approved by an Administrator.
+
+![Service Order Checkout](./images/service_order_checkout.png)
+
+## Service Order Preview
+
+When the User clicks the Order Service button from the previous step, a Service Order is created and saved in the respective database. A User can browse its issued Service Order(s) by the "My Service Orders" tab. A freshly issued Service Order acquires the state of *INITIAL*. By selecting a Service Order, the User navigates to the Service Order Overview and Management page. Here, once again, the User may change the requested duration, add notes towards the Administrator, or edit the respective Order Items (change the user-defined characteristics).
+
+![Service Order Overview](./images/service_order_preview.png)
+
+Once the Service Order is reviewed by an Administrator, the state is expected to switch to *ACKNOWLEDGED*, which signals that the order is ready to be processed by the orchestrator. When this happens, the state will switch once more to *IN PROGRESS* and eventually to *COMPLETED*, once the order is successfully fulfilled. At this stage, the User can browse each Order Item and navigate to the created service instances in the Service Inventory. Each service contains relevant information about its execution and deployment and can also be edited.
+
+![Service Order Overview - Completed](./images/service_order_preview_completed.png)
+
+The User can edit the created Services or opt to terminate the Service Order earlier than the requested duration, by selecting the Order Item and click on the termination icon.
\ No newline at end of file