b2c-custom-objects

Manage custom business data in SFCC B2C Commerce via Script API and OCAPI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables developers to store and manage domain-specific data within Salesforce Commerce Cloud B2C, providing a centralized approach to persist custom information, configurations, and business entities across sites and global scopes.

Core Features & Use Cases

  • CRUD with Script API: Use CustomObjectMgr to create, read, update, and delete custom objects.
  • OCAPI Data Access: Expose and manage custom objects via OCAPI for external integrations (site-scoped and global).
  • Shopper Custom Objects (SCAPI): Read-only access to custom data from storefronts where appropriate.
  • Usage Patterns: Store site-specific configurations, integration caches, or business-entity data (e.g., loyalty or vendor data) and query across objects.

Quick Start

Create a site-scoped custom object type like SiteConfig with a key such as "myConfigKey" and read it from a script.

Frequently Asked Questions about b2c-custom-objects

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

FAQPage Schema
How do I store and manage custom business data in SFCC B2C Commerce?

Store custom business data in SFCC B2C Commerce by using the Script API's CustomObjectMgr for CRUD operations or OCAPI data endpoints for external integrations. This supports site-scoped and global configurations across storefronts.

Can I expose SFCC custom objects to external systems via OCAPI?

Yes, SFCC custom objects can be exposed and managed via OCAPI data endpoints for external integrations. Both site-scoped and global custom objects are supported, requiring appropriate permissions for the targeted object types.

How do I read site-specific configurations from a storefront in Salesforce Commerce Cloud?

Read site-specific configurations by creating a site-scoped custom object type like SiteConfig with a key, then retrieving it via the Script API. Shopper Custom Objects via SCAPI offer read-only access to this custom data from storefronts.

What permissions do I need to access custom objects in SFCC?

Accessing custom objects requires Script API access to CustomObjectMgr or OCAPI data endpoints, plus appropriate permissions for the defined object types. Shopper objects require additional permissions if storefront access is needed.

Does the B2C custom objects Skill support global configurations across multiple sites?

Yes, the Skill supports both site-scoped and global configurations. This allows you to persist custom information, integration caches, and business entities across multiple storefronts within Salesforce Commerce Cloud.

What are the limitations of using Shopper Custom Objects in SCAPI?

Shopper Custom Objects accessed via SCAPI are limited to read-only access from storefronts. Full CRUD operations require using the Script API's CustomObjectMgr or OCAPI data endpoints with appropriate permissions.