Practical, experience-driven writing on Salesforce Commerce Cloud, the wider Salesforce Platform, and software engineering — no fluff, just what actually worked in production.
Interactive tools and hands-on environments built for Salesforce Commerce Cloud engineers and architects.
Interactive quizzes for testing and strengthening Salesforce Commerce Cloud knowledge.
Practice Salesforce Commerce Cloud concepts and Business Manager workflows in a free, hands-on environment.
Independent technical reports on Salesforce Commerce Cloud cartridges, covering implementation, dependencies, compatibility, and engineering considerations.
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.
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.
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.
Bite-sized facts and re-thoughts straight from LinkedIn.
Pushing URL Rule settings from Staging to Production requires selecting BOTH the Catalogs and Libraries data replication groups.
If a merchandiser fills in the explicit pageURL attribute, it completely overrides your configured URL syntax rules.
The wildcard pattern sitemap*xml is strictly reserved for Salesforce B2C Commerce's internal automated sitemap generator.
Why I built a cartridge audit tool to help Salesforce Commerce Cloud teams evaluate the engineering health, performance, maintainability, security, and technical debt of existing cartridges before bringing them into production.
For a long time I thought technical debt only meant messy code. Working on production SFCC projects taught me that the real cost is much bigger.
A look into my engineering mindset for reviewing Salesforce Commerce Cloud cartridges, identifying hidden risks, and why maintainability matters more than simply having working code.
Every article is based on personal, hands-on work — not theory copied from documentation.
Nothing here is copied as-is. Every explanation is rebuilt in plain language from first principles.
Complex jargon is translated into something you can actually use on Monday morning.
Articles and concepts are reinforced with hands-on questions powered by Quizerva.
Have an SFCC or Salesforce story worth telling? Let's put it into words.