Previous loading restrictions

An Inbound or Outbound Master includes requirements that apply to multiple Inbound or Outbound Products at a loading/unloading point. For example: At a site there is a loading point where 10 Outbound Products are loaded with identical loading requirements. Instead of maintaining the requirements 10 times for the individual products, these requirements can be stored once in an Outbound Master . When the Outbound Products are assigned to this Outbound Master , the requirements maintained at the master level are transferred to the individual Outbound Products.

‍

The creation and maintenance of an Outbound Master (Inbound Master similarly) is done as follows:

1. Create the Outbound Master as an object and maintain the requirements
2. Assign the associated Outbound Products to the Outbound Master

‍

Important: As soon as Outbound Products are assigned to an Outbound Master , the originally stored data of the individual Outbound Productswill be overwritten. This means they are deleted and cannot be restored. If Outbound Products are removed from an Outbound Master , the master's requirements remain, but the data is simply no longer synchronized. From this point on, they must be manually edited at the product level.

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.

‍

In cases where free text fields are not maintained in all input languages available on Loady, Loady defaults to the standard language English . This means that free text fields must always be maintained in at least English. Otherwise, data in free text fields cannot be saved. If Loady is used in another language, e.g., German, to maintain the content in English, the input language must be changed via the language selection for free text fields to English.

If the data is only maintained in English, the English entry will be displayed as a fallback when Loady is used in another language.

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.

Requirement Profiles are designed so that the objects contained therein (Business Partner, Site, Unloading Point, Inbound Product) cannot be exchanged or replaced by others after creation. This is because a requirement profile establishes a unique combination of these objects.

‍

Therefore, if a Business Partner, an Inbound Product or an Unloading Point needs to be adjusted within a requirement profile, a new requirement profile with the desired objects must be created. If the requirement profile with the original objects is no longer needed, it must be deleted.

Loady currently does not support PDF uploads. You can upload the PDF to a website and insert a link as a URL in the corresponding free text field in Loady.

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.

We are happy to support you with the initial setup of the data. Based on our experience, we can recommend some best practices. Generally, during the initial data setup on Loady, it is advisable to designate a central contact person to coordinate and monitor the setup (e.g., ensuring all sites are created, all products assigned).

‍

Additionally, expertise from various departments is required for data setup. Which departments actually need to be involved in the data setup depends on the client's organization and the distribution of responsibilities. Based on previous experience, expertise from the following departments is needed:

‍

• Sites and loading/unloading points within your own company: employees from site management or those responsible for loading/unloading points
• Company products: Employees from product management, quality management, or technical marketing
• Business Partners and all associated objects such as sites, unloading points, inbound products and associated unloading requirements are usually maintained or managed by customer service or sales employees
• Previous loading restrictions: Employees from quality management, technical marketing, or those responsible for loading points
• Tenders: Employees from the purchasing organization
• ERP structure: Key users or employees from IT departments