14 docs tagged with "Commerce"

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.

This recipe uses DX Engine and DX Graph to provide an entry point for CPQ (Configure, Price and Quote) capabilities common in custom products, B2B/B2B2C use cases, and more. The product in this example is a custom couch, whose options we will populate in DX Graph and access from DX Engine. Prices are cumulative, with some options adding to the total cost, and others reducing it. Logic for the flow through elements lives in DX Engine.

This recipe explains how you can create a DX Engine Connection to the commercetools Commerce Engine.

This recipe demonstrates preparing and supplying product data for something like a highly detailed product comparison page. We are accessing data from multiple sources, and using Conscia to unify arrays of product data in real-time to deliver a richer and more performant web experience.

In the following recipe, we will walk through an add to cart flow that includes authentication and an inventory check before successfully adding a product to the cart. We will use Elastic Path Commerce Cloud APIs as well as an API mock service to serve in the place of external systems.

In the following recipe, we will walk through an add custom discount to cart flow that includes validating a user-supplied coupon code against an external promotions engine, and mapping that response back to the schema required by Elastic Path in order to add the custom discount. We will use Elastic Path Commerce Cloud APIs as well as an API mock service to serve in the place of external systems.

In the following recipe, we will walk through a flow where a merchant has marked an order fulfilled through their Order Management System (OMS). Conscia is listening for a webhook from the OMS, and marks the commerce order fulfilled and sends an SMS notification to the shopper letting them know their order is on the way. We will use Twilio and Elastic Path Commerce Cloud APIs as well as a Postman call to simulate a webhook event from an OMS.

You can implement a solution based on this recipe that retrieves an order from Commercetools, parsing the order identifier from either a typical DX Engine Context JSON format or from the structure of a webhook from the Adyen payment provider. This approach should apply to almost any commerce and payment system integration or any wherever incoming data formats contain the same data in different structures.

In the enterprise space, growth by merger is a common and successful strategy. However for the IT-facing teams, this kind of marriage can introduce duplicate systems - multiples of tax, content management, or search platforms servicing the frontend, but also multiple WMS, OMS and ERP systems in the backend. Customers could think they're placing one order, but multiple business units are receiving their own piece of the final delivery.

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.

You can implement a solution based on this recipe that retrieves a shopping cart from commercetools. The same approach would be applicable for other commerce vendors.

This recipe shows how to use Twilio SendGrid to send email messages, pulling subject, content, and recipient information from various sources. The Orchestration Component that sends the email is designed as a generic template that can be reused for many purposes.

In the following recipe, we will walk through a flow where a shopper checks out on the storefront and their payment is authorized and then captured following the merchant's order validation. We will use Stripe and Elastic Path Commerce Cloud APIs as well as a Postman call to simulate a webhook event from an Order Management System (or similar).

You can implement a solution based on this recipe that updates a shopping cart in Commercetools. The same approach would be applicable for other commerce vendors.