Production readiness

Use this checklist when promoting a working Global-e integration from SFCC Staging to SFCC Production. It assumes Installation and Configuration are complete and tested on Staging, and walks through what to verify before replication, what replication does and does not carry, and what to finish by hand on Production before enabling Global-e for shoppers.

See also: Installation, Configuration, Cartridges, Requirements, Jobs, Failover and recovery.

Overview

A production rollout has four phases:

1. Verify Staging — every Global-e artifact is present, and instance-specific values are entered in the Production context.
2. Replicate — code replication first, then data replication.
3. Complete Production by hand — the items Salesforce B2C Commerce does not replicate.
4. Go live — run GlobaleSettings, enable Global-e, clear caches, and smoke-test.

What replication carries

Plan the manual steps around what Salesforce B2C Commerce data replication does not move between instances:

Artifact	Carried by replication	What to do on Production
Cartridges (code version)	Code replication	Activate the replicated code version; confirm Global-e cartridges are inside it
System object attributes, custom object definitions	Data replication (global metadata)	Verify after replication
Site preferences (ge*), order preferences, URL rules, payment and shipping methods	Data replication (site)	Verify values in the Production context
Price books, promotions, customer groups	Data replication (global / site)	Verify
Site and Business Manager cartridge paths	Data replication (site settings)	Verify; fix on Staging and re-replicate rather than editing Production directly
Job schedules	Not replicated	Import metadata/jobs.xml on Production and assign flows to Production site IDs
Service definitions, profiles, and credentials	Not replicated — passwords are stripped from any export	Import metadata/services.xml on Production; create Globale-{merchantId} and any SFTP credentials by hand
Custom Log Settings	Not replicated	Configure the GLOBALE custom log on Production
GLOBALE_* custom object records	Optional (site Custom Objects task)	Prefer populating them on Production by running GlobaleSettings — see Custom objects

Salesforce reference: Data Replication Processes in B2C Commerce.

Before you start

Coordinate the following with Global-e Merchant Support before touching Production:

Item	Why
Production merchant account is enabled on the Global-e platform	Platform-side behaviour (countries, payment methods, checkout settings) must be enabled by Global-e before the SFCC steps below
Production API base URL (geApiUrl), Client JS SDK base URL (geClientJsBaseUrl), Client JS Merchant ID (geClientJsMerchantId), and Merchant GUID	Production values differ from the QA / integration environment used on Staging
Your Production storefront hostname(s)	Global-e calls the Globale-* storefront endpoints on your Production domain for cart validation, order creation, and order updates
Production OCAPI Data API client ID, secret, base URL, and OCAPI version	Required for new integrations — see Configuration → Data API
A test order plan (test country, payment method, refund)	Agree who places, confirms, and refunds the go-live test orders

Also confirm that every instance — Staging and Production included — runs SFCC Compatibility Mode 17.7 or newer (Requirements).

Staging checklist

Work through this list on Staging. Where a value is instance-specific, enter it in the Production instance-type context on Staging so it is replicated with the correct value.

Code

Check	Expected
Global-e cartridges are in the active code version on Staging	int_globale plus the storefront cartridge for your architecture — see Cartridges
The build is a tagged release, not a development snapshot	Use a release from the SFCC-Releases mirror or a tagged SFCC-certified build
Client assets are compiled	If you build from source, run the compile scripts in package.json before upload — see Installation
No QA, mock, or sandbox-only cartridges are in the cartridge path	Only cartridges intended for shoppers

Cartridge paths

Administration → Sites → Manage Sites → (Your Site) → Settings

Check	Expected
Storefront site path	Global-e cartridges in the position documented in Configuration — SFRA: brand cartridges : int_globale_sfra : int_globale : app_storefront_base; SiteGenesis: int_globale_sitegenesis : int_globale : brand cartridges; headless: int_globale_headless before int_globale
Business Manager path	int_globale on the Business Manager site path so organization-context GlobaleSettings steps resolve — see Cartridges → Business Manager cartridge path
Sites not operated by Global-e	No Global-e storefront cartridge, unless the site uses a popups-only cartridge for the Country Switcher

Metadata

Check	Where	Expected
System object custom attributes (ge*)	Administration → Site Development → System Object Types	Present on Site Preferences, Product, Order, Basket, Price Book, Shipping Method, and the other objects listed in Metadata
Custom object definitions	Administration → Site Development → Custom Object Types	Every GLOBALE_* type from metadata/meta/custom-objecttype-definitions.xml
Demo data	—	Nothing from metadata/demo/ (including DEMO_GLOBALE_* types and demo customer groups) is destined for Production

If anything is missing, re-import from metadata/ in MERGE mode in the order given in Installation → Import metadata.

Site preferences

Merchant Tools → Site Preferences → Custom Site Preference Groups

Select the Production instance type before editing so the value replicates to Production.

Preference	Production value
Global-e Enabled (geEnabled)	No until go-live; you enable it on Production as the last step
Global-e API Base URL (geApiUrl)	Production API base URL from Global-e (for example https://connect.bglobale.com)
Global-e Client JS SDK Base URL (geClientJsBaseUrl)	Production SDK base URL from Global-e
Client JS Merchant ID (geClientJsMerchantId)	Production merchant account ID (for example 10001)
Service Endpoint Config (geServiceEndpointConfig)	Empty unless you intentionally override a service; remove any QA-only overrides — see Services configuration
Used SFCC CAPI Type (geCAPIType) and the OCAPI / SCAPI groups	Production client IDs, domain, and versions for headless / Commerce API integrations — see Commerce API support
Global-e Product Settings (GLOBALE-PRODUCT group)	Same as Staging (image view type, attribute keys)
Global-e Catalog Jobs (geCatalogFeedConfig, geRestrictedItemsFeedConfig)	Production SFTP and feed settings if these jobs are in scope

Full descriptions are in Metadata → Site Preferences.

Order preferences

Merchant Tools → Site Preferences → Order

Preference	Expected
Limit Storefront Order Access	Allow List containing every Globale-* endpoint listed in Configuration → Order Preferences
Filter Storefront Orders by Customer Session	No
Auto-Fail Orders	Set (not empty). Use 4320 minutes by default; 20160 when your Global-e account is configured to place orders on payment update — see Configuration

Payment and shipping

Check	Where	Expected
Payment processor GLOBALE	Merchant Tools → Ordering → Payment Processors	Exists (metadata does not create it — see Configuration → Payment Processor)
Payment method GLOBALE	Merchant Tools → Ordering → Payment Methods	Enabled and assigned to processor GLOBALE
Shipping methods	Merchant Tools → Ordering → Shipping Methods	All seven present and online: GLOBALE, GLOBALE_STANDARD, GLOBALE_EXPRESS, GLOBALE_STORE_COLLECTION, GLOBALE_HUB, GLOBALE_DIRECT, GLOBALE_WYOL
Shipping method Tax Class	Each Global-e method	Standard or a valid custom tax class — never Undefined (a fresh import can reset it) — see Configuration → Shipping methods
Default currency	Administration → Sites → Manage Sites → (Your Site) → General	The merchant base currency — see Configuration → Default Currency Settings

URL rules

Merchant Tools → SEO → URL Rules → Pipeline URLs

Alias	Pipeline
globale/checkout/pspredirect	Globale-PaymentRedirect

Price books and promotions

Check	Expected
Base price book(s)	geBasePricebook = true, online, correct geApplicableToDynamicCountries scope
Fixed price book(s), if any	geFixedPricebook = true, online, non-empty geApplicableToFixedCountries, currency matches each fixed country
Cache price books	Leave to GlobaleSettings — the job generates and imports them on each instance when Enable Cache Price Books (geEnableCachePriceBooks) is on
Promotions and customer groups that use session.custom.ge* attributes	Present and scheduled for Production — see Promotions and Customer groups

Configuration detail and the post-change checklist are in Price calculation.

Services

Administration → Operations → Services

Check	Expected
Service instances	Every Globale-* service from metadata/services.xml is present and enabled
Service profiles	GLOBALE-* profiles present with Enable Rate Limit unchecked (as shipped), in particular GLOBALE-SENDCART used by Globale-SendCartV2
Mock mode	Disabled on every Global-e service
Communication log	Enabled on Global-e services for at least the first weeks after launch
Merchant GUID credential	Globale-{geClientJsMerchantId} (for example Globale-10001) exists with an empty URL and the Merchant GUID as password — see Configuration → Merchant GUID credentials
SFTP credentials	Globale-SFTPCatalogFeedUpload, Globale-SFTPRestrictionsFeedUpload, Globale-SFTPDownload filled in only for the feeds in scope

Service definitions and credentials are not replicated. Treat this section as a preview of what you will re-create on Production; the Staging Merchant GUID is typically not the Production one.

Jobs

Administration → Operations → Jobs

Check	Expected
Job definitions	GlobaleSettings, GlobaleProducts, GlobaleOrderNotifications, GlobaleCatalogFeed, GlobaleOrderStatusFallback imported from metadata/jobs.xml
Site assignment	Flows assigned to the Global-e operated site IDs — replace the sample RefArchGlobal — see GlobaleSettings → Site context
Enabled jobs	Only the jobs in your integration scope; GlobaleProducts stays on Staging / development only (GlobaleProducts) and product attributes reach Production through catalog replication

Job schedules are not replicated; you repeat the import on Production.

Open Commerce API settings

Administration → Site Development → Open Commerce API Settings

Check	Expected
Data API, context Global	The dedicated Global-e client with the resources from metadata/ocapi-settings/wapi_data_config.json — see Configuration → Data API
Shop API (headless / Commerce API only)	Your headless client with the resources from metadata/ocapi-settings/wapi_shop_config.json
Account Manager API client	Assigned to the Production instance as well as Staging; enabled

Custom objects

Merchant Tools → Custom Objects

On Staging, confirm GLOBALE_APP_SETTINGS, GLOBALE_COUNTRIES, GLOBALE_CURRENCIES, GLOBALE_CULTURES, GLOBALE_CURRENCY_RATES, GLOBALE_ROUNDING_RULES, GLOBALE_COUNTRY_COEFFICIENTS, and GLOBALE_HUB_DETAILS hold records after a GlobaleSettings run — this proves the merchant account, GUID, and API base URL are correct.

Do not rely on replicating these records to Production. Run GlobaleSettings on Production instead, so the data reflects the Production merchant account. The queue objects GLOBALE_ORDER_NOTIFICATION, GLOBALE_INBOUND_ORDER_FALLBACK, GLOBALE_INVENTORY_NOTIFICATION, GLOBALE_COUPON_REDEMPTIONS, and GLOBALE_LOCAL_STORAGE are created on Production during operation and must not be overwritten by Staging records.

Replicate to Production

1. Code replication first. Replicate the code version that contains the Global-e cartridges and activate it on Production. If the cartridge path reaches Production before the cartridges do, storefront requests fail.
2. Data replication second. Include the tasks that cover the artifacts above: global metadata (system object types, custom object types), global preferences and OCAPI settings, sites (site preferences, cartridge paths, URL rules, payment and shipping methods), price books, promotions, and customer groups.
3. Follow Salesforce guidance during the run: no Business Manager edits on either instance, no jobs running on the target, one replication process at a time, and do not clear caches by hand immediately after — replication clears them as its last step.
4. Use the replication Undo only as an emergency rollback of the data step; it does not touch code.

If your organization does not use data replication, perform every item in the Staging checklist directly on Production with the same import files.

Production checklist

Complete these on Production after replication. Everything here is either not replicated or is instance-specific.

Step	Where	Detail
Activate the code version	Administration → Site Development → Code Deployment	Global-e cartridges are inside the active version
Verify cartridge paths	Administration → Sites → Manage Sites	Storefront site path and Business Manager path as on Staging. If wrong, fix on Staging and re-replicate
Import services	Administration → Operations → Import & Export	Import metadata/services.xml in MERGE mode
Create the Merchant GUID credential	Administration → Operations → Services → Credentials	Globale-{geClientJsMerchantId} with the Production Merchant GUID as password, URL empty. One credential per merchant account ID used on the instance
Create SFTP credentials	Same screen	Only for feeds in scope (Globale-SFTPCatalogFeedUpload, Globale-SFTPRestrictionsFeedUpload, Globale-SFTPDownload)
Check service settings	Administration → Operations → Services	All Globale-* services enabled, mock mode off, rate limit off on GLOBALE-* profiles, communication log on
Import jobs	Administration → Operations → Import & Export	Import metadata/jobs.xml; assign flows to Production site IDs; keep every job disabled for now
Configure custom logging	Administration → Site Development → Development Setup → Custom Log Settings	Add the GLOBALE category (at least INFO for launch week) so GLOBALE_* custom logs are written
Verify site preferences	Merchant Tools → Site Preferences → Custom Site Preference Groups	Production values for geApiUrl, geClientJsBaseUrl, geClientJsMerchantId, geCAPIType and related groups; geEnabled still No
Verify order preferences	Merchant Tools → Site Preferences → Order	Allow list, session filter No, Auto-Fail Orders set
Verify payment and shipping	Merchant Tools → Ordering	Processor GLOBALE exists; method GLOBALE enabled; seven GLOBALE* shipping methods online with a valid Tax Class
Verify URL rule	Merchant Tools → SEO → URL Rules	globale/checkout/pspredirect → Globale-PaymentRedirect
Verify OCAPI settings	Administration → Site Development → Open Commerce API Settings	Data (and Shop, if headless) client JSON present; settings can take a few minutes to become effective
Verify metadata	Administration → Site Development	ge* attributes and GLOBALE_* custom object types present
Check edge security	eCDN / WAF / bot management	Server-to-server calls from Global-e to the Globale-* endpoints on your Production hostname must not be blocked by storefront password protection, IP allow lists, or bot rules. Ask Global-e Merchant Support for what you need to allow-list
Share Production details with Global-e	Secure channel	Production storefront URL(s), OCAPI Data client ID and secret, OCAPI version — see Configuration → Data API

Go-live

Run these in order on Production:

1. Run GlobaleSettings manually and wait for it to finish with status OK. Check that GLOBALE_APP_SETTINGS, GLOBALE_COUNTRIES, GLOBALE_CURRENCIES, and the other configuration custom objects now contain records, and that the GLOBALE custom log and the job log show no errors. A failure here almost always means a wrong geApiUrl, geClientJsMerchantId, or Merchant GUID.
2. Enable the GlobaleSettings schedule — daily at an off-peak time (the shipped trigger is 02:00 UTC). Enable the other Global-e jobs only as their scope is confirmed: GlobaleCatalogFeed, GlobaleOrderNotifications, and GlobaleOrderStatusFallback (the last only once Global-e has enabled the SFTP feed for your account) — see Jobs → Typical setup order.
3. Set Global-e Enabled (geEnabled) to Yes on each Global-e operated site.
4. Invalidate the page cache for each site (Administration → Sites → Manage Sites → (Your Site) → Cache) and the Business Manager site, so cached pages pick up Global-e pricing and the Client JS SDK.
5. Smoke-test the storefront (below) with Global-e Merchant Support on the call.

Smoke test

Area	What to verify
Client JS SDK	Welcome pop-up / Country Switcher loads on a Production page and lists your operated countries
Pricing	One dynamic country and one fixed country (if any) show the expected prices on PDP, PLP, and cart; one non-operated country is unaffected — see Price calculation → Storefront Validation Checklist
Checkout hand-off	Proceeding to checkout from an operated country opens Global-e checkout; Globale-SendCartV2 shows a successful call in the service communication log
Order creation	A test order creates an SFCC order with payment method GLOBALE and a GLOBALE* shipping method, and the order carries Global-e order attributes — see Order lifecycle
Order updates	Status, dispatch, or refund updates arrive as expected (Global-e → SFCC via Globale-OrderUpdateStatus; SFCC → Global-e via GlobaleOrderNotifications if in scope)
Domestic flow	Domestic shoppers still see native SFCC pricing and checkout
Logs	No errors in the GLOBALE custom log or in service communication logs

If fixed-price countries show prices that look dynamically converted, see Limitations → Storefront Request Cache before changing configuration.

Rollback

Situation	Action
Global-e checkout or pricing misbehaves after go-live	Set Global-e Enabled (geEnabled) to No on the affected site and invalidate the page cache. Domestic checkout continues; operated-country shoppers stay on SFCC — see Failover and recovery
The new code version breaks the storefront	Re-activate the previous code version on Production. Remove Global-e cartridges from the cartridge path only if the previous code version does not contain them
Data replication introduced wrong configuration	Use the replication Undo on the last process, or correct the value on Staging and re-replicate

Disabling geEnabled does not replay orders that were already in progress; orders paid on Global-e are still delivered through the fallback flow described in Failover and recovery.