SFCC Integration Guide

Complete guide for integrating SFCC with Forter Agentic Orchestration.

This guide is specifically for merchants using Salesforce Commerce Cloud (SFCC). For other platforms, see Shopify Integration or Custom Integration.

How It Works How It Works

With SFCC integration, Forter:

1. Pulls your product catalog via SFCC OCAPI (Shop API)
2. Generates and maintains the AI-optimized feed automatically
3. Creates orders directly in your SFCC instance via OCAPI Basket/Order APIs

You provide: OCAPI credentials
You implement: Nothing - Forter handles everything

Prerequisites Prerequisites

Before starting, ensure you have:

• SFCC Instance — Sandbox or production Business Manager access
• OCAPI Permissions — Ability to configure OCAPI settings and create API clients
• Forter Account — Contact your Forter representative to enable Agentic Orchestration
• Tax Nexus List — US states where you collect sales tax

Step 1: Configure SFCC OCAPI Credentials Step 1: Configure SFCC OCAPI Credentials

A. Configure Shop API Settings A. Configure Shop API Settings

1. Log in to SFCC Business Manager

2. Navigate to: Administration > Site Development > Open Commerce API Settings

3. Click on Shop API tab

4. Add this JSON configuration:

   {
       "_v": "23.1",
       "clients":[
           {
               "client_id":"forter-agentic-commerce",
               "allowed_origins":[],
               "resources":[
                   {
                       "resource_id":"/products/**/*",
                       "methods":["get"],
                       "read_attributes":"(***)",
                       "write_attributes":"()"
                   },
                   {
                       "resource_id":"/product_search",
                       "methods":["get","post"],
                       "read_attributes":"(***)",
                       "write_attributes":"()"
                   },
                   {
                       "resource_id":"/categories/**/*",
                       "methods":["get"],
                       "read_attributes":"(***)",
                       "write_attributes":"()"
                   },
                   {
                       "resource_id":"/baskets/**/*",
                       "methods":["get","post","put","patch"],
                       "read_attributes":"(***)",
                       "write_attributes":"(***)"
                   },
                   {
                       "resource_id":"/orders/**/*",
                       "methods":["get","post"],
                       "read_attributes":"(***)",
                       "write_attributes":"(***)"
                   }
               ]
           }
       ]
   }
   

5. Click Save

Key Points:

• client_id: Must be forter-agentic-commerce (or your chosen name)
• Read-only for products/categories
• Read/write for baskets/orders (required for checkout)

B. Enable Account Manager B. Enable Account Manager

1. Navigate to: Administration > Organization > Account Manager
2. If not enabled, click Enable Account Manager
3. Follow the prompts to complete setup

C. Create API Client C. Create API Client

1. Navigate to: Administration > Site Development > Open Commerce API Settings > API Client

2. Click Add API Client

3. Fill in the details:

   Client Name: Forter Agentic Commerce
   Client ID: forter-agentic-commerce (must match the client_id in OCAPI settings)
   Token Endpoint Auth Method: Client Secret Post
   Access Token Format: JWT
   Scopes (select all that apply):
   ✔️ SALESFORCE_COMMERCE_API:{tenant_id}.shopper-products-read
   ✔️ SALESFORCE_COMMERCE_API:{tenant_id}.shopper-categories-read
   ✔️ SALESFORCE_COMMERCE_API:{tenant_id}.shopper-search-read
   ✔️ SALESFORCE_COMMERCE_API:{tenant_id}.shopper-baskets-orders
   Allowed Grant Types:
   ✔️ Client Credentials
   Redirect URIs: (leave empty)
   

4. Click Save

5. IMPORTANT: Copy the Client Secret immediately - it's only shown once!

D. Test Your Credentials D. Test Your Credentials

Test with curl to ensure everything works:

# Get access token
curl -X POST https://account.demandware.com/dwsso/oauth2/access_token \
-H "Content-Type: application/x-www-form-urlencoded" \
-u "forter-agentic-commerce:YOUR_CLIENT_SECRET" \
-d "grant_type=client_credentials"

# Test product access
curl -X GET "https://YOUR_INSTANCE.demandware.net/s/YOUR_SITE_ID/dw/shop/v23_1/product_search?count=10" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"

If successful, you'll receive product data.

Step 2: Configure in Forter Portal Step 2: Configure in Forter Portal

Log in to the Forter Portal and navigate to Integrations > SFCC.

A. Basic Store Information A. Basic Store Information

B. SFCC Platform Configuration B. SFCC Platform Configuration

C. Store Policies C. Store Policies

D. Tax Configuration D. Tax Configuration

E. Order Management E. Order Management

Step 3: Payment & Fraud Settings (Optional) Step 3: Payment & Fraud Settings (Optional)

By default, you handle payment validation and authorization on your SFCC instance. This section is only needed if you want Forter to handle fraud detection and payments.

Option A: Merchant-Side Validation/Authorization (Default) Option A: Merchant-Side Validation/Authorization (Default)

What happens:

• Forter creates orders in SFCC with payment references
• SFCC processes payments through your existing payment provider
• SFCC handles fraud checks through your existing rules

Configuration: No additional setup needed - this is the default behavior.

Settings in Portal:

Enable Forter Validation: false (default)
Enable Forter Authorization: false (default)
Enable Forter Capture: false (default)

Option B: Forter-Side Validation/Authorization (Optional) Option B: Forter-Side Validation/Authorization (Optional)

What happens:

• Forter validates orders for fraud before creating them in SFCC
• Forter authorizes/captures payments via Forter Payment Orchestration
• Orders are created in SFCC with completed payment status

Configuration Required:

Contact your Forter representative to obtain:

Settings in Portal:

Enable Forter Validation: true
Enable Forter Authorization: true
Enable Forter Capture: true (or false for manual capture)

Step 4: Catalog Sync & Testing Step 4: Catalog Sync & Testing

A. Initiate First Sync A. Initiate First Sync

After configuring SFCC credentials in the portal:

1. Forter automatically tests the OCAPI connection
2. Initial catalog sync begins (pulls all products via OCAPI)
3. Products are normalized to AI-optimized format
4. Feed is distributed to AI platforms

Processing Time:

• < 10,000 products: Minutes
• 10,000 - 100,000 products: Under an hour

• 100,000 products: A few hours

B. Verify Catalog B. Verify Catalog

Check that products were synced by updating inventory for a test product:

curl -X POST \
 https://{site_id}.agentic.checkouttools.com/v1/inventory \
-H "Authorization: Bearer YOUR_FORTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
 "id": "TEST-SKU-001",
 "quantity": 100
 }'

If the product exists, you'll receive:

{
   "success": true,
   "updated": 1,
   "results":[{"success":true,"id":"TEST-SKU-001"}]
}

C. Test Checkout Flow C. Test Checkout Flow

Test end-to-end checkout in the test environment:

1. Create a checkout session:

curl -X POST \
 https://{site_id}.agentic.checkouttools.com/checkout_sessions \
-H "Authorization: Bearer sk_test_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: test-001" \
-d '{
 "items": [{ "id": "TEST-SKU-001", "quantity": 1 }],
 "buyer": {
   "first_name": "Test",
   "email": "test@example.com"
 }
}'

2. Add shipping and complete order:

curl -X POST \
 https://{site_id}.agentic.checkouttools.com/checkout_sessions/{session_id}/complete \
-H "Authorization: Bearer sk_test_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
 "fulfillment_address": {
   "name": "Test User",
   "line_one": "123 Test St",
   "city": "San Francisco",
   "state": "CA",
   "postal_code": "94102",
   "country": "US"
 },
 "payment_data": {
   "token": "tok_test_visa_4242",
   "provider": "test"
 }
}'

3. Verify order in SFCC Business Manager

The order should appear in: Merchant Tools > Ordering > Orders

Step 5: Go Live Step 5: Go Live

Production Checklist Production Checklist

• Replace test OCAPI credentials with production credentials
• Update Forter Portal with production SFCC instance URL
• Verify production catalog sync completes successfully
• Test at least one production order end-to-end
• Configure monitoring and alerting
• Enable AI platform distribution (OpenAI, Google, etc.)

Monitoring Monitoring

Use the Forter Portal to monitor:

• Catalog Health — Product count, sync status, errors
• Order Volume — Checkout sessions, completions, failures
• OCAPI Usage — API call volume, rate limits
• Error Rates — Failed checkouts, SFCC API errors

Troubleshooting Troubleshooting

"Invalid OCAPI credentials""Invalid OCAPI credentials"

Solution:

• Verify Client ID matches OCAPI Shop API settings
• Check Client Secret (no extra spaces)
• Ensure scopes include required tenant ID
• Wait 5-10 minutes for settings to propagate

"Insufficient permissions""Insufficient permissions"

Solution:

• Check OCAPI Shop API resources include /baskets/** and /orders/**
• Verify API Client scopes include shopper-baskets-orders
• Confirm OCAPI version matches your instance

Products not syncing Products not syncing

Solution:

• Test OCAPI product_search endpoint with curl
• Check SFCC rate limits (100 req/10s)
• Review Forter Portal logs for sync errors
• Verify products are online and searchable in SFCC

Orders not appearing in SFCC Orders not appearing in SFCC

Solution:

• Verify basket creation permissions in OCAPI settings
• Check SFCC Business Manager for failed orders
• Review Forter Portal logs for OCAPI errors
• Confirm site ID is correct

SFCC-Specific Considerations SFCC-Specific Considerations

Rate Limits Rate Limits

SFCC OCAPI has rate limits:

• ~100 requests per 10 seconds
• ~1000 requests per minute

Forter automatically handles rate limiting with exponential backoff.

Catalog Size Catalog Size

For large catalogs (>100k products), consider:

• Enabling SFCC search result pagination
• Monitoring initial sync duration
• Using inventory updates for real-time changes

Multiple Sites Multiple Sites

If you have multiple SFCC sites:

• Configure each site as a separate integration in Forter Portal
• Each site gets its own API credentials and configuration
• Orders are routed to the correct site based on Site ID

Quick Reference Quick Reference

Required OCAPI Resources Required OCAPI Resources

{
   "products":["get"],
   "product_search":["get","post"],
   "categories":["get"],
   "baskets":["get","post","put","patch"],
   "orders":["get","post"]
}

Required OCAPI Scopes Required OCAPI Scopes

shopper-products-read
shopper-categories-read
shopper-search-read
shopper-baskets-orders

Next Steps Next Steps

• Catalog & Inventory — Product data synchronization details
• Checkout & Payments — Payment processing and order management
• FAQ — Common questions

Support Support

For SFCC-specific integration questions, contact your Forter representative or email support@forter.com.