Skip to main content

Hearing about other customer or partner examples to share with others is always helpful when sharing commercetools roadamp announcements.   One feature update that continues to be on our Roadmap is updates to Standalone pricing.  Some early projects may have gone live with ct Embedded pricing, but now that commercetools has continued to enhance Standalone pricing, I think it would make sense for a project to consider cutting over.

Are there any other reasons why someone has decided to switch to Standalone pricing?  (Outside of some of the obvious reasons like limit improvements).  Was this a high LOE for a team to do?

Hi @Ben Hedrick ,

At he beginning of our project We decided to use StandalonePrice because there are scenarios where the client will have already a price but not a product definition or vice-versa.

It is important to mention that We are loading the catalog using the Import APIs.

Standalone pricing helped us to create the price independently from the catalog feed, and this was our main driver.

 

However later We decided to implement external pricing, but that is another story…(perhaps other thread)

Regards,

Obed

Reply


Terms & ConditionsCookie settings
© 2024 commercetools GmbH - All rights reserved