2 docs tagged with "Storyblok CMS"

You can implement a solution based on this recipe that converts a commercetools cart to an order after authorizing payment with the Adyen payment provider. This approach should apply to almost any commerce and payment system integration and wherever one web service depends on the response from another.

In the following recipe, we will merge content items from the CMS with product records from a commerce engine in order to populate product pages, whether a Product Detail Page (PDP), Product Listing Page (PLP), landing page, or anywhere products are featured with extended information. This is a typical use case in a headless commerce implementation -- needing to match up additional data with product data, be it pricing or inventory or product care instructions. Frequently developers write glue code in the frontend to address this use case and end up making multiple API calls and stitching together data from the backends. An orchestration layer can configure this data unification.