How can composable commerce support performance for cross-sell, up-sell and substitutions?

Whatever you use for your backend, all the numerous automatic user interfaced will require coding. However, the important element to take into account is how closely coupled or controlledwill your front-ends be into the backend. If you’re not using composable commerce for a service, it is going to like quite tightly control and couple and will limit your abilities or make execution harder.

See our products:

What exactly does that mean?

Platform limitations will be the largest cost of most traditional execution. Whether you use a SaaS established or on-premise variant of a legacy platform, minor changes like adding a cross-sell connection to your products catalogue, in addition to bigger changes like extending customer information, will require custom development and database modifications. These kinds of customizations raise your technical debt and slow future advancement.

But for a Composable Commerce structure, to execute cross-sell, substitutions or other merchandise relationships, all that’s required is a simple API call to bring the relationship. Similarly, for more complicated customizations, it is simply a few more API calls to configure the data structure changes.

Cross-Sell Example Request

Elastic Path Commerce Cloud is your first composable commerce platform. To execute cross-sell from a brand-new example of an Elastic Path shop, there are 3 steps.

Step 1: Enable the goods extended data container

The response of the request includes the ID for this container. That ID is going to be used in Step 2.

Step 2: Insert the Cross-Sell connection to the goods"stream" ("flow" is the is the name of the instrument used to produce the container)

as soon as you’ve got the container created, the next step is to add the area. Below is the payload used to make the Cross Sell area. They key takeaways from this section is to ensure:

  • “field type” is set to”relationship”
  • the validation rules say”type” is set to”one-to-many” relationship
  • the validation rules say”into” is set to the”product”

The remaining fields are rather self-explanatory. Therefore, in this instance you’re about products to other goods. These kinds of relationships can be leveraged for numerous use cases.

Step 3: Start adding products to the connection

Now that your Cross-sell relationship area is set up, you just have to begin adding products to the area. This is achieved by calling the connection end-point created when you made the cross-sell field.

POST the collection of product IDs into the next endpoint where undefined equals the product you’re updating.


The origin of those product references may come from your merchandising group, 3rd party tools or analytics or where you choose.

Related posts:

Contain the information when you want it

When the connection is set it can be recovered with the normal products API call. To regain the cross sell products, simply add “include=cross_sell_ids” into the query string of the merchandise endpoint to add product information for all the related goods in one request to the API.

Example: Include=cross_sell_ids

The answer: The figure below shows the response that has the cross_sell solutions. The response comprises two different relationship types. The first is”main_image” that is an integrated relationship between the item and its principal image. The second is that the one we just created and populated.

From the”data” array, the initial object is the product we’re requesting. Towards the end of the answer is another thing named”included” at which the details of the products listed above in the relationships item”cross_sell_id” that is the listing of product_ids which are cross sell things. These are sample products composed of information from placeholder content websites from around the net. My favourite is for producing creative paragraphs of text for descriptions. However, I digress.

This is solely a single case of adding a cross sell connection with Elastic Path. If you would like to add connection like “Substitutions”, all you’ll have to do is repeat steps 2 and 3. The same thing goes for adding an”Up-Sell” connection also. For each extra area, you create a single API call to the platform.

To extend different items such as Customers or Orders or Carts, the routine is exactly the same. Step 1, make the container, step two add the fields and step 3, insert the information. No other platform is much easier to extend the information or APIs.

Why is this so significant?

The resulting changes are instantaneous. They become a part of the API and don’t need any coding to make. Objects can be linked to themselves or to other items. Another typical example is a customer wishlist. To create a client”wishlist”, you’d create a connection field on the Client object that’s a one-to-many connection to products. The choices this approach creates is almost infinite.

See also:

Feature or Capability

If you asked me if”Wishlists” were an”Out-Of-The-Box” characteristic of Elastic Path we’d say”No”. But, Elastic Path is more than capable of simply implementing wishlists or other kinds of relationship functions with some API calls.

Inversely, consider how many features that come as an out-of-the-box attribute in different platforms you don’t use but still need to maintain the code around. By maintaining the platform clean and simple, and using API calls for just the functionality you would like, we empower extension without complications.