Reference

The lists a configurator is built out of: everything a rule may say, and everything Product Configurator stores.

All of these are generated from the extension's own code, so they cannot drift from what the version you installed does.

• The rule grammar: the three verbs, the two kinds of target, and the option types a condition may be written against.
• Settings: the two setting keys (whether it is on, and how long detailed logging stays on), the three tables the rules live in, and what Product Configurator fixes on purpose.
• What this holds about a person: every column of those three tables, and why none of them is about anybody.
• Security verdict: each control of the shared security baseline, and whether this extension meets it.
• What it costs: the queries and page weight it adds to nineteen stock pages.

Two things those lists cannot tell you, because they are not lists:

• Which rules a product needs. The grammar says what you can write. Whether a memory size should disappear when a motherboard is picked, or whether an engraving option should be revealed rather than always offered, is a question about your own products. The guides walk the shapes that come up most.
• What happens at the edges. What a customer with JavaScript off sees, what a refusal says and in whose words, what happens to a cart line already added, what a copy and a delete carry, and what an uninstall leaves behind are all on limits and guarantees. Read it beside this page.

Two more facts that are neither a list nor a limit:

• The permission string to grant a user group is extension/product_configurator/module/product_configurator, and it governs the module's own screen only. Writing rules on a product needs permission to modify products, which is checked again when the rules are stored rather than assumed.
• Where the rules are written is a tab called Configurator on OpenCart's own product form, and they save on the product form's own Save button. There is no second screen and no second save.