Global Custom Options

Magento’s native custom options are defined per product, so a “Gift Wrap” or “Engraving” option has to be rebuilt by hand on every product that needs it — and changing it later means editing each product again.

Global Custom Options fixes that. You build an option set once as a template, assign it to as many products as you like, and the module writes those options onto each product as real Magento custom options. Templates can be translated per store view, imported from a product that already has options, and bulk-managed by CSV.

Compatibility

Magento

Open Source 2.4.9 GA (and later 2.4.x).

PHP

Tested on 8.4 and 8.5.

Storefront

Writes native product custom options — works on Luma and headless (standard catalog GraphQL/REST).

Scale

One template → unlimited products, with three apply modes.

Native options under the hood

A template doesn’t add a parallel option system — it writes standard Magento custom options onto each assigned product. So the storefront, cart, checkout, order, PDF and the catalog GraphQL/REST APIs all see them exactly like hand-built options. Nothing on the frontend needs to know this module exists.

Quick start

1. Enable the module: Stores → Configuration → AgenticEcom · Catalog & Products → Global Custom Options → Enable = Yes.

2. Go to Catalog → Inventory → Global Custom Options and click Add New Template (or Import From SKU to seed one from a product that already has options).

3. Build your options in the Custom Options section (one row per option).

4. Open Assign to Products, pick an Apply Mode, and tick the products.

5. Click Save Template & Sync — the options are written to every assigned product.

Building a template

The template edit screen has four sections:

Template Details

Field	What it does
Template Name	Human label for the template (e.g. Engraving & Personalisation).
Identifier	Unique code used as the CSV upsert key. Leave blank to auto-generate from the name (lowercase, numbers, underscores).
Status	Enable/disable the template.

Custom Options

Add one row per option. Each row has a Title, a Type, Required toggle, Price, Price Type, SKU, Sort Order, and a Values box (for select types).

Option types

• Text Field, Text Area — free text (use the row’s own Price).
• Dropdown, Radio Buttons, Checkbox, Multiple Select — selectable types; each uses the Values box (one value per line).
• Date, Date & Time, Time — date/time pickers.
• File Upload — customer file attachment.

Values syntax (select types)

For Dropdown / Radio / Checkbox / Multiple Select, put one value per line in the Values box as:

Label | price | price_type

price and price_type are optional (default 0 / fixed). For example:

Classic Serif | 0 | fixed
Modern Sans | 0 | fixed
Cursive Script | 3 | fixed

Price type

Fixed — a flat amount added to the price. Percent — a percentage of the product price. Applies to both option-level and value-level prices.

Assign to Products

Pick an Apply Mode, then tick the products this template should be written to. On Save Template & Sync, the options are pushed to every selected product.

Replace

Replace — remove all existing custom options on the product, then write this template’s. Use when the template should be the single source of truth.

Update

Update — replace existing options whose title matches one in the template, add any new ones, and leave the rest untouched. Use to refresh a shared option without touching product-specific ones.

Add

Add — add this template’s options on top of whatever the product already has. Use to layer an extra option set on.

Replace is destructive

Replace deletes every existing custom option on the assigned products before writing the template’s. If products already carry hand-built options you want to keep, use Update or Add instead.

Per-Store Label Overrides

Translate option and value labels per store view without leaving the template. Add one row per language in Option Title Translations and Option Value Translations:

Column	Meaning
Default Title	The option/value title exactly as typed in the builder — used to match the override.
Store Locale	The store-view language the override applies to (e.g. de_DE).
Override Title	The translated label written for that store view.

How translations are applied

On sync, the default-scope labels are written first, then for each override the module writes a store-view-scoped label row for the matching option/value. Locales resolve to every store view configured for that language, so one de_DE override covers all your German stores. Anything without an override falls back to the default label.

Import options from a product

Already have a product with the perfect option set? Turn it into a reusable template in one step. Catalog → Global Custom Options → Import From SKU:

1. Enter the Product SKU that already has custom options.
2. Give the New Template Name.
3. Click Run Import — the product’s options are read into a new template you can then edit and assign elsewhere.

CSV import / export

Bulk-create and bulk-edit templates in a spreadsheet. Import CSV and Export CSV are on the grid toolbar.

The CSV is flat/long — one row per option value (or per option for single-value types), grouped by the code column:

code,name,is_active,option_title,option_type,option_required,option_price,option_price_type,option_sku,option_sort,value_title,value_price,value_price_type,value_sku,value_sort
gift_options,Gift Options,1,Gift Wrap,checkbox,0,2.5,fixed,,10,Standard,2.5,fixed,,1
gift_options,Gift Options,1,Gift Wrap,checkbox,0,2.5,fixed,,10,Premium,5,fixed,,2
gift_options,Gift Options,1,Engraving Text,field,0,10,fixed,,20,,,,,

Import behaviours

• Add / Update — create new templates and overwrite any whose code matches.
• Add Only — create new templates only; existing codes are skipped and reported.

Round-trip

Export CSV produces a file in exactly this format, so the quickest way to start is to export, edit in a spreadsheet, and re-import. Templates are matched on the code column.

Grid management

The templates grid supports search, column controls, paging and mass actions — Enable, Disable and Delete selected templates. The Assigned Products column shows how many products each template is currently written to.

Configuration

Stores → Configuration → AgenticEcom → Global Custom Options

Field	What it does
Enable Global Custom Options Module	Master on/off switch for the module.

FAQ

Do customers see a new kind of option on the storefront?

No — the module writes standard Magento custom options onto each product, so the storefront, cart, checkout and order behave exactly as they would with hand-built options. The template system is purely an admin-side authoring tool.

What’s the difference between Replace, Update and Add?

Replace wipes all existing options on the product then writes the template’s; Update swaps only options whose title matches the template (keeping the rest); Add layers the template’s options on top. Pick per save in the Apply Mode dropdown.

Can one template be different per language?

Yes. Use Per-Store Label Overrides to give option and value titles a translated label per store-view locale. The default label is the fallback for any store view without an override.

I already built options on a product — can I reuse them?

Yes — Import From SKU reads an existing product’s custom options into a new template you can then assign to other products.

How do I move templates between environments?

Export CSV on one store and Import CSV on another. Templates are matched and upserted on the code column, so re-importing updates rather than duplicates.

Is it secure?

Every admin controller is behind the AgenticEcom_CustomOptions::manage ACL resource; saves and imports are POST-only; CSV input is validated and option payloads are sanitised before being written through Magento’s own custom-option repository. Verified clean on PHP 8.4 and 8.5.