Globale-OrderUpdateStatus webhook cannot deliver a status change (merchant outage, rate limit, network error, and so on), Global-e can optionally write the same status payload to an SFTP folder. The SFCC job GlobaleOrderStatusFallback downloads those files and applies the updates, with deduplication against updates already received via webhook.
Prerequisites
Contact Global-e Merchant Support to request enablement. Merchant-facing technical setup on SFCC is documented in GlobaleOrderStatusFallback.
What merchants get
- Durable recovery when the webhook fails or is delayed
- Same status-apply behaviour as the live webhook (including cancellation / completed transitions where supported)
- No double-application when the webhook later succeeds (shared
OrderStatusUpdateTimededup)
What merchants do not need to change
- No storefront customization is required for the OOTB path
- The live webhook remains the primary channel; the job is complementary
See also
- GlobaleOrderStatusFallback — job steps, BM setup, IMPEX layout, troubleshooting
- Order lifecycle — inbound status notifications
- Jobs overview

