Skip to main content
This page covers two recovery scenarios: disabling Global-e when services are unavailable, and order-create fallback when SFCC cannot create an order during checkout but Global-e still completes the sale. See also: Checkout flow · Order lifecycle · Introduction → SOTM · Metadata → Order (geIsOrderCreatedFallbackScenario)

​
Disable Global-e integration (manual failover)

If Global-e services are unavailable, operators can disable the integration by setting site preference geEnabled (display name Global-e Enabled) to No. Domestic checkout continues on SFCC. Operated-country shoppers no longer route to Global-e until the preference is re-enabled and Global-e settings are current (run the GlobaleSettings job after re-enabling — see Configuration).

​
Order-create fallback (SOTM recovery)

Checkout normally creates a minimal SFCC order in the shopper session via Globale-OrderCreate or Globale-OrderCreateV2. Session loss, stock issues, or basket drift can cause this step to fail after the shopper has already paid on Global-e.

​
How recovery works

1
Order create response — On failure, the cartridge may return SFCC order number -1 (ORDER_CREATE_BYPASS_NO) — this applies to both Globale-OrderCreate and Globale-OrderCreateV2. Global-e treats this as a signal to continue and send Send Order To Merchant (SOTM) with the full order payload.
2
SOTM creates the order — Globale-OrderSendToMerchant searches for an existing order by SFCC or Global-e order number. If none exists, the cartridge builds a temporary basket from the SOTM payload (generateBasketFromPayload), creates the SFCC order, then applies the same place/confirm and attribute updates as the happy path.
3
Fallback flag — Orders created from an SOTM-generated basket set geIsOrderCreatedFallbackScenario on the order (and basket during generation). This drives coupon/price-adjustment handling differences in the SOTM handler.
Recovery is automatic on the Global-e side once order create returns -1 or when SOTM arrives without a matching SFCC order. Merchants should monitor GLOBALE_ORDER_* logs for collision or validation errors (for example duplicate MerchantOrderId or cart-hash mismatch when sfccCartHashValidation is enabled).

​
What this is not

  • Manual geEnabled disable does not replay failed orders; it only stops new Global-e checkout sessions.
  • SOTM must not receive MerchantOrderId = -1 in the payload (that value is reserved for the order-create bypass response only).
For endpoint sequencing and status transitions after recovery, see Order lifecycle.