TerraCore adapts to every operation, not the other way around

Two farms in the same town can operate very differently. One lives off cattle, another off crops, and a third mixes both. Each has its foreman, its administrator and people who record data every day.

A system that treats them all the same ends up getting in everyone's way. That is why, at TerraCore, a good part of the product work is not about adding screens but about deciding what each person sees and what they can do.

What an operation sees depends on what it does

Each account has an operation type: livestock, crops or mixed. That setting decides which modules show up in the menu.

• Livestock: sees Animals and Animal health, and does not see Crops.
• Crops: sees Crops, and does not see Animals or Animal health.
• Mixed: sees everything. It is the default.

Only an administrator can change the type, from the subscription section. It is a presentation decision: it adjusts menus and routes so a crop farm does not walk through cattle modules it will never open.

Roles: who records and who administers

In an operation with more than one person holding an account, not everyone needs the same power. TerraCore separates two roles.

The operator does not see the users, sites, finance or subscription sections in the menu. They cannot import CSV files either.

The menu is drawn according to the role, but the server decides whether an action is allowed, checking the role stored in the database on every request.

There is also a small rule that prevents honest mistakes: an operator can reverse or delete an inventory movement only if it is their own and within the following 10 minutes. An administrator can always do it.

Importing what the farm already had

Almost no farm starts from zero: they have spreadsheets with animals, supplies or batches. TerraCore lets you import them from a CSV file, with one template per module.

Import is available for Animals, Crops, Supplies, Production and the vaccination history in Animal health. An administrator runs it, and it works like this:

• The file is read and validated in the browser, with a preview of the first 25 rows.
• Only the valid rows are sent to the server.
• The format is comma-separated CSV, not .xlsx.
• In Animals, Crops and Animal health the import is all or nothing. In Supplies and Production it can be partial.

The Production import never discounts inventory and does not bring prices or costs.

Animal health with dates you can see

Each vaccination record belongs to an animal and carries the dose, the result, the veterinarian and, optionally, the supply used and the quantity discounted from inventory.

The next dose is written by whoever records it, and from there it shows up in the weekly and monthly calendar of the section. It is a reminder that comes from a piece of data someone chose to write down, not from a guess by the system.

Supplies with a minimum that is watched

Each supply has a minimum quantity. On the Supplies screen it shows up as critical when it falls below it, so you see it before the feed runs out.

In-app notices

TerraCore generates notifications and activity for the active administrators and operators of the account. They are notices inside the application: there is no email or phone message channel for them.

Each company sees only its own

Every record belongs to a company, the customer account, and that ownership comes from the session of whoever is asking, never from what travels in the request or in the address. Two farms can use the same platform without mixing their data.

What stays at the center

None of this is about giving TerraCore more options. It is about giving it less noise: each person sees what is theirs and loading data is not a separate job.

When the platform adapts to the operation, the team uses it. And a system that gets used every day is the only one that really leaves reliable data behind.

---