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

# Readiness Assessment

Complete the following steps when deploying the Global-e integration from SFCC Staging to SFCC Production.

**In the Staging Environment:**

1. Check the Global-e metadata, if something is missing, import the metadata from the **link\_globale/metadata** folder.
2. Check Global-e Shipping Methods. There should be seven methods: GLOBALE, GLOBALE\_STANDARD, GLOBALE\_EXPRESS, GLOBALE\_STORE\_COLLECTION, GLOBALE\_HUB, GLOBALE\_DIRECT, and GLOBALE\_WYOL. If missing, import the metadata from the **link\_globale/metadata** folder.
3. Check Global-e Payment Methods and Payment Processor on Staging – GLOBALE. If missing, import the metadata from the **link\_globale/metadata** folder or create it manually (Payment Processor).
4. Check the Tax Class for Global-e Shipping Methods. it should not be set to **undefined** (after fresh import it might be reset to undefined).
5. Check the configuration of Global-e custom Site Preferences. Add values for Production (on Staging, in a Production context, so it is replicated properly).
6. Check the time configuration of 'Auto-Fail Orders' (**Merchant Tools** > **Site Preferences** > **Order**). By default, the recommended time is 4320 minutes. If the site preference **Place Order On Payment Update** (`gePlaceOrderOnPaymentUpdate`) is set to **Yes** then the recommended time is 20160 minutes.
7. Check all Price books, including the Fixed Price books, if any configured in Global-e custom Site Preferences.
8. Check Global-e Services, Job Schedules on Staging and Production. If missing, import them from the **link\_globale/metadata** folder on Staging and Production.
9. Check that the GLOBALE Service profile is configured so that the Rate Limit is disabled (Enable Rate Limit = false).
10. Check the definitions for Global-e Custom Objects on Staging – GLOBALE\_\*. If missing, import the metadata from the **link\_globale/metadata** folder.
11. Check that **int\_globale** and the Global-e extension (**int\_globale\_sitegenesis** for SiteGenesis Pipeline or Controller-based storefront, **int\_globale\_sfra** for SFRA-based storefront) cartridges are uploaded into the current code version on SFCC Staging, to be replicated properly to SFCC Production.
12. Check that **int\_globale** and Global-e extension cartridges are in the cartridge path of your Site (Global-e-operated Sites).
13. **If all the above is verified and looks good, perform Data Replication to Production** (Services, Job Schedules, Metadata, Site Preferences, Custom Object Definitions, Shipping Methods, Payment Methods, Customer Groups, etc.). If anything prevents you from making a data replication from Staging to Production, perform all the above manually on Production (if possible).
14. Perform Code Replication to Production.

**In the Production Environment:**

1. Check that **int\_globale** and Global-e extension cartridges (**int\_gloable\_sitegenesis** for SiteGeesis, **int\_globale\_sfra** for SFRA) are in the cartridge path of your Site (operated by Global-e Sites) on Production.
2. Manually check the Global-e custom Site Preferences, Services, Job Schedules (should be assigned to proper Site(s)), Custom Object definitions, Payment, and Shipping Methods on Production.
3. Run Global-e Settings Job manually.
4. Enable the Global-e Settings Job to run daily at 2:00 am UTC (or other off-peak time).
5. Check that GLOBALE\_\* custom objects now have some records and verify that there are no errors in the GLOBALE\_ERROR custom error log on Production.
6. Enable **Global-e** in Global-e custom Site Preferences on Production.
7. Clear manually the cache of the Site(s) and BM on Production.
8. Run tests on the Storefront of your Production.