When your logistics operation is spread across multiple locations, maintaining your (master) data can be quite a task. And yet, working with accurate data can save you and your colleagues a significant amount of time. Earlier, we explained how Boltrics’ Central Layer module provides a solution for managing all your master data from one place. But does this module also fit your situation? In this blog, we share three scenarios where Central Layer is applied in practice.

A quick refresher: what is Central Layer again?

Central Layer is the module within 3PL Dynamics that allows you to manage data centrally (or decentrally). For example, all your sites can work with the same customer articles, units, regions, and ports, or contracts can be centrally adjusted when they change.

3 scenarios for applying Central Layer in your organization

You can use this central layer in various ways. The most common? Across different operations but with a single administration (1). Alternatively, if you have separate entities (2) or a single database with different financial administrations (3). Let’s break them down for you one by one.

1. Central Layer with underlying databases per site

The first scenario we often encounter involves a central database with separate databases for each site. This scenario is applied when you have, for example, distinct logistics operations with separate customer service teams or across different sites, but still maintain centralized order management or a central customs department. In this case, a database is created as the Central Layer, containing the activities you want to manage centrally. Secondary to this, there are various databases with their own processes and activities. New incoming orders are then distributed from the master database to the appropriate underlying databases via the central layer, based on business logic. This ensures that all your underlying operations consistently work with accurate data.

2. Separate databases with a data warehouse

Another scenario we encounter is when a separate database is used for each site but there is no central order administration. For instance, each site has its own customers, and there is barely an overlap in processes. This scenario often arises when these sites have distinct customer service departments and when your clients perceive the different sites as separate companies. For example, when you operate in multiple countries or regions.

By utilizing a data warehouse, comprehensive analyses and reports can be generated. Furthermore, invoices can be centralized within one financial system, such as Business Central, SAP, or Workday.

3. One logistics database – financially separated

The third common scenario occurs when you manage a single logistics database – a working administration – in which two companies are closely intertwined. For instance, you handle both warehouse activities and transport operations. Although both logistics branches are separate entities, users do activities for both warehousing and transport. Furthermore, your customers make no distinction between the two companies; they view them as one. However, legally and financially, revenues and costs must remain separate. In this case, Central Layer ensures a single logistics database while maintaining a separate financial administration.

What others say about Central Layer

With Central Layer, we can easily store and ship customer goods from multiple sites. Inventory numbers fluctuate enormously as a result of bottlenecks in the supply chain – often caused by global events such as COVID-19, the blockage of the Suez Canal, or the recent situation on the Red Sea. With Central Layer, we are able to respond to these functions adequately, by diverging to other storage locations. And directly continue the shipping process from these locations. - Martijn Put – Supply Chain Improvement Manager at Nedcargo