THE KEY IDEA
A demo lets you explore the experience. A real implementation adds each business's rules, access and operating conditions.
The demo helps define what you need
A prototype lets you test screens and discuss everyday work. You can register a product, move a task or prepare a quote with fictional information. This makes it easier to identify necessary features before commissioning an implementation.
Altum's public demonstrations keep examples in the browser. They do not share information among employees and should not be used as a business's primary records. This limit lets you explore without entering real customer data.
Adapting a foundation has different levels
Logo, colors, copy and catalog data can be configured when operations are similar. Changing inventory rules, adding branches or connecting invoicing requires additional work.
| Part of the project | What is defined |
|---|---|
| Identity | Brand, contact, language and authorized assets |
| Operations | Statuses, owners, exceptions and rules |
| Data | Fields, import, retention and quality |
| Access | Users and allowed actions by role |
| Integrations | Providers, costs and failure handling |
| Delivery | Testing, documentation and agreed maintenance |
The scope should distinguish these parts so the business knows what it is commissioning.
Permissions are checked on the server
Hiding a button does not prevent an operation by itself. A private application must check who makes the request and what data they can access. It also needs to separate each client's information when a product foundation serves multiple businesses.
Before launch, test unauthorized users, other people's records and simultaneous changes. In practice, two people may edit the same order; the system must detect the conflict or apply a defined rule, avoiding silent overwrites.
Preparing data includes being able to recover it
An import should start with a small, reviewable sample. Agree on required fields, how duplicates are corrected and who authorizes the result.
Backups need a policy and a restoration test. A saved file is not enough if nobody knows how to restore it or it does not contain the expected information. Frequency and retention are defined according to operations and the contracted service.
Deliverables must be verifiable
Prepare a list of journeys: create, view, correct, cancel and export. Also check errors and recovery. The business should receive access, instructions and clear support terms.
You can try Altum Soporte to understand a service journey and review its specifications. To learn about the foundation of this website, see how Altum is built.
Make it concrete in your business.
Choose a path to continue exploring what you just read.
Explore service: Databases ↗Try Altum Soporte →