---
type: concept
title: The 16-Module Library
aliases:
  - module library
  - the 16 modules
  - module catalog
  - 12 core + 4 extension
modified: 2026-04-07
tags:
  - modules
  - module-library
  - product-catalog
  - adoption-case
---

# The 16-Module Library

> The 16 modules of SuiteCentral 2.0, decomposed as 12 core operational modules + 4 extension/platform modules, with one-line descriptions from Watch-track narration where available.

## What this page is

A catalog page. The definitive 12-core-plus-4-extension split is from [[sources/22-module-library]] — the authoritative text reference that exists explicitly for AI assistants to read. The one-line descriptions per module come from [[sources/narration-scripts]] where available.

Two modules have their own dedicated wiki pages already — [[pages/modules/context-sidecar|Context Sidecar]] and [[pages/modules/mdm-central|MDM Central]] — because they are named differentiators in [[sources/01-executive-summary]]. The other 14 are catalogued here rather than filed as individual pages, until future ingests surface enough content per module to justify promotion.

## Why it matters (to the adoption case)

The 16-module footprint is one of the pitch's anchor numbers (per [[sources/01-executive-summary]] slide 3 and reinforced by [[sources/22-module-library]]: *"Total library footprint represented in executive/demo flow: 16 modules (12 core + 4 extension/platform)"*). Squire leadership needs to know *what's actually in the 16 modules* — not just the headline count. This page answers that question.

The module set also reveals **the operational scope of SuiteCentral 2.0**: it is not a single-purpose tool but a full operational stack covering contracts, customers, finance, inventory, MDM, payments, portals, quality, service, suppliers, sync, vendor collaboration, and workflow orchestration. That breadth matters for the [[pages/entities/squire|Squire]] transformation thesis — a single consulting firm handling all these operational surfaces across clients cannot scale manually.

## The 12 Core Operational Modules (per [[sources/22-module-library]])

These are the core operational modules — the day-to-day business-function modules that handle a specific operational domain. Numbering follows the source order.

| # | Module | What it does | Watch narration available |
|---|---|---|---|
| 1 | **SupplierCentral** | Manages onboarding, qualification, and ongoing supplier operations. Compliance checks and profile completeness are visible before activation. Reduces onboarding delays and supplier-related disruption. | Yes |
| 2 | **PaymentCentral** | Orchestrates payment initiation, approval, and settlement tracking. Every step is captured with clear status and control checkpoints. High-risk items can be routed through additional review before release. | Yes |
| 3 | **CustomerCentral** | Unifies account records, lifecycle stages, and engagement history. Sales, support, and finance teams share one customer timeline. Operational flags surface risk, service issues, and expansion opportunities early. | Yes |
| 4 | **MDMCentral** → [[pages/modules/mdm-central|full page]] | Golden-record master data management with duplicate detection, merge workflows, and stewardship queues. Built into the core (not sold as a separate product). | Yes |
| 5 | **SyncCentral** | Monitors integration jobs, sync status, and remediation paths. Failures and retries are visible with clear operational context. Improves integration reliability and recovery speed. | Yes |
| 6 | **QualityCentral** | Tracks inspections, defects, and corrective-action workflows. Issues are prioritized with clear ownership and status visibility. Audit signals document what changed, when, and why. | Yes |
| 7 | **PayoutCentral** | Manages disbursement runs and downstream payout visibility. Teams monitor batches, exceptions, and completion status in one flow. Operational controls reduce manual intervention for routine payout cycles. | Yes |
| 8 | **InstallerCentral** | Launches with active installer routing context. Nearby installer candidates are ranked by **proximity, skill, and availability**. Dispatch actions remain governed with audit-ready execution metadata. Live operations can accept, reroute, or escalate assignments in real time. *(Installer network management with proximity-based scheduling, rating systems, and performance tracking per docs/modules/SUITECENTRAL-16-MODULES-DEEP-DIVE.md. Dashboard has Schedule, Technicians, Parts Inventory, Performance tabs.)* | Yes (VTT, not narration-scripts) |
| 9 | **ServiceCentral** | Coordinates service requests, ticket states, and resolution workflows. Teams triage quickly with shared context across customer and operations data. Escalations and handoffs are tracked to protect response commitments. | Yes |
| 10 | **InventoryCentral** | Tracks movement, availability, and fulfillment readiness in real time. Planners see status changes across receiving, picks, and outbound flow. Exception signals help prevent stockouts, delays, and manual fire drills. | Yes |
| 11 | **FinanceCentral** | Reconciliation workflows, controls, and reporting checkpoints. Transaction states are visible across approvals, posting, and exception handling. Teams can spot breaks quickly and resolve issues before close deadlines. | Yes |
| 12 | **ContractCentral** | Manages agreement intake, terms, and renewal milestones. Key obligations and dates are visible before they become revenue or risk issues. Reduces leakage and keeps legal, finance, and operations aligned. | Yes |

## The 4 Extension / Platform Modules (per [[sources/22-module-library]])

These are the extension/platform modules — they either extend the operational stack across all modules (Workflow, Portal), provide external-user surfaces (Vendor Portal), or demonstrate platform-level capability (Context Sidecar).

| # | Module | What it does | Watch narration available |
|---|---|---|---|
| 1 | **WorkflowCentral** | Orchestrates cross-system workflows and automated handoffs. Business rules drive routing, approvals, and exception handling. Teams can monitor each step with transparent status and ownership. | Yes |
| 2 | **PortalCentral** | Shared operational workspace across internal and external users. Requests, updates, and status visibility stay synchronized across teams. Standardized flows reduce ad hoc communication and process drift. | Yes |
| 3 | **Vendor Portal** | Vendor-facing workspace for documents, updates, and status. Shared visibility reduces email churn and back-and-forth coordination. Procurement teams can validate submissions and resolve issues faster. | Yes |
| 4 | **Context Sidecar** (platform demo) → [[pages/modules/context-sidecar|full page]] | Zero-click ERP-embedded intelligence. The killer app of SuiteCentral 2.0. The "platform demo" label signals it is as much a demonstration of platform architecture as a product module. | Yes (both full and highlight variants) |

## Correction notes

**Customer Payment Portal is NOT a module.** It has a Watch-track demo video (`customer-payment-portal-demo.webm`) and a narration entry in [[sources/narration-scripts]], but the authoritative 16-module list in [[sources/22-module-library]] does NOT include it. Conclusion: Customer Payment Portal is a **demonstration of a sub-feature** of CustomerCentral or PaymentCentral (the customer-facing payment experience), not a standalone module. An earlier version of this page incorrectly counted it as module #5; this has been corrected.

**Installer Central narration — RESOLVED 2026-04-07**: the module *does* have a VTT captions file at `public/media/demos/captions/installer-central-proximity.vtt` with 4 cues. The absence from `public/js/narration-scripts.js` just means Installer Central uses the **native HTML5 `<track>` captions path**, not the Web Speech synthesis path that the other modules use. The player's config (line 110 of `public/squire-v2-media-demo/watch/videos/player.html`) explicitly lists its captions file. Narration text:

> "Installer Central launches with active installer routing context. Nearby installer candidates are ranked by proximity, skill, and availability. Dispatch actions remain governed with audit-ready execution metadata. Live operations can accept, reroute, or escalate assignments in real time."

This brings the module count to **16 modules with narration coverage** (15 via narration-scripts.js + 1 via native VTT). No gap.

## Evidence routing patterns (per [[sources/22-module-library]])

Useful structural metadata for how module evidence is organized on the demo site:

- **Dashboard evidence**: module-specific dashboards at `/public/<dashboard-name>.html`
- **Demo video evidence**: canonical URL template `/squire-v2-media-demo/watch/videos/player.html?video=<module-id>`
- **AI Field Mapping live interactive tool**: `/ai-field-mapping-editor.html` (not a demo video — an actual interactive tool)
- **Context Sidecar reviewer proof**: `/squire-v2-media-demo/read/context-sidecar-proof.html` (a Read-track page specifically about Context Sidecar evidence)
- **Context Sidecar raw JSON**: technical proof only, not the primary reviewer path

## Sources

- [[sources/22-module-library]] — authoritative 12-core + 4-extension module list, evidence routing patterns
- [[sources/narration-scripts]] — one-line descriptions per module (15 of 16 modules have narration entries)
- [[sources/01-executive-summary]] — slide 3 "16-module footprint" claim