spryker · lenadoc · Sep 21, 2023 · Sep 21, 2023 · Sep 21, 2023 · Sep 21, 2023
diff --git a/_data/sidebars/scos_dev_sidebar.yml b/_data/sidebars/scos_dev_sidebar.yml
@@ -4240,21 +4240,6 @@ entries:
       include_versions:
       - "202204.0"
       nested:
-      - title: Punchout Catalog
-        include_versions:
-      - "202204.0"
-    - title: Punchout Catalog feature integration
-      url: /docs/scos/dev/technology-partner-guides/order-management-erpoms/punchout-catalogs/punchout-catalog-feature-integration.html
-      include_versions:
-      - "202204.0"
-    - title: Eco - Punchout Catalogs feature integration
-      url: /docs/scos/dev/technology-partner-guides/order-management-erpoms/punchout-catalogs/eco-punchout-catalogs-feature-integration.html
-      include_versions:
-      - "202204.0"
-    - title: Eco - Punchout Catalogs + Product Bundles feature integration
-      url: /docs/scos/dev/technology-partner-guides/order-management-erpoms/punchout-catalogs/eco-punchout-catalogs-product-bundles-feature-integration.html
-      include_versions:
-      - "202204.0"
     - title: Payment partners
       nested:
         - title: Adyen

diff --git a/_data/sidebars/scos_user_sidebar.yml b/_data/sidebars/scos_user_sidebar.yml
@@ -997,27 +997,6 @@ entries:
       - "202005.0"
       - "202009.0"
       nested:
-      - title: Punch Out
-        include_versions:
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-        nested:
-        - title: Punch Out
-          url: /docs/scos/user/features/technology-partner-integrations/punch-out/punch-out-feature-overview.html
-          include_versions:
-          - "201907.0"
-          - "202001.0"
-          - "202005.0"
-        - title: Punchout
-          url: /docs/scos/user/features/technology-partner-integrations/punch-out/punchout.html
-          include_versions:
-          - "202009.0"
-        - title: Punchout
-          url: /docs/scos/user/features/technology-partner-integrations/punch-out/punchout-feature-overview.html
-          include_versions:
-          - "202009.0"
       - title: Integrating technology partners
         url: /docs/scos/user/features/technology-partner-integrations/integrating-technology-partners.html
         include_versions:
@@ -3265,25 +3244,6 @@ entries:
         - "202009.0"
         - "202108.0"
         - "202204.0"
-      - title: Punchout Catalogs
-        url: /docs/scos/user/technology-partners/order-management-erpoms/punchout-catalogs.html
-        include_versions:
-        - "201903.0"
-        - "201907.0"
-        - "202001.0"
-        - "202005.0"
-        - "202009.0"
-      - title: Punchout Catalogs
-        url: /docs/scos/user/technology-partners/order-management-erpoms/punchout-catalogs/punchout-catalogs.html
-        include_versions:
-        - "202108.0"
-        - "202204.0"
-        nested:
-        - title: Punchout Catalogs overview
-          url: /docs/scos/user/technology-partners/order-management-erpoms/punchout-catalogs/punchout-catalogs-overview.html
-          include_versions:
-          - "202108.0"
-          - "202204.0"
     - title: Marketplace Integrations
       nested:
       - title: ChannelPilot Marketplace

diff --git a/_includes/pbc/all/install-features/202204.0/install-the-product-bundles-feature.md b/_includes/pbc/all/install-features/202204.0/install-the-product-bundles-feature.md
@@ -287,11 +287,3 @@ console data:import product-concrete
 Ensure that, in the database, the configured data has been added to the `spy_product_bundle` table and the `product_bundle` publishing has been triggered.
 
 {% endinfo_block %}
-
-## Related features
-
-Integrate the following related features:
-
-| FEATURE | REQUIRED FOR THE CURRENT FEATURE | INTEGRATION GUIDE |
-| --- | --- | --- |
-| Product Bundles + Punchout GUI |  | [Eco: Punchout Catalogs + Product Bundles feature integration](/docs/scos/dev/technology-partner-guides/{{page.version}}/order-management-erpoms/punchout-catalogs/eco-punchout-catalogs-product-bundles-feature-integration.html) |
diff --git a/docs/acp/user/intro-to-acp/acp-overview.md b/docs/acp/user/intro-to-acp/acp-overview.md
@@ -15,7 +15,7 @@ The App Composition Platform (ACP) lets Spryker Cloud Commerce Operating System
 
 The following apps are supported:
 
-- [Algolia](/docs/pbc/all/search/{{site.version}}/base-shop/third-party-integrations/integrate-algolia.html), a Search Engine
+- [Algolia](/docs/pbc/all/search/202307.0/base-shop/third-party-integrations/algolia/integrate-algolia.html), a Search Engine
 - [Payone](/docs/pbc/all/payment-service-providers/payone/integrate-payone.html), a Payment Service Provider (PSP)
 - [Usercentrics](/docs/pbc/all/usercentrics/integrate-usercentrics.html), a Consent Management Platform (CMP)
 - [Bazaarvoice](/docs/pbc/all/ratings-reviews/{{site.version}}/third-party-integrations/integrate-bazaarvoice.html), a platform for User-Generated Content (UGC)

diff --git a/...domain-model-and-relationships/customer-login-by-token-reference-information.md b/...domain-model-and-relationships/customer-login-by-token-reference-information.md
@@ -83,6 +83,4 @@ http://mysprykershop.com/access-token/eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImp0aS
 
 In the Spryker Commerce OS, token generation is performed using a facade method, which is why no GUI is present. To generate a token, see [HowTo: Generate a token for login](/docs/pbc/all/customer-relationship-management/{{page.version}}/base-shop/generate-login-tokens.html).
 
-Token-based authentication works closely with the [Punch Out](/docs/pbc/all/punchout/{{page.version}}/punchout-catalogs.html) feature. It lets B2B buyers log in from their ERP system to a Spryker company user account using a token without entering the username and password and to buy products from the Spryker ecommerce shop.
-
 To make the feature more flexible, we have implemented the functionality that lets you disable switching between the Business-on Behalf accounts. For example, if the user logs in to the pre-defined company account that has Business-on-Behalf feature integrated, the shop owner can disable the ability to switch between the accounts. In case the Business-on-Behalf is disabled, the company user logs in to the default account and can't switch between the company users within their company account.
diff --git a/...domain-model-and-relationships/customer-login-by-token-reference-information.md b/...domain-model-and-relationships/customer-login-by-token-reference-information.md
@@ -82,6 +82,4 @@ http://mysprykershop.com/access-token/eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImp0aS
 
 In the Spryker Commerce OS, token generation is performed using a facade method, which is why no GUI is present. To generate a token, see [HowTo: Generate a token for login](/docs/pbc/all/customer-relationship-management/{{page.version}}/base-shop/generate-login-tokens.html).
 
-Token-based authentication works closely with the [Punch Out](/docs/pbc/all/punchout/{{page.version}}/punchout-catalogs.html) feature. It lets B2B buyers log in from their ERP system to a Spryker company user account using a token without entering the username and password and to buy products from the Spryker ecommerce shop.
-
 To make the feature more flexible, we have implemented the functionality that lets you disable switching between the Business-on Behalf accounts. For example, if the user logs in to the pre-defined company account that has Business-on-Behalf feature integrated, the shop owner can disable the ability to switch between the accounts. In case the Business-on-Behalf is disabled, the company user logs in to the default account and can't switch between the company users within their company account.
diff --git a/...punchout/202212.0/install-features/install-the-eco-punchout-catalogs-feature.md b/...punchout/202212.0/install-features/install-the-eco-punchout-catalogs-feature.md
diff --git a/...0/install-features/install-the-eco-punchout-catalogs-product-bundles-feature.md b/...0/install-features/install-the-eco-punchout-catalogs-product-bundles-feature.md
Original file line number	Diff line number	Diff line change
Expand Up		@@ -83,6 +83,4 @@ http://mysprykershop.com/access-token/eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImp0aS

		In the Spryker Commerce OS, token generation is performed using a facade method, which is why no GUI is present. To generate a token, see [HowTo: Generate a token for login](/docs/pbc/all/customer-relationship-management/{{page.version}}/base-shop/generate-login-tokens.html).

		Token-based authentication works closely with the [Punch Out](/docs/pbc/all/punchout/{{page.version}}/punchout-catalogs.html) feature. It lets B2B buyers log in from their ERP system to a Spryker company user account using a token without entering the username and password and to buy products from the Spryker ecommerce shop.

		To make the feature more flexible, we have implemented the functionality that lets you disable switching between the Business-on Behalf accounts. For example, if the user logs in to the pre-defined company account that has Business-on-Behalf feature integrated, the shop owner can disable the ability to switch between the accounts. In case the Business-on-Behalf is disabled, the company user logs in to the default account and can't switch between the company users within their company account.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -82,6 +82,4 @@ http://mysprykershop.com/access-token/eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImp0aS

		In the Spryker Commerce OS, token generation is performed using a facade method, which is why no GUI is present. To generate a token, see [HowTo: Generate a token for login](/docs/pbc/all/customer-relationship-management/{{page.version}}/base-shop/generate-login-tokens.html).

		Token-based authentication works closely with the [Punch Out](/docs/pbc/all/punchout/{{page.version}}/punchout-catalogs.html) feature. It lets B2B buyers log in from their ERP system to a Spryker company user account using a token without entering the username and password and to buy products from the Spryker ecommerce shop.

		To make the feature more flexible, we have implemented the functionality that lets you disable switching between the Business-on Behalf accounts. For example, if the user logs in to the pre-defined company account that has Business-on-Behalf feature integrated, the shop owner can disable the ability to switch between the accounts. In case the Business-on-Behalf is disabled, the company user logs in to the default account and can't switch between the company users within their company account.