Run a courier network, not just a courier company.

Your integrator sits on top of partner couriers who each run their own operation — own staff, own vehicles, own AWB series. CourierManager models this natively.

• Separate "operating companies" inside one instance, each with its own AWB series, logos, invoice templates, bank accounts, and financial records.
• Separate partner portals — each partner sees their own shipments, their own settlements, their own metrics. The customer sees one unified brand.
• Multi-tenancy at the architectural level — share one instance with logical separation, or run a fully dedicated instance per entity when data residency demands it.

A Cluj-to-Constanța shipment is picked up by partner A in Cluj and delivered by partner B in Constanța. Under your brand. Without manual dispatcher intervention.

• Destination-based and client-preference-based routing between own fleet, partner couriers, and lockers.
• 20+ built-in courier-partner integrations — FAN, Cargus, Sameday, DPD, GLS, Speedy, Econt, MyGLS, DHL Express, DHL eCommerce, NovaPosta, InPost, Meest, Elta, and more (full directory →). Orders flow out; status updates flow back.
• Status-code translation: each partner sends its own codes; we normalize everything to a standard 8-status set, so your dashboard doesn't care whether FAN says "Livrat" or Cargus says "Delivered."

Paying partners correctly at scale is the operational detail that kills integrators who try to stitch it together in spreadsheets.

• Multi-currency COD flow: collect in local currency, settle to the client in EUR or RON.
• Two-layer settlement: partner courier reconciliation → bank transfer → client payout. Each step traceable, each step reversible, each step documented.
• Configurable settlement cadence per client, per partner — different payment terms for different relationships.
• Financial artifacts generated automatically: courier deconts, client deconts, COD receipts, invoices, direct compensation (invoice ↔ COD), credit and debit notes.