One foundation, several OPALs.
The link between OPAL and shop
The Subshop Framework provides what an OPAL needs to keep data per subshop: the inheritance, the storage and the switch in the mall section. It works in the background – its benefit becomes visible in the OPALs that build on it.
What the Subshop Framework delivers
With the OPALs that build on it
For shop operators who use a subshop-specific OPAL:
- The component is the prerequisite for all subshop-specific OPALs.
- You decide per subshop whether it inherits the main shop's data or keeps its own.
- The switch for this sits in the same place in the mall section in each of these OPALs.
For your own modules
For developers who want to make their own module subshop-capable:
- You can also use the component in your own modules – without any of the OPALs that build on it.
- Your module only registers its table. Storage, inheritance logic and the switch in the mall section are already in place.
- There is a ready-made storage pattern each for assignments (such as cross-selling) and master data (such as countries); a helper provides the matching table structure.
Part of the OPAL family
OPALs are building blocks from OXID eSales: a proven, solid foundation that needs to be adapted to your system landscape and integrated into your shop.
This OPAL builds on it
The Subshop Framework is the shared foundation this OPAL builds on:
OPAL Cross-Selling per Subshop
Own cross-sells and accessories per subshop – matching each subshop's assortment.
To the OPALFrequently asked questions
Price
€5/month
OPALs are also available in subscription packages.