Skip to content

Requirements and install

Product Configurator installs like every other extension sold here. Follow the shared procedure rather than a Product Configurator-specific one:

What is specific to Product Configurator

The permission entry to tick at step 3 of the shared procedure is:

extension/product_configurator/module/product_configurator

Tick it under both Access Permission and Modify Permission, for every user group that should be allowed to reach the module's own screen. Writing rules on a product needs no permission of its own. It needs permission to modify products, which whoever edits your catalogue already has.

Copy rules from, on the Configurator tab, needs no entry of its own either. It appears for a user group that has Access Permission on the entry above and Modify Permission on catalog/product, and is left off the tab for any other group, rather than shown as a button that would fail when you save.

Enabling it also grants two screens to the user group that enabled it, because every Kyvero extension ships them and nothing else in the store grants them:

  • Personal Data, under Customers, answers what each installed Kyvero extension holds about one named person. Product Configurator's answer is nothing, stated on the screen rather than left out.
  • Remove everything held about a person gets both Access and Modify. Product Configurator holds nothing about anybody in its tables. The one thing it lists is the diagnostic log every Kyvero extension shares, which names nobody and which an erasure keeps, so its settings screen counts that one file and still offers the link (see what this holds about a person).

Any other user group that should see Personal Data needs extension/product_configurator/customer/personal_data ticked under Access Permission by hand.

Enabling the module is what creates Product Configurator's three tables and its settings, and what registers it on the screens it works through. Nothing happens on upload alone, which is why the extension list's own + (install) step is not optional. Enabling it again, which is what an update does, leaves every rule you have written as it was.

It arrives switched off. Enabling the extension does not start changing your product form or your storefront; the module's own Status does that, and it is one field on one screen. See the quick start.

A store below OpenCart 4.0.2.0 is refused, and says so on the screen rather than half-installing: no tables, no settings, nothing. Below that release the seams every part of this extension rides do not resolve the same way, and an extension that half-works is indistinguishable from a broken one.

A store newer than the newest release tested is not blocked. The module's screen says so and everything carries on working. The releases a full install-to-uninstall pass has run against are listed in the extension's extension.json.

Nothing you have to set up first

There is no key to enter, no service to connect to and no template to prepare. Product Configurator has one store-wide setting that changes what it does (whether it is on), plus the Detailed logging switch every Kyvero extension carries; see what Kyvero extensions log. Everything else is written on a product, on a tab of the product form.

It also needs nothing of your theme. The rules are enforced by OpenCart's own validation, and the instant hiding on the storefront is added to the page your theme already renders. A theme that has rewritten the product form keeps its own page and loses only the hiding; see what the customer sees.

Updating to a newer version

Follow updating to a newer version in the order it gives. One thing matters here:

Your rules survive it. An OpenCart update is an uninstall followed by an install, and removing Product Configurator deliberately leaves its three tables and every rule in them alone. Reinstalling puts the extension back over the rules it left behind, so an update is never a re-authoring job. See what a removal leaves.