Delivery conditions

Target audience

• Customer organizations;
• Supplier organizations;
• Supplier warehouse organizations.

---

Purpose

• Enables use of delivery conditions in all Floriday domains, currently only applicable for direct sales.

---

Guidance

Delivery conditions are used by a supplier organization to specify under which conditions goods are delivered from a dispatch warehouse to a customer location. Delivery conditions currently only apply to Direct sales.

• A delivery condition may be set as a general delivery condition, which applies to all customers organizations.
• A delivery condition may be set as a customer specific delivery condition instead. These are usually created when a supplier has made a seperate agreement with customers regarding delivery (e.g. deviating time frames, no transport / delivery costs, delivery on Non-working days, etc.).

A delivery condition contains:

• Dispatch warehouses;
• Delivery regions;
• Incoterms;
• Transport and delivery costs;
• Minimum delivery quantity;
• Order periods;
• Non-working days with deviating timeframes.

---

Dispatch warehouses

A delivery condition applies to one or more dispatch warehouses.

---

Delivery regions

As per August 2024 the following delivery regions are supported in Floriday. New delivery regions can be added or existing regions can be modified. Please refer to the Floriday application for the latest supported regions.

---

Incoterms

As per August 2024 the following Incoterms are supported in Floriday. New Incoterms can be added. Please refer to the Floriday application for the latest supported Incoterms.

• DDP - Deliveries are brought to a logistic hub;
• EXW - Deliveries are picked up at supplier warehouse;
• FCA - Deliveries are brought to the airport of departure.

See Business rules - Incoterms for more information.

---

Transport and Delivery costs

A supplier organization may define seperate Transport and Delivery costs n the delivery conditions. By default, Transport and delivery costs are included. These surcharges only apply when a supply line is configured to have Including service: "Delivery" marked as false.

• A supplier organization that uses supply based on Price groups needs to set Including services in the Price groups.

• Other supply types such as Customer offers have a seperate option to configure the Included services.

As a part of the Transport and delivery costs, a supplier organization may set a Cost per unit or a Cost per delivery.

• The Cost per unit applies per Load carrier when an order is placed on supply lines excluding delivery costs.
• The Cost per delivery applies per delivery when an order is placed on supply lines excluding delivery costs. The Cost per delivery is dropped when a specified amount or volume is reached.

Transport and delivery costs are charged in the price per piece of the sales order. This is currently the only way for Financial service providers to process these costs.

---

Minimum delivery quantity

A supplier organization may set a minimum delivery quantity. By default this minimum quantity is one package and can optionally be set as multiple packages, one or more layers or one or more load carriers. If this minimum quantity is not reached once the latest order moment has passed, a supplier organization may decide not to deliver by accepting or cancelling the order.

Customer initiated sales orders remain uncommitted until the minimum delivery quantity is met. By default Floriday confirms orders when the minimum delivery quantity is met with the exception of loadcarrier(s): a minimum delivery quantity of a Load carrier is met when a Load carrier is loaded to 80% capacity.

A supplier organization may configure their Trade settings in Floriday to manage orders that do not reach the minimum delivery quantity.

• If this trade setting is disabled (default), the supplier can manually approve these orders for the duration of an hour after the latest order moment. If approved, the order is committed. Without manual approval, the orders are automatically cancelled after one hour.
• If this trade setting is enabled, orders are automatically cancelled if the minimum quantity has not been reached. Orders are automatically committed if the minimum quantity is reached.

Read the Helpcenter article: Pending orders for more information.

---

Order periods

A supplier organization configures their order periods by setting:

• The days when orders may be placed (1: days, eg. Monday, Tuesday, Wednesday, Thursday);
• Each day includes 2: orderTimeFrames, which consist of:
• Times before which can be ordered (3: latestOrderTime, eg. 06:00, 13:00);
• Calculated Day(s) when the goods will be delivered (4: deliveryDaysOffset, e.g. 0, +1);
• Times at which goods will be delivered (5: latestDeliveryTime, e.g. 15:00, 07:00).

Below is an image from the Floriday supplier application for a visualisation of this concept:

Note: The supplier API also includes the option to add an additionalPrice within these orderTimeFrames. This additionalPrice is currently not used, but may be used in the future to add additional costs for night time deliveries for instance.

---

Non-working days

Non-working days allow supplier organizations to specify on which National holidays (NL, BE and DE) a supplier organization does not deliver. In other words, the orderTimeFrames for Non-working days are dropped. Instead, the next available orderTimeFrame is chosen.

Note that orders may still be placed on Non-working days, as long as the delivery time is not on a Non-working day.

If a supplier organization decides to add a deviating time frame, the next available orderTimeFrame is replaced with the deviatingTimeFrame set by the supplier organization. See Example 3 below for a detailed explanation.

📘

National holidays without fixed dates

Some National holidays do not have a fixed date every year. We currently do not have a native feature that calculates the National holidays each year, but use an external source for this calculation.

In order to implement the Non-working days, you will need to create your own calculations of when these National holidays occur each year.

The external source we use can be found here: https://www.codeproject.com/Articles/10860/Calculating-Christian-Holidays.

Below are some practical examples to visualize how the Non-working days function. We use Ascension Day as our example, which is on a Thursday by default.

Example 1 - A single same day order period

The supplier organization has set the same order period for Monday through Friday. On the selected weekdays, anything ordered before 06:00 is delivered on the same day at 13:00.

The order and delivery days for this supplier organization will look like this:

• Orders before Monday 06:00 are delivered on Monday at 13:00.
• Orders before Tuesday 06:00 are delivered on Tuesday at 13:00.
• Orders before Wednesday 06:00 are delivered on Wednesday at 13:00.
• Orders before Thursday 06:00 are delivered on Thursday at 13:00.
• Orders before Friday 06:00 are delivered on Friday at 13:00.

This also means that anything ordered after 06:00 will be delivered the next working day at 13:00.

Take note that Saturday and Sunday are not enabled in this example. Anything ordered after Friday 06:00 (including the weekend) will be seen as ordered before Monday 06:00 and will therefor be delivered the next Monday at 13:00.

With regards to Ascension Day, the Thursday as a delivery day is ignored. Instead, Friday is chosen as the next available delivery day.

With Ascension Day as a Non-working day, the order and delivery days for this supplier organization will look like this:

• Orders before Monday 06:00 are delivered on Monday at 13:00.
• Orders before Tuesday 06:00 are delivered on Tuesday at 13:00.
• Orders before Wednesday 06:00 are delivered on Wednesday at 13:00.
• Orders before Thursday 06:00 are delivered on Thursday at 13:00.
• Orders before Friday 06:00 are delivered on Friday at 13:00.

Note: Orders before Friday 06:00 include orders placed on Thursday.

---

Example 2 - Multiple order periods per day

The first example was fairly simple where ordering and delivering was done on the same day. In practice, a supplier organization usually has more than one orderTimeFrame per day. Our next supplier is no different.

This supplier organization has two orderTimeFrames per working day:

• Orders before Monday 06:00 are delivered on Monday at 13:00.
• Orders before Monday 13:00 are delivered on Tuesday at 07:00.
• Orders before Tuesday 06:00 are delivered on Tuesday at 13:00.
• ...
• Orders before Friday 13:00 are delivered on Monday at 07:00.
• Orders before Monday 06:00 are delivered on Monday at 13:00.
• Etc.

See the coloured timeline in the image for a visual representation.

• The green bar represents the order period with the green dot.
• The purple bar represents the order period with the blue dot.

---

With this in mind, we can now establish Thursday as a delivery date. We will include the latest delivery time on Wednesday and first delivery time on Friday as a reference:

• Orders before Wednesday 06:00 are delivered on Wednesday at 13:00
• Orders before Wednesday 13:00 are delivered on Thursday at 07:00.
• Orders before Thursday 06:00 are delivered on Thursday at 13:00.
• Orders before Thursday 13:00 are delivered on Friday at 07:00.
• Orders before Friday 06:00 are delivered on Friday at 13:00.

On Ascension Day, Thursday as an order date and as a delivery date is ignored:

• Orders before Wednesday 06:00 are delivered on Wednesday at 13:00
• Orders before Wednesday 13:00 are delivered on Thursday at 07:00.
• Orders before Thursday 06:00 are delivered on Thursday at 13:00.
• Orders before Thursday 13:00 are delivered on Friday at 07:00.
• Orders before Friday 06:00 are delivered on Friday at 13:00.

---

Example 3 - Deviating time frames

In addition to Non-working days, a supplier organization may also configure a different delivery time for the day after a Non-working day. This is referred to as the deviatingTimeFrame and applies to the first valid orderTimeFrame that would be chosen in case of a Non-working day.

For the sake of simplicity, we will use the supplier organization from Example 1 with the same order period for Monday through Friday. On the selected weekdays, anything ordered before 06:00 is delivered on the same day at 13:00.

The supplier has selected Ascension Day as one of their Non-Working days.

The order and delivery days for this supplier organization will look like this:

• Orders before Monday 06:00 are delivered on Monday at 13:00.
• Orders before Tuesday 06:00 are delivered on Tuesday at 13:00.
• Orders before Wednesday 06:00 are delivered on Wednesday at 13:00.
• Orders before Thursday 06:00 are delivered on Thursday at 13:00.
• Orders before Friday 06:00 are delivered on Friday at 13:00.
• Orders before Monday 06:00 are delivered on Monday at 13:00.

This time, the supplier organization has set a different delivery time for the day after the Non-working day. Below is another visual representation of this feature from the Floriday supplier application.

Because the supplier selected a deviating delivery time, the standard delivery time for Friday is replaced:

• Orders before Monday 06:00 are delivered on Monday at 13:00.
• Orders before Tuesday 06:00 are delivered on Tuesday at 13:00.
• Orders before Wednesday 06:00 are delivered on Wednesday at 13:00.
• Orders before Thursday 06:00 are delivered on Thursday at 13:00.
• Orders before Friday 06:00 are delivered on Friday at 15:00.
• Orders before Monday 06:00 are delivered on Monday at 13:00.

As stated before. the deviatingTimeFrame only applies to the delivery time after the Non-working day. Subsequent delivery times are unaffected.

---

Implementation model

---

Interaction model