Ecommerce architecture
We have already made some good process in moving from idea to code. However this doesn't mean we have everything right. Feel free to provide feedback and ideas.
The objective is to provide for each component a symfony2 bundle having a standard interface which can be easily overridden by the developer to comply with customer specific requirements.
This is the main engine which drives typical ecommerce process flows such as order to cash. Check out this page for more info. It can be used as a standalone workflow engine outside of Vespolina.
This bundle handles product related information in general such as product name, description, dimensions and so on. Using a ProductInterface the product can be extended with ease.
The merchandise bundle handles sell able products. It wraps products into sellable products. Please read more here why we make a difference.
The pricing bundle is responsible for determining and maintaining prices of entities in general. As long as an entity supports the PriceableInterface it can be priced. Please read here more about the design. For general information about typical pricing concepts.
This generic interface relates different objects to each other.. Classification can happen differently:: hierarchical, tags, ...
Translation ?
The document service handles configuration and common operations on business documents such as sales orders, delivery notes, quotations, ... Please read here more about how to use this service.