Previous loading restrictions

Transferring data between Loady and other systems requires integration via one of our APIs (Application Programming Interfaces). Loady offers various standardized APIs for different applications. Our customers' IT departments configure these integrations according to their specific needs. This means that data transfer must be individually defined within the customer's business processes.

‍

Please contact the responsible integration manager or IT department directly. They can explain exactly how data transfer between Loady and other systems is initiated and executed.

In many submodules, free text fields are available that can be used. If the data could benefit from a structured field (e.g., recurring data), please contact the Customer Success Team. We will work with you to find a solution.

Missing dropdown values can be requested in the same way. If it's a value commonly used as a standard in the (chemical) logistics environment, it can be added quickly.

If an integration is performed via the Loady API, the reference numbers of the Ship-to-Parties from the ERP/TMS system must be used for creating Business Partners on Loady.

Initially, the object structure should be set up in Loady (sites, loading points, assignment of products to loading points, company products, business partners including sites, unloading points, assignment of products to unloading points). It is important to consider the dependencies between the individual object types (e.g., a loading point cannot be created before the site has been set up; a company product cannot be assigned to an unloading point at a business partner before the business partner, the business partner's site, and the unloading point exist).

‍

‍

Once the object structure has been set up, you can begin managing the requirements at the level of the respective objects.

Currently, only data related to created lanes can be downloaded. This includes data for actively used lanes under Lane Management or data for lanes assigned to a tender (Loady4Tender), can be downloaded.

For additional data exports, the Customer Success Team can be requested.

Simply send us your idea by email to support@loady.com. We collect all ideas and evaluate them based on feasibility, effort, and suitability for Loady. You will receive an update on the status of your idea. If it involves a new, complex functionality, we will also contact you to clarify the specific requirements.

‍

There is no universal solution for structuring data in Loady. The structure in Loady should mirror the data structure of the ERP system. The following provides some guidance to minimize potential conflicts.

‍

Object names should be clear and unambiguous to ensure good clarity. For a functional exchange of data between the ERP system and Loady, the field ERP Reference Number, which must be maintained for each object, is crucial. The exact designation from the ERP system must be entered here.

‍

For optimal clarity and assignment of different loading/unloading requirements, it is recommended that separate loading/unloading points be created for clearly distinguishable loading procedures.

‍

The following are examples of how loading/unloading points can be divided according to different loading procedures:

• Bulk products vs. packed products
• Container vs. truck loading

‍

For example, a site could be created in Loady that includes several loading/unloading points.

In this example, these are clearly separated by the type of goods being loaded or the processes required for loading:

• Site: 001
  
  • Loading Point: 001_Bulk
  • Loading Point: 001_Packed_ Truck Loading
  • Loading Point: 001_Packed_ Container Loading

‍

Should any ambiguities arise regarding the data structure, our Customer Success Team is happy to provide individual consultation.

If you have general questions about Loady, please contact support@loady.com. If your questions specifically relate to Previous Loading Restrictions or ePLR-Check, please contact plr-support@Loady.com

‍

All questions that are related to Loady but concern processes or systems within the customer's company must be directed to the respective responsible parties within the company (e.g., IT department, application owner, administrators, support mailboxes).

‍

The attached table shows which topic categories Loady or your own team can support.