Lemon - GreenCommerce

The Lemon release is the second version of 2026 and is therefore optional. This release includes various security improvements, such as multi-factor authentication for logging in via a cloud/online account. It also allows multiple items/relationships to be added or edited at once in several screens by selecting them. Additionally, updates have been made in the WMS App to support the new work order workflow. Read all release notes:

It is possible to increase or decrease the net and gross weight of multiple purchase or sales order lines at once. A field has been added to the edit screen with a checkbox indicating whether the field should be used as a difference. If a value goes below 0, an error message is shown.

Both checkboxes are controlled by a parameter (MultBewNetAlsVers and MultBewBruAlsVers). Contact us if you want to use this.

The item day prices have been extended with a new column “AvailabilityNote.” This can be filled in via the standard day price schedule as well as the schedule that shows separate columns per price group. When generating price lists, the note is automatically carried over. You can also adjust it manually afterward. The export of the price list as an Excel file has been extended with an extra tag that makes the newly added note available: #ITEM_AVAILABILITYNOTE

When creating transport orders, the transport order date is based on the parameter “PurchaseTransportOrderDateDetermination”. A value of 0 sets it to the delivery date, 1 sets it to the loading date.

In GreenCommerce, settings have been added to the sublocation group to indicate whether the group's sublocations should be suggested during order picking for production or cutting. If this setting is enabled, sublocations can be filtered when selecting them in the WMS App. If staging locations are chosen, these can also be filtered in the WMS App, just like in the work order.

A new task “Correct Sales Orders” has been added. Correcting sales orders now falls under this task. Any role with the “Edit Sales Orders” task automatically receives the “Correct Sales Orders” task as well.

For security reasons, creating a user via creating a contact person has been restricted. This is now only possible for users with the system administrator role.

In GreenXchange, it is no longer possible to select a crop whose harvest date has not yet been reached. Crops selectable in the “Create In Stock” screen are now filtered by “harvestable on selected date.”

The “Description” field is already received and stored in the sales order when an order is placed. It is now also possible in the other direction. When reading the delivery order message in the GreenCommerce inbox, the “Description” field is now also transferred to the purchase order.

A new setting has been added in GreenXchange to indicate whether new orders should be visually marked. When enabled, new orders in the orders screen and the stock screen are marked with a green plus icon. The plus disappears when the order is opened or when the new option “Mark New Order Seen” is selected.

When determining batch results in the DataWarehouse service, only the most recently calculated batch result per batch-company combination is now included. This prevents duplicates in the BatchResultLine table.

In the pop-up screen for splitting sales order lines, an extra prompt has been added asking whether the loading location should be notified if the sales order line is already fully loaded. This is only shown if the order line is part of a loading plan, is fully loaded, and the loading location has already been notified about this plan. If the “Remember” checkbox is checked, the choice is saved for next time.

To manage database space more efficiently, a new button “GX Carriers” has been added to the relationship linking requests screen. This allows the user to choose which carriers should receive a relationship linking request, keeping the log much more organized.

When a user doesn’t use Adobe Reader but another PDF reader, a pop-up about opening an external application used to appear. This has been removed.

For cutting instructions of a purchase return, the destination is now also populated in the message. This is based on the supplier and included in the message sent to the sender. Additionally, in the loading plan at the service provider, the supplier is set as the handling end customer. When importing the cutting instruction, a relationship link must be created for the supplier.

When creating a purchase correction, it is now possible to immediately inform the loading location about the cutting. The checkbox is enabled by default if the purchase order line’s location can receive a cutting instruction, the parameter ‘SaveAndInformImmediately’ is on, and the user has the task ‘InformLoadingLocationAboutLoadingPlan.’

In GreenCommerce, an extension has been added to receive and process the number of pallet positions from FreshBabel messages. This is controlled by a setting managed via jem-id. Contact us if you want to use this.

Sales returns are now reset to 0 when a correction is deleted. This sets the quantity, number of pallets, and number of pallet positions to 0. The sales order line is removed from the return. It is possible to create an “empty” inbound instruction for a sales return set to 0, which will clear the linked purchase order at the service provider when the instruction is imported.

For this reason, a filter/checkbox “Hide empty lines” has been added in the returns screen, enabled by default. Purchase returns are still fully deleted.

When adding a transport order, a new checkbox “Inform Receiving Location” has been added. This checkbox appears in multiple places and works as follows:

  • Users without the task ‘Inform Receiving Location(s) about Purchase’ cannot see the checkbox.
  • If there are no communication settings for the receiving location to send an inbound instruction, the checkbox is visible but disabled (greyed out).
  • If the user has the parameter ‘SaveAndInformImmediately’ enabled, the checkbox is checked by default.

This informs the receiving location of the purchase order line or transfer order. The screen is used for scheduling a transport order and moving lines to another transport order.

In the WMS App inbound overview, the codes of the loading locations for the inbound items are now displayed.

The field “ClientReference” has been added to Sales Order and can be selected as a column in the sales orders screen. This field contains the order reference from the cutting instruction.

A parameter “ccPrgsTMDatum” has been created, allowing days to be added to the ‘through date’ so that future programs can also be included.

A message setting has been created to link the supplier by code (relationship link) instead of GLN when importing delivery orders. This is managed via jem-id. Contact us if you want to use this.

On the ‘Extra’ tab of a relationship (Master Data), under ‘Financial,’ an additional field can be added to record the VAT number of the relationship’s fiscal entity. This field may be hidden or greyed out if no fiscal entity is entered.

A new milestone “ContainerArrivalDateChanged” has been added, which triggers when a container’s date is changed. This includes actions like rescheduling a delivery or moving a container to a different delivery.

The column ‘TotalAmountInElementCosts’ has been added to the order. It can be added to the orders screen and shows the total amount of all elements in the order.

For SSCC ranges where numbers are not generated but come in via, for example, an import from the packing station, the ‘LastIssuedNumber’ is now also set. This ensures the SSCC ranges screen shows correct information (such as available numbers) for these ranges.

A period filter for issued SSCC numbers has been added to the SSCC screen.

The existing milestone SsccNumberFromRange has been extended to trigger when an SSCC range runs out.

Een bestaande mijlpaal SsccNummerUitReeks is uitgebreid zodat ie afgaat wanneer een SSCC reeks opraakt.

Similar to the ‘PrintOrder’ table, a table for ‘SystemDocumentPrintOrder’ is now available. It stores the basic details of a print action for a system document (such as layout, number of copies, printer, and creation time).

This allows better monitoring of which print orders are executed and identifies actions causing delays (via timestamps) or failures (via status).

A new status has been added to print orders: ‘Failed’ (= 3). This status is applied when printing cannot be completed.

The “Fill and Accept” option in the Orders screen can now be used when multiple orders are selected. The suggested data in the “Fill Order” screen, such as ‘Loading Date’ and ‘Unloading Date,’ is only populated if it is the same for all selected orders (otherwise the fields remain empty). Fields left empty will not be changed in the orders when saved.

The “Correct Purchase Order Line” screen has been expanded to allow selecting the loading plan date. The checkbox “Inform Loading Location” has also been moved, and both fields are now together in the “Loading Plan” section. The loading plan is created on the correct date when correcting the purchase order line. The loading date always starts on the day the purchase order line correction is created. This is controlled by a setting. Contact us if you want to use it.

In the Excel export, it is now possible to select a template when working with XLSX files. An existing Excel file is filled with data from the export. The old .XLS file must first be saved as .XLSX.

When scheduling transfer routes in loading plans, the loading plans from which the transfer orders are taken are now also notified.

New parameters have been added to set the period when the Orders screen opens: ‘ccOrdersFromDateOffset’ and ‘ccOrdersThroughDateOffset.’ By default, the screen opens with a period from today up to 7 days ahead.

The transport instruction (700) message has been extended with a 'Temperature' field containing minimum and maximum temperatures. For now, both are set equal and filled with the temperature from the transport order.

 

A new column ‘TotalNetWeightUsedBasedOnPalletOrItemWeight’ has been added to the order. It can be added to the orders screen. The column sums the net weights of all used pallets, using the pallet’s active weight. If the pallet has no active weight, it falls back to the net weight from the item master.

In the 700 transport instruction message, the identification points of the loading and unloading locations are filtered so that only one GLN identification point is included. This concerns the logistical GLN. An identification point is a unique number used to recognize a relationship.

When accepting orders, the system now only asks to send an order confirmation if the customer is set to receive one (message 101 – order confirmation or message 106 – delivery order). If the customer is not set to receive an order confirmation, it cannot be sent. This ensures sales order lines can still be split later in the process even after they have been handled logistically.

The gross weight on the SSCC label is now calculated as follows: the non-rounded gross weights of the pallet lines are summed, and the total is then rounded up to the nearest whole number.

Extensions have been made in the GreenCommerce API to provide additional data for handling invoices (invoice lines). The connector between GreenCommerce and FreshBabel has also been extended to correctly create and send an invoice message (#300) to an invoice recipient.

The added fields in the GC API for invoice lines:

  • TransactionType as a new field
  • Populating reference and customer reference for invoice lines based on service/element registrations
  • Populating reference and customer reference for invoice lines based on activity

A new milestone ‘OrderReturnedToProduction’ has been added, which triggers when an order is moved back to production (i.e., when a completed order is reopened).

The original message when accepting a outgoing confirmation is now displayed again in the outgoingconfirmations screen.

The functionality to link items to an active program line from the old order import (via InterCommIT) has also been added to the new order import. This is controlled by a message setting “100002 – Take item from a valid program line (100 – Sales Order),” allowing it to be enabled or disabled per customer.

Note: Previously, items were only matched using GTIN (message) and EAN code (ItemNumber). Now, SenderCode (message) and code (ItemNumber) are also considered.

When adding a new item number, it is now possible to add multiple relationships at once. The field has been renamed from Relationship to Relationships. Relationships for which the item already has an item number can no longer be selected.

By selecting multiple item numbers, they can also be edited at once in a new screen. Only the fields that are filled in will cause changes to the item numbers.

The sublocation (Master Data → Locations) has been extended with a checkbox ‘Loading Only.’ Pallets at this sublocation will be excluded when handling work orders for production and stock transfer orders.

When creating a batch reservation (consumption) for an order, the system now checks whether the batch has an inspection block and whether it can be used in the order. A message appears if the user tries to reserve a batch with an inspection block while the order setting does not allow it. Ignored messages are logged.

When checking a product notification of type ‘production in progress,’ the system verifies that the pallet number to be reported off has not already been reported off within the order. If it has, a message appears and the inbox message cannot be imported.

A new parameter ‘SupplierStockFilter’ has been developed, allowing the filter to be activated per company in the desired screens. Multiple suppliers can be selected in the filter. Once at least one supplier is filtered, batches originating from production will no longer be shown.

To store the last used handling setting per user per screen, a new parameter ‘DefaultHandlingFilter’ has been added. When opening a screen, this value is reused. This applies to the following screens:

  • Sales Orders
  • Sales Order Invoicing
  • Purchase Orders
  • Stock Planning
  • Transport Planning

The login form layout has been improved, and better feedback is now shown when logging in via the cloud provider fails. Additionally, GreenCommerce now includes an option for system administrators to invite users for a cloud account: “Invite for cloud identity.”

If a user is already logged in via the cloud, a timer appears when opening GreenCommerce. Previously, the timer could be stopped using ‘reset’ to allow logging in with a different account. This has now been changed to ‘cancel.’

Also, the ‘Online Login’ (cloud login) screen used to appear behind the GreenCommerce login screen. This has been adjusted so the correct screen is shown in front.

GreenCommerce production capabilities have been expanded. Previously, tracking was only possible at the order level; it is now also possible at the line level. This is controlled by a parameter—contact us if you want to use it.

When planning consumption, item, and/or batch usage, the consumption can be distributed across the lines on which the order is scheduled. This is useful when the packer has received the reservations via instructions.

With this setting enabled, it becomes mandatory to select a plan when reporting off a pallet for (line) orders. Orders must be scheduled on one or more lines. Scheduling can be done in the Production App or via Production Planning in GreenCommerce.

When completing and undoing the completion of a supplier return loading, the number of batches with an inspection block for the involved batches is now recalculated.

In the QC App inspection reports overview, the filters ‘Type’ and ‘Template’ have been added. The selected values are remembered for future sessions.

The description for the parameter has been changed to: “The entered value represents the number of days after the invoice is created before a notification is given. If an invoice remains open longer than the entered value, a notification is shown when creating a sales order for the customer. A value of 0 disables the notification.”

When adding a sales order, the invoice number of the open invoices is now displayed instead of the ID.

An endpoint to retrieve sales order line corrections has been added to the GreenCommerce API.

It is now possible to work with sublocation main groups. The stock to be picked in the WMS App takes this into account. Pallets with a sublocation main group that does not match the work order’s main group are filtered out of available stock, as the order picker cannot access them. Sublocation main groups can be set up under a location. When creating work orders for Production (Orders and Line Orders), a ‘Sublocation Main Group’ can be assigned.

A new property ‘ClaimCorrectionReference’ has been added to the purchase order. This property shows the sales order ID of the correction sales order, if known.

The parameter ‘TemporaryPalletRegistrationRemoval’ has been disabled.

The IsTransit attribute registration at the pallet line level was no longer used and has been disabled.

In the ‘Pallets in Stock’ overview, the traffic light icon is now shown for a pallet if any of the pallet lines come from a transit batch. This means it will appear more often for customers working with transit.

Multiple purchase orders can now be moved at once by selecting them. A validation has been added to prevent the process from being interrupted midway. Only orders with the same date can be selected.

In the import module, it is now possible to change the arrival and loading/unloading dates of containers within a delivery when transport is delayed.

  • Menu item [Move to] has been renamed to [Move to Delivery]
  • New menu item [Move Container] has been added to indicate that this involves changing dates.

In the container move form, you can choose to update the arrival date at the port, as well as the loading and unloading dates tied to the linked purchase order.

For the sections Stock (Transfer Orders), Production (Orders and Line Orders), and Outgoing (Loading Plan), it is now possible to assign the generated work order to employee groups. One or more groups can be specified in the field ‘Available for Group(s).’

More data is now carried over from a program line than just the item. This includes: location as loading location, pallet packaging, production remark, and order pick remark. For all fields, if the value is not set in the found valid program line, it falls back to the data from the message.

The order pick remark is also a new field on the order line and can now be added as a column in the Orders screen.

In GreenXchange, if an order was reported off and the pallets were then put in transport, it could happen that the transport order was not completed. Changes have been made in the FreshBabel connector and Tasks API to prevent reporting inside while loading has not yet been completed.

When a company uses stock transfer orders (parameter: PalletRegistration and WorkInstructionLicense), a user with the task RequestConsumptionReservation can request stock for an item or batch reservation. This option is available as the menu item ‘Request Stock’ and opens a screen to add a stock transfer order.

Using the [Group Lines] checkbox, the display of lines to be transported can now be grouped. Grouping is done by from- and to-relationship plus location.

Newly added keyboard shortcuts allow quick adjustments:

  • The + key on the numeric keypad increases the load/unload sequence, depending on the active mode.
  • The – key on the numeric keypad decreases the load/unload sequence, depending on the active mode.

A new parameter allows disabling the validation of unique GGNs. This lets different production locations be registered as separate relationships with the same GGN if they have a multi-site GGN. By default, the setting is ON, requiring GGNs to be unique.

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