Introduction
Running deliveries for multiple client businesses is a complex challenge. Each client has unique needs for branding, service levels, rates, workflows, and reporting.
For 3PLs and multi-customer couriers, the best solution is multi-tenancy. This software architecture keeps each client's data isolated while allowing you to manage everything from one place. Most delivery platforms, however, are not built this way.
What multi-tenancy actually means
In software, a tenant is a distinct account with its own data, users, and configuration isolated from all other accounts on the same platform. Multi-tenant software hosts multiple clients on a shared platform, with data and workflows isolated so each client sees only their own information — but the operator (the 3PL) can see all of them from a single dashboard.
Multi-tenancy is an architectural property, not a feature you can add later. Platforms built as single-operator tools and later retrofitted with "client accounts" often achieve only partial isolation, with combined reporting, shared rate structures, or permission models that don't hold cleanly under scrutiny.
What true multi-tenancy enables for 3PLs
Per-customer service definitions and rates
Each client has their own service menu (Standard, Express, Same-Day). The 3PL configures each client's complete rate card once, and the system applies it automatically. These rate cards include:
- Base rates and weight increment pricing
- Zone-based pricing
- Applicable fees like fuel surcharges, residential fees, and after-hours fees
Isolated order data and customer records
Client A's orders, customers, delivery history, and exceptions are completely isolated from Client B's. This isn't just a permissions question — it's an architectural requirement. For 3PLs handling clients who compete in the same market, data isolation isn't optional. [1]
Per-customer scan workflows
Different clients often have different standard operating procedures for package handling. A multi-tenant platform with configurable scan profiles lets the 3PL match each client's SOP from the same dispatcher interface and the same driver app — without the need for custom development. [1]
Outbound webhooks per customer
Many clients have their own order management systems that need to receive delivery events. A multi-tenant platform with per-customer webhook configuration lets each client subscribe to their own events, with retry logic on failure. [1]
Billing reports by customer account
At the end of the billing period, the 3PL needs deliveries completed for each client, by service type, by date range, by delivery status — all exportable as CSV without manual assembly. The on-time report compares actual timestamps to client-agreed due dates. [1]
Production and test environment separation
When onboarding a new client or training new dispatchers, test activity should not contaminate production reporting. Environment separation keeps test orders isolated from production metrics. [1]
Why most delivery software fails 3PLs
3PLs who try to use single-operator platforms run into predictable problems:
- Separate accounts per client: Achieves data isolation but fragments the dispatcher's view. Aggregating performance data is manual. Per-account subscription cost adds up.
- Shared account with permission-based separation: False data isolation at the architectural level — it's a permissions layer over a shared data model. Billing reports include all clients, not one at a time.
- Spreadsheets alongside the platform: Rate cards, billing calculations, and exception tracking end up in spreadsheets because the platform can't model per-client pricing and reporting correctly.
Alchemira's multi-tenant architecture
Alchemira was built multi-tenant from day one. Its key capabilities:
- Per-customer services and rate cards
- Configurable scan profiles per customer
- Per-customer notification templates
- Per-customer webhooks with retry logic
- CSV-export billing reports filtered by customer
- On-time reports with variance in minutes
- Production and test environment separation
- Unified dispatcher view across all customer accounts [1]
Questions to ask delivery software vendors
- Is multi-tenancy architectural, or layered on top via permissions?
- Can I configure separate services, rates, and fees per customer without touching other customers?
- Can I see all customers' routes in one dispatcher view?
- Do billing reports segment cleanly by customer with CSV export?
- Can scan workflows be configured per customer?
- Do webhooks fire per customer, or is there a single outbound feed?