salesforcecommercecloud/b2c-ops
B2C Commerce operator and administrator runbooks for job health, checkout and failed orders, eCDN edge traffic, and incident triage.
Investigate B2C Commerce checkout or payment failures, increased failed orders, or falling order volume. Compare bounded order evidence, integration logs and affected data; separate payment failures from traffic and reporting gaps.
Investigate bots, scrapers, crawlers, credential or token abuse, API abuse, and edge 403/429 or error spikes hitting a B2C Commerce storefront or SCAPI through the eCDN (CDN edge). Review WAF, firewall and rate-limiting protections, correlate available traffic evidence, and propose narrowly scoped rule changes for approval.
Investigate failing, slow or silent calls from B2C Commerce to external services (payment, tax, shipping, OMS, search, email, custom APIs) using Metrics API third-party signals (call volume, p95 duration, remote exceptions by host) with logs and service configuration. Decide whether the provider is slow or unreachable, whether calls stopped, or whether the fault is elsewhere.
Review B2C Commerce scheduled jobs during routine operations or investigate failed jobs, missing runs, stale imports, and green executions with incomplete results. Check logs and business data before proposing a rerun.
Find and investigate FAILED B2C Commerce orders, quantify their share of indexed orders, and correlate failed inputs with logs and jobs. Covers SCAPI status-filter limitations and the OCAPI Shop order_search fallback.
Investigate slow or erroring B2C Commerce storefront, SCAPI, OCAPI or SFRA responses using Metrics API signals (overall traffic and p95, SCAPI family latency and status class, SFRA controller duration and errors, SCAPI hook time, cache, third-party calls, system workload, Managed Runtime). Localize a latency or error change to a layer, route or dependency and since when, then hand off with evidence.
Investigate B2C Commerce incidents using B2C MCP logs, SCAPI code-mode job/data reads, and CLI fallbacks. Route error spikes, stale data, or checkout failures to focused runbooks and produce a team or Support handoff.