Examples of ECS connections with Commerce Connect?
Examples of ECS connections with Commerce Connect?
Sitecore commerce connect with ECS
The Commerce Connect core framework contains a number of generic, extensible abstract service layers that work with different external commerce systems.
The Commerce Connect service layers:
When you build an e-commerce solution using Commerce Connect, you should use the APIs in the Commerce Connect service layers instead of directly accessing the APIs in the external commerce system. The reasons for this are:
Using sitecore commerce connect we can connect with external commerce system
There are some of the demo videos and solution for sitecore commerce connect connector with ECS
Refer the below URLs for sitecore commerce connect with nopcommerce
connector:nopcommerce connector
PreRequisites and installation guide for sitecore commerce connect with ECS(nopcommerce)
Installation guide and code base
nopcommerce -installation guide
video instructions:nopcommerce with sitecore commerce connect part-1
nopcommerce with sitecore-2
ucommerce connector for sitecore
ucommerce connector for sitecore https://xchangesitecore.com/examples-of-ecs-connections-with-commerce-connect/ Vikash Raaj
The Commerce Connect core framework contains a number of generic, extensible abstract service layers that work with different external commerce systems.
The Commerce Connect service layers:
- Carry essential e-commerce information between the webshop solution and the back-end e-commerce system(s).
- Encapsulate and provide an abstraction of the business logic of the external commerce system(s).
- Track and follow-up visitor behavior. They provide new goals, page events, marketing automation campaigns, and reports.
When you build an e-commerce solution using Commerce Connect, you should use the APIs in the Commerce Connect service layers instead of directly accessing the APIs in the external commerce system. The reasons for this are:
- The customer engagement is built into the service layers. If the service layer APIs are not used, the built-in commerce scenarios for personalization, reporting, and marketing automation are not triggered or deployed.
- Some external commerce systems do not support all the scenarios that Commerce Connect supports. Therefore, you should use the Commerce Connect APIs to benefit from the fallback functionality built into Commerce Connect.
- If you make customizations and extensions to the APIs to accommodate unique features in one external commerce system, the features will not necessarily be supported in another commerce system. Using the standard Commerce Connect APIs lets you replace the external commerce system with a minimum of effort.
- In case multiple external systems are integrated using the Connect pipelines, you only have to call the Connect APIs as a single point of entry, rather than calling each external system individually.
Using sitecore commerce connect we can connect with external commerce system
- sitecore commerce connect with Insight commerce
- Ucommerce connector for sitecore
- nopcommerce for sitecore
There are some of the demo videos and solution for sitecore commerce connect connector with ECS
Refer the below URLs for sitecore commerce connect with nopcommerce
connector:nopcommerce connector
PreRequisites and installation guide for sitecore commerce connect with ECS(nopcommerce)
Installation guide and code base
nopcommerce -installation guide
video instructions:nopcommerce with sitecore commerce connect part-1
nopcommerce with sitecore-2
ucommerce connector for sitecore
ucommerce connector for sitecore https://xchangesitecore.com/examples-of-ecs-connections-with-commerce-connect/ Vikash Raaj
Comments
Post a Comment