Noticing that our users responsible for shipping have to perform complex tasks with different carriers (phone, single-carrier web interfaces), we have developed a unique interface to address this challenge: the shipping form.

This tool, fully integrated with Woop, is connected to our carrier catalog (taking into account their network, constraints, and specifics) and also to retailers, thus offering our users a contextualised, seamless, and efficient experience.

Now, a sales advisor can ship goods to their end customer or initiate a product return from home, all in just a few clicks.

Note: a setup step is required before the first use of the form. HERE

Step 0: Choosing the Retailer/Store Pair + Form

This step is useful for several reasons. Firstly, it allows the user, if their profile permits, to choose from the two dropdown menus between several retailers and/or several stores before filling in the form.

It is also at this stage that it will be possible to choose between the different shipping forms created (whether for home delivery or return). More information on the setup HERE.

The stores offered will only be those of the previously selected retailer, and all retailer contexts will remain separate from each other.

Example: If you have a profile with a "manager" role for retailer context X, you will only have access to stores A, B, C, D, and E. A profile with the "salesperson" role for the same retailer, but for store B, will not see stores A, C, D, and E. Similarly, a profile with a role in another retailer's context will not be able to access the shipping forms of retailer X.

This preliminary step (referred to here as step 0) is now mandatory for all users with the user right: Display personalised shipping form(s), even if they do not have a configured shipping form.

When the "see more" separator is displayed, it means that an "old generation" order funnel is available.

The Standard Flow: Home Delivery

Step 1: The "Shipping" Block

This block allows you to enter the departure and arrival addresses of the goods.

The departure location will include, in the case of a standard delivery flow, all the collection points provided for the retailer/store pair as well as the option to enter a custom address. For the latter, you can either enter it manually or use auto-completion to assist your search.

You can do the same for entering the delivery address (manually or via auto-completion).

By clicking on the box, you will have the option to enter additional address details to specify a floor, entry code, or any other useful information for the delivery.

Once you have pressed "next", we will check eligibility with the carriers connected to the retailer to exclude those unable to deliver based on geographical criteria, such as:

• the country or postcode,
• a minimum or maximum distance,
• a predefined geographical area.

Step 2: The "Shipment Content" Block

The shipment content block is used to define the goods to be delivered. The block is divided into two parts: a Parcel part and a Products part.

It is possible to add multiple parcels for delivery using the button on the right, and for each of them, several products as well. Here is an example of a parcel/products distribution:

• Parcel 1
  • product A
  • product B
  • product C
• Parcel 2
  • product A
  • ...

To define your parcel, there are several fields to fill in:

The parcel type (dropdown menu) allows you to choose between several types of parcels such as Standard, Crate, or Pallet. This choice will not affect the predefined weight or dimensions. This field can be hidden in the setup.

The parcel dimension (dropdown menu) allows you to retrieve the different parcel configurations set at the retailer level, including the name, weights, and dimensions. The Other choice allows you to manually enter the parcel dimensions using fields.

The parcel volume (decimal value entry field) is an optional field allowing you to specify the parcel volume (in m3 or cm3). When this field is not filled in, Woop will calculate the parcel volume itself when the order is placed (during the Post Order).

The weight(decimal value entry field) represents the weight of the parcel with all its products, expressed in kilograms.

The quantity (integer entry field) corresponds to the number of parcels with the same information present in the shipment content block. Defaulted to 1, you can choose to hide this field in the settings.

Example: If you enter 5 in quantity, it's as if you pressed "add a parcel" 5 times with the same information for each of them.

The footprint (decimal value entry field) is an optional field corresponding to the area occupied by the parcel on the ground (possible units: m2, cm2 or Pallet)

The checkbox Add references to the parcel allows you to add a Reference to the parcel as well as the associated Delivery barcode for each parcel represented by the Quantity field

Once the parcel is filled in, and if the block has been made visible in the settings, you can then add products.

NB: By default, you will always have a product added as general merchandise. You can remove it, but you will need at least one to validate the Parcel stage.

You can then add other products of your choice either via the Add product button or by searching in a product catalog via the Search a product from the catalog field. The latter option will only be possible if you have added a catalog on the retailer page (via the settings tab).

Some types of products require additional information, such as hazardous products. More details here.

Depending on the settings of your shipping form, the following product fields may be accessible, while remaining non-mandatory:

• Description: the name of the product (free text field)
• Typology: this field allows you to classify the product according to its typology in order to filter out any carriers unable to transport certain products (Dropdown menu, example: hazardous products)
• CUG: The Unit Management Code allows you to add a product reference specific to the shipper (character string)
• EAN: corresponds to the product barcode (numbers)
• Dimensions and weight: allows you to enter dimensions and a weight specific to the product. (Length, width, height in mm, cm or m and Weight in mg, g or kg)
• Product families: Allows you to provide more details on the product nomenclature (free text field)
• Product price: Allows you to specify the selling price of a product (value + currency)
• Product services: This field allows you to set one or more specific services for the product in question (dropdown menu with the list of services).
  NB: Once this field is filled, step 3 of the form (services) will have the service: "Service by product"

NB: filling in these fields can be simplified via the management of a product catalog

Once the parcels and products are entered, a new check at the carrier level is carried out. This time, it focuses on the capacities and constraints of the carriers on the delivery of the goods:

• Minimum / maximum weight, volumetric weight
• Quantities, developed size, volume or footprint
• Type of products
• etc

Step 3: The "Service" block

The service block includes all the services available for the carriers eligible at this stage. In other words, if a carrier is not eligible following the parcel/products stage, the form will not offer its various services.

At this stage, the form therefore offers main services and sub-services, representing all the possibilities to deliver the desired goods. Once this is chosen, a new check of carriers is carried out, in order to exclude those not offering the requested service(s).

If the delivery tags option has been activated in the form, and if tags have been predefined in the dedicated block present on the settings tab of the retailer page, then the user may be required to make choices to successfully complete the delivery.

The set of tags here will depend on the configuration carried out at the retailer level. This may involve a checkbox, a dropdown list or a yes/no selector.

NB: If some tags are not from the settings block on the Retailer page, they will appear as editable text fields. This may be the case for an order modification made by API.

Step 4: The "Delivery" block

This step allows the user to choose the day and time slot for the collection and delivery of the goods. At this point in the form, the carriers eligible for delivery during the previous step will be consulted to retrieve their delivery schedule. The results are offered day by day and pooled between the carriers.

The collection schedule

If activated in the settings, the user may be asked for a collection date for the goods at the store (or exchange place).

The first date on which the user is positioned has been dynamically calculated thanks to the promise engine. This allows for the calculation of the earliest possible collection date based on the constraints of the various carriers eligible at this stage of the form. Then, the user can choose a time slot, which will depend on the existence of a shipping schedule, the carrier's working hours at the exchange place level and the type of exchange place specified in the order (Pre-registered exchange place or delivery address).

Example: If a shipping schedule, it will take precedence over the carrier's working hours at the exchange place level.

The delivery schedule

Example: the user clicks on 1 July, the proposed results will be the slots of all eligible carriers, sorted in chronological order. The user clicks on the slot [12:00-14:00] and the carriers Niji and Luigi are available but not Chronopost.

Managing delivery slots

Once again, the first date on which the user is positioned has been dynamically calculated thanks to the promise engine. This allows for the calculation of the earliest possible delivery date based on the constraints of the various carriers eligible at this stage of the form. Once the date is chosen, different slots may be offered.

Several cases are then possible for the display of slots, which can be either:

• Intelligent, in that these slots will have been brought up by our route optimisation engine. The proposed slots will therefore be inserted into an existing or upcoming route via our route management module: Route Planner,
• Dynamic, directly from the connected carrier's information system. The rules for displaying slots depend here on the carrier,
• Static, with a theoretical schedule provided at the retailer / carrier exchange place level. When a schedule with capacity is added, it can be defined either in decrement to the order or the parcel.

Example: an order with 3 parcels has 2 eligible carriers: X and Y. The schedule for carrier X is set "per parcel" and Y "per order". When choosing the carrier, the form will display the available slots for both carriers based on their remaining capacity (minimum 3 for X and 1 for Y) and depending on the chosen carrier, 3 or 1 will be deducted from the remaining capacity.

NB: There are also static slots called "default", which will be offered when none of the 3 types of slots above are possible. These slots can be of 2 types: "default retailer" provided via the retailer page and "default global" defined by WOOP. There is no order capacity management for default schedules.

In summary, a slot can be:

• Intelligent,
• Dynamic,
• Static,
  • theoretical with capacity
  • default without capacity

The form, depending on the configuration adopted, can offer the display and choice of the carrier. If the choice is not made or if the carriers are not displayed via the configuration, then the WOOP orchestration engine will find the best carrier once the order is finalised. 

The price of the order

This feature is designed to automatically calculate delivery fees so that the user can see a VAT-inclusive amount to be re-invoiced to the end customer. It should be noted that this amount is completely unrelated to the carriers' rate cards and therefore, to what a carrier charges the retailer. 

To function, you will need to:

• activate the order price function in the form settings (delivery tab)
• add in the technical tab of the retailer page, a rate management at the retailer level (and not carrier)

Step 5: The "Additional Information" block

The final step before completing the form aims to gather additional information about the order, namely:

• the order references
• the customer's information

Order references

The order references can take 2 forms:

• the order number is a unique identifier required in the Woop Information System in a retailer context. You will find it in API calls under the field: externalOrderId or in the Woop interface under the title: Technical ID.
  NB: The order number of a delivery whose status is completed can also be reused.
• the business reference is an additional and optional identifier in the form (activatable if needed in the settings) that can be used by the retailer for its own needs.
  If the field is not activated or not filled in, it will take the same value as the order number.

Both references can be automated thanks to the auto/manual generation feature available in the settings tab of the retailer page. For this, a timestamp will be generated and placed between a prefix and a suffix of your choice, among:

• the ID of the exchange place
• A store identifier
• A store name
• The current date or the hour and minute

Recipient's details

The fields to be filled in this section are used to identify the end customer, the recipient of the delivery. This data will be useful, among other things, for parcel tracking, label printing, and notification management.

Completing the form

Once the entire form is filled in, the complete the form button is activated. 

NB: If you wish to go back to modify a block, you will need to go through the validation of each subsequent block to recheck the carriers' eligibility.

Once validated, a technical POST / Order call is made based on the entered information to create an order in the WOOP information system.