One foundation, several processes.
A common foundation for the supply chain OPALs
At their core, many supply chain features need the same thing: an independently shippable delivery unit with status, shipping method, cost share and tracking. The framework provides this common model once, centrally – other OPALs build on it instead of rebuilding it every time. It works in the background.
These OPALs use the framework
The framework is the common foundation – these OPALs build on it and share the same delivery unit model:
OPAL Shipment Tracking
Track shipments per delivery with tracking number and status – transparent through to delivery.
To the OPALPart 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.
Features at a glance
OXID
<OPAL/>
An independently shippable delivery unit
The common model with its own number, status (open → ready → shipped, final status cancelled), assigned shipping method, share of shipping costs and optional tracking including the expected delivery date.
One status, the same in all modules
The order status is derived from the delivery units. That way, all OPALs built on top of it behave the same, and customer communication is consistent everywhere.
Direction-neutral for splitting and merging
The same model supports both splitting an order (one becomes several) and merging several orders (several become one) – via the roles "source" and "target".
Original order stays unchanged
The original orders are never changed. What the customer ordered remains readable, unchanged, even after splitting or merging.
Notifications stay with the module
The framework only defines how notifications are sent; the respective module built on top handles sending the emails. That way, all customer communication stays where it belongs functionally.
Frequently asked questions
Price
€5/month
OPALs are also available in subscription packages.