SFCC Cartridge

Essential knowledge

Changed on:

17 Apr 2025

Overview

This article covers key functionalities of the SFCC connector and considerations when setting up the connector.

Some feeds are covered by the out-of-the-box connector, whilst others might need to be added as customisations.
When setting up the connector, you must consider exception handling and monitoring.

Master Data
- Product Catalogue feed (SFCC → Fluent, GQL)
- Locations sync (Fluent → SFCC, GQL)
Order feed (GQL)
- FinancialTransaction feed (Event API)
Order update sync (GQL)
PDP Store Locator
- Default: uses SFCC inventory
- Optional: FOs call (GQL)
Availability Check
- PDP → Checkout FOs calls (GQL)
- Internal SFCC inventory drives PLP pages

Fluent → SFCC inventory feed not OOTB
Category/Product export:
- Category export job
- Standard product (SFCC = Master product) & Variant product (SFCC = Variation product) product export job
- The job will only upload entities which have been updated since the last successful upload. This logic is driven from the Product.lastModified and the ‘fluentUploaded’ and ‘fluentUploadedDate’ custom attributes on the Product object
- The default batch sizes are set to 50 and you can override this number buy inputting a value for the productExportBatchSize and categoryExportBatchSize preferences
- Limitations:
  - GQL is used, so product upsert solution via Event API is not supported (this includes orchestrated product status updates)
  - Must run category export job before product export job, and export standard products before variant products
Exceptions/Monitoring
- Configure job failure email notifications
- Fluent errors are logged in a custom SFSC object
- For order push failure: set order push max retries, and a custom attribute flagged against the order will be updated with relevant error details. Enable retires setting otherwise no retry on 401, etc.