Global Data Bundle for Magento 2 — Store-Wide Data for Headless
Global Data Bundle hands a headless Magento 2 storefront everything it needs on every page in a single GraphQL query — store configuration, the category navigation tree and available payment methods. Instead of three or four separate round-trips on each render, your Astro front end pre-warms one bundle to its edge cache and reads it locally, with zero per-page calls back to Magento. It is the site-wide companion to the Product Shell and CMS Sync bundles.
No subscriptions — pay once. Includes 365 days of free updates & support. Keep using the version you have for as long as you like, and renew any time at 60% of the price for another year of updates.
Every headless page needs the same handful of facts — so stop fetching them every time
Currency and locale, the store's base URLs and settings, the category tree for the menu, the payment methods for checkout — a headless storefront needs this same site-wide data on practically every page. Fetch it fresh each render and you've added three or four GraphQL round-trips to every single request, for data that barely changes. Global Data Bundle packages all of it into one query you fetch once, cache at the edge, and read locally — so your pages stop waiting on Magento for things they already know.
Store config · Category tree · Payment methods · One query · Pre-warm to the edge · Zero per-page round-trips · Magento 2.4.9 · PHP 8.4 / 8.5
| Store configuration | Currency, locale, base URLs and the store settings your front end reads on every page. |
|---|---|
| Category tree | The navigation tree for menus and breadcrumbs, fetched once instead of per request. |
| Payment methods | The available payment methods your checkout needs, in the same bundle. |
| One cacheable call | Pre-warm the bundle to your edge cache and read it locally — no per-page calls back to Magento. |
What you'll use it for
- Bootstrap the storefront — load the site-wide essentials once at build or warm-up, then serve every page from cache.
- Render menus and breadcrumbs — use the cached category tree instead of querying it on each navigation render.
- Set up checkout — have the available payment methods ready without an extra live call.
- Cut Magento load — remove the repeated site-wide queries that otherwise hit your backend on every page view.
How it works
The same pattern, for the whole site
It completes the bundle family. Where the Product Shell Bundle pre-warms product data and the CMS Sync Bundle pre-warms content, Global Data Bundle pre-warms the site-wide layer — the configuration, navigation and payment data every page depends on. All three share the same idea: fetch the slow-to-change data once, cache it at the edge, and let the front end read it locally, so Magento is only ever queried for what's genuinely live. Together they're how a headless storefront stays fast without hammering the backend.
Specifications
| Query | globalDataBundle — one call for all site-wide data |
|---|---|
| Store config | Currency, locale, base URLs and store settings |
| Navigation | Category tree (nodes with structure) |
| Checkout | Available payment methods |
| Design | Pre-warm to an edge blob; zero per-page round-trips |
| Family | Site-wide companion to Product Shell Bundle and CMS Sync Bundle |
| Delivery & licence | Composer install, per-domain licence key, updates via Composer |
Works with
Part of the AgenticEcom suite for Headless & Astro:
Completes the bundle trio with Product Shell and CMS Sync; refresh the cache with Astro ISR. Included in the Enterprise bundle and the Astro frontend licences.
See it in action
Frequently asked questions
What data does the bundle return?
The site-wide essentials a headless storefront needs on every page: store configuration (such as currency, locale and base URLs), the category navigation tree, and the available payment methods — all in one query.
Why fetch this once instead of per page?
This data changes rarely but is needed everywhere. Fetching it on every render adds several round-trips per page; fetching it once and caching it at the edge removes them, so your pages don't wait on Magento for facts they already hold.
How does it relate to the other bundles?
It's the site-wide layer of the same pattern: Product Shell Bundle pre-warms product data, CMS Sync Bundle pre-warms content, and Global Data Bundle pre-warms configuration, navigation and payment data.
How do I keep the cached data current?
Pair it with Astro ISR, which fires a purge when relevant content changes, so the bundle is refreshed when it needs to be rather than on a timer.
Which Magento and PHP versions are supported?
Magento Open Source 2.4.9 and later 2.4.x, verified on PHP 8.4 and 8.5.
