> ## Documentation Index
> Fetch the complete documentation index at: https://docs.global-e.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Global-e Order

After checkout, Global-e synchronizes order state to SFCC through authenticated **`Globale-*`** controller endpoints. This page covers post-create updates; the checkout sequence is in [Checkout flow](/checkout-flow-sfcc).

**Read order:** [Checkout flow](/checkout-flow-sfcc) → [Order lifecycle](/order-lifecycle-sfcc) (this page) → [Failover and recovery](/failover-sfcc).

**See also:** [Metadata → Order](/metadata-sfcc#order) · [Hooks](/hooks-sfcc) · [Configuration](/configuration-sfcc)

## Order numbers on the storefront

By default (unless configured otherwise on the Global-e side), international shoppers see the **Global-e order number** on order confirmation, order history, and transactional emails. Domestic orders continue to show the SFCC order number.

The Global-e order number is stored on the SFCC order as **`geOrderNumber`** and is what international shoppers see on confirmation, order history, and emails (unless configured otherwise on the Global-e side). See [Metadata → Order](/metadata-sfcc).

## Post-create endpoint summary

| Global-e notification | SFCC endpoint | Typical OOTB effect |
| - | - | - |
| Send Order To Merchant (SOTM) | `Globale-OrderSendToMerchant` | Order **Created** → **New**; confirmation **Confirmed**; international attributes written |
| Perform payment | `Globale-OrderPerformPayment` | Payment **Paid**; export **Ready for export** |
| Update order status | `Globale-OrderUpdateStatus` | Status changes (for example **Cancelled**). Optionally, if Global-e enables SFTP export for the merchant, the same payload can be delivered via SFTP for the [order status SFTP fallback](/order-status-sftp-fallback-sfcc) job |

\| Update shipping info | `Globale-OrderUpdateShippingInfo` | Tracking number/URL updated; SFCC shipping status not set to **SHIPPED** |
\| Order refund | `Globale-OrderRefund` | Refund notification; notes/logs by default |

Platform setting **`sfccPlaceOrderOnPaymentUpdate`** (Global-e App Settings) changes timing: when enabled, **place** and **confirm** run on **`Globale-OrderPerformPayment`** instead of SOTM.

## Order confirmed

When Global-e confirms the order, it sends **Send Order To Merchant** to **`Globale-OrderSendToMerchant`**.

OOTB the cartridge places the order (status **New** unless deferred by **`sfccPlaceOrderOnPaymentUpdate`**) and sets confirmation status to **Confirmed**. This update normally arrives within seconds of order create.

If no matching SFCC order exists (for example order create failed in checkout), SOTM can create the order from the payload — see [Failover and recovery](/failover-sfcc). Orders created this way are flagged with **`geIsOrderCreatedFallbackScenario`**.

## Order paid

When payment and fraud checks pass, Global-e sends the payment update to **`Globale-OrderPerformPayment`**.

OOTB payment status becomes **Paid** and export status **Ready for export**. This notification is expected after order confirmed (or performs place/confirm when **`sfccPlaceOrderOnPaymentUpdate`** is enabled).

## Order cancelled

If payment/fraud checks fail or Global-e does not confirm the order, Global-e may send **`Globale-OrderUpdateStatus`** and/or **`Globale-OrderRefund`**.

The customer is refunded on the Global-e side. OOTB the SFCC order status becomes **Cancelled**; payment status remains **Not Paid**. These updates normally follow order confirmed.

## Shipping status updated

When shipment events occur on the Global-e side, Global-e may call **`Globale-OrderUpdateShippingInfo`**.

Tracking number and URL are updated from the payload. OOTB SFCC order shipping status is **not** set to **SHIPPED**. Merchants can update SFCC shipping status when the order is dispatched to the Global-e hub.

## Order refunded

When an order is refunded on the Global-e side (not via a merchant API call to Global-e), Global-e sends **`Globale-OrderRefund`**.

OOTB the cartridge does not update order custom attributes on refund notifications. Refund notifications add an order note (subject **`GLOBALE_REFUND_NOTIFICATION`**); processing errors are written to the **GLOBALE** custom log (for example message prefix **`ORDERS_REFUND_UPDATE`**). Customize behavior with **`globale.onAfterRefund`** — see [Hooks](/hooks-sfcc).