Base for Fulfillment Operators — What's Missing and How to Fix It
Base (formerly known as BaseLinker) is excellent for sellers, but fulfillment operators hit walls fast. Five critical gaps — each costing time or money — and what to do about each of them.
Table of contents
Contents
- Base is great — just not for you
- Gap 1: Multi-tenant — one account, many clients
- Gap 2: No per-client billing
- Gap 3: No client-facing view
- Gap 4: Inbound scheduling still runs on email
- Gap 5: No per-client ticket system
- Conclusion: a layer on top of Base
Base is great — just not for you
Base (also known as BaseLinker) is one of the best order management platforms in Polish e-commerce. It integrates 1000+ platforms, runs automation rules, prints labels, and syncs stock. If you’re a single seller with one store — Base is for you.
But a fulfillment operator is not a seller. An operator is a company that serves other sellers — 5, 10, 20 clients simultaneously, each with their own configuration, pricing, expectations, and legal status. And this is where Base runs into fundamental limitations.
This isn’t a criticism of Base — it does what it was designed to do extremely well. But if you’re using it as the operational hub for your entire fulfillment business, you’ll eventually hit each of the following walls.
Gap 1: Multi-tenant — one Base account, many clients
The problem
Base works per account. Most operators have one Base account and connect their clients’ marketplace accounts or stores to it as integrations. But all those orders share the same workspace.
There’s no native concept of a “fulfillment client” in Base. You can’t say: “these are Client A’s orders, those are Client B’s, and each sees only their own.”
How operators cope today
Most commonly: a separate Base account per client. Reasonable in theory, until you have 10 clients — then you’re managing 10 logins, 10 configurations, and 10 subscriptions. Cost: at least 1,000-3,000 PLN/month in subscription fees alone, not counting management overhead.
Alternatively: one shared Base account with tags as a client separator. This quickly becomes chaos beyond 5-6 clients.
Fix
A layer above BL that understands the concept of a “fulfillment client”: isolates their orders, stock, history, and access permissions. Each client sees only their own data.
Gap 2: No per-client billing
The problem
Base has no built-in billing mechanism between the operator and clients. You can issue an invoice through an external system, but Base won’t tell you: “Client X occupied 23 pallets for 15 days, had 430 outbound orders, 18 returns — here’s what to invoice.”
How you gather data for invoicing is 100% your problem. And because there’s no native place for per-client pricing in Base, most operators end up in Excel.
How operators cope today
Excel. Tags + CSV reports + manual rate calculations. Or a custom Base API script (expensive to maintain). We covered this in detail in the article 5 Methods for Billing Fulfillment Clients in Base.
Fix
A system with native per-client pricing: each client has their own rate structure (storage, inbound, outbound, returns, additional services), and the system automatically calculates charges based on BL data.
Gap 3: No client-facing view
The problem
Your client (the e-commerce store) wants to know: how much stock do I have, where are my orders, what came back as a return. In Base you could give them access to your account — but then they see every other client’s data. That’s a dealbreaker.
The absence of a secure, isolated view for the end client is one of Base’s biggest shortcomings from a 3PL perspective.
How operators cope today
Sending weekly PDF reports by email. Phone calls to answer “how much stock do I have?” Shared Google Sheets with restricted access. None of these scale or build trust.
Fix
A dedicated client portal: login-protected, synced with Base, showing only that client’s data. We covered this in depth in the article Client Portal for Fulfillment — Is It Worth It?.
Gap 4: Inbound scheduling still runs on email
The problem
A client has a delivery tomorrow. They need to notify you: when the truck arrives, how many pallets, which SKUs, the CMR number. There’s no inbound booking form in BL. No system to accept this information, store it, and assign it to the correct client.
Result: inbound bookings land in email inboxes. Some end up in spam, some get lost in a thread mixed with unrelated topics, some arrive on Saturday when nobody’s checking. Your warehouse finds out about a delivery late.
How operators cope today
A Google Form (free but no integration). Emails to a dedicated address. Phone calls. None of these sync with the rest of your system.
Fix
Inbound scheduling as part of the client portal: client fills out a form (date, pallet count, SKUs, CMR), the booking goes into the system attributed to that client and date, your warehouse sees it in a delivery calendar. Automatic notifications.
Gap 5: No per-client ticket system
The problem
A client has a problem. An order shipped to the wrong address. Damaged goods. A disputed invoice line. They send an email. The email lands in a generic support inbox. Someone responds. The client follows up. The email thread becomes 20 messages long with other issues mixed in.
Base has order notes, but that’s not a support system. There’s no per-client history, no SLA, no priority, no status tracking.
How operators cope today
Email. In better cases: Freshdesk or Zendesk (cost: 200-500 PLN/month), but without integration with BL and the client’s fulfillment data.
Fix
Tickets integrated with the client portal: the client opens a ticket, sees its status, gets notified of responses. You see all tickets per client with full context (stock levels, order history, invoices).
Conclusion: a layer on top of Base
None of these gaps are “bugs” in Base — Base simply wasn’t designed as a multi-tenant platform for fulfillment operators. It’s a tool for sellers.
The solution is a business layer above BL that closes all five gaps simultaneously:
| Gap | Solution |
|---|---|
| Multi-tenant | Client isolation in one unified system |
| No per-client billing | Automatic per-client invoicing |
| No client view | White-label client portal |
| Inbound scheduling | Scheduling module with notifications |
| No ticket system | Per-client support system |
This is exactly what v5v is: a business layer on top of Base that lets you, as a fulfillment operator, focus on operations instead of administration. See pricing or book a call to find out how quickly you can deploy this.