Eight Modules. One Unified Platform.
Marketing Central is not a collection of loosely coupled tools. It's a coherent platform where every module shares the same identity layer, the same data model, and the same understanding of Liberty's organizational structure. Each module is described in detail below — click through to any for the full spec.
Architecture
How the Platform Is Layered
From the franchisee's browser to Dynamics GP, every request flows through a consistent stack. Authentication is checked first. Access scope is derived from the Admin System. Data lives in Azure. Integrations are first-class, not add-ons.
The Modules
Explore Each Module
Every module is documented in full, including RFP requirements addressed, key capabilities, and technical approach. Use the cards below to navigate.
Franchise Storefront & DAM
Faceted search, product discovery, 1,093-product catalog, US/CAN toggle, fund-eligible filtering.
Design Builder
Live preview, editable-PDF import, locked regions, state disclaimers, print-faithful PDF output.
Commerce & Checkout
Multi-wallet checkout, USD/CAD, carrier-rated shipping, order history, cancellation window.
Fund Management
Zee + MRA ledger, 6 fund states, hard March expiration, freeze controls, 5-year audit trail.
Claims Management
Self-service submission, reviewer workflow, direct-to-AP ACH routing, Canada unification.
Reporting & Dashboards
Role-scoped views, YOY/YTD, scheduled exports, franchisee + corporate dashboards.
Vendor Portal
Product management, pricing, order telemetry, shipping quotes, approval workflow.
Administration & RBAC
Six user roles, Admin System-scoped access, emulation, office lifecycle, audit logging.
Design Philosophy
Why the Modules Integrate, Not Just Coexist
The platform's value isn't in any individual module — it's in what happens at the intersection. A franchisee's Zee Fund balance shows up at checkout because it's the same balance the claims module tracks and the reporting module displays. An admin's scope in the RBAC layer determines what they see in every module, consistently, without per-module configuration. A vendor's order status update reaches the franchisee's order history without any manual intervention.
Shared Identity Layer
Every user action in every module passes through the same authentication and authorization layer. A Marketing user emulating a franchisee sees exactly what that franchisee sees — scoped to their office, their fund balance, their order history — because the same permission check runs regardless of which module is rendering the page.
Shared Data Model
An office record is one object with one ID. When the Admin System updates an office's address, that update propagates everywhere — to the Design Builder's auto-populate fields, to the shipping address on the checkout, to the claims form. No module maintains its own copy of location data that can drift out of sync.