--- title: "2026-11-16 - Chain InventoryModule 2026-11.1" slug: "2026-11-16-chain-inventorymodule-2026-11-1" updated: 2026-11-16T06:35:05Z published: 2026-11-16T06:35:05Z canonical: "products.egretail.cloud/2026-11-16-chain-inventorymodule-2026-11-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://products.egretail.cloud/llms.txt > Use this file to discover all available pages before exploring further. # 2026-11-16 - Chain InventoryModule 2026-11.1 # Released 16 Nov 2026 ### [InventoryService] Upgrade IntegrationPlatform to 4.3.14 and smoke test batch jobs (LIP batch save drops items under load) [(RTC-65447)](https://jira.eg.dk/browse/RTC-65447) InventoryService **No more missing records in large imports** Large imports into Inventory, such as stock data and POS sales, could lose some records under heavy load while the import still reported success. All records are now saved. ### [INV] Evaluate and generalise references on ItemTransaction exports/imports [(RTC-58096)](https://jira.eg.dk/browse/RTC-58096) InventoryService **References on item transaction lines** Item transaction lines can now carry a list of free-text references. Each reference has a type, for example "ServiceOrderId", and a value. One line can have several references, including more than one of the same type. The "Inventory.ItemTransaction.Export" contract has a new "references" list on each transaction line. Each entry has "referenceType" and "value". The list is empty when a line has no references. References can't yet be added through data import or from Management. ### [INV] Handle goods receipt storages in management and API [(RTC-64096)](https://jira.eg.dk/browse/RTC-64096) InventoryService **Goods receipt storages in management and API** Goods receipt storages now show with their own category name in the "Temporary storages" grid and on storage label PDFs, and you can filter the grid by this category. These storages are created automatically from goods receipts, so they can no longer be created manually from the "New storage" dialog or through the CreateStorage API. ### [INV] GoodsReceipt-to-storage follow-up: idempotency guard + content conditions [(RTC-61757)](https://jira.eg.dk/browse/RTC-61757) InventoryService **Goods receipt-to-storage processing improvements** - Only items with a filled "storageId" in a goods receipt are put away into a temporary storage. - Fix: Items from a goods receipt are put away only after the processing is successfully finished. ### [Inventory] Rework GoodsReceipt processing flow (ImportSplitter) [(RTC-56631)](https://jira.eg.dk/browse/RTC-56631) InventoryService **Goods receipts are no longer lost when processing fails** Goods receipts from Procurement are now saved in Inventory before they are processed. If processing fails, the receipt is retried instead of being lost, so stock from received goods stays complete. Received goods can take up to about half a minute longer to show in stock. ### [OMS-SO] Create PutAway transaction to pick up when creating InternalRepair (via API) [(RTC-59209)](https://jira.eg.dk/browse/RTC-59209) Service Orders **Repair items are put into their Inventory storage automatically** When an internal repair is created with a storage ID, through the CreateInternalRepair API or in Management, the service item is now put into that storage in Inventory and the order history records it. If Inventory rejects the put-away, the order is still created. A warning icon appears next to the storage ID and the order history gives the reason. Users with permission to manage service orders can click the icon to try again. A storage ID can only be set on internal repairs. If a prefill link carries a storage ID for any other service type, the storage ID is left out. Inventory **Service order number on storage lines** The add lines to storage API (POST api/storages/{storeNumber}/{storageId}) accepts an optional ServiceOrderNumber. Each service order gets its own storage line. Sending the same request again for the same storage and service order number is only applied once. The number is added as a ServiceOrderNumber reference on PutAwayStorage and PutBackStorage transaction lines, so it is included in Inventory.ItemTransaction.Export. ### Storages - Print storage label from instore app [(RTC-59336)](https://jira.eg.dk/browse/RTC-59336) InventoryService **Print storage labels with service order numbers** A temporary storage can be printed as a label with a QR code and a list of all items in the storage (GTIN, item name and quantity). The label is opened through the link temporary-storage-label/[storageId]. Adding ?autoprint=true to the link opens the print dialog automatically. When any item belongs to a service order, an "Order number" column is shown on the label and in the storage lines grid. A new storage category, "Received goods", is used for storages created automatically during goods receipt and can't be selected when creating a storage manually. ### [Inventory] Improvements to stock status grid [(RTC-64894)](https://jira.eg.dk/browse/RTC-64894) InventoryService **Stock status grid performance improvements** The performance of Stock status grid is significantly improved. ### [Inventory] Decouple validation from line processing in PutAwayMerger [(RTC-64101)](https://jira.eg.dk/browse/RTC-64101) InventoryService **Put-away imports with unknown items are skipped as a whole** When an imported put-away contains an item that does not exist in Inventory, the whole put-away is skipped. None of its lines are added to the storage, stock or item transactions, even when another put-away in the same import updates the same storage. When the missing item is created later, the put-away is processed again in full, so no quantities are counted twice.