One account for logistics, one channel for each merchant
The channel is the unit of work: it contains everything needed to ship on behalf of a client. When a new merchant arrives, you open one, connect their store and choose the couriers; the rest of your flow does not change.
- Merchant or logistics contracts, your choice per channel
- Orders from the store and marketplaces of the merchant, or from your WMS
- A dedicated returns channel, if the merchant wants it separate
Each department sees its part, across all clients
Users and permissions are assigned by section. The warehouse prints, customer service follows exceptions, administration closes the accounts: everyone works across all channels, without accessing what they do not need.
At month end, the re-invoicing is already split by client
Every shipment starts within the channel of its merchant, so the courier cost is already in the right place. Before paying, Nelson compares courier invoices with the contracts and tells you what to dispute: you do not pass on to the client a surcharge you should not have paid.
Check invoices with NelsonPost-shipping becomes an item on your price list
Notifications, tracking page and review request with the merchant's brand: a service you can sell together with warehousing, which the end customer sees as coming from the store they bought from.
- The brand of the merchantLogo, colours and domain of each client on the tracking page and notifications. The logistics company does not appear.
- One more sales channelBanners and product suggestions on the page the customer opens several times while waiting for the parcel.
- Reviews on deliveryThe request goes out when the courier delivers, with the store name of the merchant.
DHL · delivery tomorrow morning
InPost · collected from the LockerPlug into your warehouse without changing it
The WMS stays yours: via REST API and webhooks it sends orders to Qapla' and receives labels and tracking events. Labels come out in ZPL or PDF, including on network printers, with PrintNode.
API and webhooks- couriers with label creation and printing
- 45+
- couriers for tracking
- 450+
- native eCommerce platforms
- 16
- connectable marketplaces
- 110+
Frequently asked questions
What does it mean that Qapla’ is multi-client for logistics?
In the same account, the logistics company creates a channel for each merchant. Each channel has its own couriers, assignment rules, sender, notifications, tracking page and returns, while the logistics team works across all channels from a single panel.
Does the end customer see the brand of the logistics company or of the merchant?
The brand of the merchant. Email, SMS, WhatsApp and the tracking page use the logo, colours and domain of the merchant: the logistics company stays behind the scenes.
Can I split courier costs by merchant?
Yes. Every shipment belongs to the channel of its merchant, so courier costs can be read and exported client by client. With Nelson, courier invoices are checked line by line before payment.
Does Qapla’ connect to my WMS?
Yes, via REST API and webhooks: the WMS sends orders and receives labels and tracking events. Alternatively, each channel connects directly to the store and marketplaces of the merchant.
How does the partner programme work for logistics companies?
Logistics companies that offer Qapla’ to their merchants can join the partner programme. Terms and details are agreed in a call with the Qapla’ team.