Create a reusable template
Group native Magento custom options into a template your team can apply across selected products. Maintain store-view labels where you need them.

Build a custom-option template once and apply it to selected products. Maintain reusable native Magento options while preserving merchant options and other templates.
For Magento Open Source 2.4.9. Review the module guide for installation, dependencies and frontend integration requirements. We can help check the fit with your existing store.
Group native Magento custom options into a template your team can apply across selected products. Maintain store-view labels where you need them.

Each template tracks the options it created. Later synchronisations preserve options owned by the merchant or another template, reducing accidental interference.

Check the module guide, supported version and setup requirements for your store.
Install and configure on staging. Test the workflows that matter to your team.
Deploy the tested configuration and use the included support when you need help.
Review the supported version and module guide, and test on staging with your current theme and extensions. Luma presentation and headless integration requirements vary by module; contact us if you need help checking compatibility.
The one-time licence includes 12 months of updates and priority support. Purchased versions remain usable. Renewal is optional and never billed automatically; see the current purchase terms for eligibility and renewal details.
Yes. AgenticSuite includes the Astro storefront and all headless and Luma-compatible modules listed on this website. You can buy this module for the store you run today, or discuss the complete platform for a frontend rebuild.
Global Custom Options 1.0.2 lets you define native Magento product custom options in a template, assign products in Admin, and apply the template on save. Text, selectable, date/time and file-upload options use Magento's standard product option flow. The Luma product page and cart were tested on Magento Open Source 2.4.9.
Saving the template syncs its currently selected products. Removing an assignment stops future syncs; it does not remove options already applied. Options written by releases before 1.0.2 have no ownership record. On the first sync after upgrading, the old options remain and a second copy may be added, so review a representative previously assigned product first.
Build templates in Catalog > Inventory > Global Custom Options. Choose products in the searchable assignment grid. Import options from an existing product SKU to start a new template. Set option and value label overrides for store-view languages. Export templates to CSV, edit them and import them by template code. The 1.0.2 CSV includes option_key so separate options with the same title survive a round trip; legacy files without the key remain importable. Import rejects duplicate or empty headers and incorrect row widths before making template changes. CSV import updates template definitions; open and save the imported template to apply it to products.
Installed through Composer, upgraded, compiled and exercised on Magento Open Source 2.4.9 / PHP 8.5.10, including admin product selection, CSV import/export, native option sync, Luma product pages and cart. Other editions, versions and custom themes need separate qualification. No external service or AgenticEcom Core is required. A headless storefront can consume Magento's native option data but must implement its own option and checkout flow.
Read the Global Custom Options user guide for setup, sync modes, CSV format and the upgrade caveat.
A one-time purchase includes 12 months of updates and support. Renewal is optional and never billed automatically. Eligible standalone extensions may renew at 60% of the then-current regular list price before term end or within 30 days afterward, plus applicable tax. Purchased versions remain usable afterward. See the AgenticEcom licence and your order terms. Support: support@agenticecom.net.
No. Version 1.0.2 refreshes only the options owned by that template. Options from earlier releases are untracked and stay in place on the first sync.
No. It matches the positions previously applied by that template.
Export CSV, then import it on the destination. Keep option_key so same-title options remain separate. Review the imported template and save it with its target product assignments.
Keep improving the store you run today. When you need a full frontend rebuild, AgenticSuite combines the Astro storefront, visual admin and included module collection.
Your source code.
Your data. Your direction.
Review the setup requirements, choose your module and get started. We’re here if you need to check the fit.