Skip to content

Reference

The lists a Product Bundles configuration is built against.

  • The bundle form: every field on Catalog → Bundles, tab by tab.
  • The API: the two read resources an integration may call, every field on each, and what the promise covers.
  • Settings: every setting key, its default, and the tables a bundle is kept in.
  • What this holds about a person: every column about somebody, and what removes it.
  • Security: the baseline controls, and how Product Bundles answers each.
  • What it costs: what it adds to nineteen stock pages, in queries, bytes and requests.

The enumerable parts of this section are written from the extension's own code by oce docs:reference, so they cannot drift from what the version you installed does. The field page is read out of the same language file the admin screen renders.

What a generated list cannot tell you

  • The settings screen is short. Extensions → Extensions → Modules → Product Bundles holds the module's Status switch, the Where bundles show tickboxes, the shared Detailed logging switch under Diagnostics, and the button to what it holds about a person. Everything else about a bundle is a property of that bundle, edited on its own form. There is no configuration to work through before the extension is useful: every surface starts ticked.
  • The Report tab on the bundle form is read-only. It is OpenCart's own product report for the bundle: each visit to its page, by IP address, shop, country and date, recorded while your store's product-report setting is on. It has nothing to set.
  • Nothing on the form sets stock. A bundle's availability is derived from its components every time it is asked for; see Limits and guarantees.