Real WMS, with per-merchant data walls.
Each merchant's data is walled off. Your warehouse staff sees everyone. Your merchants only see themselves. Per-merchant billing rules. WMS-grade pick-pack-ship without a separate WMS bill. White-label the surface if you want.
Multi-merchant fulfillment, run on one platform.
Regional and national 3PLs. 4 to 80 merchants per operator.
The actual problem, grounded in reality.
Running a 3PL is two software problems pretending to be one. You need a warehouse system that holds inventory accurate to the bin across 40 merchants, and you need a billing system that invoices each merchant for the work you actually did (the picks, the packs, the storage days, the special handling). The market has solved each of these badly. ShipHero, Extensiv, Logiwa, Cin7 Core: each takes a different shortcut and exposes you to a different category of risk.
The shortcut you've probably accepted: a warehouse system that bolts on a billing module, where the billing rules are a UI form with 12 fields and the WMS does not know about chargebacks, marketing moments, or the merchant's actual SLA. Or a billing tool that integrates with your WMS via nightly CSV, where 'hands' do the reconciliation when the numbers do not match. Either shortcut produces a per-merchant invoice your CFO does not trust.
CCEN treats multi-tenancy as something the platform was built around, not something added later. Each merchant's data is walled off at the database level. Permission rules apply at the API. White-label subdomain per merchant. Billing rules attach to merchant contracts. The merchant logs into their own surface (yours, branded as theirs) and sees only their data. You log into the operator console and see all merchants.
What changes on CCEN
Per-merchant operations that are designed in, not bolted on.
Per-merchant walls, by design
Each merchant's data is walled off at the database level. Permission rules apply at the API. White-label subdomain per merchant. Your merchants do not see each other's data, ever.
Billing that knows what your team did
Pick fees, pack fees, storage fees, special-handling fees, kitting, inserts, returns, all rolled up per merchant from real warehouse events. The invoice exports cleanly to your accounting system or to QuickBooks.
Pick paths optimized across the floor
Path optimization runs across every merchant's stock in the warehouse. Multi-merchant batches are valid when bins are adjacent and the merchants' SLAs allow it. Single-merchant batches when they don't.
Same platform, different views
Your warehouse staff sees the operator console: every merchant, every order, every bin. Your merchants see their own surface: their orders, their inventory, their listings. Same platform underneath, two views on top.
Audit log per merchant
Every action records the actor, the merchant context, the timestamp. Disputes get resolved in seconds because the log is honest. Merchant asks why we shipped 4 instead of 5? Show the log.
What changes for your team and your merchants.
Onboard a merchant in an afternoon
Wizard-driven onboarding: brand, warehouses, channels, billing rules. Most 3PLs onboard a new merchant in 2 to 4 hours of operator time, including the white-label subdomain.
Month-end goes from days to hours
Billing rolls up live from real ops events. The invoice is ready when the cycle closes. No reconciliation phase. No 'hands' on the spreadsheet.
One platform, no merchant portal to maintain
Your merchants log directly into CCEN's per-merchant surface, branded as yours. You don't build a portal. You don't maintain integrations. The platform is the portal.
App screenshot · Merchant switcher · Cardinal 3PL operator console
28 merchants. Tap a tile to drop into their view. Placeholder image.
Talk to a 3PL specialist.
Bring a current invoice and a recent merchant SLA dispute. We'll show how the same scenario plays out on CCEN.
Tools you'd typically replace
Most 3PLs run a warehouse system plus a billing tool plus a customer portal. CCEN replaces all three with one platform that the merchant logs into directly.
Reference setup
A regional 3PL running 28 merchants and 4 warehouses on CCEN.
We had ShipHero plus a custom billing app plus a Notion portal we'd patched together for merchants. CCEN replaced all three. Our merchants log directly into their own surface. Our invoicing went from a 3-day month-end to two hours.
Common questions from 3PL operators
- Can merchants log into CCEN directly?
- Yes. Each merchant gets a white-labeled subdomain. They see their own orders, inventory, and listings. They cannot see other merchants. They cannot see your operator console.
- Can we customize the merchant surface?
- Yes. Per-merchant theme, logo, custom domain. Hide surfaces you don't want merchants to see. Add custom apps for specific merchant programs.
- How does billing work?
- Billing rules attach to merchant contracts. Picks, packs, storage, special handling, kitting, returns all roll up to invoice line items. Invoices generate on a cadence you set, export to your accounting system, or import directly into QuickBooks or NetSuite.
- Can we run a merchant's DTC store from CCEN?
- Yes. The merchant's full back office is in CCEN. They can run Shopify in front and CCEN behind, or use CCEN as their full operations platform. Your call as the 3PL, your merchant's call on the storefront side.
- What about merchant-owned carrier accounts?
- Supported. Each merchant can attach their own UPS, FedEx, USPS accounts. Rate shopping picks the cheapest qualifying rate from the merchant's accounts plus your overlays.
- Can we onboard a new merchant in a day?
- Yes. Merchant onboarding is a wizard: brand, warehouses, channels, billing rules. Most 3PLs onboard a new merchant in 2 to 4 hours of operator time.
Built for 3PLs and fulfillment. See it run.
A 30-minute call with a real engineer. We connect a sandbox to your Shopify, Amazon, or EDI partner and walk through the workflow you care about. No slides. No discovery deck. The product, on data that looks like yours.