* B2C Commerce *

Hi @Utkarsh Srivastava

We have already created a Menu Action under a Menu Item within Merchant Tools. 

However, the requirement is to display a new custom tab within the Customer detail page (alongside tabs like General, Addresses, etc.) when accessed from Merchant Tools. (As Shown in Image) 

We reviewed the shared documentation but did not find a specific approach to achieve this. 

Based on our understanding, adding a custom tab directly within the standard Customer detail page in Business Manager is not supported through standard extension mechanisms. Business Manager extensions allow adding menu items, actions, and modules, but not modifying the core layout of existing system pages such as adding new tabs.  

Could you please confirm if the understanding is correct? If there is any alternative approach to achieve similar functionality (for example, through a custom module or separate page), we would appreciate your guidance. 

Thanks 

Harsh

The storage model for B2C Commerce Cloud is fundamentally different from core Salesforce. Core Salesforce allocates storage in MB across two buckets: data storage and file storage. Each record consumes roughly 2KB depending on the object. B2C Commerce is built for high-volume transactional data, and its storage model is tied to your edition and order volume rather than the per-record allocation model you're used to in core.

From my experience, the mistake most teams make is trying to apply core org sizing logic to Commerce Cloud. They run capacity planning based on their core storage dashboard and assume Commerce works the same way. It doesn't. The architectures were designed for different use cases: core for relational CRM data, Commerce for catalog and transactional throughput.

If you're planning a B2C implementation, start with the Commerce Cloud technical documentation on data storage and catalog limits rather than extrapolating from your core org. The constraints you need to plan around are different: catalog size, indexing performance, and order processing volume are the bottlenecks, not record storage in the traditional sense.

It is worth noting that the Default Scopes in the above referenced documentation need to be one on each line, not comma-delimited or any other format. This field should look like this: 

roles 

tenantFilter 

profile

Your Approach Is Valid (with Caveats) 

You're using OMS in a **hybrid model**—both for web commerce fulfillment *and* manual direct sales. This is supported, but requires careful design to avoid conflicts. 

**Key considerations:** 

**1. Separation of Order Sources** 

- Use the **Order.Type** or **Order.OriginatingChannel** field to distinguish direct sales orders from web orders 

- Consider different **Order Delivery Methods** for B2B direct vs. web checkout 

- This lets you route orders through different fulfillment logic based on source 

**2. Order Activation Timing** 

Your workflow activates the Order *after* manual validation and Order Delivery Group setup. This works well for direct sales but differs from typical web checkout, where: 

- Commerce Cloud usually auto-creates the Order Summary during checkout 

- Order Delivery Groups are often auto-assigned based on inventory rules 

**Solution:** Keep web orders on the standard Commerce Cloud → OMS integration path, and use your manual workflow only for direct sales orders. Gate your custom automation with a check on order source. 

**3. Fulfillment Order vs. Work Order** 

- **Fulfillment Orders** = picking/packing existing inventory 

- **Work Orders** = manufacturing or assembly 

Your split makes sense for a manufacturer. Just ensure your downstream systems (WMS, ERP, production scheduling) can consume both record types appropriately. 

**4. Potential Conflicts to Watch** 

| **Risk** | **Mitigation** | 

|----------|----------------| 

| Duplicate Order Summary creation | Ensure your direct-sales activation flow doesn't trigger the same OMS integration that web checkout uses. Use Process Builder/Flow filters on `Order.Type`. | 

| Inventory allocation conflicts | If both channels share inventory, implement **Inventory Reservation** records or use OMS's built-in allocation engine to prevent overselling. | 

| Shipment record duplication | If you integrate with a 3PL or carrier system, make sure only *one* process creates Shipment records per Order Summary. | 

**5. Missing Pieces to Consider** 

- **Returns & Refunds:** OMS supports Return Orders and Credit Memos. Plan how direct sales returns will flow (manual RMA vs. self-service). 

- **Invoicing:** Without Revenue Cloud or Finance, you'll need to generate invoices from Order Summary or integrate with an external billing system. 

- **Order Amendments:** If customers change orders post-activation, OMS supports Change Orders, but the UX is complex without CPQ. 

### Recommended Architecture 

Before scaling this: 

✅ **Test both order sources end-to-end** in a sandbox   

✅ **Confirm inventory doesn't double-allocate** between web and direct sales   

✅ **Verify Order Summary status transitions** match your business states   

✅ **Check reporting**—ensure Sales Cloud reports can distinguish order types   

✅ **Plan for exceptions**—cancellations, partial shipments, backorders   

✅ **Document the process** for your sales team (when to activate, how to handle split shipments, etc.) 

### Bottom Line 

Your workflow is **architecturally sound** for a B2B manufacturer doing direct sales + web commerce. The main risk is collision between manual and automated order flows—mitigate that with clear source-type filtering and separate automation paths. Since you're already operational, I'd recommend: 

1. **Formalize the order type taxonomy** (direct vs. web) 

2. **Add validation rules** to prevent manual activation of web orders 

3. **Build a dashboard** showing order pipeline by source and fulfillment stage 

4. **Plan your invoice/payment flow** if you haven't already 

You're not missing anything fundamental—this is a legitimate use of OMS outside pure commerce. Just keep the two channels logically separated in your automation, and you'll be fine.

This is a common issue with Order Management flows, and the generic error usually points to missing required fields or incorrect data structure. 

I can help you troubleshoot the "Add Order Item Summary" action in your Salesforce Flow. Based on common issues with this action, here are the key things to check: 

### Common Causes of the Generic Error 

**1. Required Fields in the Order Item Summary** 

The action requires specific fields to be populated in your `orderItemSummary` object within the `newItems` list. Make sure you're setting: 

- **Product2Id** - Reference to the product 

- **Quantity** - Item quantity 

- **Type** - Must be a valid value (typically "Order Product") 

- **OrderSummaryId** - Reference to the parent Order Summary 

- **TotalPrice** or **UnitPrice** - Pricing information 

**2. Reason Code Validation** 

You mentioned including a `reasonCode` - ensure this is a valid picklist value that exists in your org. Invalid reason codes will cause silent failures with generic errors. 

**3. Missing Context Fields** 

While not explicitly listed as "required" in the documentation, these fields often cause issues when missing: 

- **OrderItemId** - If you're adding items related to existing order items 

- **OriginalOrderItemSummaryId** - For return/exchange scenarios 

### Recommended Troubleshooting Steps 

**1. Enable Debug Mode** 

In your flow, add a Debug statement right before the action to log the exact values you're passing: 

- Log the entire `newItems` collection 

- Verify each field has a non-null value 

- Check data types match expectations 

**2. Simplify Your Test** 

Start with the absolute minimum required fields: 

``` 

newItems (Collection of ConnectApi.OrderItemSummaryInputRepresentation): 

  - orderItemSummary: 

      - Product2Id: [valid product ID] 

      - Quantity: 1 

      - Type: "Order Product" 

      - OrderSummaryId: [your order summary ID] 

      - UnitPrice: 10.00 

  - reasonCode: [valid reason code or leave blank initially] 

``` 

**3. Verify Order Summary State** 

The Order Summary must be in a valid state to accept new items. Check: 

- Order Summary status allows modifications 

- No active fulfillment processes are blocking changes 

- The Order Summary isn't already closed/completed 

**4. Check Field-Level Security** 

Ensure the running user has: 

- Create permission on OrderItemSummary 

- Edit access to all fields you're trying to populate 

- Read access to Product2 and related objects 

**5. Review Salesforce Order Management Setup** 

- Verify Order Management is properly enabled in your org 

- Check that your products are configured for Order Management 

- Ensure price books are properly associated 

### Alternative Approach: Use Apex Instead 

If the declarative action continues to fail, consider creating a simple Apex action that provides better error messages: 

```apex 

@InvocableMethod(label='Add Order Item Summary with Error Details') 

public static List<Result> addOrderItemSummary(List<Request> requests) { 

    List<Result> results = new List<Result>(); 

    for (Request req : requests) { 

        Result res = new Result(); 

        try { 

            // Your order item summary creation logic here 

            // This will give you actual error messages instead of "something went wrong" 

            res.success = true; 

        } catch (Exception e) { 

            res.success = false; 

            res.errorMessage = e.getMessage() + ' | ' + e.getStackTraceString(); 

        } 

        results.add(res); 

    } 

    return results; 

} 

``` 

### Next Steps 

1. **Check Flow Debug Logs**: Run the flow with debug enabled and examine the exact error in Setup → Debug Logs 

2. **Test via Workbench**: Try creating an OrderItemSummary via Workbench REST API to see if it's a flow-specific issue 

3. **Verify API Version**: Ensure your flow is using API version 50.0 or higher (Order Management requirement)