Fulfilment & 3PL
One WMS, multiple merchants, no chaos.
Tremo WMS is multi-tenant from the ground up. Every fulfilment customer has their own environment inside your WMS: own stock, own carrier rules, own packing slips, own portal. No white-label licence, no separate instances.
14 days free · No credit card · Your data, exportable
Configurable per merchant
Three example merchants in the same Tremo, each with their own settings. Guaranteed separation at the database level.
| Setting | Merchant A | Merchant B | Merchant C |
|---|---|---|---|
| Carrier | PostNL | DPD | DHL |
| Cutoff time | 16:00 | 14:30 | 17:00 |
| Packing slip | Own logo | White-label | Tremo default |
| Pick fee | € 0.40 | € 0.55 | € 0.30 |
| Portal URL | a.your3pl.com | b.your3pl.com | c.your3pl.com |
What keeps 3PL owners up at night
You have 4 merchants, 6 carriers, 2 warehouses and one spreadsheet that has to make sense of it all. Four patterns we see again and again:
Per fulfilment customer: own carrier rules, own packing slip template, own cutoff time, own billing rates, own portal branding. All in the same Tremo WMS.
Customer portal per merchant. They see their own stock, orders, return status and advice — without ever seeing your other customers. Calls turn into self-service.
Carrier rules out of the box: by weight, country, customer or cutoff. Defaults inherit per fulfilment customer. One click on 'ship' picks the right carrier automatically.
Per-merchant tariffs (pick, pack, shipping, storage) are tracked automatically. Audit-log per action so you can bill transparently — even during disputes.
What 3PLs find here
A WMS that doesn't fall apart when the third customer joins. Real multi-tenant — not one tenant with a tab for customers.
- Strictly separated per customer
Customer A can never see customer B's data — not in the UI, not through an API. The separation lives in the database itself, not in the UI. Full audit export on request.
- Customer portal per merchant
Own URL, own branding (logo, colour theme), own users. Merchants see orders, stock and advice — nothing else.
- Carrier rules per customer
DPD for customer A, DHL for customer B, PostNL as fallback. Auto-pick by weight, country, customer or cutoff. Defaults inheritable.
- Per-customer packing slip templates
Own logo, own footer, own sender on the slip. No designer needed, everything editable in the UI.
- Per-customer carrier credentials
Every merchant has their own PostNL or DPD account? No problem. Tremo WMS ships with the right credentials per shipment.
- Audit-log per action
Who picked what, when it was booked, which return was accepted. Searchable in the UI, exportable for disputes or compliance.
Frequently asked questions
What 3PL operators and fulfilment managers want to know before switching.
How many fulfilment customers can I host?+
Does each customer get their own environment or just a tab?+
Can I put my own branding on merchants' portals?+
How does invoicing merchants work?+
What if one merchant wants their own Supabase instance?+
Can I automate onboarding of new merchants?+
One WMS, all merchants.
Try Tremo WMS free for 14 days. Migration onboarding for existing 3PLs included. No credit card.