Mushroom - GreenCommerce

The Mushroom release is the third version of 2026 and is therefore not mandatory. This release includes various technical changes, such as the ability to cancel an order. Changes have also been implemented regarding GreenXchange. Furthermore, we have made changes to allow for allocation based on sales requirements within the context of Sales FIFO. Read the full release notes:

A GLN determination based on the Batch/Crop Group has been added, making it available in the Pallet/Pallet Line column selector via *TeeltGlobalLocationNummersAlsTekst* (Crop Global Location Numbers as Text)

Two new items have been added to the menu under 'Administration': 'Close commercial period' and 'Commercial closing'. These cannot be used yet, so some configuration work is required.

An option has been added to several inventory screens to display the customer’s recommended daily prices for the selected items in a new window. This has been added as both a button and a right-click action in the screen used to search for an item from a sales order line, as well as an option in the Batch Sales screen (adding a sales order line from inventory).

The ability to transfer product through a transfer order has been discontinued. The “Transfer” button in the batch card has been removed, and the associated system parameters “Transfer, “DefaultTransferMachine”, and “DeregisterPalletOnTransfer” have consequently been discontinued.

A small victory for software housekeeping. Every system eventually accumulates enough old buttons and settings to qualify as an archaeological site.

Two additional fields (‘LatestUnloadingDate’ and ‘LatestUnloadingTime’) have been added to the ‘Add Delivery’ screen to record the expected departure time from the port. These fields can be adjusted when creating or modifying a delivery, subject to a chronological check (the latest unloading date cannot precede the arrival date). Additionally, an option to enter a departure date has been added when creating a delivery.

When recalculating service registrations for purchase orders, the system now considers the actual number of unique batches associated with the purchase order lines to determine the quantity and the billable quantity. Additionally, recalculation of service registrations has been implemented for specific logistics events, such as moving a purchase order line or splitting and deleting a batch within a purchase order.

An option has been added under the same setting used for printing standard customer pallet labels. This setting can now also be enabled for business partners classified as suppliers. When a 'Return to supplier' shipment plan is created for a supplier with this option active, the "Print pallet label" button automatically appears in the WMS app. If a business partner is both a customer and a supplier, the same setting applies to both types.

Source references from the pallet lines are now available in the WMS App (displayed as a comma-separated list). The sorting order is determined first by the manual 'order' property, then by the source reference, and finally by the 'id' property. This ensures that pallets (such as mixed pallets) with the same source reference are kept neatly together.

Sub-locations have been made scannable in the QC App. When an inspector scans a sub-location code, a list of the pallets present appears. After selecting the desired pallet, the standard outbound inspection workflow continues.

In the 'View available batches' overview within the outgoing inspection process, inspections performed on the displayed batches are now retrieved and shown (the most recent inspection is visible). Clicking on the inspection allows the full inspection report to be opened immediately in a new screen.

A new fact table has been added (REP.FeitVerkoopOrderRegelDynamischeOpslag) in which the dynamic price markups per sales order line are broken down in detail. In addition to basic information, this table contains specific data such as the markup basis, the coverage type, the markup amount, the markup percentage, and the calculated markup amount per package.

The bulk copy button has been replaced by a new button that allows contacts to be copied one by one. A window opens where the new code can be entered immediately; contact-specific fields (such as Chamber of Commerce and VAT numbers) are automatically cleared, and existing contact groups are now copied along with the contact.

The 'Recalculate specifications' function for services has been restricted and is now available only when the user has been explicitly assigned the 'Recalculate service registration specifications' task. This task is not linked to a role by default, in order to prevent unintended effects on the services being calculated.

When sending 704, 800, and 802 messages from the GreenCommerce Connector, the full name and address details for all four entities (importer, exporter, consignor, and consignee) are now populated. Additionally, the corresponding EORI numbers are included as identifiers; the system uses dynamic logic to determine whether to use the business partner's general EU EORI number or the specific registration number derived from the country-specific customs settings.

The multi-edit functionality in the Sales Order, Purchase Order, and Inventory Planning screens has been updated to allow the number of packages for multiple lines to be adjusted or set to zero simultaneously, provided these lines have not yet been allocated.

A change has been made at the line level to the “OpmerkingPicklijstOrder” field in the “UitslagInstructie” message; “OpmerkingPicklijst” has replaced it as the first field. This field will initially be included in the message.

On the inbound side, the “OrderNotes” and “Note” fields have been merged with the “OpmerkingOrderPick” field. Within the message, these will be separated by a semicolon (;).

When creating a link via the inbox, the external item ID—if known—will be displayed after the description. If the setting to link based on the ID is active, the values ​​within the "( )" and the linking key will be automatically swapped.

A new system parameter, 'WerktMetTeeltVerplichting', has been introduced, making it possible within standard GreenCommerce to mandate specific cultivation values ​​(such as variety, company, and delivery location). Additionally, a notification has been added to the cultivation location screen for instances where an incorrect GLN is entered, and the field label now reads 'GLN' instead of 'EAN'.

To support the specific way Fris operates within standard GreenCommerce, the pricing calculation has been made configurable to use a 'calculated pallet factor' (whereby total pallet costs always reduce the product value). Additionally, a specific field has been introduced for each order line to indicate that no pallet costs need to be calculated.

In terms of code, the member management functionality has been moved from FrisGreenCommerce to the standard GreenCommerce. Member management is now activated via the new system parameter ‘WrktMetLedenBeh’ (which adopts the value of the old parameter ‘IsFrisNw’), without any functional changes for users.

A 'Cancel' button has been added to the 'New orders' screen, allowing the status of one or more selected orders to be set to 'Cancelled' in bulk. This enables any changes made to an order to be disregarded. Additionally, the GreenCommerce API now records the specific timestamps for processing and cancellation ('TijdstipVerwerkt' and 'TijdstipGeannuleerd'), which can also be displayed as columns in the overview. Finally, the 'Delete' button has been relocated, and its functionality is now restricted to the 'System administrator' role.

The FreshBabel Messenger GreenCommerce Connector has been modified so that pallets from a shipment are only included in the intake instruction once the shipment has actually been completed. Additionally, the `shipment.finished_undone` event has been added to the Tasks API (for locations using LscCommunication) to notify the receiving location if a shipment is reversed, thereby preventing pallets from being incorrectly registered as received.

When the loading date of an order (and consequently the delivery date of the sales order) is changed, the applicable data for each order line (such as item, loading location, pallet packaging, package price, remarks, and program line) are redetermined based on the program line valid at that time. This mechanism is triggered via the "MoetProgrammaRegelsOpnieuwBepalen" attribute on the order.

When manually creating a service record, the specific settings ‘Physical stock determination’ and ‘Charge to relation’ are now correctly inherited from the service relation’s master data. This ensures consistent behavior with automatically generated services.

The ‘Sub VAT number’ field at the business partner level is now always available and can be filled in without first specifying a tax group. The field is therefore no longer greyed out.

A new location setting, 'Inventory reservation policy' (WerktMetVoorraadReserveerRichtlijnen), has been added for logistics partners. When enabled, strict validation checks comparing the consumed quantity against the reserved quantity are skipped during the verification of a production confirmation (though the item itself is still validated). Upon acceptance of the confirmation, the item reservations are immediately set to zero.

It is now possible to seamlessly add pallets containing valid interchangeable items to a work order. When generating work instruction specifications, the interchangeable item is correctly carried over from the sales order line or consumption record and is marked with a specific interchangeable icon in the details screen. In the Windows application, the 'Item Inventory' and 'Available Pallets' tabs now also display all permitted interchangeable items.

To optimize performance, details are no longer calculated for service records that have already been invoiced or are non-billable. Additionally, the 'last modified' timestamp of an itemized record is no longer updated if the quantities remain unchanged, which significantly improves the speed of this process. As a result, viewing the details is now faster.

A comments field (with a maximum length of 6 characters) has been added to GreenXchange, which can be filled in when changing the color of an order. This comment is also immediately visible in the details screen in GreenXchange, making it clear on the shop floor which line or greenhouse the order is scheduled for.

The new system parameter 'WerktMetGxVerwerkingObvOpdrachten' now makes it possible to handle GreenXchange processing via production orders instead of purchase orders within standard GreenCommerce. Additionally, the new parameter 'WerktMetVerplaatsingenVerlagenOfOphogen' ensures that when quantities in a linked transfer order are modified, the associated parameters (quantity, number of pallets, and pallet spaces) are automatically adjusted accordingly.

The new system parameter ‘VrrdPlanningTDatum’ has been added (default value 0). This allows the ‘to date’ filter field in the inventory planning to be automatically incremented by a preset number of days.

Product forecast fields in GreenXchange are disabled for dates prior to the crop's first harvest date. This ensures that quantities can only be forecast from the moment product is actually expected.

The API has been extended to allow the retrieval of lookup values ​​that were previously used but are now blocked (such as an inspector who has left the company) for a quality control template. This ensures that historical data remains correctly visible in the QC App without displaying blank fields.

The new company-specific system parameter ‘OrdersDefinitiefMakenMetNietCommercieelDefinitieveRegels’ makes it possible to correct a purchase order line before the purchase order is finalized, provided the line has been fully received. During message processing (delivery orders and instructions), lines that have already been corrected are skipped and logged to prevent the entire message from stalling.

When simultaneously scheduling multiple sales order lines for shipment (from different locations), the system now considers the earliest loading time for each specific location, rather than the general loading time for the sales order.

Additional logging has been added for the addition and removal of services. This logging records actions. It can be viewed via the log button on the Purchase Order, Batch Info, Sales Order, and Job pages.

The check to determine whether a cost item has been allocated—performed when finalizing a purchase or sales order—is now skipped if the order consists exclusively of element lines. These cost items are excluded from the batch result and can be settled later via purchase invoices.

The new system parameter ‘OrdersDefinitiefMakenMetNietCommercieelDefinitieveRegels’ makes it possible to finalize purchase and sales orders containing lines that still have the status ‘indication’ or ‘sales commission’. The price can subsequently be adjusted once using a special menu button (after which the status changes to ‘standard’). Invoicing remains blocked as long as this status is active.

The new system parameter ‘MaximaleAfwijkingInputOutputBijProductieOpdrachten’ allows you to set a maximum difference (as a percentage) between the consumed weight and the resulting net weight. If this margin is exceeded, the user receives a warning when finalizing the order. This check applies specifically to orders involving a machine of the ‘other machine’ type and requires the location setting to be configured to ‘consumption booked’.

A new location setting has been added that allows you to specify which check is performed when finalizing tasks on machines of the ‘Other machine’ type. You can choose between 'consumption recorded' (consumption must be registered) or 'crop recorded' (a crop must be registered for the result batch). Once finalized, the crop associated with the batch can no longer be changed. This setting is only available if the system parameter ‘WerktMetTeeltVerplichting’ is active.

When working with batch suitability based on the ‘PartijGeschiktheidSuggestieLicentie’, it is now possible to factor in batch suitability when allocating sales order lines on a FIFO basis. Consequently, the first available batch may be skipped if it is unsuitable; only batches marked in green (100% suitable) are allocated. This functionality is also available from the inventory planning screen.

When using the ‘PartijGeschiktheidSuggestieLicentie’ (Batch Suitability Suggestion License), it is now possible to filter the inventory by entering the sales requirement filters. The overview then immediately displays which batches are 100% suitable.

Two new system parameters have been introduced: ‘WerktUitsluitendMetToegewezenWerkInstructieSpecificaties’ and ‘WerktMetPalletBeschikbaarheidBijToewijzen’. These enable the automatic allocation of resources for sales and production orders—based on FIFO (and, where applicable, pallet availability)—as far as possible, prior to their conversion into work instructions for order pickers.

The Services tab within a batch now displays only the relevant specifications by default. These are the specifications associated with the start of the day, which determine the billable quantity. If desired, all daily specifications can still be displayed by selecting the corresponding checkbox in the left-hand menu.

Er zijn geen release notes met dit label gevonden.

Stay up-to-date

Please subscribe to our newsletter and be the first one to be up-to-date about GreenCommerce.

Subscribe now