steveoliver / commerce_stock_ Goto Github PK

Just to follow up on the #drupal-commerce discussion:

Right now, when the stock_level field is added to an entity (typically a commerce_product_variation) it creates a DB table that is never used (e.g. commerce_product_variation__stock_level). Actual stock value is stored in cs_inventory_location_level. Clearly it needs to be stored in cs_inventory_location_level in order to be location-aware, but still its illogical to have a DB table created to hold nothing. But maybe it could be used to hold the backorder availability value? Strictly speaking, I think it could hold it now by using $entity->set('stock_level', $value) with 0 or 1. The nomenclature is wrong, but we could just call the field "stock" or "stock availability" instead of stock level, and the stock api could store the backorder availability as a bool in this field. You could change it from a decimal to a tinyint to hold a boolean.

From the point of view of my project and its custom StockFormatter (which displays stock level and availability in the product view display), it would be trivial to change from using a custom field on the entity to represent backorder availability, to using the value stock field provided by commerce_stock.