Release 2026.4.1
2026.4.1
This Oct 12 2026 Production Release focuses on clearer stock ownership, cleaner imports, and better warehouse visibility. You can now manage stock allocation by marketplace shop from the product screens, so each shop's stock is shown and handled separately. Order imports now check shipping addresses before invoices are created, with correction and confirmation steps for unresolved addresses. Managers also get a Global Pick & Pack Monitoring view across tenants and date ranges. We've also fixed bundle binding conflicts, ASN retry and counting flows, waybill opening for Others orders, and product search accuracy. Nothing is
Feature
Bin codes and stock ownership
Bin codes and stock ownership gives warehouse staff clearer detail on where stock belongs and who owns it. This replaces a less visible setup where the bin and owner behind a stock wallet were harder to confirm during warehouse work. In WMS, staff can now see the bin from the address code together with the wallet owner. That makes it easier to connect a stock location with the shop allocation it supports. The detail also matches the product-side stock split, so warehouse and product teams are looking at the same ownership picture. Fusion keeps the bin and owner visible together, reducing guesswork during stock checks.
Steps
Feature
Stock allocation by shop
Stock allocation by shop lets you split a product's stock across marketplace shops and merge it back when needed. Instead of treating one product's stock as a single shared number, Fusion can now show and handle the amount that belongs to each shop. In the product screens, staff can view the split per shop and use multi-shop filtering to focus on the allocations they need. When stock changes, deductions, cancellations, and transfers follow the owner, so stock leaves the right shop allocation. Zalora and Shopify now publish the real figure and show real failures. Fusion also keeps each listing tied to its own shop's stock, reducing
Steps
Improvement
VPB archive and reconnect choices
VPB archive and reconnect choices helps keep bundle stock bindings clean when catalogs are removed or restored. Previously, deleting a catalog could leave retired bundle records still connected to marketplace bindings. Now, archiving a catalog retires those bindings so they no longer keep pushing stock. If a retired binding is reconnected, Fusion prompts first, giving staff a clear choice before it becomes active again. The release also adds a VPB health report to help spot older orphaned bindings. Fusion includes reconciliation support for leftover cases, so teams have a guided way to clean up past issues.