ERP for Third-Party Logistics (3PL): Multi-Client Stock, Activity-Based Billing, and Warehouse SLAs

A third-party logistics (3PL) company stores, packs, and ships goods owned by others. The business looks similar to ordinary warehousing, but there is a fundamental difference: the stock on the shelves is not yours, your customers are goods owners who demand visibility and performance according to an agreement, and your revenue comes from a variety of service rates rather than from selling goods. Systems designed for a shop or factory rarely fit this model.

This article covers the ERP and warehouse system needs for 3PL and warehousing service companies: a multi-owner data structure, the flow from receiving to shipping, activity-based rates and billing, SLA measurement, customer portals, and integration with online stores and couriers. The aim is to help owners and operations managers understand what needs to exist before choosing or building a system.

Summary

• A 3PL system must separate stock and transactions per goods owner (client), because one warehouse serves many clients with different rules
• Revenue comes from many rate types: storage, inbound and outbound handling, packing, shipping, and additional services, so billing must be automated from activity records
• SLAs such as on-time shipping and stock accuracy need to be measured from system data, not from claims
• A customer portal and integration with clients' online stores reduce status inquiries and manual entry errors
• Start with the core flow of receiving, storing, picking, and shipping, then add complex rates and per-client profitability analysis

What sets 3PL apart from an ordinary warehouse

In a company's own warehouse, the goods on the shelf are that company's assets. In a 3PL, every unit belongs to a client. That difference changes a lot.

• Stock ownership: every item must always be linked to its owning client, and stock reports must not mix between clients
• Per-client rules: each client can request different rules for receiving, quality checks, packing, labeling, and shipping
• Revenue source: service fees, not goods sales margin
• Accountability: loss, damage, and stock differences are contractual responsibilities that can mean compensation
• Visibility: clients want to see their own stock and order status at any time

Consequently, the system must be designed as multi-client from the start. Installing a single-owner warehouse application and patching it for other clients usually ends in mixed data and manual billing. A similar multi-tenant approach is discussed from the product side in multi-tenant architecture for building SaaS products.

Core operational flow and the data to record

The basic 3PL flow has five stages. A good system records each stage with a traceable trail.

1. Notification and receiving of inbound goods

Clients usually send an advance shipping notice first, listing items, quantities, and the estimated date. When the truck arrives, staff match the physical goods against the notice, record differences and damage, take photos where needed, then mark the goods as received. The receiving mechanism with lot numbers and expiry dates is covered in lot, batch, and expiry date tracking with ERP, which is highly relevant for food, cosmetics, and pharmaceutical clients.

2. Storage and putaway

Goods are placed in specific shelf locations. The system needs to know the location of each unit, shelf capacity, storage type (ambient, chilled, hazardous), and rules such as first in first out or first expired first out. These practices are discussed more broadly in warehouse management systems for growing businesses.

3. Order receipt and picking

Client orders, whether from online stores or manual uploads, enter as pick instructions. The system groups orders, determines the most efficient pick path, and guides staff through handheld devices or barcode scanners. Scanning during picking reduces mispicks significantly.

4. Packing and shipping

Goods are packed according to client instructions, labeled, and handed to the chosen courier or fleet. The system records weight, dimensions, tracking number, and shipping cost. For companies running their own fleet, route and vehicle management is in fleet and transport management with GPS and ERP.

5. Returns and special handling

Returned goods from end buyers come back to the warehouse for inspection, are classified as resellable, needing repair, or damaged, then their stock is updated per the client's instructions. Special handling such as attaching labels, making bundle packs, or gift wrapping is recorded as an additional billable service.

Activity-based rates and billing

This is the part that most distinguishes a 3PL. Revenue comes from many rate types, and each client may have a different agreement. Examples of rate components:

• Storage: per pallet, per shelf, per cubic meter, or per unit, calculated daily or monthly, sometimes at a higher rate for chilled storage
• Inbound handling: per pallet, per carton, or per unit on receipt
• Outbound handling: a per-order fee plus a per-line or per-unit pick fee
• Packing: packaging material cost and packing labor cost
• Shipping: courier rates passed through with or without an added margin
• Additional services: labeling, kitting, quality inspection, product photography, and returns handling
• Monthly minimum fees and penalties or discounts by volume

For accurate billing, every activity must be recorded automatically as a billable event: receiving one pallet, picking one order, adding one label. At period end, the system calculates the total based on the client's rate card and produces an invoice with a breakdown. This works similarly to milestone billing in project billing and milestones for service businesses, except that the trigger is an operational activity.

Some frequent traps:

• Activities not recorded in the system and therefore not billed, known as revenue leakage
• Rate cards stored in separate spreadsheets and out of sync with the system
• Storage calculations that do not follow daily stock changes
• Invoice disputes because clients cannot see the breakdown of activities billed

Measuring SLAs and warehouse performance

3PL contracts generally contain service targets. Those targets are only worth something when measured objectively from system data. Common indicators:

• Order processing time: from order received to handed to the courier
• Pick accuracy: the percentage of orders shipped with the right items and quantities
• Stock accuracy: the comparison between physical count and system record
• Receiving time: from goods arrival to being available for sale
• Damage and loss rate
• On-time delivery by couriers
• Response time to client inquiries

Show these indicators on an internal dashboard and, if agreed, on the client portal. Complaint handling and escalation based on service levels is discussed in customer support ticket systems and SLAs. Stock accuracy is maintained through routine cycle counting, following the principles of stocktaking without stopping operations.

Customer portal and integration

3PL clients want to know their stock and order status without having to call. A customer portal showing stock per location or warehouse, receiving history, order status, and invoices saves the service team a lot of time. The design of such a portal is discussed in B2B customer and supplier portals.

Automatic integration brings even greater benefit.

• Clients' online stores: orders flow automatically into the warehouse, and stock and tracking numbers are returned automatically
• Marketplaces: stock and order synchronization so no double selling occurs
• Couriers: label creation, tracking, and shipment status updates
• Accounting system: invoices and payments
• Other client systems: the client's ERP, if they have one

A commonly used technique is webhooks and APIs for near-instant updates, as discussed in webhooks and real-time integration for business. If you also handle imports, landed cost and customs documents affect the value of clients' goods, which you can see in landed cost: calculating imported goods cost in ERP.

Profitability per client and per service

Not all clients are equally profitable. A client with large volume but many small items and high returns can be costlier to serve than a client with few but high-value orders. A system that records actual costs enables analysis such as the following.

• Revenue and direct costs per client: labor, packaging materials, space, and shipping
• Cost per order and per unit compared with the rate charged
• Space utilization: the percentage of capacity filled and value per square meter
• Labor productivity: orders per person per hour
• The most and least profitable services

The results help determine the next contract price, decline or renegotiate loss-making clients, and decide on investments such as extra racking or automation.

Common mistakes in building a 3PL system

• Using a single-owner warehouse system so client stock gets mixed
• Billing on estimates rather than activity records, so revenue leaks and disputes rise
• No barcode scanning, so accuracy depends on human care
• No portal or reporting for clients, so the service team is overwhelmed answering status questions
• Manual integration through spreadsheets that is prone to delay and error
• Not measuring SLAs, so performance disputes cannot be settled with data
• Not separating returned, damaged, and resellable goods

Steps to start

1. Map the core flow and the types of service you offer, including variations per client

2. Design the client, item, location, and rate card data as the foundation

3. Apply barcode scanning at receiving, picking, and shipping

4. Automate recording of billable activity and invoice issuance

5. Build an SLA dashboard and a basic client portal

6. Add integration with clients' online stores and couriers, starting with the largest client

Frequently asked questions

Does a small 3PL need a specialized ERP? Not necessarily specialized, but the system must support multi-client, activity-based rates, and location tracking. Many ERPs can be customized for that.

How do we handle clients with different rates? Store a rate card per client in the system with effective dates, and let the billing calculation refer to it.

Is a separate warehouse management system needed? It depends on scale. At small scale, the warehouse module in an ERP may be enough. At high volume and complex operations, a dedicated warehouse system integrated with the ERP is more suitable.

How do we prevent revenue leakage? Record every billable activity automatically at the point of work, and reconcile activity counts with invoices each period.

How do we keep client data separate? Design data ownership per client at the database and access rights level, and test that a user of one client cannot see another client's data.

Conclusion

A 3PL company sells operational reliability, and that reliability is proven by data: accurate stock per client, activity that is recorded and billed correctly, measurable SLAs, and visibility for goods owners. A system designed as multi-client with activity-based rates, barcode scanning, a customer portal, and integration to online stores and couriers helps you grow the business without losing control of cost and margin. Start with a tidy core flow, then add profitability analysis and automation gradually.