b2c-custom-job-steps

Create custom batch job steps for Salesforce B2C Commerce cartridges.

51|16|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/SalesforceCommerceCloud/b2c-developer-tooling --skill b2c-custom-job-steps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-custom-job-steps
Source: https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/tree/main/skills/b2c/skills/b2c-custom-job-steps
Command: npx skills add https://github.com/SalesforceCommerceCloud/b2c-developer-tooling --skill b2c-custom-job-steps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Custom job steps for Salesforce B2C Commerce batch processing can be complex and repetitive. This skill provides a structured approach to define and implement both task-oriented and chunk-oriented steps within a cartridge, promoting reuse and consistency.

Core Features & Use Cases

  • Steptypes.json driven definitions: Centralize step configuration at cartridge root using steptypes.json.
  • Task-oriented and chunk-oriented steps: Support for single operations and bulk processing with lifecycle hooks.
  • Use cases: Create a product export job, customer data sync, or maintenance tasks by implementing script modules under cartridge/scripts/steps and referencing them in steptypes.json.

Quick Start

Place steptypes.json at the cartridge root, implement your step modules under cartridge/scripts/steps, and run or invoke through the CLI/UI to execute batch jobs.

Frequently Asked Questions about b2c-custom-job-steps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom batch steps for Salesforce B2C Commerce?

Custom batch steps for Salesforce B2C Commerce are created by defining step configurations in steptypes.json at the cartridge root and implementing script modules under cartridge/scripts/steps. This structure supports both task-oriented and chunk-oriented processing.

What is the difference between task-oriented and chunk-oriented batch processes in B2C Commerce?

Task-oriented batch processes execute single operations, while chunk-oriented processes handle bulk data processing with lifecycle hooks. Both are supported within the cartridge environment for use cases like data imports, exports, and synchronization.

How does steptypes.json manage custom job steps in a B2C cartridge?

Steptypes.json manages custom job steps by centralizing step configuration at the cartridge root. It references the script modules implemented under cartridge/scripts/steps, promoting reuse and consistency for scheduled jobs and data synchronization.

Can I use custom job steps for product exports and customer data sync in B2C Commerce?

Yes, custom job steps can be used for product exports and customer data sync in B2C Commerce. You implement the specific logic as script modules under cartridge/scripts/steps and register them in steptypes.json for execution.

Where do script modules for custom batch steps need to be placed in a B2C cartridge?

Script modules for custom batch steps must be placed under the cartridge/scripts/steps directory. This enforces a structured approach within the cartridge environment, ensuring they are correctly referenced by the root steptypes.json file.