3. Using the services¶

3.1. AvailabilityChecker¶

The name speaks for itself, this service checks availability for given stockable object. It takes backorders setting into account, so if backorders are enabled, stockable will always be available. Backorders can be enabled per stockable if it is available on demand. If none of this is the case, it means that backorders are not enabled for the given stockable and AvailabilityChecker will rely on the current stock level.

There are two methods for checking availability. ->isStockAvailable() just checks whether stockable object is available in stock and doesn’t care about quantity. ->isStockSufficient() checks if there is enough units in the stock for given quantity.

3.2. InventoryOperator¶

Inventory operator is the heart of this bundle. It can be used to manage stock levels and inventory units. It can also fill backorders for the given stockable, this is a very powerful feature in combination with InventoryChangeListener. Creating/destroying inventory units with a given state is also the operators job.

3.3. InventoryChangeListener¶

It simply triggers InventoryOperatorInterface::fillBackorders(). This can be extended by implementing InventoryChangeListenerInterface. Events can be configured like explained later on the documentation Summary.