FAQ
Clear answers about Core, modules, scope and cost.
The important boundaries are explained before implementation, not discovered after launch.
What is Schéma Core?
Schéma Core is the shared foundation for identity, users, permissions, settings, records, security, updates and activated capabilities. It is configured with the first useful solution, not sold as empty software.
Are Retail, Bookings and the other solutions separate systems?
No. They are business-specific configurations of the same Core and module family. This is why capabilities and data can be added without creating six unrelated codebases.
Do I have to buy every module?
No. Only the capabilities required for the agreed workflow are activated. Another module can be added later when it solves a real need.
Can a website work without the Core?
Yes. A simple business can use a standalone Launch, Essential or Business website. The Core becomes relevant when the website needs connected customers, bookings, commerce, inventory, suppliers, jobs or other operations.
Can I edit the site and visible elements myself?
Yes. Page content, images, links and business-controlled design values are editable from WordPress. The complete-element controls expose applicable colour, typography, spacing, border, size and responsive settings. Security, routing and accessibility mechanics remain system-owned.
Who owns and prepares the data?
The business confirms the accuracy and legal use of its data. Schéma structures, validates and imports the agreed material, and records what was imported. Poor or incomplete source data may require additional preparation.
How are POS, fiscal services and payments handled?
Schéma can provide the operational experience and connect the appropriate supported provider route. Regulated fiscal functions, merchant accounts, terminals, provider subscriptions and transaction charges remain separately scoped unless explicitly included.
What is included in the price?
The proposal separates one-time design, configuration, migration, integration, testing and training from recurring hosting, licence, updates, support or usage. Third-party provider and hardware costs are listed separately.
Can we start small and add more later?
Yes. That is the intended architecture. The first phase should be the smallest combination that creates useful operational value without blocking the next step.
When does Schéma AI make sense?
AI makes sense when a defined job, relevant data, review step, expected value and recurring usage are clear. It does not replace missing operational records or human authorisation.
How long does implementation take?
A simple website may take a few weeks. A connected operational system depends on data quality, number of users and locations, integrations, provider approvals, review speed and the complexity of the workflow.
What happens after launch?
The installed system follows the agreed hosting, update, security, backup and support arrangement. Further capabilities are proposed only when they have a clear business reason.
SCHÉMA DIGITAL
Still not sure which route fits?
Tell us the workflow in ordinary language. We will translate it into the smallest useful Schéma architecture.