Release Notes Wemalo Update 2025-04
EL-1864 Wemalo: Quantity in Return Cannot Exceed Output
Release Notes
In the past, there was an issue where the system allowed users to register a returned quantity that exceeded what was originally sent out. For instance, despite only one unit being shipped, the system enabled the booking of two units under a specific SKU. This inconsistency was possible even when certain settings were thought to prevent such occurrences.
Now, the improved system ensures that the quantity being returned cannot exceed the quantity initially dispatched. The backend has been updated to adequately verify and track all returned shipments. This means that regardless of the number of separate return instances, the cumulative total of returned items is consistently checked against the total quantity shipped. This validation process guarantees that no more than the dispatched quantity is recorded in returns, thus maintaining inventory accuracy and preventing discrepancies in stock levels.
EL-2112 Implement Logic for Configurable Product Weight Selection Gross or Net
Release Notes
The logic for selecting the weight of configurable products based on gross or net preferences was previously not implemented. This meant that users could not specify their preferred weight type, leading to potential confusion and inconsistency in product weight representation.
With the new implementation, users can now configure their preference for product weight selection in the application settings. By setting “useProductWeight” to “brutto”, the system retrieves the gross weight of the products. If the gross weight field is empty, it automatically defaults to the net weight. Conversely, when “useProductWeight” is set to “netto” (which is also the default setting), the system consistently retrieves the net weight of the products. This ensures that all product weight calculations align with the user’s preference, enhancing clarity and accuracy in product information management.
EL-2122 Rectify Address Data Split in Adding Goods Order
Release Notes
Previously, when adding a goods order, the address data was not properly consolidated, resulting in split and incomplete addresses. This caused confusion and delays in processing orders.
Now, users can expect that address data is accurately and cohesively integrated into the goods order entry process. This ensures that the entire address is captured correctly, enhancing the efficiency and reliability of order fulfillment.
EL-2231 Regenerate Actual Target Summary Excel File by Every Request
Release Notes
The process of generating the Actual Target Summary Excel file was initially inefficient and redundant. Each time a request was made, the Excel file was regenerated from scratch, even if it had already been created, leading to unnecessary processing and resource usage.
Now, when the Actual Target Summary Excel file is generated for the first time by Wemalo, it is automatically uploaded to storage. This ensures that for any subsequent requests, the system no longer attempts to regenerate the file. Instead, it retrieves the existing stored file, optimizing the process, saving time, and reducing resource consumption.
Improvement EL-1833 Remove EAN via REST-API is Now Possible
Release Notes
In the past, the system did not allow the removal of a primary EAN from a product when using the REST API on instances other than DynTest. This limitation restricted the ability to manage product identifiers efficiently across various environments.
Now, the improved system enables seamless removal of primary EANs from products through the REST API on all instances, not just DynTest. Users can expect consistent behavior regardless of the environment, enhancing overall flexibility and control in managing product data. This change ensures that product information management is more adaptable and aligned with users’ needs.
Shipping – EL-2022 Shipping Profile EU Countries Incomplete
Release Notes
In the previous configuration under “Configuration->Shipping Profile->Countries,” the preselected option for EU countries was incomplete. Both Sweden and Germany were omitted from the list, leading to potential confusion and operational inefficiencies.
With the update, the expected outcome is a complete and accurate selection of EU countries, including Sweden and Germany. This ensures that all EU member states are consistently represented, facilitating smoother shipping operations and reducing the likelihood of errors in order processing. Users can now confidently rely on the shipping profile settings for precise country selections within the EU region.
EL-2068 Add LS to Required Documents for Partial Check and Extend API Functionality
Release Notes
The requirement to set a MUST have DELIVERYNOTE or BILL on order creation via the REST API was implemented. Users can now specify the need for documents during goods order creation using three parameters: `need_document_bill` (already existing), `need_document_deliverynote`, and `need_external_check`, where each parameter can be set to true or false.
Additionally, there was a new requirement to have a DeliveryNote, similar to the BILL partial reason setup, for customers. An API endpoint was introduced to check the partial reason “EXTERN” setup in customer data. Furthermore, the “EXTERN” partial check was added to ensure that if an external API returns a 200 OK with a JSON success: true, the external validation for the order is confirmed.
These enhancements aim to streamline order validation processes by supporting more comprehensive documentation requirements and enabling seamless interaction with external systems for order verification.
EL-2083 Send Webhook Only When Saved Correctly
Release Notes
Previously, when products were added to Wemalo, a webhook was triggered regardless of whether the product was successfully saved in the database or not. This led to instances where the dashboard received updates about products that did not exist or were improperly recorded.
Now, the process ensures that a webhook is only sent to the dashboard if the product has been correctly saved in the database. This prevents discrepancies and ensures that all data sent to the dashboard is accurate and reflective of the current state in Wemalo.
EL-2085 Use Lot if it is Activated to Pack Next Article
Release Notes
In the past, when processing articles for the same barcode with multiple charges, Wemalo only considered the quantity from the first charge, assigning this as the totalQuantity. This approach often led to inaccuracies in inventory and order fulfillment.
Now, the expected outcome is to ensure greater accuracy and efficiency. For any article under the same barcode with multiple charges, the system calculates the totalQuantity by summing up the quantities of all charges. This adjustment improves accuracy in inventory management and enhances the reliability of order processing, ensuring that stock levels correctly reflect all available quantities.
EL-2102 Add Metadata to Orders in Wemalo
Release Notes
Previously, the metadata associated with orders in Wemalo was not displayed prominently in the frontend, making it less visible and accessible to users. Now, this metadata is prominently displayed on the frontend interface, allowing users to easily access and interact with important order information. This enhancement improves user experience by providing clear and immediate visibility of relevant order details directly within the application.
EL-2137 Reject Reservation by Back2Draft – UpdateAddress – CreatePickList if Order is in Queue of Smart Reservation
Release Notes
Previously, when an order was placed in the queue of the smart reservation mart, the reservation could be mistakenly rejected when actions like updateAddress or createPickList were initiated by the Back2Draft. This caused confusion and potential disruptions in the reservation process as warehouse teams sometimes inadvertently intervened manually.
Now, with the new update, reservations within the smart reservation mart operate smoothly without requiring manual intervention or the need to recreate relocation orders. Warehouse staff can trust that reservations begin automatically when a relocation order is created, ensuring a seamless workflow and reducing the chances of any reservation being unintentionally rejected. This adjustment aligns the reservation process more closely with the warehouse’s operational requests and expectations.
EL-2139 Show Articles of Picklist on Different Storage Cell
Release Notes
Previously, the system displayed articles of a picklist within a single storage cell, which made it challenging to manage and locate items efficiently. Users struggled to differentiate and organize items when they were all grouped together.
With the latest update, users can now view articles of a picklist distributed across different storage cells, providing a more structured and organized approach to inventory management. Data is presented in a well-organized list format, allowing for easier navigation and quicker identification of specific items within distinct storage locations. This enhancement improves the overall efficiency of accessing and managing inventory, reducing the time and effort required for item retrieval and organization.
EL-2145 Checking SKU and Quantity at Booking of Return Order
Release Notes
Previously, the system did not effectively check the SKU and quantity during the booking of a Return Order, which could result in the return quantity exceeding the originally shipped quantity.
Now, the system accurately validates that the quantity entered for return does not exceed the quantity that was originally shipped. This ensures that the return process respects the original order constraints, preventing inventory discrepancies and improving overall inventory accuracy.
EL-2185 remove generate shipping label by goodsorder parcel position
Release Notes
In previous versions, the feature to generate a shipping label by goods order parcel position was available, yet it posed operational inefficiencies and complexities for users. As a result, this feature has now been removed to streamline processes and improve user experience.
The expected outcome is a more intuitive and seamless workflow, where users no longer encounter the cumbersome task of generating shipping labels based on parcel positions in a goods order. This change aims to simplify the shipping process, enhance productivity, and reduce the potential for errors. With this update, users should experience a smoother and more efficient method of handling shipping labels, contributing to overall operational excellence.
Continuing with the rest of the document from this point forward:
EL-2189 add sum of stock from all storage in getallStock endpoint
Release Notes
In the previous implementation of the getAllStock endpoint, the stock count from various storage facilities was individually listed but not aggregated, making it difficult for users to quickly assess the total stock availability across all locations.
Now, the getAllStock endpoint includes a new feature that calculates and provides the sum of stock from all storage facilities. This enhancement allows users to effortlessly view the total stock count, offering a comprehensive overview of inventory levels at a glance. This improvement is expected to streamline stock management and reporting processes, aiding in more efficient decision-making.
EL-2194 add stockfrom all storage to the Shop
Release Notes
In the past, the system lacked a comprehensive approach to managing stock distribution from multiple storage locations to the shop, leading to potential inefficiencies and inconsistencies in inventory levels across outlets.
Now, the process ensures a seamless transmission of stock from all storage facilities directly to the shop by using the “all” flag. This improvement effectively streamlines the inventory flow, guarantees that stock levels are updated accurately, and enhances the overall operational efficiency by ensuring that no storage unit is overlooked. As a result, the shop is better equipped to meet customer demand with timely replenishments, contributing to an improved shopping experience.
EL-2220 return goods for external goodsOrder
Release Notes
The process of returning goods for an external goods order resulted in the backend displaying 0 available. When a return with a reference was made, it was necessary to verify that the scanned product existed within the main goods order.
Currently, when initiating a return for an external goods order, the expected outcome is to see accurate availability information from the backend. In the case of returns with a reference, the system ensures seamless verification by checking if the scanned product is part of the main goods order, simplifying and streamlining the process.
EL-2239 use cell barcode in creating inventoryAPI and check storageCell with the storage Id
Release Notes
Previously, when creating an inventory through the API, the system continuously ran into an endless loop if the cell ID was not found or did not exist. This caused significant delays and frustration for users attempting to verify storage cells using the storage ID.
With the latest update, the system now promptly checks whether the cell ID is present when using a cell barcode for inventory creation. If a cell ID is not found or does not exist in the database, an immediate error message is displayed to the user. This ensures that users are promptly informed about the issue, allowing them to take corrective action without experiencing any unnecessary delays or system hangs.
EL-2352 Implement Dual-Field Search for Tracking Number and Barcode in Return Process
Release Notes
Users previously struggled to locate announced returns because the search functionality was restricted to either tracking numbers or barcodes, but not both. Now, with the implementation of the Dual-Field Search, users can seamlessly and effectively find announced returns using either the tracking number or the barcode. This enhancement significantly boosts productivity and minimizes errors in the return process, allowing for a more streamlined and efficient operational experience.
EL-2353 Setup Config to handle stock source for woocommerce
Release Notes
The WooCommerce plugin previously only allowed stock fields to be managed without alternative options. Users now have enhanced flexibility in managing their inventory with the addition of a configuration flag, ‘stock_source’. This flag provides three values to choose from: Stock, AltStock, and Both. As a result, administrators can now configure their preferred stock source seamlessly. This update allows stock to be effectively transferred, tracked, and displayed either as standard stock, as alternative stock, or in both categories, streamlining inventory management and improving operational efficiency.
EL-1997 Provide attribute name in wemalo api
Release Notes
In the past, editing article attributes in the Wemalo API was limited to providing the external code and an array of languages for the attribute title, known as “Bezeichnung.”
Now, users have the ability to provide the attribute name in the API. This enhancement allows for more precise and flexible attribute modifications directly through the API. Users can now input an array with language-specific titles related to the attribute ID. For example, this can be formatted as an array named ‘reasontitle’ with key-value pairs like {‘en’ => “AttributeTitle”, “de” => “Attribut Titel”}. This upgrade facilitates a more streamlined and multilingual approach to handling attribute details.
EL-2147 add invoiceNumber to GoodsOrder
Release Notes
The system previously lacked the ability to adjust the invoice number field within a goods order by adding a prefix and postfix from Billbee when these were available. As a result, the invoice numbers did not align with the expected format that included these additional elements, potentially leading to inconsistencies in data handling.
Now, the system is enhanced to incorporate the prefix and postfix to the invoice number field in a goods order automatically. If an InvoiceNumber_Prefix and/or InvoiceNumber_Postfix from Billbee is available, the system ensures that the full invoice number in Wemalo is constructed using the format: InvoiceNumber_Prefix . InvoiceNumber . InvoiceNumber_Postfix. This improvement provides consistency and clarity in invoice management, ensuring that all required elements are present and correctly formatted.
EL-2234 In shop connector config match dispatcher with the dispatcherProfileId in Wemalo
Release Notes
The previous configuration of the shop connector matched the dispatcher using the external ID, which led to inconsistencies and potential mismatches. Now, the configuration accurately matches the dispatcher profile from the shop with the dispatcherProfileId in Wemalo, ensuring a more reliable and streamlined connection process between systems. This change aims to enhance accuracy and operational efficiency by using the correct identifier for dispatcher profiling.
EL-2242 quantity with specific storageId
Release Notes
Previously, there was an issue where quantities were transmitted from all available warehouses, regardless of their specific storageId, when the quantity was below a certain threshold. This could lead to inaccurate inventory data and potential fulfillment errors.
Now, the system ensures that quantities are transmitted only from the warehouse that is configured in the system settings. This assures precise tracking and management of inventory based on the designated storage location, resulting in improved accuracy and fulfillment efficiency.
EL-2255 flag position by return order
Release Notes
Previously, when the checkbox to check the return SKU in the return order was set to true, it allowed the creation of a return order. However, if the checkbox was then set to false, users were unable to add an external product for the same client in the return order.
Now, when the checkbox is set to false, users are able to add external products for the same client in the return order without any issues, thus enhancing the flexibility and usability of the system for managing return orders.
EL-2262 billbee cancel Order by Tag
EL-2277 flag cancel Order in Billbee
EL-2283 update docu for GoodsReceipt Add API
Release Notes
The documentation for the GoodsReceipt Add API previously lacked detailed information regarding the additional fields that could be utilized to enhance the data retrieved during the receipt process. Users had limited insights into specific components such as estimated time of arrival and order details, which could impact the accuracy and efficiency of their inventory management.
With the updated documentation, users now have access to comprehensive details when using the GoodsReceipt Add API. The expected outcome includes visibility into key information such as the estimated time of arrival (eta), along with a complete view of the base JSON structure which contains crucial order metrics like ordered boxes (orderedBoxes), ordered palettes (orderedPalettes), ordered pieces (orderedPieces), and the gate number (gateNumber). This enhancement enables users to optimize their logistics and supply chain management by leveraging precise and timely data.
EL-2293 remove NonAscii Characters in javascript
Release Notes
The task previously involved dealing with strings that contained non-ASCII characters, resulting in potential issues such as data corruption or display errors. The solution involves utilizing a JavaScript function to efficiently remove these non-ASCII characters, ensuring clean and valid string data. As a result, when the provided sample code is executed, it now successfully returns a sanitized string, ‘Markenname LimitedyE###C’, free from unwanted non-ASCII characters, thus improving data handling and presentation.
EL-2296 support gzip encoding in RestClient
Release Notes
Previously, the RestClient did not support gzip encoding, causing issues when interacting with certain shops that returned their responses in compressed form. This led to challenges in correctly interpreting and processing the data received.
Now, with the updated implementation, the RestClient checks the content encoding of the response before reading it. If the response is compressed using gzip encoding, it is correctly decompressed and read, ensuring seamless and accurate data processing. This enhancement allows for improved compatibility and functionality when communicating with servers that utilize compression, providing a more robust client experience.
EL-2297 check the crtlId of MHD or Lot if not available in frontend
Release Notes
In the previous version, users faced issues when attempting to check the control ID (ctrlId) of MHD or Lot, as it was not consistently presented in the frontend screens. This inconsistency led to difficulties in accessing necessary information, resulting in potential delays and errors in processing.
Now, with the updated system, users can expect a more reliable and streamlined experience. The control ID is consistently available in the frontend, ensuring that users can effortlessly verify and access the information they need directly from the screens without any hindrance. This enhancement is designed to improve accuracy and efficiency in workflows, minimizing any disruptions or confusion previously encountered.
EL-2299 map dispatcherProfile between shop config and wemalo externalId
Release Notes
In the previous system configuration, there was a limitation in mapping the dispatcherProfile between the shop configuration and the Wemalo externalId. This issue particularly affected tags that were assigned via Shopify to define shipping options. Moreover, there was an oversight in handling dispatcher names containing spaces, such as “DHL Schweiz”.
With the updated implementation, the system now accurately maps the dispatcherProfile by recognizing and correctly associating it with the corresponding Wemalo externalId. Tags provided by Shopify are seamlessly integrated to specify shipping choices. Furthermore, dispatcher names with spaces are now correctly processed, ensuring that configurations like “DHL Schweiz” are interpreted and applied consistently across platforms. This update enhances the coherence and flexibility of shipping option definitions, aligning the shop configuration seamlessly with external systems.
EL-2303 get shopify fulfillment service from config if it differs of default value
Release Notes
The Shopify fulfillment service in the configuration was previously not always being checked against the default value. This led to potential mismatches or inconsistencies in the fulfillment process settings. The execution now ensures that the Shopify fulfillment service is retrieved from the configuration only if it deviates from the default value, maintaining alignment across the system.
Additionally, the Location ID related to the Shopify fulfillment app integration with Wemalo was not being consistently verified. The update now ensures that this ID is accurately checked, guaranteeing that the integration operates smoothly and without errors, facilitating a more reliable and seamless workflow.
EL-2305 prevent parallel handover process through dock management
Release Notes
Previously, there was an issue where multiple handover processes could execute in parallel through dock management. This overlap sometimes led to inefficiencies and coordination problems, affecting the overall workflow and resource allocation. With the latest update, the dock management system now restricts the handover processes from overlapping in execution. This ensures that each handover process is managed sequentially, enhancing operational efficiency and reducing potential for conflicts or resource misallocation. The improved coordination facilitates smoother transitions and optimized use of dock resources.
EL-2307 ignore sync packages without trackingnumber based on handover date
Release Notes
Previously, packages without tracking numbers were synced into the system, regardless of their handover date. This sometimes resulted in outdated or irrelevant package information cluttering the system.
Currently, packages that lack a tracking number are excluded from syncing into the system if their handover date is older than 14 days. This ensures that only relevant and timely package information is processed, enhancing the accuracy and efficiency of the system’s package tracking capabilities.
EL-2310 prevent duplicate importing of cancelled orders
Release Notes
In the past, there was an issue where cancelled orders were being imported into Wemalo even after they had been marked with the cancel_received_by_ tag in the shop. This caused unnecessary duplication and confusion.
With the implementation of a new feature, the system now effectively checks for the presence of the cancel_received_by_ tag on cancelled orders within the shop. If this tag is found, the order cancellation is no longer imported into Wemalo. This enhancement ensures that only necessary information is processed, reducing errors and streamlining the workflow.
EL-2312 sync all products stock to the shop
Release Notes
Previously, there was a challenge in synchronizing all product stock levels with the Billbee shop, which led to inconsistencies between the warehouse inventory and the online store. This situation occasionally resulted in overselling or underselling products due to outdated stock information.
With the implementation of the “Sync All Products Stock” feature, the system now ensures all product stock levels are accurately updated and aligned with the Billbee shop in real-time. This enhancement maintains consistent inventory data, providing customers with accurate availability information and improving overall inventory management and sales operations.
EL-2325 calculate Virtual quantity of products on booking of its child products and sending articles
Release Notes
The system previously did not account for the virtual quantity of products when booking child products, which could lead to discrepancies in inventory management. Additionally, the process for checking the setlist contents for articles was not consistently streamlined, potentially causing errors.
With the latest update, when child products are booked, the system now accurately calculates and adjusts the virtual quantity of parent products, ensuring more accurate inventory tracking. Furthermore, the contents of the articles setlist are now automatically sent for verification, improving the overall accuracy and reliability of inventory data. This enhancement optimizes the workflow and reduces the likelihood of errors, making inventory management more efficient and effective.
EL-2333 compare products if not set in shop connector config
Release Notes
Previously, when adding a new product to Wemalo, the shop connector configuration did not automatically set fields for product comparisons. This meant that users had to manually compare products to ensure accuracy and completeness before integration.
Now, with the current enhancement, the system automatically compares product fields if they are not set in the shop connector configuration. This ensures consistency and accuracy, allowing for a more streamlined process when adding new products to Wemalo. Users can now rely on the system to perform necessary checks, reducing the potential for errors and saving valuable time.
EL-2336 filter assigning user list of picklist by registered or updated logged in user
Release Notes
Previously, the list of users available for assignment in the picklist was not filtered, potentially overwhelming users with choices that were not relevant to their current context.
Now, the picklist displays only those users who are registered or have recently updated information, significantly streamlining the selection process. This ensures that you are presented with a concise and relevant list of potential assignees, tailored to the specific needs of your warehouse assignment tasks.
New Feature EL-1782 checking sku and quantity at booking of Return order EL-1900 all and virtual stock to allstocks endpoint
Release Notes
In the past, the system was not consolidating all virtual stock into the all stocks endpoint, leading to discrepancies in product information. Additionally, there was a dependency on the external shop ID, which limited the flexibility of stock analysis.
Currently, the all stocks endpoint now includes all virtual stock, ensuring a comprehensive overview of stock levels. Independent of the shop requirement, the external ID is no longer necessary, streamlining the process. Furthermore, to enhance request performance, consideration of the product type is incorporated with the flag indicating if it’s a parent product. A new endpoint, getAllVirtualStock, has been introduced to deliver all virtual SKUs with identical fields to those in the all stocks endpoint. This includes necessary fields such as Quantity, Available, Reserved, and FullStock, providing a more detailed and accessible inventory management system.
EL-2027 extend AllStocks returned fields
EL-2066 using price percentage for Partlist of Product
Release Notes
Previously, the system did not allow users to input percentage values directly into the parts list for each product, which required manual calculations and external references to manage pricing strategies.
Now, users have the ability to seamlessly input percentage values into the ‘percentage value’ field within the parts list table. This enhancement facilitates easy computation of price adjustments directly within the system. As a result, the data in the LVS backend is updated accurately, and the correct percentage values are transmitted effectively to Shipconnect, ensuring pricing synchronization and efficiency across platforms.
EL-2089 add fields to content of item in wemalo-ship
Release Notes
The task involved the incorporation of additional fields into the content of items in the Wemalo-ship system. Previously, the items/contents lacked detailed information, specifically missing the ‘ean’ field. Additionally, the metadata did not include the ‘shippingFee’ field, which was necessary for providing comprehensive shipping information.
With the changes implemented, each item’s content now contains the ‘ean’ field, enhancing product identification and traceability. Moreover, the ‘shippingFee’ field is now part of the metadata, allowing users to access crucial shipping cost information effortlessly. These enhancements ensure a more informative and efficient system, improving the overall user experience.
EL-2093 Add Filtering in Bin Status Report of Reserved Articles
Release Notes
In the past, users were unable to filter by SKU in the Bin Status Report of Reserved Articles. When attempting to search, the page remained unchanged, providing no feedback or results as expected.
Now, users can efficiently filter by SKU, resulting in an updated and responsive report display upon searching. Additionally, selection fields like “Merkmal,” “MHD B2B,” and “Auftragsinfo” are streamlined to enhance usability, ensuring only relevant options are visible in the overview. This improvement optimizes the accessibility and functionality of the report for a more user-friendly experience.
EL-2179 add a header to allow increase of rate limits
Release Notes
In the past, the rate limits for API requests were hard-coded, leading to limited flexibility in managing request thresholds across different routes. Users often encountered restrictions that hindered optimal performance and customization.
Now, with the introduction of a new header that incorporates a multiplier, users have the ability to increase rate limits seamlessly across all routes. This enhancement allows for greater control over API request flows, accommodating varying traffic demands and improving overall efficiency. By adjusting the header, users can ensure their applications operate smoothly without the constraints of previous limitations.
EL-2235 Import Pudo Nummer von JTL
Release Notes
In the past, the “Pudo Nummer” from JTL was not correctly transferred to wemalo, and the field labeled “extra info” was not included during the transmission to ship-connect. This resulted in incomplete order information being passed along the shipping process, potentially causing confusion or delays.
Currently, with the implemented changes, the “Pudo Nummer” is accurately transferred from JTL to wemalo, ensuring that this critical information is preserved and utilized effectively. Additionally, the “extra info” field is now seamlessly included in the data sent to ship-connect, providing comprehensive order details. This enhancement improves the accuracy and efficiency of the shipping workflow, reducing the likelihood of errors or omissions in the logistics chain.
EL-2266 weclapp API Update requires compression
Release Notes
In the past, the weclapp platform’s API calls were made without mandatory compression, which could result in larger response sizes and potentially slower data transfer rates. With the update implemented since February 1, 2025, compression is now activated for all API calls in stages. From this point forward, the platform consistently uses compression for any response exceeding a few hundred bytes, thereby improving data efficiency and transfer speeds.
EL-2278 change storage id via GoodsOrder Rest API
Release Notes
Prior to this update, users faced a limitation where they could not reassign an entire order to a different storage facility through the GoodsOrder Rest API. This was particularly inconvenient in scenarios where operational requirements necessitated a complete transfer of inventory to a new storage location.
With the introduction of a new endpoint, users can now seamlessly change the allocated storage ID for an entire order. This enhancement provides greater flexibility and efficiency in managing inventory logistics. Users are now empowered to easily reallocate resources and optimize their storage solutions, ensuring more streamlined operations and improved adaptability to changing storage needs.
EL-2289 Split order and copy all data with plenty
Release Notes
Previously, there was a need to split certain positions within orders to accommodate fulfillment from varying warehouses. The challenge arose when attempting to fulfill these orders in a shop that required the same external ID, which was found to be not allowed due to identical shop names.
Currently, upon splitting an order, a unique identifier in the format of plenty_12345_splitted_1(…..999) is added as the external ID. The system’s connector, with a configuration setting, interprets this adjustment. For successful submission to the shop, the external ID must exclude the suffix _splitted_1(….999).
With this solution, once an order is split, both resulting orders are submitted to the plenty system. Each part of the order is processed distinctly as separate packages or shipments, thus ensuring they are recognized as part of the same original order and fulfilled appropriately.
EL-2321 PICTURE – RETURNS – connect camera and import picture to the WE-Retoure order
Release Notes
The process of connecting a camera and importing pictures into the WE-Retoure order was initially cumbersome, requiring manual selection and connection steps.
Now, users can seamlessly connect any compatible camera to the WE-Retoure order system, which automatically lists all available cameras. Users have the flexibility to select their desired camera to begin streaming directly on the webpage. This integration is designed to simplify the picture import process, allowing users to either press a button on the camera or use the on-screen canvas for quick and efficient image acquisition. This enhancement greatly streamlines the workflow, ensuring a more efficient and user-friendly experience.
EL-2403 Warenausgang mit Identifikationsnummer
Bug
EL-2014 Wemalo: Inventur Bericht ist manchmal veraltet
Release Notes
The inventory report in Wemalo frequently showed discrepancies. Specifically, the variance report inaccurately indicated an excess of 214 units. This issue often occurred with files.
To resolve this recurring problem, the solution of deleting the file was consistently implemented. After deletion, Wemalo successfully regenerated the file, resulting in accurate data that aligns with the expected inventory counts. This process is expected to ensure consistency and reliability in inventory reporting moving forward.
EL-2174 use storagecell for goodsorder position in frontend edit page
Release Notes
Previously, when attempting to use the storage cell for a goods order position on the frontend edit page, selecting a storage cell and its associated attribute within the goods order edit page did not apply the chosen storage cell to the order as expected.
Now, when a user selects a storage cell and its corresponding attribute for a goods order position on the frontend edit page, the selection is accurately applied to the order, ensuring that the goods are properly allocated to the chosen storage location. This improvement streamlines the order editing process and ensures alignment between the user’s selections and the system’s application of those choices.
EL-2343 get bookes Products from article booked in Delivery order for SmartReservation
Release Notes
Previously, when attempting to retrieve booked products from articles within a delivery order for SmartReservation, there were instances where the productQuantityMap hashmap was found to be empty. This situation occurred when all products in a single thread had been booked, leading to potential disruptions in the reservation process.
With the recent update, the expected outcome ensures that even when all products within a thread are fully booked, the productQuantityMap hashmap consistently reflects accurate booking information. This enhancement improves the reliability of data representation in delivery orders, facilitating smoother operations and better inventory management in the SmartReservation system.