Magento
Open Source 2.4.9 GA (and later 2.4.x).
Sync Data (Suite Parent)
Sync Data is the small infrastructure module that ties the headless-storefront sync suite together. It owns one thing: the shared “Sync Data” admin menu and its ACL resource. Each of the suite’s data modules attaches its own admin page and permission under this parent, so they appear as one tidy, ordered group in the admin and share a single access-control branch.
Compatibility
Section titled “Compatibility”PHP
Tested on 8.4 and 8.5.
Type
Infrastructure — menu + ACL parent only.
Install
Comes in automatically with any sync module.
What attaches under it
Section titled “What attaches under it”| Menu leaf | Provided by | What it does |
|---|---|---|
| CMS Block Bundle | CmsBlockBundle | Bundles CMS blocks for a headless storefront |
| CMS Page Bundle | CmsBlockBundle | Bundles CMS pages for a headless storefront |
| Product Shell Bundle | ProductShellBundle | Pre-warmed product shells (JSON + GraphQL) |
| Global Data Bundle | GlobalDataBundle | Store config + categories + payment methods |
| URL Rewrite Bundle | UrlRewriteData | URL rewrites for headless routing |
| Schema Explorer | SchemaDiscovery | Discover the GraphQL API surface |
Why a separate parent module?
Section titled “Why a separate parent module?”One menu, stable order
Each sync module declares its own menu leaf with a fixed sort order, so the group always renders in the same sensible sequence regardless of install order.
One ACL branch
The parent owns AgenticEcom_SyncData::sync_data; every sync module’s view permission hangs off
it, so an admin role can be granted the whole suite (or individual tools) cleanly.
Always installed together
Every sync module depends on this parent, so the menu and ACL always exist — no module has to duplicate them, and none can render an orphaned menu item.
Do I need to configure Sync Data?
No — it has no configuration. It only provides the shared admin menu and ACL resource that the sync modules attach to. Configure each sync module on its own page instead.
Why is it installed if I only wanted one sync module?
Every sync module depends on this parent so the “Sync Data” menu and its permission branch always exist. Installing any one sync module brings it in automatically — it’s lightweight and has no runtime behaviour of its own.
Can I grant access to just one sync tool?
Yes — because each tool’s permission hangs off this parent’s ACL branch, you can grant an admin role the whole suite or any individual tool from System → Permissions → User Roles. Verified clean on PHP 8.4 and 8.5.