Skip to main content
Global-e ships six cartridges. Every Global-e site needs int_globale plus one storefront cartridge (or popups-only variant). See Installation and Configuration for upload, metadata import, and Business Manager steps.

​
Required cartridges

Choose one storefront cartridge per site (int_globale_sitegenesis, int_globale_sfra, or int_globale_headless). SFRA and SiteGenesis cartridges extend templates, models, and controllers for Global-e checkout and pricing.

​
Optional cartridges

Popups cartridges provide a lightweight integration (Client JS SDK / Country Switcher) without full cross-border checkout.

​
Cartridge path (summary)

Path order details are in Configuration.
int_globale must appear after cartridges that override its controllers, models, or factories.

​
Upload with the b2c CLI

From the repository root, deploy the cartridge set for your architecture to the active code version (replace the hostname with your sandbox): If you build client assets from source, run the compile scripts in package.json before deploy. See Installation for metadata import order.

​
Business Manager cartridge path

Organization-context job steps in GlobaleSettings (for example GlobaleUpdateCachePriceBooksConfigHash with <context site-id="Sites"/>) resolve scripts from the Business Manager cartridge path, not from storefront site paths. Add int_globale to the BM path: Administration > Sites > Manage Sites > Business Manager (header link) > Settings > Cartridges Or use the B2C CLI (recommended for automation):
Only int_globale is required on the BM path for org job steps — storefront cartridges (int_globale_sfra, brand overrides, and so on) stay on each storefront site.

​
Next steps

1
Installation — upload cartridges and import metadata
2
Configuration — site cartridge path, site preferences, jobs
3
Metadata reference — full site-preference and custom-attribute list
4
Production readiness — checklist for promoting the integration from Staging to Production