SkinHarmony Site Suite
The WordPress control plane that transforms the site into a live commercial node.
SkinHarmony Site Suite is not a simple plugin, not a page builder, and not a collection of isolated modules. It is the system that organizes the site, offer, B2B CRM, templates, translations, claims, pricing, licenses, Smart Desk, Core, and assisted automations. Its role is to grow a beauty network without losing identity, commercial control, and operational traceability.
WordPress displays and collects. Suite orchestrates. Universal Core decides. Smart Desk executes the center’s operations. Sensitive actions always remain under responsible approval.
Why it exists
The beauty supply chain doesn’t need another website. It needs orchestration.
A brand must protect identity, materials, claims, and pricing. A distributor must activate territories and partners without losing visibility. A franchise must replicate standards, offers, and processes. A center must convert traffic and contacts into relationships, appointments, orders, and continuity. When these levels operate with separate tools, the network becomes slow, fragile, and difficult to control.
Site Suite is designed to connect these levels within a single system: a replicable, controllable commercial foundation adaptable to brands, distributors, partners, centers, e-commerce, and WaaS nodes.
Protects the brand language
Templates, protected terms, claims, CTAs, pages, translations, and materials are not left to individual manual edits. Suite maintains an approved source and makes it reusable in subsequent nodes.
Reduces activation times
Page Factory, template registry, B2B CRM, lead-to-project, onboarding, and operational connectors compress repeatable work. Speed comes from standardization, not from improvised pages.
Connect sales and operations
The site is no longer just a showcase. It becomes a node that collects leads, prepares proposals, organizes requests, protects prices and claims, and forwards only useful information to Smart Desk or the sales network.
Makes the network readable
Each node has status, role, readiness level, license, project, commercial relationship, connections, and next action. Growth is no longer scattered across emails, isolated pages, and disconnected tools.
Technical datasheet
Suite is an application layer on top of WordPress, designed to coordinate commercial nodes.
Product identity
Site Suite is the proprietary layer that transforms WordPress into a commercial Control Room. It is not sold as a universal plugin, but as preconfigured technology for advanced beauty projects, distributor networks, franchising, vertical brands, and WaaS sites.
Operating perimeter
WordPress hosts pages, content, online purchasing, B2B CRM, templates, modules, and configurations. Render hosts connected services as needed: Universal Core, Smart Desk, update server, operational endpoints, and network components.
Data sources
Suite reads WordPress options, meta, products, orders, leads, nodes, licenses, templates, translations, events, and operational states. Sensitive or cross-tenant data must remain separated and go through scope, permissions, audit, and responsible approval.
Controlled outputs
The system produces drafts, pages, templates, reports, translations, claim verifications, proposals, node statuses, keys with defined scope, readiness level, alerts, and suggested actions. Publication and sensitive interventions remain under control.
Architecture
Four separate levels, one unified commercial experience.
WordPress
It is the public and administrative shell: content, pages, e-commerce, leads, modules, templates, light CRM, and commercial area. The client sees a website; Suite treats it as an operational node.
Site Suite
It is the command center: connects modules, controls readiness level, prepares pages, organizes projects, manages nodes, accesses, templates, leads, connectors, translations, pricing, and approved materials.
Universal Core
It is the operational judge: it assesses risk, alignment, automation level, claims, pricing, required confirmations, policies, and next action. It does not replace the owner: it prevents blind decisions.
Smart Desk
It is the operational node of the center. When connected, it receives configurations, keys, plan, modules, brand kit, and authorized perimeter. Suite prepares and governs; Smart Desk works on the center.
Checklist map
The Suite map organizes the system into readable blocks, not scattered functions.
Each block has a precise role: to collect, organize, verify, create, connect, or protect. This is the difference between a platform with orchestration and a set of plugins. Site Suite does not try to do everything in one place: it coordinates the right modules and prevents commercial work from losing order.
Check 01 · Foundation and Control Room
Bootstrap, module registry, administrative menu, system status, configurations, and operational views provide Suite with an orderly base. The owner does not have to search for scattered functions: they see what is active, what is connected, and what requires attention.
Check 02 · B2B CRM and Node 360
Leads, accounts, partners, distributors, projects, follow-ups, and nodes are managed as a commercial lifecycle. A contact does not remain a record: it becomes a program, proposal, relationship, and next action.
Check 03 · Pricing, orders and consistency criteria
Value Chain Pricing, Price Guard, B2B Order Connector, online purchase and order request allow protecting prices, conditions, proposal status and assisted sales. The system must not invent price lists: it uses approved sources.
Check 04 · Template, Page Factory and clone
Template registry, master source, Page Factory and Site Clone serve to replicate pages and sites without losing style, CTA, hierarchy, colors, rhythm and components. The clone must not be an interpretation: it must start from the real source.
Check 05 · Licenses, updates and Smart Desk Connector
The suite manages plans, license state, app key, module gates, grace period and Smart Desk connections. Activation is not a blind switch: it must be tracked, reversible and aligned with the node contract.
Check 06 · Core, translator and Claim Guard
The translator works on protected terms, tone, target language and commercial meaning. Universal Core assesses risk and alignment. Claim Guard prevents content from pushing unauthorized promises or sensitive formulations.
Check 07 · WaaS, analytics and brand governance
Lead Intelligence, events, DAM, approved materials, reputation, upsell and brand governance transform the site into a measurable commercial node. The focus is not only on the page: it observes the behavior of the network.
Check 08 · Onboarding and controlled automations
Project Builder, intake, trial, assisted setup, soft gate and daily automation reduce manual work. Automations prepare, organize and report; sensitive interventions remain under responsible control.
Check 09 · Warehouse, online purchase and settlement
Products, stock, orders, catalogs, fulfillment, barcode and settlement enter the map as controlled surfaces. Where automation is not fully verified, the system maintains reading, preview and manual control.
Check 10 · Nyra, network and readiness level
Nyra makes the status readable: what is ready, what is fragile, what needs verification, where priority is required. Enterprise Health, Control Tower and readiness level are not decoration: they serve to decide where to intervene first.
Check 11 · Tracking, social and conversion stack
Events, attribution, conversions, product card, social channels and tracking serve to understand if the node is really working. The value is not only publishing content, but reading if that content generates action.
Check 12 · Security, release and ownership
Release governance, update server, ownership map, extraction planner, security and audit prevent the platform from growing as an uncontrolled monolith. Every evolution must have an owner, boundary, test, and rollback.
Controlled translator
The language is not just translated. It must preserve the positioning.
The translator connected to Core must not simply move words from one language to another. It must protect terms, tone, commercial promise, claims, CTAs, and the meaning of the source page. For this reason, the Suite works with registers, protected dictionaries, claim control, and checks before publication.
Italian source
The text is created in the native language with a high tone, clear promise, and approved terms.
Multilingual draft
The translation produces an aligned version but does not decide alone what is publishable.
Core control
Core evaluates risk, sensitive terms, claims, alignment, and the need for verification.
Controlled publication
Only content aligned with brand, offer, and boundaries is brought to the site or target node.
Clear roles
Suite does not replace other engines: it coordinates them.
Suite orchestrates
It collects configurations, prepares pages, organizes nodes, connects CRM, templates, modules, connectors, and materials. It is the command center of the site and the WordPress supply chain.
Universal Core evaluates
It decides risk, priorities, confirmations, blocks, readiness level, and allowed automation level. Its role is to prevent fragile, inconsistent, or out-of-scope actions.
Nyra explains
It translates the technical verdict into a useful reading: what to do now, what to postpone, what to verify, and why a step is ready or not.
Codex accelerates
It can create pages, reports, checks, adaptations, and repeatable automations within scope and lock. It does not work ad hoc: it must follow contracts, Core gate, shared memory, and tests.
Who it is for
It is designed for those who need to grow without losing control.
Beauty brand
For companies that need to maintain continuity between website, e-commerce, catalog, materials, claims, channels, partners, and centers. Suite helps replicate identity and process without rebuilding everything from scratch.
Distributors
For networks that need to activate territories, catalogs, leads, proposals, partners, and orders with greater control. The relationship does not remain with a single contact: it becomes a readable commercial node.
Franchising and groups
For those who need to replicate standards, pages, offers, modules, and workflows across multiple points of sale, maintaining a central perimeter on identity, prices, claims, templates, and node status.
Advanced centers
For centers that want more than just a showcase website, but a node connected to leads, agenda, offers, Smart Desk, CRM, approvable automations and commercial continuity.
Safety boundaries
The strength of the Suite also lies in knowing what it should not do alone.
A platform with orchestration is not powerful because it does everything automatically. It is powerful because it distinguishes between repeatable work, assisted action, necessary verification and responsible approval. For this reason, Site Suite must not publish risky claims, change official prices, access customer data, activate payments, modify tenants or synchronize sensitive systems without defined boundaries and approval.
Commercial value
Site Suite makes something difficult sellable: the continuity between website, network, and operations.
The value is not having another WordPress backend. The value is being able to tell a brand, a distributor, or a network: your website will not be an isolated page. It will be a node connected to CRM, approved content, offer, translation, Claim Guard, pricing, templates, Smart Desk, and assisted automations. This enables selling significant setups, WaaS fees, and more complete programs, because the client does not buy just graphics: they buy method, continuity, and control.
Summary
Suite is the orchestration that makes SkinHarmony replicable.
Where a normal website publishes pages, Site Suite builds nodes. Where a plugin adds functions, Suite maintains orchestration. Where automation risks running uncontrolled, Core and Nyra restore order, risk management, priorities, and responsible approval. This is the difference between creating a website and building a commercial platform for the beauty supply chain.