b2c-custom-objects
B2C Custom Objects
Custom objects store business data that doesn't fit into standard system objects. They support both site-scoped and organization-scoped (global) data, with full CRUD operations via Script API and OCAPI.
When to Use Custom Objects
| Use Case | Example |
|---|---|
| Business configuration | Store configuration per site or globally |
| Integration data | Cache external system responses |
| Custom entities | Loyalty tiers, custom promotions, vendor data |
| Temporary processing | Job processing queues, import staging |
Custom Object Types
Custom objects are defined in Business Manager under Administration > Site Development > Custom Object Types. Each type has:
- ID: Unique identifier (e.g.,
CustomConfig) - Key Attribute: Primary key field for lookups
- Attributes: Custom attributes for data storage
- Scope: Site-scoped or organization-scoped (global)
Script API (CustomObjectMgr)
Getting Custom Objects
var CustomObjectMgr = require('dw/object/CustomObjectMgr');
// Get a single custom object by type and key
var config = CustomObjectMgr.getCustomObject('CustomConfig', 'myConfigKey');
if (config) {
var value = config.custom.configValue;
}
Creating Custom Objects
var CustomObjectMgr = require('dw/object/CustomObjectMgr');
var Transaction = require('dw/system/Transaction');
Transaction.wrap(function() {
// Create new custom object (type, keyValue)
var obj = CustomObjectMgr.createCustomObject('CustomConfig', 'newKey');
obj.custom.configValue = 'myValue';
obj.custom.isActive = true;
});
Querying Custom Objects
var CustomObjectMgr = require('dw/object/CustomObjectMgr');
// Query with attribute filter
var objects = CustomObjectMgr.queryCustomObjects(
'CustomConfig', // Type
'custom.isActive = {0}', // Query (uses positional params)
'creationDate desc', // Sort order
true // Parameter value for {0}
);
while (objects.hasNext()) {
var obj = objects.next();
// Process object
}
objects.close();
Deleting Custom Objects
var CustomObjectMgr = require('dw/object/CustomObjectMgr');
var Transaction = require('dw/system/Transaction');
Transaction.wrap(function() {
var obj = CustomObjectMgr.getCustomObject('CustomConfig', 'keyToDelete');
if (obj) {
CustomObjectMgr.remove(obj);
}
});
Getting All Objects of a Type
var CustomObjectMgr = require('dw/object/CustomObjectMgr');
// Get all objects of a type
var allConfigs = CustomObjectMgr.getAllCustomObjects('CustomConfig');
while (allConfigs.hasNext()) {
var config = allConfigs.next();
// Process
}
allConfigs.close();
CustomObjectMgr API Reference
| Method | Description |
|---|---|
getCustomObject(type, keyValue) |
Get single object by type and key |
createCustomObject(type, keyValue) |
Create new object (within transaction) |
remove(object) |
Delete object (within transaction) |
queryCustomObjects(type, query, sortString, ...args) |
Query with filters |
getAllCustomObjects(type) |
Get all objects of a type |
describe(type) |
Get metadata about the custom object type |
OCAPI Data API
Get Custom Object
GET /s/-/dw/data/v25_6/custom_objects/{object_type}/{key}
Authorization: Bearer {token}
Note: Use /s/{site_id}/dw/data/v25_6/custom_objects/... for site-scoped objects, or /s/-/dw/data/v25_6/custom_objects/... for organization-scoped (global) objects.
Create Custom Object
PUT /s/-/dw/data/v25_6/custom_objects/{object_type}/{key}
Authorization: Bearer {token}
Content-Type: application/json
{
"key_property": "myKey",
"c_configValue": "myValue",
"c_isActive": true
}
Update Custom Object
PATCH /s/-/dw/data/v25_6/custom_objects/{object_type}/{key}
Authorization: Bearer {token}
Content-Type: application/json
{
"c_configValue": "updatedValue"
}
Delete Custom Object
DELETE /s/-/dw/data/v25_6/custom_objects/{object_type}/{key}
Authorization: Bearer {token}
Search Custom Objects
POST /s/-/dw/data/v25_6/custom_object_search/{object_type}
Authorization: Bearer {token}
Content-Type: application/json
{
"query": {
"bool_query": {
"must": [
{ "term_query": { "field": "c_isActive", "value": true } }
]
}
},
"select": "(**)",
"sorts": [{ "field": "creation_date", "sort_order": "desc" }],
"start": 0,
"count": 25
}
Search Query Types
| Query Type | Description | Example |
|---|---|---|
term_query |
Exact match | {"field": "c_status", "value": "active"} |
text_query |
Full-text search | {"fields": ["c_name"], "search_phrase": "test"} |
range_query |
Range comparison | {"field": "c_count", "from": 1, "to": 10} |
bool_query |
Combine queries | {"must": [...], "should": [...], "must_not": [...]} |
match_all_query |
Match all records | {} |
Shopper Custom Objects API (SCAPI)
For read-only access from storefronts, use the Shopper Custom Objects API. This requires specific OAuth scopes.
Get Custom Object (Shopper)
GET https://{shortCode}.api.commercecloud.salesforce.com/custom-object/shopper-custom-objects/v1/organizations/{organizationId}/custom-objects/{objectType}/{key}?siteId={siteId}
Authorization: Bearer {shopper_token}
Required Scopes
For the Shopper Custom Objects API, configure these scopes in your SLAS client:
sfcc.shopper-custom-objects- Global read access to all custom object typessfcc.shopper-custom-objects.{objectType}- Type-specific read access
Note: SLAS clients can have a maximum of 20 custom object scopes.
The custom object type must also be enabled for shopper access in Business Manager.
Searchable System Fields
All custom objects have these system fields available for OCAPI search queries:
creation_date- When the object was created (Date)last_modified- When the object was last modified (Date)key_value_string- String key valuekey_value_integer- Integer key valuesite_id- Site identifier (for site-scoped objects)
Best Practices
Do
- Use transactions for create/update/delete operations
- Close query iterators when done (
objects.close()) - Use meaningful key values for efficient lookups
- Index frequently queried attributes
- Use site-scoped objects for site-specific data
- Use organization-scoped objects for shared configuration
Don't
- Store sensitive data without encryption
- Create excessive custom object types
- Use custom objects for high-volume transactional data
- Forget to handle null returns from
getCustomObject() - Leave query iterators open (causes resource leaks)
Common Patterns
Configuration Store
var CustomObjectMgr = require('dw/object/CustomObjectMgr');
var Site = require('dw/system/Site');
function getConfig(key, defaultValue) {
var configKey = Site.current.ID + '_' + key;
var obj = CustomObjectMgr.getCustomObject('SiteConfig', configKey);
if (obj && obj.custom.value !== null) {
return JSON.parse(obj.custom.value);
}
return defaultValue;
}
function setConfig(key, value) {
var Transaction = require('dw/system/Transaction');
var configKey = Site.current.ID + '_' + key;
Transaction.wrap(function() {
var obj = CustomObjectMgr.getCustomObject('SiteConfig', configKey);
if (!obj) {
obj = CustomObjectMgr.createCustomObject('SiteConfig', configKey);
}
obj.custom.value = JSON.stringify(value);
});
}
Processing Queue
var CustomObjectMgr = require('dw/object/CustomObjectMgr');
var Transaction = require('dw/system/Transaction');
// Add to queue
function enqueue(data) {
var key = 'job_' + Date.now() + '_' + Math.random().toString(36).substr(2, 9);
Transaction.wrap(function() {
var obj = CustomObjectMgr.createCustomObject('JobQueue', key);
obj.custom.data = JSON.stringify(data);
obj.custom.status = 'pending';
});
}
// Process queue
function processQueue() {
var pending = CustomObjectMgr.queryCustomObjects(
'JobQueue',
'custom.status = {0}',
'creationDate asc',
'pending'
);
while (pending.hasNext()) {
var job = pending.next();
Transaction.wrap(function() {
job.custom.status = 'processing';
});
try {
var data = JSON.parse(job.custom.data);
processJob(data);
Transaction.wrap(function() {
CustomObjectMgr.remove(job);
});
} catch (e) {
Transaction.wrap(function() {
job.custom.status = 'failed';
job.custom.error = e.message;
});
}
}
pending.close();
}
Detailed References
- OCAPI Search Queries - Full search query syntax and examples
More from salesforcecommercecloud/b2c-developer-tooling
b2c-docs
Search and read B2C Commerce Script API documentation and XSD schemas using the b2c CLI. Use this skill whenever the user needs to look up class methods, understand API signatures, find available properties on commerce objects (baskets, orders, products, customers), or check XML schema formats for imports. Also use when writing server-side scripts and needing API reference — even if they just say "what methods does Basket have" or "what fields can I import for products".
116b2c-webdav
List, upload, download, and manage files on B2C Commerce instances via WebDAV. Use this skill whenever the user needs to upload files to IMPEX directories, download exports from an instance, list remote files, create or delete directories, or zip/unzip files on the server. Also use when managing file transfers to sandboxes or browsing instance file systems -- even if they just say 'upload a file to the instance' or 'check what's in the IMPEX folder'.
103b2c-slas-auth-patterns
Implement SLAS authentication patterns in B2C Commerce including passwordless login (email OTP, SMS OTP, passkeys), session bridging between PWA Kit/Storefront Next and SFRA, hybrid authentication (B2C 25.3+), token refresh flows, trusted system on behalf of (TSOB), and JWT validation. Use this skill whenever the user asks about shopper authentication beyond basic login, token exchange flows, passwordless or biometric auth, keeping sessions alive across storefronts, handling 409 Conflict errors on token endpoints, refreshing shopper tokens, or validating JWTs — even if they don't mention SLAS by name.
90b2c-config
Inspect and debug CLI configuration, instance connections, and authentication. Use this skill whenever the user needs to check which dw.json or credentials are active, manage multiple instance profiles, retrieve OAuth tokens for scripting, troubleshoot authentication failures or connection errors, or integrate with VS Code or other editors. Also use when environment variables override config or the wrong sandbox is being targeted -- even if they just say 'why is it connecting to the wrong instance' or 'get me an access token'.
90b2c-controllers
Create storefront controllers using SFRA or classic patterns with server.get/post, middleware chains, and res.render/json. Use this skill whenever the user needs to build a page route, handle form submissions, create AJAX endpoints, extend or override existing controllers, or add middleware to a request pipeline. Also use when debugging route registration or response rendering -- even if they just say 'new page endpoint' or 'handle a POST request'.
86b2c-scapi-schemas
Browse and retrieve SCAPI OpenAPI schema specifications. Use this skill whenever the user needs to list available SCAPI APIs, inspect endpoint paths or request/response shapes, explore data models for products or orders, check which fields an API returns, or understand SCAPI versioning. Also use when looking up API details before building an integration -- even if they just say 'what fields does the product API return' or 'show me the SCAPI endpoints'.
84