SFCC Cartridge Reports
Independent technical reports on Salesforce Commerce Cloud cartridges. Explore implementation details, dependencies, compatibility, and engineering considerations before adopting, upgrading, or maintaining a cartridge.
Cartridge Reports
Independent technical reviews of Salesforce Commerce Cloud cartridges and integrations.
Publisher: Adyen
The Adyen SFRA cartridge (v26.2) demonstrates a highly robust payment integration layout, featuring a modular architecture, comprehensive workflow diagrams, and strict security compliance. Key strengths include extension via prepend/append middleware and decoupled asynchronous webhook processing using Custom Object queues. The assessment identified localized recommendations to optimize transaction boundaries and background job scalability, ensuring robust operation under high transaction volumes.
Publisher: Cloudinary
The Cloudinary integration is a mature media integration cartridge using Salesforce Service Framework services and SFRA extension patterns to integrate Cloudinary media capabilities into SFCC storefronts. The assessment identified localized areas for engineering review, including upgradeability details under template shadowing and transaction handling logic. Addressing these details would further improve the cartridge's overall health and maintenance profile.
Publisher: WorldPay
The cartridge provides broad payment integration capabilities, including tokenization, webhook processing, refunds, partial capture, 3DS/SCA, PCI scope reduction, multi-currency support, and fraud signal passing. It also demonstrates several sound SFCC engineering practices, including use of the service framework, append/prepend patterns, page caching, and asynchronous webhook processing. However, the assessment identified several areas requiring remediation before the cartridge should be considered enterprise-ready, including order access controls, credential storage, transaction handling, session data usage, large-scale job processing, model/template shadowing, and the absence of unit tests. Overall, the cartridge is functionally capable but requires targeted engineering improvements, particularly around security, platform governance, upgradeability, and maintainability.
int_aci
Publisher: ACI
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_afterpay
Publisher: Afterpay
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_apruvd
Publisher: Apruvd
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_bolt
Publisher: Bolt
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_chaching
Publisher: Chaching
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_chargeafter
Publisher: Charge After
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
cloudinary-pwa-kit
Publisher: Cloudinary
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_flexpay
Publisher: Flexpay
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_lyra
Publisher: Lyra
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_mollie
Publisher: Mollie
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_monei
Publisher: MONEI
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
newrelic-logs
Publisher: New Relic
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_paidy
Publisher: Paidy
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_pixlee
Publisher: Pixlee
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_portone
Publisher: Portone
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_sequra
Publisher: Sequra
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_signifyd
Publisher: Signifyd
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_weareplanet
Publisher: Planet
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
int_woosmap
Publisher: Woosmap
Scheduled for independent engineering evaluation covering architecture, dependencies, configuration overhead, and platform compatibility.
About the Reports
Independent engineering reference material documenting observable SFCC cartridge implementation patterns.
Examining Implementation Realities, Not Marketing Claims
In Salesforce B2C Commerce, third-party cartridges sit directly in your application’s cartridge path. When you adopt a cartridge, you are not simply enabling an isolated feature or calling a SaaS API—you are introducing custom code directly into your controller pipeline, hook registrations, and request lifecycle.
Every cartridge brings its own architectural patterns, third-party libraries, Business Manager configurations, and ongoing maintenance requirements. A cartridge can be functional, well-documented, and widely used in production while still introducing silent architectural debt, quota risks, or upgrade friction.
SFCC Cartridge Reports are independent technical reference documents created by experienced B2C Commerce engineers. Their purpose is to document what can be directly observed from the codebase, service framework configurations, schemas, and release documentation. By providing developer-level transparency into cartridge internals, these reports help engineering teams, technical architects, and merchants understand code quality, integration mechanisms, and operational trade-offs before adopting, inheriting, or upgrading a cartridge.
Salesforce, Commerce Cloud, SFRA, and Demandware are trademarks or registered trademarks of Salesforce, Inc. This independent research project is not affiliated with or endorsed by Salesforce.