|
Current Problem
Related to MST-I-1789 but not the same thing - that one's about SKU-level stock buckets, this is about the lot-level Breakdown array. GET /api/Product/StockLevels gives you Level (free stock) and TotalStockLevel (total) at SKU level. But set Breakdown=true and the lot-level array only returns free stock. It sums to Level every time, never the total. So there's no way to tell which lot the committed stock belongs to. Mintsoft clearly has this data - the product stock detail screen shows allocations broken out one by one with order number, batch number, best before and quantity. It just doesn't come through the API. For us that means committed stock can't be tied to a lot, so it has to sit in an unlotted bucket with no batch number at all. One of our clients is a food supplement business where batch and BBE traceability is a legal requirement, and stock with no batch number won't come out properly on a recall report. It breaks order fulfilment too. When the client system gets a shipment confirmation naming a specific lot, it can't relieve the stock, because the units are sitting in unlotted rather than in the lot the shipment is asking for. On their Cin7 Core integration that's leaving orders shipped in Mintsoft but stuck and uninvoiced. Also worth flagging: the published docs for this endpoint (support article 360028854492) show a sample response with Level but no TotalStockLevel, even though it's there in live responses. Anyone working from the docs wouldn't know it exists. This'll hit any Mintsoft 3PL with batch-tracked clients, not just Cin7 Core. |
|
| Idea to resolve Problem | Add committed/allocated quantity to each entry in the Breakdown array, either as an additional field or as a distinct Type value, and update the published API documentation to include TotalStockLevel. |