What Is Split Shipment Configuration in Commerce Cloud + OMS?

Walmart’s latest e-commerce push shows where retail fulfillment is heading: its U.S. e-commerce sales grew 24% in Q2 2026, while store-to-door deliveries jumped 40%, with 70% of e-commerce orders fulfilled the same day or faster.

That speed creates a difficult operational reality for retailers: when inventory sits across stores, warehouses, and distribution centers, a poorly configured Commerce Cloud + Order Management System (OMS) can turn one customer order into several costly shipments.

For decision makers, split shipment configuration directly affects shipping cost, inventory utilization, delivery promises, customer experience, warehouse workload, and ultimately margin.

Salesforce Order Management is designed to manage processes across the order lifecycle. Its routing capabilities can evaluate inventory across locations and prioritize fulfillment using rules such as minimizing the number of shipment splits.

The challenge is aligning fulfillment rules with business strategy. Prioritizing speed can drive unnecessary shipments, while always aiming for one-package delivery can delay orders. The right approach depends on inventory, product type, customer promise, location, shipping cost, and business priorities. 

What Is Split Shipment Configuration in Commerce Cloud + OMS?

A split shipment happens when items in a single customer order are fulfilled from different locations. For example, imagine a customer purchases:

• One pair of running shoes
• Two T-shirts
• One backpack

The shoes may be available at Warehouse A, the T-shirts at Store B, and the backpack at Warehouse C.

If the OMS sends each item from the location where it is immediately available, the customer receives three packages. That may solve the inventory problem, but it can create a transportation and customer-experience problem.

Salesforce describes its “Find Routes with Fewest Splits” capability as a way to identify the smallest set of locations that can fulfill an order. The routing logic first looks for one location that can fulfill the complete order, then considers combinations involving additional locations when necessary.

This is the core idea decision makers should understand: the goal is not to eliminate every split shipment. The goal is to make the right split at the right time.

Top Split Shipment Configuration Mistakes in Commerce Cloud + OMS

To help decision-makers pinpoint vulnerabilities in their fulfillment architecture, we have analyzed the most critical split shipment mistakes that plague enterprise retailers.

Mistake #1: Sourcing from the Nearest Node Without Real-Time Basket-Level Optimization

Many Commerce Cloud and OMS implementations configure inventory sourcing strictly based on proximity to the end customer. On paper, shipping from the nearest physical location seems logical to reduce transit times. 

However, when an order contains three items and Node A has Item 1, Node B has Item 2, and Node C has Item 3, proximity-only routing immediately splits the order three ways.

A national home goods retailer configured its OMS to assign each item to the closest store. A customer ordered a lamp, duvet cover, and pillowcases. The system split the order across three locations instead of consolidating it.

• Three shipments: One from a suburban store, one from a regional hub 50 miles away, and one from a flagship store across the state.
• Higher fulfillment cost: Shipping and handling increased from $9.50 to $29.80.
• Margin loss: The $120 order became a negative-margin transaction.

The OMS optimized item-level fulfillment but failed to optimize the total order cost.

The Fix: Implement consolidated basket routing logic. The OMS should first scan for a single inventory location that can fulfill 100% of the basket before evaluating split options. 

If a single source is available, even if it is 200 miles further away, the lower cost of a single parcel almost always outweighs the slight proximity advantage of multiple short-haul packages.

Mistake #2: Misaligned Safety Stock and Buffer Thresholds Between Commerce Cloud and OMS

A frequent architectural pitfall occurs when Commerce Cloud and the OMS maintain different safety stock settings. For example, Commerce Cloud may show 3 units as available, while the OMS keeps 2 units as a safety buffer at the store level.

When a customer places an order, Commerce Cloud accepts it based on the available inventory. But when the OMS tries to fulfill it, the order may fail because the store has already reached its buffer threshold. The OMS then sends the order to another fulfillment location, potentially creating an unnecessary split shipment.

“The storefront says the item is available, but the OMS says we can’t fulfill it. That mismatch can push the order to another store and increase fulfillment costs.”

The Fix: Centralize inventory availability logic within a single source of truth. Leveraging end-to-end platform capabilities such as those delivered via expert Agentforce commerce implementation services helps maintain consistent inventory rules across Commerce Cloud and OMS, reducing fulfillment failures and unnecessary rerouting.

Mistake #3: Ignoring Packaging and Dimensional Weight (Dim Weight) Escalations

Standard OMS split algorithms often evaluate basic carrier rates but overlook dimensional weight, box sizes, and packaging costs. When an order is split into two packages, each shipment can carry its own dim weight charge, fuel surcharge, residential delivery fee, and packaging cost.

• Higher shipping charges: Each additional package can trigger separate carrier and surcharge fees.
• Packaging inefficiency: Smaller item groups may require more boxes and void fill.
• Hidden split costs: Two “cheap” shipments can cost more than one consolidated shipment.

The Fix: Incorporate volumetric freight logic into split evaluation. The OMS should calculate the total dimensional weight, packaging, and surcharge impact before approving a split.

Mistake #4: Over-Prioritizing Store Ship-from-Store (SFS) Without Floor-Labor Cost Thresholds

Enabling physical retail stores as fulfillment nodes (Ship-from-Store) is a cornerstone of modern omni-channel retail. However, failing to factor associate pick-and-pack labor costs into split rules causes severe margin erosion. 

Picking an item in a distribution center costs approximately $0.95 to $1.40, whereas picking an item off a busy retail store floor by a store associate costs between $3.50 and $5.50 in direct labor time.

When split configurations route single items to multiple retail stores, store associate labor costs double or triple, while store inventory accuracy degrades due to simultaneous customer foot traffic.

The Fix: Apply dynamic labor cost penalties within OMS fulfillment routing. Store nodes should only be assigned splits when distribution centers are entirely out of stock or when store inventory exhibits high markdown risks that justify liquidation via online orders.

Mistake #5: Lack of Dynamic Hold Times for Multi-Node Consolidation

Many legacy OMS rule sets execute split decisions instantaneously upon order placement. If Item A is available at DC-East today, but Item B is in transit to DC-East and arriving tomorrow, a rigid system immediately splits the order, sending Item A today and Item B from DC-West.

By failing to configure intelligent order hold windows (e.g., 12 to 24-hour consolidation holds), organizations sacrifice massive consolidation opportunities for minor, unnecessary speed gains.

The Fix: Establish business-class delayed fulfillment rules. For non-expedited orders, permit the OMS to hold single-item splits for a defined window to aggregate items at a primary consolidation hub.

How Decision Makers Should Configure Split Shipment Rules

The configuration process should start with business objectives, not technical settings. Before defining OMS rules, decision makers need to determine what they are trying to optimize and how much fulfillment complexity the business can afford.

1. Define the Primary Business Goal

Start by deciding what matters most to the business: lower fulfillment costs, faster delivery, better inventory utilization, higher complete-order fulfillment, stronger customer experience, or balanced profitability. 

2. Create Clear Fulfillment Priorities

Once the goal is clear, establish a simple decision hierarchy:

• First: Can one location fulfill the complete order?
• Second: If not, can two locations fulfill it without missing the promised delivery date?
• Third: If additional locations are necessary, choose them based on inventory availability, distance, shipping cost, and delivery requirements.

This approach favors consolidation first while still protecting delivery commitments.

3. Add Product-Specific Rules

Not every product should follow the same fulfillment logic. Different categories have different costs, urgency, and handling requirements.

For example:

• Standard apparel: Prioritize consolidation and lower shipping costs.
• Urgent replacement parts: Prioritize delivery speed.
• Large furniture: Prioritize locations equipped for oversized shipments.
• Perishable goods: Prioritize freshness and delivery time.

These rules prevent a one-size-fits-all routing strategy from creating unnecessary costs.

4. Set a Realistic Split Threshold

A split should not happen simply because multiple locations have inventory. Use historical data to determine when another shipment is economically justified.

Review:

• Average order value
• Average shipping cost
• Packages per order
• Delivery SLA
• Gross margin
• Return rate
• Customer complaints

Use these metrics to establish practical limits for how many shipments an order can support.

5. Test Before Going Live

Before deploying the rules, test common and difficult scenarios, including one-location and multi-location fulfillment, low inventory, store inventory, backorders, preorders, express shipping, mixed product categories, high-value orders, and partial cancellations. 

A Simple KPI Framework for Split Shipment Performance

Decision makers should not judge configuration based only on whether orders are successfully shipped.

Summing Up

Configure split shipment rules around business priorities. The costliest mistakes occur when proximity or speed is prioritized over total basket profitability, resulting in inflated shipping fees and customer friction.

A high-margin routing strategy balances fewest-split logic, product-specific rules, real-time inventory accuracy, and financial caps. By aligning Salesforce Commerce Cloud and OMS configuration with actual margin drivers, you turn fulfillment routing into a measurable bottom-line advantage.

Ready to eliminate costly split shipments and boost your enterprise fulfillment margins? Partner with Ksolves, your trusted expert in Agentforce commerce implementation services. Our team will audit your inventory routing and design precision fulfillment rules tailored to your business outcomes. Contact us today to streamline your omnichannel operations!

FAQs

What is a split shipment in Commerce Cloud + OMS?

A split shipment occurs when products from one customer order are fulfilled and shipped from multiple locations. The locations may include warehouses, distribution centers, or retail stores.

Are split shipments always bad?

No. Split shipments can be useful when they significantly improve delivery speed or allow a retailer to fulfill an order that one location cannot complete. The objective is to avoid unnecessary splits.

How does Salesforce Order Management help minimize split shipments?

Salesforce Order Management provides routing capabilities that can evaluate available inventory and identify fulfillment combinations with fewer splits. Its routing approach can consider one location first and then additional locations when required.

What is the biggest split shipment configuration mistake?

One of the most common mistakes is optimizing for a single factor—such as proximity or delivery speed—without considering shipping cost, inventory accuracy, order value, customer promise, and product type.

Should every product have the same split shipment rule?

No. High-value, oversized, perishable, promotional, urgent, and standard products may require different fulfillment priorities.

How should retailers measure split shipment performance?

Track split shipment rate, packages per order, shipping cost per order, ship-complete rate, on-time delivery, cancellation rate, inventory utilization, and customer service contacts.

Can stores be used as fulfillment locations?

Yes. Retail stores can serve as fulfillment locations when the inventory and operational model support it. Salesforce describes fulfillment locations as potentially including distribution centers, warehouses, and retail stores.

What should decision makers do before changing routing rules?

Start with historical order data. Identify where splits happen, why they happen, how much they cost, and whether they improve delivery performance. Then create business rules and test them against realistic fulfillment scenarios.