Configuring Back-in-Stock Notifications

Catalog Feed

Catalog Feed from Commerce Cloud to Marketing Cloud Engagement

Use the Marketing Cloud Connector for Commerce Cloud to send a regular catalog feed.

The default catalog feed configuration sends the onlineAvailability flag. However, this flag indicates that the product is set to be available online and not that it is in stock or out of stock. Override the catalog feed script to use the getAvailabilityModel().isInStock() method and output it in the feed.

Catalog Importing in Engagement

Import the catalog into a data extension using Automation Studio. Create a data extension using the product catalog field list described in Einstein Recommendations Catalog Field Definitions.

If you’re using or planning to implement Einstein Recommendations, you can instead use the catalog import in Engagement, setting the schedule options as appropriate. Set the import notification settings to monitor the success or failure of the import.

Back-in-Stock Notifications

Create a Notification Sign-Up on the Product Detail Page

• Override the productAvailability.isml in a new cartridge.
• Render an alternative template if the stock is unavailable.
• Use a form to capture the notification request.
• Use a controller to handle the UI request and pass it to model.
• Use a model to invoke the b2c-crm-sync ServiceMgr to send the request to Service Cloud.

Create a Service Cloud Flow to Receive the Notification Requests

• The flow resolves the customer to a contact record or creates a contact.
• The flow creates an associated Back In Stock Notification custom object record with:
  • Master and detail relationship to the contact record
  • Product ID and SKU
  • Status of requested or sent

Use MC Connect to connect Service Cloud and Engagement. Consider using a multi-org setup.

After setup, use Contact Builder to configure synchronized data sources. Select only the objects and fields that you require. We recommend the contact object and the Back In Stock Notification custom object.

Depending on the configuration of your Service Cloud, sync other prerequisite objects.

Deliver Back-in-Stock Notification Emails with Engagement

Use Content Builder to create the emails. Ensure that your email is created with a link to the product display page to let customers directly access the product from their inbox.

Create a data extension to use as the entry source for the journey in Journey Builder.

Use Automation Studio to create an automation. Use the SQL query to create the audience based on the stock now being available. Ensure that the SQL query collects the required fields across the sync data extensions and product catalog IGO_Products (or user-created product) data extension. Ensure that the SQL query adds the contacts to the journey data extension.

Suggested fields are:Ensure that the SQL query collects only records where the status of the back-in-stock notification is requested. Append only new records into the journey data extension.

• ContactID
• EmailAddress
• SkuID
• ProductName
• ProductLink
• ImageLink
• BIS_ID (the ID of the back-in-stock notification record from the synchronized data extension)

Create your journey using the data extension as your entry source, evaluating new record entries. Create at least two journey activity steps. The first step sends the email, and the second step updates the back-in-stock notification record status to sent. This journey prevents more than one notification from being sent for each logged request.

Configure your automation and journey to run daily after the product catalog import completes.

Use Service Cloud to create required reports on back-in-stock notification sign-ups, for example, to share with stock management.

Get insights about shopper purchases using Google Analytics 360.

Related Content

Review earlier steps in this solution. Back-in-Stock Notification Workflow Back-in-Stock Design Considerations Integration Reference Implementations for Back-in-Stock Notifications