A-Z Glossary

Opened by selecting a cow from the alerts or from the ranking: her liters over the period, one point per milking, next to her quality tests for the same days. Seeing both together is the point — a drop in liters next to a rising somatic cell count tells a different story than the same drop on its own.

From a sale's detail, every line links to the batch it sold and that batch's already-existing traceability tree: which milk pools the batch consumed, which milking session each pool came from, and which cows contributed those liters. Selling does not create new traceability — it reuses exactly what the batch already had since it was produced.

Loss of the pregnancy before calving. The cow returns to the "open" status.

The period the animal was not on the farm: from which day to which day, for what reason and to what destination. It is the real fact behind everything else. An animal can have several absences over its life, but only one open at a time: until the return is registered, no new departure can be registered for it.

An external role for whoever keeps the books. Looks at Finance, Sales and every report, and records and edits expenses and other income. Cannot create or edit a sale, and records nothing in the herd, milking or cheesemaking.

An informational plan line, with no quantity, no inventory draw and no cost — for forage or pasture that's always available and not worth measuring serving by serving. It shows up on the plan as a reminder, but takes no part in the milking-grid suggestion or in daily consumption.

A manual correction to stock, always with a reason: loss, expired, damage, correction or other. It is signed: negative when product was lost, spilled or discarded, positive when there turned out to be more than the system said. It is the tool for making the inventory match what is actually on the shelf. The balance an item starts with is also an adjustment, with the "Initial stock" reason.

How far ahead each alert appears: calvings at 60/30/7 days, dry-off ~14 days ahead, and heats when they are due.

An animal is sold from its record, by registering its departure with the reason "Sold": the modal asks for the buyer (a customer or an occasional sale), the amount and, optionally, the weight. That creates a real sale with an animal line, which shows in Sales, in the profit and loss ("Animals" row), in the cash flow and in that animal's profitability.

The animals list shows, by default, only the ones that are on the farm today. Those that left are not deleted: they are hidden. A note under the list says how many animals are hidden, so the herd never looks smaller than it is without an explanation.

Cancels a mistaken service or event. Annulling a service also annuls the events linked to it (a pregnancy check on a service that never happened means nothing) and returns any semen straw it drew to stock. Either way, Mi Finca recomputes the female’s reproductive and lactation status — and every service’s outcome — from what remains, so the record is never left pointing at a fact that no longer exists.

Cancels a health event recorded by mistake. Mi Finca recomputes the animal’s health status from the events that remain active and, if the event carried a treatment, releases the inventory it had reserved.

Breeding via semen (straw) applied by a technician, without a direct mount. The semen source is recorded as the sire.

Next to each pending item on the home (calvings, dry-offs, heats, health, withdrawals, inventory) the owner and the manager have an “Assign” button. It opens the task form already filled with the item’s title, animal and date: only the assignee is left to pick before saving. The task remembers where it came from and shows a shortcut to the record that closes it, such as “Record calving” or “Go to inventory”.

Conversation panel that answers with your farm's real data. For every question it looks up the records it needs, and it always tells you which period the answer covers.

There is no save button. Each box saves itself when you press Enter or leave it, and says where it stands: saving, saved with a check, or the reason it was refused in plain words — retype the number and it tries again. Clearing a box is not a delete: an empty box simply has nothing to say about that cow and that shift.

Price per liter of milk and per kilo of cheese. They serve as suggested values in sales and financial reports.

From a batch's detail page you can open its reverse-traceability tree: which milk pools it consumed, which milking session each pool came from, and which cows contributed those liters — with each cow's real milked amount, never split proportionally between animals. An annulled batch keeps its trace even though its pools no longer show as active.

A 1 to 5 scale in steps of 0.25 (1 = emaciated, 5 = obese) that estimates an animal’s fat reserves by sight and touch. It is recorded with a date because what matters is the trend: a cow losing condition after calving is an early warning. It is a record only — it does not generate automatic alerts.

Farm logo and primary color. The logo shows up on the dashboard home, next to the greeting; the color tints buttons and links. On buttons and chips the system always picks whichever text color (white or black) reads better on your color; when the color is used as text or as a link on a light background and falls short of 4.5:1 against white, the preview shows a warning, but you can still save it.

Birth of the calf. The cow starts lactating and her reproductive status returns to "open".

Average number of days between consecutive calvings of the same cow. The herd figure averages the intervals whose most recent calving falls in the last 12 months. The shorter it is, the more efficient the reproduction.

The grid is built to be filled without touching the mouse: type the liters, press Enter, type the next cow. Thirty cows in one shift should take a few minutes and one hand — the other one is usually busy.

Inflows (cheese, milk and animal sales, and other income) and outflows (inventory purchases, animal purchases and expenses) by period, with a running balance that starts from the range's first period. It is a simplified cash approximation: a sale counts on the day it was sold, a purchase on its movement day and an expense on its own date — the system does not yet know whether a sale has been paid.

One concrete production run of a product, identified by a batch number (date + that day's sequence). It starts by consuming one or more milk pools and the recipe's ingredients, and it closes by weighing the cheese that actually came out — that weigh-in is what makes it "ready" (`READY`) and triggers the stock movement. A batch's product can never be changed once it is created.

The dedicated record for what gets used up making cheese: rennet, cultures, salt, calcium chloride, packaging and plant detergents. You give it a name, a type, the unit stock is kept in and, if you want them, a minimum for the low-stock warning and the quantity already on hand. From there it lives in the same inventory as everything else: purchases with supplier, price, lot number and expiry date, adjustments with a reason, movement history, average cost, and low-stock and expiry alerts. The unit is the stock unit — three bottles of 100 ml go in as 300 ml — and it locks as soon as the input has movements, because changing it would leave everything already recorded meaningless. The Cheesemaking tab puts cheese inputs on top and general supplies below (plus medications, when the area holds any), so whatever was already recorded as a general supply stays where it is and does not need moving. Automatic deduction when a cheese batch is recorded arrives with the cheesemaking module.

The cheeses the farm produces (fresh, semi-hard). It will feed the product catalog.

Four views derived from weighed batches: real yield against the recipe's expected yield, production grouped by day/week/month, cost per kilogram (null-honest — one batch with an unpriced ingredient leaves the whole product's cost blank, never a made-up number), and the merma trend, always signed, never clamped.

Closing a session needs at least one entry; it creates the milk pools and locks the entries against further changes. Reopening undoes that: it deletes the pools the close created and returns the session to open, so entries can be corrected and the session closed again — the same replay-the-mistake philosophy used elsewhere in Mi Finca, nothing about a wrong close is unrecoverable. Reopening is not possible once a cheese batch used milk from that milking or a sale sold milk from it: that batch or that sale has to be corrected or deleted first.

Each column header carries its shift’s state — no session yet, open, or closed — its total, and the action that goes with it: Close while it is open, Reopen once it is closed. A closed column is read-only: the boxes stop taking liters, because that milk is already pooled by destination. Correcting it is the same as always — reopen from the header, fix the numbers, close again.

While the animal is away from the farm — for any reason, transferred and lost included — its record is fully closed: everything can be seen, nothing can be changed and nothing can be added. No details, no records, no photos, no genealogy, no medication. Not even records dated before the departure. The only things you can do are register the return or undo the departure, and either one reopens the whole record.

Of the breeding services resolved in the last 12 months, the share that led to conception. A female counts as conceived if she became pregnant at any point (pregnant, calved or even aborted); only "not pregnant" counts as failed, and services still awaiting confirmation are excluded. Formula: conceived ÷ (conceived + failed).

The unit the item is actually used in, and the unit all stock is kept in. If you buy 3 bottles of 100 ml, 300 ml go in, not 3 bottles. That way a 15 ml dose comes straight off the stock, with no conversions and no thinking about half-used containers.

An outgoing movement that comes out of the day’s work: it is created when a health event — treatment, vaccination, deworming, or a disease with treatment — is recorded with a medication from the catalog. The form shows "Deduct from inventory" with a quantity already proposed, the suggested dose times the duration in days, and all of it stays editable: you can raise it, lower it, type zero or clear the field, and in those last two cases nothing is deducted. Below it, the lot expiring soonest is proposed (FEFO), with its date and how much is left; you can pick another lot or leave it as "No lot assigned". If the medication was typed by hand, outside the catalog, there is nothing to deduct from and the form invites you to pick one from the catalog. If the quantity leaves stock negative a warning appears, but the event is saved all the same: health records are never blocked by inventory. Annulling the health event releases its consumption and the stock comes back. Marking a due protocol as applied with one click deducts nothing, because no quantity or lot is asked for there: if the deduction matters, record the full vaccination instead.

How much one container of an item holds, in its stock unit: 100 if you buy 100 ml bottles, 500 if the rennet comes in 500 ml bottles. It is optional and is entered on the record of a general supply, a cheese input or a medication — for a medication it is counted in the dose unit, its stock unit, so that unit has to be entered first, or the record warns "Enter the dose unit first: the content per container is counted in it." and refuses to save the record. When it is saved, the purchase opens by container: the "Buy by the container" switch is on, you type how many containers and the price per container, and Mi Finca shows the total live and, once a price is typed, the price per unit, before saving (2 bottles of 100 ml at ₡1,000 each go in as 200 ml at ₡10.00 per ml). The content is editable inside the purchase itself, and an item without one can be bought by container too: type what one holds and leave "Save as the usual content" ticked, as it comes, so the next purchase opens ready. Turning the switch off sends the purchase back to asking for the quantity and the total paid, for whatever arrives loose. Stock, average cost and deductions stay in the stock unit, and so does the initial quantity when the record is created; the content can be changed at any time, because it only describes how the next purchase arrives. Correcting a purchase offers the same two ways, opening by container when the quantity is a whole number of containers. Feed does the same with kilograms per sack; semen straws have no container, the straw is the unit.

Two reports over the same period, grouped by day, week or month: feed cost (per nutritional group, with cost per head-day and a per-feed breakdown) and feed efficiency (liters of milk produced per kilogram of feed consumed, lactating cows only). Both are computed from daily consumption already registered, never from the milking-grid suggestion.

Only people with the finance permission (owner, manager, viewer and accountant) see costs. Without it they disappear from the screen: inventory average cost and purchase prices, the Valuation and Reports tabs of Purchases, feed and cheese costs, and an animal’s purchase price. Sale prices are not costs and stay visible. Without the permission you also cannot change the origin of an animal that has a purchase price recorded: Mi Finca refuses it so a price you cannot see is never erased, and someone with the finance permission makes the change.

Currency for the farm’s prices: Costa Rican colón (CRC) or US dollar (USD).

A saved buyer with a name, phone, email and optional notes — the name cannot repeat within the same farm (case-insensitive). A customer can be deactivated once they stop buying without losing the history of their past sales, and reactivated later if they come back.

The real record of what a group or an animal ate on a day — per individual cow for lactating and pre-calving, per whole group (with the headcount present captured) for calves, heifers and dry cows. Saving a consumption draws each feed down from inventory; the "Prefill" button fills the form with the suggested ration from the active plan, editable before saving.

Every day, at the hour you choose in the Operations tab (5:00 farm time by default), Mi Finca e-mails what is pending today: calvings, dry-offs, heats, health tasks, milk withdrawals, inventory alerts and production drops. You choose which sections it carries; each person only sees the ones their role allows, and on a day with nothing pending nothing is sent.

The female that was served; mother of the future offspring.

While the animal is away nothing can be added, whatever the date: not even a record dated from when it was still here (see "Closed record"). When the animal is on the farm, no record can be dated on a day it was not here. Entering last month’s treatment today, back when the cow was here, is normal and allowed; dating one into the months she spent on another farm before coming back is not.

The milking screen is one worksheet per day: a row per cow, a column per shift, and a box for the liters where the two cross. You pick the date and the whole day is in front of you — nothing to choose beforehand, nothing to open. The rows are the cows that can be milked that day (lactating, present on the farm, not frozen); the columns are the shifts the farm milks, plus any shift that already has milk recorded that day, plus any column you add by hand. At the bottom the day’s total and, separately, how many of those liters are withheld.

Each person on the team asks for days off from Team → Time off with “Request time off”: first and last day, type (day off, vacation or other) and an optional note. The request stays Pending until the owner or a manager approves or rejects it, with an optional reply. The owner and the manager can also record an absence directly for anyone on the team with “Record absence”, approved on the spot, even for a day already gone. Whoever asked can cancel their request while it is still pending; the owner and the manager can cancel any. If a task is later assigned to that person on an approved day off, the app warns before the form closes.

Days from a calving to the first subsequent service that achieved conception. Cows still awaiting a successful service (open cycles) are excluded; the herd figure averages the completed cycles whose calving falls in the last 12 months.

Two different departures that often get logged the same way, and should not be. Death is a loss the farm suffered: the animal died and nobody decided it. Slaughter is a management decision: the animal was slaughtered, almost always for meat. Choosing correctly is not paperwork — mortality is a health alarm, and slaughter is a plan.

The day the animal stopped being on the farm. It is registered from the animal’s record with the "Register departure" button, giving the date, the reason and — optionally — where it went and a note. The record is not deleted: the animal simply stops counting as present and its history stays complete.

Why the animal left the farm. It is a single fact, not two: the reason is also the status the animal ends up in. There are six options, and whether the animal can come back depends on which one you pick.

Periodic antiparasitic control derived from the deworming protocol’s recurrence interval: from the last recorded deworming, Mi Finca computes when the next one is due.

Official Individual Identification Device (DIIO): the animal’s official identifier for traceability. It is optional but recommended, and it cannot repeat within the same farm.

Every DIIO the animal has carried, newest first: the previous number, the new one, the date it changed, and which SENASA form drove the change — or "Manual change" when it was typed by hand on the animal's own form. It is append-only: a row is never edited or removed, even when a tag change is later reversed by another one.

Marking a health event as resolved. On discharge, Mi Finca recomputes the animal’s health status from the events that remain active.

A medication’s dose rate per kilogram of body weight, used to suggest a dose from the animal’s current weight. The suggestion is editable and not authoritative.

A warning for a cow whose milk has stayed below her own normal for several days in a row — not against the herd’s average, against her own history. Two rules keep it from crying wolf: a day she wasn’t milked is skipped, never counted as zero, so a quiet Sunday or a dry-off never sets it off; and one bad day is never enough — every day of the recent stretch has to be down for the alert to fire. The days-sustained number shown is the whole streak, however long it has run, not just the minimum the alert needed. A cow with too little history behind her is left out — there’s nothing yet to compare her against. When her somatic cell count has also been high over the same stretch, a small chip points at her quality tests — a nudge to go look, not a diagnosis. How sensitive the alert is — what counts as a drop, and for how many days — is set per farm in Settings → Production; left blank, it defaults to a 25% drop held for 3 days.

Not being milked. The "dry-off" before calving (the final ~60 days of gestation) is the typical case: pregnant and dry at the same time.

End of lactation, typically ~60 days before the expected calving, so the cow rests before giving birth.

60 days before the expected calving: the date when a lactating cow should be dried off so she rests before giving birth.

Visible number that identifies the animal in the field. Mi Finca can generate it automatically (H- for females, M- for males).

Corrects a detail on an already-recorded service or event: its date and notes, and — for a service — the sire breed, semen code, genetic house, straw or technician; a calving also allows fixing the outcome and offspring count. What a row actually was (its type, the sire, the check result, which service an event belongs to) cannot be edited in place — that is undone with Annul and recorded again. Moving a date is only accepted when the corrected order of events still makes sense, and the female’s status is recomputed right after.

Editing a sale's items annuls its previous stock movements (and the liters its milk lines took from their pools) and creates new ones from the corrected data — stock ends up exactly as if the original sale had never moved those kilograms. Deleting a sale annuls all of its movements and gives the stock back to the batches and the liters back to the milk pools involved; the sale disappears from the list, but the record is kept for the audit trail.

One cow’s liters within a session: the animal and the quantity given. Only lactating cows present on the farm that day can receive one, and there is at most one entry per cow per session — recording a new amount for the same cow replaces the previous one rather than adding a second row. Milk withdrawal never blocks an entry: an animal under withdrawal is milked and recorded like any other, only her destination changes when the session closes.

Corrects a departure and a return that were logged by mistake, when the animal in fact never left the farm. Unlike "Undo departure", which only reaches the currently open departure, this erases any already-closed trip from the absence history: the row disappears and any records that had been blocked for falling inside those dates are accepted again.

Computed date: service date + gestation length for the species. It is the date that drives the calving alert on the calendar.

A cost the system can't capture on its own from another module — labor, utilities, outside vet, maintenance, rent, taxes, transport or other — with a category, amount, date, an optional supplier and notes. It can be deactivated when it was entered by mistake and reactivated later; it is never fully deleted.

Eight fixed categories — labor, utilities, veterinary, maintenance, rent, taxes, transport and other — that group expenses in the P&L: every category with expenses in the period shows up as its own line, never mixed with another.

A warning about lots expiring within the next 30 days, and about lots that already expired. It is only raised while the lot still has quantity left: a lot that has been fully used up stops showing, even once its date passes. It depends on the purchase having been recorded with a lot and an expiry date.

Seven days before a member's access ends, Mi Finca e-mails them, and also the owner and managers, so it can be extended if needed. If you change the date, a new notice goes out for the new date.

Downloading the report on screen as a file, in one of three formats. PDF: a branded document, ready to print or share, with the charts included as an image and "Page n of N" numbering. Excel: a workbook with a Summary sheet and one sheet per table, with the header row frozen, filters, and number, currency, percent and date formats already applied. CSV: plain text separated by semicolons, which Excel opens in columns with no extra steps. The file is named after the farm, the report and the period — for example mi-finca_finca-san-luis_milk-production_2026-08-01_2026-08-31.pdf — and everything is built in the browser, without sending the data anywhere.

Where the number came from: the farm’s own meter or paddle test, or a laboratory. Choosing lab lets you write down which laboratory, so months later a result can be traced back to the report it came in. A farm reading carries no lab name — if you have one to write, the source is a lab.

Six roles. There is only one owner, and it is not assigned from the farm: the Mi Finca team transfers ownership. The owner and the manager assign the other five, except that only the owner appoints another manager.

The two solids, each written as a percentage of the milk. They are what becomes cheese: the same liters with more fat and protein give more kilos in the vat, which is why they belong next to the liters and not in a drawer. They move with the feed, the stage of lactation and the season.

The dedicated record for feed and forage, in seven types: concentrate, forage, silage, hay, mineral, supplement, and a catch-all "other" for anything that does not fit those. You give it a name, a type, the unit stock is kept in (normally kilograms) and, if you want them, a minimum for the low-stock warning and the quantity already on hand. From there it lives in the same inventory as everything else: purchases with supplier, price, lot number and expiry date, adjustments with a reason, movement history, average cost, and low-stock and expiry alerts — concentrate and minerals can expire, hay usually does not, so the fields stay optional either way. What is particular to feed is buying it by the sack: set how many kilograms a sack holds and the purchase opens by the sack — you type how many sacks and the price per sack, and Mi Finca works out the kilograms and the cost per kilogram for you (3 sacks of 46 kg at ₡16,100 a sack come in as 138 kg at ₡350/kg; half a sack is fine too). A loose top-up bought without a sack still fits — a switch takes the purchase back to entering kilograms and the total paid directly — and the sack size can be changed at any time, because it only describes how the next purchase arrives, not the movements already recorded. The unit itself is different: it is the stock unit, and it locks as soon as the feed has movements, for the same reason as every other typed item — changing it would leave everything already recorded meaningless. The Feeding tab puts feed on top and the rest of the supplies below; the other areas show it too, once one is actually filed there, because a mineral block or a recovery ration is sometimes bought against a different area. Consumption deductions from a nutrition plan arrive with a future module.

A nutritional group's feeding recipe: one or more ration lines, each with a feed and a ration type. Only one plan can be active per nutritional group at a time — changing a group's formula means editing its active plan, not creating a new one alongside it.

The rule Mi Finca uses to decide which lot the consumption comes out of: the one that expires soonest, even if it arrived later. That way whatever is closest to expiring gets used first and less product is thrown away. Lots with no expiry date are used last.

When an animal already exists, the form can fill an empty field (breed, for example) or correct a different one (birth date, for example). Filling in comes pre-checked; correcting comes unchecked and you decide, row by row.

Viewing expenses, other income, P&L, cash and profitability requires the finance read permission; creating or editing expenses and other income additionally requires the write permission. The Viewer only looks; Owner, Manager and Accountant can also register and edit expenses and other income. The Worker and the Veterinarian do not see Finance (see Team and roles). Selling an animal when it leaves additionally requires the sales write permission.

A signed movement log per batch, separate from the general supplies inventory because finished cheese has no supplier, no per-batch expiry, no purchase price. A batch's stock is simply the sum of its active movements — never a number stored on its own — and a product's stock is the sum of its batches. Closing a batch creates its own production movement with the weighed kilograms; nobody writes it down by hand.

A fixed amount of feed per head per day, no matter how much milk the animal gives or doesn't — the simplest ration shape, typical for calves or a pre-calving plan.

Bulk animal loading from the TrazarAgro Form 03 PDF (SENASA) for large herds; a scan or a photo does not work.

Record of the animal’s mother and father. Mi Finca validates that there are no cycles (an animal cannot be its own ancestor) and draws the family tree. A parent that has left the farm still shows up; one that was never here is noted by its DIIO.

Gross margin is revenue minus feed, health and cheese inputs — it deliberately leaves out other supplies and expenses, to show how well sales cover the direct costs of producing. Net result subtracts everything: the four cost lines, animal purchases and total expenses. Both show as "—" when any line that feeds into them has no price.

The operational view of all upcoming or overdue preventive care: vaccinations, dewormings, withdrawal-period ends and post-op follow-ups, per animal and herd-wide.

Any recorded veterinary event on an animal: vaccination, treatment, disease, deworming, surgery or checkup. Together, the events form the animal’s health timeline.

A reusable per-farm preventive plan: what is applied (vaccine, dewormer, vitamin, mineral or other), for which species, at what age the first dose goes, and how often it is boosted. Mi Finca compares each protocol against the animal’s history to compute what is due. A new protocol applies from the day it is created: an animal already past the first-dose age is due that same day, not overdue since its birth. Protocols are configured per farm in the farm settings. A protocol can also carry the catalog medication it gives and the dose per animal, in the medication’s stock unit; the dose is required when there is a medication.

The animal’s health situation: healthy, sick, under treatment or in quarantine. The upcoming health modules will update it automatically.

A bar chart of the whole herd’s liters over the period, one bar per day, week or month depending on how it’s grouped. Each bar also breaks down where that milk went — cheese, direct sale, self-consumption, calves, discarded for withholding — for the days already closed; a day still open shows its liters with no breakdown yet, because nobody has decided where that milk goes. A day nobody milked shows as an empty bar, not a gap, so a quiet Sunday reads as quiet, not as missing data.

Rennet, salt and the rest of the recipe's ingredients are drawn from the general cheese-input inventory when the batch is saved. Unlike milk, this draw never blocks: if the ingredient's stock goes negative it is a discrepancy to fix with a purchase or an adjustment, not a reason to stop production — the same doctrine as the rest of the farm's inventory.

Today’s quantity of each supply, feed, medication or straw, recorded as an inventory adjustment dated today, with no historical purchases.

In per-product and per-batch profitability, the cost of what was actually sold — the product's average cost per kilogram times the kilograms sold, never the cost of everything produced in the period. Own milk enters the cheese at zero cost (owner decision): a batch's input cost only counts what was purchased — rennet, cultures, salt, packaging — never the milk.

A card on the home dashboard mirroring the health-alerts card, so the farm sees the store room’s warnings the moment it opens the app rather than after clicking into an area. It watches every area at once and shows up to five alerts — low stock, an expiring lot, an expired lot — the most urgent first, with a link to Inventory when there are more. A store room with nothing to warn about shows a plain "no alerts" line instead of a blank card.

The seven areas the farm’s supplies are grouped into: Reproduction, Milking hygiene, Health, Cheesemaking, Feeding, Pasture and Operations. The area reflects how the item is bought and used day to day, and it decides which tab the item shows up in. It is independent of the kind of record the item has underneath: a synchronisation hormone is a medication but it is bought for Reproduction, and a syringe is bought for Health without being a medication. Every area tab shows its medications in their own section when it has any — Health always, the other areas only when they hold some, such as the hormones in Reproduction — and the same goes for cheese inputs, which Cheesemaking always shows, for semen straws, which Reproduction always shows, and for feed, which Feeding always shows; in the other areas those sections only appear when they hold something. The rest of the general supplies sit below those sections.

What the store room is worth right now: every item that still has stock, valued at its weighted average cost, with a subtotal per area and a grand total. An item whose purchases never carried a price is still listed — with its stock, because that much is certain — but shows a "No data" dash instead of a value, and that dash never gets counted as a zero in the totals. Only items with stock above zero appear; there is nothing to value in an empty or negative balance. It requires the finance permission; without it the tab does not appear, and neither do the costs in the tables.

Asks for the e-mail, the name, the role and, if you want, a last day of access. Mi Finca creates the account in the farm’s organization and sends an e-mail with the sign-in link. If the e-mail does not go out (the farm has no e-mail configured, or sending failed), the invitation is still created and the dialog shows the invitation text with a button to copy it and send it over WhatsApp or any other channel.

AI-assisted reading of a medication label: up to 3 photos (front, back, insert) and the system proposes the commercial name, active ingredient, presentation, route, per-kg dose and milk and meat withdrawal days. The proposal fills the catalog form and stays editable throughout: nothing is saved until the user confirms. Anything unreadable is left empty and flagged — never filled in with a typical value. When the label states its dose per animal instead of per kilogram ("Cattle: 10–25 mL"), that instruction cannot fill the per-kg dose field, but it is not lost: it is copied verbatim into the record’s notes, prefixed "Dose as printed on the label:"; the unit (mL, mg) does fill in on its own. The container’s net content ("100 mL") also proposes the initial quantity — or the first purchase’s quantity, when the label carried a lot — always editable, because the label cannot know how many containers were bought. If the label carried a lot number and expiry date, saving the record makes Mi Finca offer to register that lot as the first purchase, prefilled with those details, so it enters stock; if an initial quantity was entered on the record, the offer is skipped, to avoid counting the same stock twice.

An optional expiry per member. You pick the last day with access in the farm’s calendar: the person works all of that day and, from the following midnight, loses access on their next request, with nothing scheduled. The list shows them as Expired. To give access back, edit the member and pick a new day or tap “Remove expiry”. A reminder e-mail goes out seven days beforehand (see “Expiry notice”). Automatic removal from the Kinde organization at expiry comes later.

Legal name, corporate ID, registration number and date, contact email and phone. The registration date cannot be in the future. They will be used in reports and invoicing.

The animal’s status on the farm: active, sold, dead, slaughtered, transferred, lost or other. It is not edited by hand: it comes from the last departure registered. See the "Departures and returns" section.

Classification by age and lactation: calf (young), heifer (growing) and cow (adult). A female that has already calved and is milking counts as a cow regardless of age.

A warning raised when an item’s stock falls to its minimum or below. It is only raised for items that define a minimum: if the item has none, it never warns. The minimum is set when creating or editing the item, and it is worth revisiting whenever the rate of consumption changes.

The image that represents the animal in lists and in the family tree. It is chosen from the animal’s photo gallery.

Records that an animal received the protocol dose it was due, on the date given (today by default). When the protocol carries a medication, the form brings the medication, the dose per animal and the lot that expires first, all editable: saving records the treatment with the catalog withdrawal days, draws that amount from inventory and, when the medication has a milk withdrawal, puts the animal on withdrawal just like a manual treatment. An amount above the stock is warned about, never blocked: the stock goes negative until the purchase is recorded. It can also be recorded without a medication, and then inventory is not touched. The next dose is counted from this date.

Analogous to the milk withdrawal, but for meat: the time after the treatment ends during which the animal must not be sent to slaughter.

A per-farm catalog of medications: commercial name, active ingredient, presentation, default route, per-kg dose, and default milk and meat withdrawal days. It is also an inventory item like any other: it has an area (Health by default, though a synchronisation hormone is better filed under Reproduction), stock, average cost, purchases with lot number and expiry date, and a low-stock threshold. When creating one you can enter the initial quantity already on hand; that opening balance carries no price, so the average cost stays "no data" until the first priced purchase. The dose unit is also the unit stock is kept in — a 15 ml dose takes 15 ml off the shelf — which is why it locks as soon as the medication has movements recorded. Selecting one in a treatment preloads its data, which stays editable.

Who gets into the farm, with which role and until when: the owner and the manager invite, change the role or the last day of access, and remove access. The details are in Team and roles.

The list of the farm’s people: the owner first, then every member with their role, who invited them and when, and the last day they have access. Each person has a status: Active, Expired (their last day of access has passed) or Invitation pending (they have never signed in). Only the owner and the manager see it; your own card is marked “(you)” and has no actions.

Where the milk goes by default: cheese, direct sale, own consumption, calves or mixed. The milking module will use it to pre-assign production.

A sale line can be cheese or milk: each line's "Type" select decides. A milk line sells liters from a direct-sale pool — the milk set aside with that destination when a milking was closed — picked in "Milk pool" (each option shows the day, the shift and the liters it has left), and carries liters and a price per liter. Only pools of milkings closed and dated within the 7 days before the sale, inclusive, show up; selling draws the pool down exactly as a cheese batch consumes it, and a sale can never ask for more liters than the pool has left.

The result of closing a session: the entries’ liters grouped into one row per destination — cheese, direct sale, self-consumption, calves, mixed, or discarded for withdrawal. With no explicit split, the sellable liters go into a single pool at the farm’s default milk destination; splitting divides them across several destinations instead, and the split must add up to the sellable total. Pools are where cheesemaking draws its milk (cheese destination) and where Sales sells from (direct-sale destination): a direct-sale pool’s card shows how many liters were sold and how many are left.

A batch draws its liters from one or more milk pools closed that same day (or earlier). Unlike ingredients, this draw is rejected if it asks for more liters than the pool has left — they are physical, weighed-at-milking liters, and there is no way for extra to appear from nowhere. Reopening a milking session already consumed by a batch is also rejected, until the batch stops using it.

In per-cow profitability, each animal contributes liters × the price per liter configured in Settings → Production — the same price the raw milk would sell for, never made up. Without that price configured, the table cannot compute any animal's value and shows a notice to configure it.

The time after a treatment during which the animal’s milk must NOT enter the tank. It runs from the last dose (treatment end) plus the drug’s withdrawal days; while active, the animal is "not fit for milking".

The cow is being milked. It is independent of the reproductive status: for most of the gestation the cow keeps being milked.

Who milks each of the farm’s configured shifts, day by day, one week at a time. The template says who milks on each weekday and repeats every week (grey); an exception changes a single date (coloured) and “Back to the template” removes it. The owner and the manager edit it; the rest of the team reads it. If someone on the roster has an approved day off that day, they show with a warning mark: the app does not take them off the shift, the owner decides. The milking screen says “Milking today” with the names on each of today’s shifts.

The times of day when milking happens (HH:mm format). There cannot be more of them than the configured milkings per day.

The container for one shift’s milking: one per farm, date and shift. It opens empty and collects one entry per cow as they are milked. It starts "open" and, once every cow is recorded, is closed — closing is what turns the entries into milk pools by destination. A session cannot be dated in the future.

How many times milking happens per day (0-10). It limits how many milking schedules you can register.

A twelve-month bar chart comparing what came in against what went out: purchases (quantity × unit price, summed per calendar month) against consumption, both in the farm’s currency. Consumption has no price of its own — a treatment or a cheese make records a quantity, not a cost — so it is valued at the item’s current weighted average cost, the same number the valuation table shows today. That is a deliberate approximation: an item bought cheap in January and consumed in August is still valued at today’s average, not January’s price. Exact month-by-month costing of what was actually consumed is a bridge to Hito 10 (Finance), not something this report promises. It requires the finance permission; without it the Reports tab does not appear.

A card on the home with the tasks due for you today and any overdue ones still open, each with its box to mark it done. It only shows when you have something assigned. The daily digest carries the same in its “Team tasks” section; for the owner and the manager it also says how many tasks of other members are overdue. A worker gets the daily digest only if the owner or a manager switched it on for them in Settings → Members.

Breeding performed directly by a bull. The bull is recorded as the sire of the potential offspring.

Records that a cow was deliberately not milked in that shift — drying off, low yield, a treatment — with an optional free-text reason. It is not a zero-litre entry: it adds nothing to production, stays out of the cow’s averages, and never triggers the production-drop alert, which exists to warn about mastitis rather than about a planned dry-off. Marking her also pre-ticks the skip box on her suggested feed, since a cow that did not come through the parlour did not get her ration there either; untick it if she was fed anyway. Recording litres for her afterwards undoes the mark, and removing the mark makes her available again.

Viewing plans, consumption and reports requires the nutrition read permission; creating or editing plans and registering consumption (by hand or from milking) additionally requires the write permission. The Viewer and Veterinarian roles can only look; Owner, Manager and Worker can also register and edit. The Accountant does not see Nutrition. Without the finance permission, feed costs do not appear (see Team and roles).

Calves, heifers, lactating, dry or pre-calving — computed on its own from each animal's state (age, gender, whether she is lactating, whether she has a pregnancy with a near expected calving date) and never stored by hand or forced. Lactating always wins over any other state; pre-calving overrides dry or heifer but never lactating.

A sale with no customer attached, for a passing buyer not worth adding to the catalog. It is not a special customer stored in the database — it is picking the "Occasional sale (no customer)" option in the customer select. In reports, every occasional sale in the period is grouped into one single "Occasional" row, never listed one by one.

The initial load of a farm: settings, people, catalogs, herd, current status and initial stock, in that order.

Empty female: no active service and no confirmed pregnancy. Available to be bred.

How the animal arrived at the farm: birth, purchase, transfer, donation or other. If it is a birth, the entry date cannot be earlier than the birth date.

Money that comes into the farm without being a sale: breeding service, manure, pasture rental, subsidies or other. Each carries a category, amount, date, optional customer, description (required when the category is "Other") and notes. It adds to the revenue of the profit and loss — one row per category —, to the cash flow and to the home "Income" tile. It can be deactivated when it was a mistake and reactivated later.

Unlike the supplies inventory — which never blocks, because its opening balance can be incomplete — finished cheese IS rejected if an adjustment would take a batch's stock below zero. A batch's kilograms are weighed on a scale, not an estimate: the same doctrine that already governs milk pool consumption.

A sale can never ask for more kilograms than a batch has left — it is rejected, the same as a stock adjustment that would take a batch negative. A batch that is already sold out simply does not appear as an option when building the sale.

A cow sold three years ago still shows up as the mother of her offspring, and a dead bull still shows up as a father. That is deliberate: genealogy is a fact of the past and does not change because the animal is gone. Hiding an animal from the herd list never removes it from its children’s family tree.

An amount of feed proportional to the liters a cow gives, with a minimum daily amount per head that never drops below — so a cow giving little milk still gets a feed baseline. It's the farm's real formula: for every 3 liters of milk, 1 kilogram of feed is given, with a floor of 5 kilograms a day split across that day's milkings.

On each animal's detail page, compares her real registered feed cost in the period against an estimate based on her current nutritional group's consumption over that same period — two numbers side by side, neither made up: if the animal has no nutritional group (for example, an adult male), both estimates come back empty instead of an error.

A reminder generated a fixed number of days after an unresolved surgery, to check how the animal is recovering. It clears once the surgery event is discharged.

~45 days after calving (voluntary waiting period). From this date on, the cow is ready to be bred again.

Check (palpation or ultrasound) after the service. Positive result → the female becomes "pregnant"; negative → she goes back to "open".

Pregnancy confirmed by palpation, ultrasound or non-return to heat.

An optional sale price per product. Once sales arrive, the suggestion will fall back to the cheese price configured on the farm if the product has none of its own; if that is missing too, there will be no suggestion — zero will never be proposed just because the data is missing.

The catalog of cheeses produced, each with its recipe: the ingredients and amounts per 10 L of milk, plus the expected yield in kilograms per 10 L. The recipe is what suggests doses when capturing a batch, and what computes how much "should" have come out, against what the scale actually showed.

How the female contributes to production today: calf, heifer, in production (lactating) or dry. Lactation rules: if she is milking, she is "in production" even if she is young.

A table per period (month, quarter or year) with revenue — cheese, milk, animals and other income, each on its own row, and other income split by category —, four cost lines, animal purchases, one line per expense category present, total cost, gross margin and net result. Pick the date range and the period type; every period in the range always shows up, even when nothing happened — a gap reads as "no activity", never as missing data. Expenses and other income each export as a report (PDF, Excel or CSV) from their tab, with the same filter shown on screen.

An incoming movement that adds stock: how much arrived and on what date. Optionally you record which supplier it came from, the price, the lot number and the expiry date. The price is not required, but it is what feeds the item’s average cost; the lot and expiry are what make expiry alerts possible. Any item with a unit can be bought two ways. A loose purchase asks for the quantity and the total paid, and Mi Finca works out the price per unit, so nothing ever needs dividing: a 3,785 ml gallon at ₡4,000 comes in as 3,785 ml at ₡1.0568 per ml. A purchase by container asks for what one container holds, how many arrived and the price of each — a switch, "Buy by the container", is on by default when the content is saved on the item. The content is editable right there, and "Save as the usual content" keeps it on the item for the next purchase. A summary under the price shows the quantity, the total and the price per unit before saving. When the price per unit is 5 or more times the last purchase, or 5 times below it, Mi Finca warns about it and the button turns into "Save anyway": it takes a second click to save, and changing any amount clears that confirmation. Correcting a purchase from the history offers the same two ways; only people with the finance permission see it, because correcting without seeing the price would erase it. When a medication has just been created by scanning its label and the label carried a lot and expiry, Mi Finca offers to open this purchase already filled in with those details, by container, with the content per container saved on the medication or, when it has none, the one read off the label — unless an initial quantity was entered on the record, in which case the offer is skipped, to avoid counting the same stock twice. When the item has been bought before, a muted line under the price field shows what it cost the last time — the price, the date and, when there was one, the supplier — plus its per-sack or per-container equivalent for an item bought that way. It is a reference only: the price field is never pre-filled from it, prices move and the day’s figure is always the user’s to type.

What the farm paid for an animal with origin "Purchase". It is entered on the animal form and counts as a cost in the period of its entry date: in the profit and loss ("Animal purchases" row), in the cash flow and in that animal's profitability, so that a steer bought and sold again does not look like pure profit.

The global list of everything the farm has bought, gathered from every area into one page: a period filter (this month, last 3 months, this year, or a custom range) plus area and supplier filters narrow the table down to whatever question is being asked. Each row is one purchase movement — date, item, area, quantity and unit, unit price, total, supplier and lot — and the card above the table adds up the spend and the count of the filtered rows. It is read-only: nothing here records a purchase, it only reports the ones already recorded through each area’s own Buy action. Without the finance permission, the table shows neither the unit price nor the total, and the card does not add up the spend.

What the animal is kept for: dairy (milk/cheese production), fattening, or breeding (a bull kept as a sire). Dairy requires a female; breeding requires a male.

A measurement of the milk on a given day: somatic cells, fat, protein. You write down whichever numbers you have — one is enough, all three if the laboratory sent them — plus which milk was measured and who measured it. It sits beside the day’s milking without touching it: recording quality never changes liters, destinations or pools. A test recorded by mistake is annulled, and the record stays in the audit trail.

A manual health-status override that isolates an animal. Health events do not change it automatically: the quarantine stays in place until it is explicitly cleared.

The assistant only reads: it never registers, edits or deletes anything. If you ask it to record something, it points you to the screen where you can.

Every row of an animal’s health and reproduction history shows who recorded it, by name (never by e-mail). Rows recorded before this feature existed have no author and show a dash.

For farms that measure the tank or the buckets and do not weigh each cow. In the shift card, turn on "Record the milking total", enter the liters and the cows milked (prefilled with the cows that can be milked), save, and close the shift as usual. A farm can use it for some milkings and weigh cow by cow in others — milk recording, say — each milking has its own mode.

The milking grid's "Register feed servings" button creates a daily consumption in one click for every eligible cow in that session, with exactly the amount the suggested column showed at that moment. A cow can be excluded before registering (for example, if she already ate through another path). Retrying the same session's registration never duplicates: any cow already registered for that session is skipped, and only what was still missing gets completed.

The animal genuinely came back. The absence is closed with the date it returned and the animal counts in the herd again, with an editable record. The departure is not deleted: it stays in the history, and it is exactly what explains why there are no weights, services or treatments in those months. It can only be registered after a transfer or a loss: a sold, dead or slaughtered animal does not return.

Takes the person off the farm right away: they lose access on their next action, even with the app open, and leave the farm’s Kinde organization. Everything they recorded stays on the farm. The owner’s access cannot be removed, and nobody removes their own.

A ready (`READY`) batch is read-only; correcting its pools, ingredients or weight requires reopening it first. Reopening only applies to a batch that is already closed, and is rejected if it has any active sale or adjustment on its stock (see "Reopening or deleting blocked by outbound stock"). Without that block, reopening annuls the production movement the close had created — it is re-created, with the new weight, the next time it closes.

A batch with any active adjustment or sale on its stock cannot be reopened or deleted until those movements are annulled first — otherwise stock would stop reflecting reality. The message says exactly that: annul the sales or adjustments before reopening or deleting.

The identification the PDF and the Excel carry: farm name, legal name, SENASA CUE, tax ID, location or address, phone and email — only the fields that are filled in, never an empty line — plus the report title and the period with the filters applied. In the PDF it sits on every page with the logo on the left and a rule in the farm color underneath, and the line "Generated by <person> · <date and time>" (in the farm time zone) goes in the footer of every page; in Excel it is the Summary sheet. The CSV carries no farm header: only the title and the period in its first lines.

The reports page works on one period: a start day, an end day, and how the days are grouped — by day, by week or by month. It opens on the last 30 days grouped by day, and every block on the page — alerts, herd production, the ranking, the tank reconciliation — reads from that same period, so widening it re-runs the whole page instead of one panel at a time.

The Reports page in the dashboard: one card per report in the system, grouped by area (Milk, Cheesemaking, Sales, Nutrition, Finance and Inventory). Each card leads to the report's own page, which is where the Export button lives — the hub never exports anything itself. Only the cards for reports the role can read are shown; a role with access to none sees a message instead of the cards.

For now, a cheese return is recorded as a positive stock adjustment on the Cheesemaking Stock tab (reason "return"), not as part of the original sale — the sale that led to the return stays unlinked to that adjustment. This is a deliberate limitation of this first version: stock gets corrected either way, but the sale-to-return link is left for later.

~21 days after a service (species-dependent). Worth checking whether the served female came back into heat — a sign she did not conceive.

Each row of the form shows up with an action: New (not in the farm), Update (it exists and the form brings different data), Tag change (the animal exists under the old tag), Unchanged, or Needs review (something could not be resolved). You can edit the name, tag number, origin, purpose, and lactation status of new animals before confirming.

The two ways a live animal leaves the farm. In a sale the owner changed and money changed hands. In a transfer the animal moved to another establishment but is still yours: your other farm, a loan to a neighbour, rented grazing. In the app a transfer is labelled "Transfer".

Every item in a sale sells kilograms from one concrete cheese batch, not from a product in general — you pick the product, then the batch, and last the kilograms and the price. That link is what lets stock come down from the exact right place, and later lets every sold kilogram be traced back to the milk and cows behind it. Each batch in the picker is named the way the cheese Stock tab names it, by the day and milking of its milk, followed by its remaining kilograms and its batch number: "Friday · afternoon · 12.5 kg (20261002-1)"; a batch with no milk recorded shows the day alone.

Viewing customers, sales and reports requires the sales read permission; creating or editing customers and sales additionally requires the write permission. The Viewer and Accountant roles can only look (the Accountant cannot create or edit a sale); Owner, Manager and Worker can also register and edit. The Veterinarian does not see Sales (see Team and roles).

Four views over the same period: sales by period (cheese kilograms and revenue grouped by day, week or month), sales by product (kilograms, revenue and the real average price actually charged for each cheese — never a made-up zero when there are no kilograms to average — plus, apart, one "Milk" row in liters with its own average price per liter), top buyers (with every occasional sale grouped into one row), and total losses (the period's negative stock adjustments, grouped by reason). Revenue always includes milk; kilograms and liters are never added together.

The dedicated record for the semen the farm keeps in the tank, one per bull: the bull’s name and, if you have them, its registration number, its breed and the genetic house. You can enter how many straws are already stored and a minimum for the low-stock warning. From there it lives in the same inventory as everything else: purchases with supplier, price, lot number and expiry date, adjustments with a reason, movement history, average cost, and low-stock and expiry alerts. What is particular to straws is the deduction: recording an insemination and picking a straw from the catalog takes exactly one off, dated on the service. Annulling the service later puts the straw back; and correcting the service date moves the movement along with it, so the inventory is never dated differently from the insemination. A natural mount spends no straw, so one cannot be assigned to it. And a service recorded without picking a catalog straw is just as valid, it simply deducts nothing — the tank never hears about it. The unit, normally the straw itself, locks as soon as movements have been recorded. The Reproduction tab puts straws on top and the rest of the supplies below.

The cow was bred (natural service or artificial insemination) and is awaiting pregnancy confirmation, typically 30-60 days later by palpation or ultrasound. If she returns to heat, she goes back to "open".

The act of breeding a female, either by natural mount or by artificial insemination. Recording it moves the female to "served". If it is an insemination and a straw from the inventory catalog is picked, one is deducted from the tank, dated on the service; a natural mount spends no straw.

You no longer open a milking session by hand. The first liters typed into a column that has no session yet create that shift’s session and then record the entry — including a column you added for a shift the farm does not normally milk. The session is still there underneath, with the same close and reopen it always had; you just stop having to think about it before you can write a number.

Which milking of the day a session belongs to: morning, afternoon, evening or night. The farm’s "milkings per day" setting drives which shifts are offered by default — one milking a day offers only morning, two add afternoon, and so on. A farm that occasionally milks outside its usual count can still open a session in any of the four shifts through the "other shifts" option; the configured count is a default, not a hard limit.

The male — or the semen source in artificial insemination — that performed the service.

Records that a protocol dose will not be given, with a required reason (for example, the cow is pregnant or sick). It creates no treatment, puts the animal on no withdrawal and does not touch inventory. A date can be set for the dose to be reminded again — for example, after calving — later than both today and the day the dose was due, and on that day the alert comes back. If the dose ends up applied after all, that application takes over and the calendar continues from it. Without a date, the calendar keeps its normal course from the day the dose was due; on a single-dose protocol, skipping without a date closes it. In the health history the event shows as “Skipped”, with its reason and, when set, the reminder date. A skipped dose cannot be resolved or edited: if it was skipped by mistake, annul it and mark the protocol as applied, or skip it again.

How many somatic cells there are in a milliliter of milk, written in thousands — 250 means 250,000 cells per ml. It is the udder-health number: cells climb when a quarter is inflamed, so a count that keeps rising on one cow is mastitis showing up long before anything can be seen in the milk, and the tank figure says how the whole herd is doing.

How much of an item is left. It is stored nowhere: it is calculated by summing every movement of the item, so it always reflects what has been recorded. It can go negative, and that means consumption was recorded before the purchases backing it were entered — a discrepancy you fix by recording the missing purchase or making an adjustment. Zero or negative stock never blocks recording a treatment, a cheese make or any other operation: inventory warns, it does not block.

A manual correction to a batch's stock: signed kilograms, a required reason, date and optional notes. The reasons are loss, damage, gift, consumption, return, correction or other. There is no editing a saved adjustment — it gets annulled and a new one is created, the same correct-by-repeating-the-action philosophy used across the rest of the system.

One table per product, expandable into its ready batches: each one shows what was produced, sold, adjusted and what remains, plus the full movement history and the adjust action. Under the batch number sits the day and milking of the milk it was made with (“Friday · morning”, or “morning and afternoon” when it pooled two milkings; just the day when the batch has no milk recorded); the suffix of the number (-1, -2) is only a counter within the day, not the milking. Only products with at least one ready batch appear here — a product with no batches produced yet stays on the Products tab, without taking up space in this one.

Your farm's Mi Finca plan: its status (Trial, Current, Grace, Paused or Cancelled), when it expires, how many users it uses and the expected charge. The owner and the manager see it read-only; payments and plan changes are recorded by the Mi Finca administrator.

Dose per kg × current weight, shown as a prefill in the treatment form; always editable, because dose and withdrawal are safety data the user confirms.

A column in the milking grid that shows, for every lactating cow, how much feed she is due based on the active plan — per-milk lines use her milk history from the last 7 days; fixed per-head rations need no history — split across the farm's configured daily milkings. It is only a suggestion shown on screen: it stays unsaved until it is registered.

Picking the product suggests a price per kilogram on its own: first the product's own price if it has one configured, otherwise the farm's general cheese price. If neither exists, nothing is suggested and the price has to be typed by hand — zero is never proposed just because the data is missing. The suggestion is an editable starting point, not a fixed price: whatever gets saved is what was actually negotiated that day. On a milk line the suggested price per liter is the farm's configured milk price; if there is none, the field stays empty and is typed by hand.

The three examples shown when you open an empty conversation. Tap one and it is sent as written, with nothing to type.

Who you buy from: the vet practice, the supply store, the neighbour who sells you alfalfa. It is stored with contact, phone, email and notes, and it is shared across every area — the same supplier can sell the farm both medications and detergent. You can create one from its own tab, or on the fly from inside the purchase form.

A generic inventory item: name, the area it belongs to, the unit it is consumed in and, if you want one, a minimum that triggers a low-stock warning. That is already enough to buy it, adjust it and know how much is left. An item only gets a specialised record — medication, cheese input, feed, semen straw — when some module needs its own attributes, such as dose per kilo or withdrawal days. When creating it you can enter the initial quantity — what is already on hand — recorded as "Initial stock", with no cost.

SENASA marks a retired tag with "R" and "REPOSICIÓN" and adds a row for the new one. Mi Finca pairs them by birth date and sex and proposes the change, always unchecked: you have to confirm it. The previous tag stays in the animal's history, so a future form still recognises it.

How much milk the tank actually holds, weighed by the farm and written down — the figure the day’s milkings get checked against. A reading covers either the whole day or a single milking, and there can be only one active reading per scope per day: weighing the tank twice for the same day (or the same milking) corrects the earlier number, it doesn’t add a second one. Readings are registered, corrected and annulled from the reconciliation table, never guessed from the milkings themselves.

One row per day, comparing what the tank was weighed at against what the day’s milkings add up to. It exists to catch what a milking log alone can’t: a leak, a spill, a capture mistake, or a milking that never got written down.

The whole month under the list of requests, with one band per person on each day they are off: solid when the absence is approved, dashed while it is still pending. Rejected requests do not show. Tapping a day lists who is off that day.

A piece of work assigned to someone on the team, with a title, a priority, a date and, when needed, an animal and notes. It can be one-off (for one day; if it is not marked, it keeps showing as overdue), daily, or on chosen weekdays, with an optional last day. The owner and the manager create, edit and delete them, and assign them to the owner, a manager or a worker. The assignee marks their own task done; the owner and the manager can mark any. The section shows the whole week, overdue tasks first, with a filter by person.

When the mother or the father were never on this farm — a cow bought already pregnant, semen from a bull at another breeder — there is no record to link to. In that case you write down the parent’s DIIO as text, and the genealogy stays as a reference instead of being lost.

The farm’s time zone (Costa Rica) and preferred language (Spanish/English). They affect dates, times and the application’s texts.

A ranking of the herd’s best-producing cows for the period: total liters, her daily average, and how many milkings were recorded for her — ordered by total liters, highest first. The daily average divides by the days she actually has entries for, never by the whole length of the period, so a cow that joined partway through does not look like a low producer just because she was there for fewer days. Tapping a row opens that cow’s detail.

Every supplier the farm has bought from, ranked by how much it has spent with them, with how many purchases back that total. It reads the whole history unless a period is picked — the area and supplier filters that narrow the Purchases table do not apply here, only the date range does, so the ranking always answers "who does the farm buy the most from" rather than "who supplies this one area." A purchase recorded with no supplier is simply left out — there is nobody to credit it to.

A medication administered as part of a health event: drug, dose, administration route, duration and its withdrawal periods (milk and meat).

The departure was logged by mistake — the wrong animal, one click too many — and never happened. Undoing it erases it: nothing is left in the history saying the animal ever left. It is not the same as registering a return, and confusing the two costs information.

The farm’s measurement system: metric or imperial.

From Animals → Import form, choose the PDF exactly as TrazarAgro generates it from the browser. A scan or a photo will not work: the file needs to carry text. If the document is not a Form 03, it is rejected with a clear message.

Each animal’s due or overdue vaccinations, derived from the vaccination protocols and the vaccination events recorded in its history.

An external role for whoever looks after the herd. Looks at and records health and reproduction (treatments, diagnoses, services, palpations), looks at milking to check withdrawals, looks at nutrition and uploads animal photos. Sees medication stock, but never a cost. Can annul only what they recorded: on other people’s rows there is no “Annul”.

If the CUE or the tax ID on the form do not match the farm's (or the farm has not configured them yet under Settings → Legal), a warning is shown. It does not block the import: check that the form really belongs to your farm before confirming. When the farm is missing the value (not when it merely does not match), the warning carries a "Save to farm" button that fills it in with the value read from the form, without leaving the review screen.

A dated body-weight entry that builds the animal’s weight history; the most recent one is the current weight used for dose suggestions.

The unit cost Mi Finca keeps for each item. Every priced purchase recalculates it by weighing what was already there against what is coming in, so the average barely moves on a small purchase and moves a lot on a big one. A purchase with no price adds quantity but leaves the average alone. If stock was at zero or negative, the purchase resets the average to the new price: averaging against negative stock would not produce a meaningful number.

It never registers a departure or deletes an animal. An animal that is in Mi Finca but does not appear on the form means nothing: the form lists one registration batch, not the whole herd. An animal that is away (transferred, sold) or deleted shows up flagged and is left untouched.

Every test says which milk the sample came from. There are three answers, and they are not interchangeable: a tank figure describes the herd, a cow figure describes that cow.

The owner and managers decide in the Members tab who gets the daily digest. By default the owner and managers get it; it can be switched on for any other member. Each person can unsubscribe from Notifications (in the sidebar, next to Sign out) or from the link at the bottom of the e-mail, and nobody else can undo that. That link opens the preferences of the farm that sent the e-mail, even when another farm is active in the dashboard.

Whether an entry’s milk is withheld is worked out only when the session is closed (or viewed), by comparing the cow’s milk withdrawal period against the session’s date — it is never decided or stored at the moment the entry is recorded, because the withdrawal window can still change afterwards. Any withheld liters always form their own pool, discarded for withdrawal, no matter what split is chosen for the rest: there is no destination that can route withheld milk anywhere else.

The difference between what the recipe expected to produce from those liters and what the scale actually showed. It is computed on its own, with a sign — negative when less than expected came out, positive the other way — and is never clamped to zero: a real positive merma says as much as a negative one.