sf-orders
Before Writing Code
Fetch live docs before implementing order management features.
- Web-search: "Salesforce Commerce Cloud SCAPI Shopper Orders API 2026"
- Web-search: "Salesforce B2C Commerce order lifecycle status transitions 2026"
- Web-search: "Salesforce B2B Commerce Order OrderItem approval workflows 2026"
- Web-search: "Salesforce Order Management OMS documentation 2026"
- Web-fetch the SCAPI Shopper Orders reference for current schemas
- Web-fetch the Salesforce Order object reference for B2B fields
Conceptual Architecture
B2C Commerce Order Lifecycle
Basket (cart)
-> Order Created (created)
-> open (confirmed, ready for fulfillment)
-> shipped -> completed
-> partially_shipped -> open
-> cancelled
-> failed (payment declined)
-> replaced (exchange)
B2C Order Status Definitions:
| Status |
Meaning |
| created |
Order object created, payment authorized |
| new / open |
Confirmed, ready for fulfillment (synonymous; varies by config) |
| completed |
All items fulfilled and delivered |
| cancelled |
Cancelled by customer or admin |
| replaced |
Replaced with new order (e.g., exchange) |
| failed |
Creation failed (payment or inventory) |
Key B2C Order Objects:
- Basket: Temporary cart object; expires after inactivity
- Order: Created from basket upon payment success; auto-generated order number
- OrderItem: Line item with product, quantity, price
- PaymentInstrument: Payment method attached to order
- ShippingOrder / Shipment: Fulfillment tracking per delivery group
B2C Order Confirmation:
- Confirmation page displays order summary, number, delivery estimate
- Confirmation email triggered via Business Manager templates or ESP (SendGrid, Mailchimp)
- Supports dynamic tokens for order number, customer name, line items
B2C Order Export for Fulfillment:
- XML export via scheduled job or real-time webhook to OMS/ERP
- Fulfillment system acknowledges receipt, sends back tracking info
- Supports partial shipment status updates per line item
B2B Commerce Order Lifecycle
WebCart (persists across sessions)
-> Checkout Flow (multi-step)
-> Order (Draft)
-> Activated (submitted)
-> Approval Workflow (optional)
-> Fulfillment / Order Splits
-> completed
B2C vs B2B Order Model Differences:
| Aspect |
B2C (SFCC) |
B2B (Lightning) |
| Cart object |
Basket (temporary) |
WebCart (persistent) |
| Order object |
SFCC Order (proprietary) |
Salesforce Order (standard) |
| Line item |
OrderItem (SFCC) |
OrderItem (standard sObject) |
| Initial status |
created -> open |
Draft -> Activated |
| Approval |
Not built-in |
Flow / Process Builder approvals |
| Payment |
Cartridge-based processors |
Apex PaymentGatewayAdapter |
| Fulfillment tracking |
XML export + status sync |
OrderDeliveryGroup sObject |
| Reorder |
Clone items to new basket |
Quick reorder button, bulk CSV upload |
| Payment terms |
Credit card at checkout |
PO, net terms, credit limits |
| Order splits |
Not native |
Parent-child order pattern via OrderSummary |
B2B Approval Workflow Concepts:
- Approval criteria: order total threshold, product restrictions, buyer role
- Routing via Flow or Process Builder to designated approver
- Actions: approve, reject, request changes, auto-escalate on timeout
B2B Order Splits:
- Multi-location fulfillment splits order across warehouses
- Parent order spawns child orders per location
- OrderSummary provides unified tracking view
- OrderDeliveryGroup tracks shipments per split
Salesforce Order Management (OMS)
Optional paid add-on for unified order orchestration across B2C and B2B.
| OMS Object |
Purpose |
| OrderSummary |
Aggregate order (unifies B2C/B2B) |
| FulfillmentOrder |
Per-warehouse fulfillment view |
| Order Broker |
Routing engine for optimal location |
OMS Capabilities:
- Omnichannel fulfillment: ship-from-store, BOPIS
- Distributed Order Management (DOM) routing
- Unified returns processing
- Service Console for agents
When to use OMS: Complex multi-location fulfillment, high order volume, omnichannel requirements, high return complexity. Evaluate ROI vs. native order management.
Order Events
| Platform |
Key Events |
| B2C |
Order Created, Status Changed, Exported, Cancelled |
| B2B |
Order Submitted, Approved, Rejected, Shipped (via Platform Events / CDC) |
| OMS |
OrderSummary Created, FulfillmentOrder Created, Shipment Confirmed, Return Initiated |
Code Examples
// Pattern: B2C order status check
// Fetch live docs for SCAPI Shopper Orders endpoints
// GET /orders/{orderNo} -> check order.status
// Pattern: B2B approval trigger
// Fetch live docs for Process Builder / Flow order approvals
// Order.Status changes from Draft -> Activated -> triggers approval
Best Practices
Order Creation
- Validate basket/cart before conversion (inventory, pricing, address)
- Capture payment authorization synchronously; handle failures with retry logic
- Use idempotent operations to prevent duplicate orders
Fulfillment Integration
- Export orders to fulfillment system within minutes of creation
- Use idempotent export to avoid duplicate orders in downstream systems
- Support partial shipment status updates per line item
B2B-Specific
- Persist carts across sessions; support multiple named carts per account
- Configure approval thresholds per buyer group or account
- Enforce credit limits at checkout before order submission
Monitoring
- Track order creation rate, export failures, and fulfillment SLA in real-time
- Alert on stuck orders (no status change within expected window)
- Monitor refund processing time and payment authorization success rates
Fetch the SCAPI Shopper Orders reference and Salesforce Order object docs for exact schemas and field names before implementing.
1---2name: sf-orders3description: Manage Salesforce Commerce orders — B2C (SCAPI order objects, status lifecycle, order confirmation, returns) and B2B (Order object, OrderItem, splits, approval workflows, fulfillment). Use when implementing order management across either platform.4allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch5metadata:6 source: https://skillmd.com/skills/orcaqubits/sf-orders7---89# sf-orders1011## Before Writing Code1213**Fetch live docs before implementing order management features.**14151. Web-search: "Salesforce Commerce Cloud SCAPI Shopper Orders API 2026"162. Web-search: "Salesforce B2C Commerce order lifecycle status transitions 2026"173. Web-search: "Salesforce B2B Commerce Order OrderItem approval workflows 2026"184. Web-search: "Salesforce Order Management OMS documentation 2026"195. Web-fetch the SCAPI Shopper Orders reference for current schemas206. Web-fetch the Salesforce Order object reference for B2B fields2122## Conceptual Architecture2324### B2C Commerce Order Lifecycle2526```27Basket (cart)28 -> Order Created (created)29 -> open (confirmed, ready for fulfillment)30 -> shipped -> completed31 -> partially_shipped -> open32 -> cancelled33 -> failed (payment declined)34 -> replaced (exchange)35```3637**B2C Order Status Definitions:**3839| Status | Meaning |40|---|---|41| created | Order object created, payment authorized |42| new / open | Confirmed, ready for fulfillment (synonymous; varies by config) |43| completed | All items fulfilled and delivered |44| cancelled | Cancelled by customer or admin |45| replaced | Replaced with new order (e.g., exchange) |46| failed | Creation failed (payment or inventory) |4748**Key B2C Order Objects:**4950- **Basket**: Temporary cart object; expires after inactivity51- **Order**: Created from basket upon payment success; auto-generated order number52- **OrderItem**: Line item with product, quantity, price53- **PaymentInstrument**: Payment method attached to order54- **ShippingOrder / Shipment**: Fulfillment tracking per delivery group5556**B2C Order Confirmation:**57- Confirmation page displays order summary, number, delivery estimate58- Confirmation email triggered via Business Manager templates or ESP (SendGrid, Mailchimp)59- Supports dynamic tokens for order number, customer name, line items6061**B2C Order Export for Fulfillment:**62- XML export via scheduled job or real-time webhook to OMS/ERP63- Fulfillment system acknowledges receipt, sends back tracking info64- Supports partial shipment status updates per line item6566### B2B Commerce Order Lifecycle6768```69WebCart (persists across sessions)70 -> Checkout Flow (multi-step)71 -> Order (Draft)72 -> Activated (submitted)73 -> Approval Workflow (optional)74 -> Fulfillment / Order Splits75 -> completed76```7778**B2C vs B2B Order Model Differences:**7980| Aspect | B2C (SFCC) | B2B (Lightning) |81|---|---|---|82| Cart object | Basket (temporary) | WebCart (persistent) |83| Order object | SFCC Order (proprietary) | Salesforce Order (standard) |84| Line item | OrderItem (SFCC) | OrderItem (standard sObject) |85| Initial status | created -> open | Draft -> Activated |86| Approval | Not built-in | Flow / Process Builder approvals |87| Payment | Cartridge-based processors | Apex PaymentGatewayAdapter |88| Fulfillment tracking | XML export + status sync | OrderDeliveryGroup sObject |89| Reorder | Clone items to new basket | Quick reorder button, bulk CSV upload |90| Payment terms | Credit card at checkout | PO, net terms, credit limits |91| Order splits | Not native | Parent-child order pattern via OrderSummary |9293**B2B Approval Workflow Concepts:**94- Approval criteria: order total threshold, product restrictions, buyer role95- Routing via Flow or Process Builder to designated approver96- Actions: approve, reject, request changes, auto-escalate on timeout9798**B2B Order Splits:**99- Multi-location fulfillment splits order across warehouses100- Parent order spawns child orders per location101- OrderSummary provides unified tracking view102- OrderDeliveryGroup tracks shipments per split103104### Salesforce Order Management (OMS)105106Optional paid add-on for unified order orchestration across B2C and B2B.107108| OMS Object | Purpose |109|---|---|110| OrderSummary | Aggregate order (unifies B2C/B2B) |111| FulfillmentOrder | Per-warehouse fulfillment view |112| Order Broker | Routing engine for optimal location |113114**OMS Capabilities:**115- Omnichannel fulfillment: ship-from-store, BOPIS116- Distributed Order Management (DOM) routing117- Unified returns processing118- Service Console for agents119120**When to use OMS:** Complex multi-location fulfillment, high order volume, omnichannel requirements, high return complexity. Evaluate ROI vs. native order management.121122### Order Events123124| Platform | Key Events |125|---|---|126| B2C | Order Created, Status Changed, Exported, Cancelled |127| B2B | Order Submitted, Approved, Rejected, Shipped (via Platform Events / CDC) |128| OMS | OrderSummary Created, FulfillmentOrder Created, Shipment Confirmed, Return Initiated |129130## Code Examples131132```javascript133// Pattern: B2C order status check134// Fetch live docs for SCAPI Shopper Orders endpoints135// GET /orders/{orderNo} -> check order.status136```137138```apex139// Pattern: B2B approval trigger140// Fetch live docs for Process Builder / Flow order approvals141// Order.Status changes from Draft -> Activated -> triggers approval142```143144## Best Practices145146### Order Creation147- Validate basket/cart before conversion (inventory, pricing, address)148- Capture payment authorization synchronously; handle failures with retry logic149- Use idempotent operations to prevent duplicate orders150151### Fulfillment Integration152- Export orders to fulfillment system within minutes of creation153- Use idempotent export to avoid duplicate orders in downstream systems154- Support partial shipment status updates per line item155156### B2B-Specific157- Persist carts across sessions; support multiple named carts per account158- Configure approval thresholds per buyer group or account159- Enforce credit limits at checkout before order submission160161### Monitoring162- Track order creation rate, export failures, and fulfillment SLA in real-time163- Alert on stuck orders (no status change within expected window)164- Monitor refund processing time and payment authorization success rates165166Fetch the SCAPI Shopper Orders reference and Salesforce Order object docs for exact schemas and field names before implementing.