B2C Commerce Headless Integration for ISV Partners - Overview & FAQ

Frequently Asked Questions (FAQs)

What is PWA Kit?

The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and our commerce-react-sdk. It provides our customers with a more flexible and agile approach to building and maintaining modern shopping experiences. PWA kit allows merchants to quickly spin up fully functioning headless storefronts that are connected to their Salesforce Commerce Cloud instance.

Headless Commerce Integration Patterns

B2C Commerce Headless integrations come in a variety of flavors. Integrations will follow several patterns, depending on whether they include front-end and back-end modifications. The table below provides guidance on what customers should expect for different patterns.
 

Are there any prerequisites that an ISV must have to start developing a composable storefront solution?

• You must be an active B2C Commerce (ISV) Partner - check out our B2C Commerce ISV Partner Onboarding Guide if you are not yet an ISV Partner
• You must have access to Account Manager
• You must complete our ‘Get Started with Headless Development’ course on Partner Learning Camp
• Developer experience with B2C Commerce API
• Developer experience with B2C Commerce Cartridges
• Developer experience with React and Node/Express.js

How does a Composable Storefront back-end integration differ from an SFRA cartridge?

Composable Storefront back-end integrations and SFRA cartridges are B2C cartridges. The main difference is that a back-end integration for a composable storefront is strictly focused on backend behavior. This integration is tasked with handling any back-end logic that cannot be completed in the front end. The integration is connected to a front-end component via APIs. Whereas an SFRA cartridge has both backend and front-end manipulation. These integrations are completely coupled and follow our architecture patterns that can be web services-based or file-based.

How does Managed Runtime work with the Composable Storefront?

Every Composable Storefront must have a project created in Runtime Admin for managing deployments. Managed Runtime (MRT) provides the infrastructure to deploy, host, and monitor your Composable Storefront. Here, the storefront code that runs in an environment is called a bundle. You can manage multiple environments from MRT such as production, development, or testing environments to better manage and maintain your storefronts.

From each MRT environment, we use a combination of React, Node, and Express frameworks to run the App Server to create these dynamic and fast websites. For more information on setting up and using Managed Runtime refer this guide on Managed Runtime Overview.

Managed Runtime is crucial in the development process for ISVs. Through the use of the Managed Runtime APIs, ISVs and merchants can set up their environmental variables and secrets for the integrations that are used in their composable storefronts. 

What is a B2C Commerce Headless integrations listing on AgentExchange?

B2C Commerce ISV Partners can list their integration is the AgentExchange either as B2C Commerce Headless Integration if your integration satisfies the requirements listed in the above table.

You can select the Listing Type as API and B2C Commerce Headless Integration while creating your AgentExchange listing via the publishing console. You can use either Composable Storefront or Headless Integration (API-only) in your listing name & descriptions based on the following conditions

1. Composable Storefront - Your integration should qualify either one of the integration sub-types listed under B2C Commerce Headless Integration in the table above.
   1. Sample AgentExchange listing name: Appy Enterprises Payment Composable Storefront for B2C Commerce
2. Headless Integration (API-only) - Your integration is a Connect Apps (API-only) sub-types listed under B2C Commerce Headless Integration in the table above.
   1. Sample AgentExchange listing name: Appy Enterprises Payment Headless Integration for B2C Commerce

What is required to get a B2C Commerce Headless Integration listing on AgentExchange?

To meet the needs of our customers’ developers and architects, we’re looking for the following to be listed as Headless capable.

1. The ISV Partner must have a publicly available REST API or SDK for facilitating integrations.
2. The ISV Partner must have an integration guide on how to implement the solution with Salesforce Commerce APIs.
3. Any resources of significant value to the developer can be included part of the headless integration, but are not required. Assets such as React components that work with our Composable Storefront or a sample app that demonstrates how the various bits come together are encouraged. ISV Partners are advised to host these assets in their website.

Why should I provide a B2C Commerce Headless Integration listing?

B2C Commerce is a clear leader in the enterprise eCommerce market and we see trends develop quickly. While mostly sophisticated customers are adopting Headless, just about every customer and prospect is looking at Headless to reap the benefits it offers. Consider this projection from Gartner: By 2023, 50% of new commerce capabilities will be incorporated as API-centric SaaS services.

What resources I will need to develop a B2C Commerce Headless Integration?

ISV partners who will be integrating with Composable Storefront, they will need access to Managed Runtime to deploy any example PWA Kit integrations.

Requirements:

• The ISV Partner must be an active B2C Commerce (ISV) Partner
• The ISV Partner must have access to Account Manager
• The ISV Partner must complete the course: Get Started with Headless Development (Provisions Version) in the Partner Learning Camp.
• Partners must complete PWA Kit & Managed Runtime workshop training before being fully provisioned.
  • SI partners need to sign up their team for upcoming live workshop for PWA Kit and Managed Runtime, via the Enablement Calendar here: https://salesforce.quip.com/RdSPATbTdy4i

If you have completed the workshop and the Managed Runtime access has not been provisioned yet, please log a case via the Help Portal:

• Select your Partner Org in the top-right dropdown menu.
• Select ‘Create a Case’ > Inquiry Type: ‘Partner Program Support’
• In the Product field, select 'Partner Programs & Benefits'.
• In the Topic field, select 'B2C Commerce ISV Partners'.
• In the Subject, add 'B2C Commerce Partner Managed Runtime Request'
• In the Description, add the URL for the Environment in Managed Runtime where the bundles created during completion of the PLC Curriculum were deployed (format should be https://<project>-<environment>.mobify-storefront.com)

The ISV partner will then be responsible for adding users in Account Manager with the Managed Runtime User role, which will allow them to log into https://runtime.commercecloud.com for access.

How do I submit my Listing?

An AgentExchange listing is the storefront for your solution and is the best way to close new business. Publishing your listing is the first step to acquiring new customers and generating user reviews. Publishing your listing is an easy, self-guided experience every step of the way.

Access the B2C Commerce ISV Partner Onboarding Guide for steps on how to create and publish your listing.

Does a B2C Commerce Headless Integration listing require certification?

B2C Commerce Headless Integration must adhere to applicable security guidelines as defined in the updated AgentExchange Partner Security Guidelines. In addition, Salesforce reserves the right to perform a security review of any solution at our sole discretion.

Keep in mind, the AgentExchange Partner Security Guidelines are not exhaustive. To secure your solutions, we encourage partners to follow all applicable enterprise security standards including Open Web Application Security Project (http://www.owasp.org/) (OWASP) guidance.

However, the Commerce Cloud Product Management team will be reviewing the integration guide for completeness. Also, Partners are required to include security best practices in their documentation.

As noted above, there is no requirement to use a Commerce Cloud Certified Developer. In most cases a Consulting partner will not be necessary to deliver a B2C Commerce Headless Integration listing.

Will a B2C Commerce Headless Integration listing cost me anything?

At this time, there is no additional cost nor additional contract terms for this listing type as it’s a discretionary program benefit. Exceptions apply for the On-Demand Sandbox usage - access the B2C Commerce ISV Partner Onboarding Guide for more details on the On-Demand Sandbox Pricing Policy.

Where will the B2C Commerce Headless Integration listing be published?

The B2C Commerce Headless Integration listings will be published on the AgentExchange Marketplace.

Are there more resources available for B2C Commerce Headless Integration listings?

Yes, there are additional resources.

• A guide template can be found here.
• An example documentation for all levels of implementation as well as the type of React components that are helpful can be seen at Algolia.
• Our friends over at Magnolia have posted a video in support of their integration guide and sample project with React component.
• For more about the Commerce APIs - visit the Salesforce Developer Center for B2C Commerce.
• For more about the PWA-Kit and Managed RunTime - take a look at the Trail that introduces PWA-Kit and Managed RunTime. There is also more detail available on the Salesforce Developer Center for B2C Commerce.
• Partners can sign-up and attend the virtual workshops on PWA Kit & Managed Runtime. 

How can I get a demo Composable Storefront and demo-managed runtime environment?

Check out our Get Started resources for the Composable Storefront. This documentation provides the instructions for setting up a brand new composable storefront by using our PWA Kit app generator.

Note: you will have to complete the ‘Get Started with Headless Development’ course on Partner Learning camp to gain access to Managed Runtime.