Guides for getting work done in Intecrop, grouped by what you came here to do.
Guided walk-throughs for getting something done the first time.
From logging in to a printed instruction, in one sitting.
Tag the applications you did for a buyer, then download a summary that shows those and nothing else.
Tag your foliar feeds once, then leave them out of the summary an auditor asks for, and off an application's PDFs.
Make a Use: Raisins tag, put it on your raisin blocks, and download a block census that lists them and nothing else.
From an account with no farm to a farm that is ready for its blocks, in three steps.
Steps for a specific task, assuming you know your way around.
Add a newly planted block — and, first, its crop or cultivar if your farm does not have it yet.
Put the people who tell your team to go and apply on your farm's list, so an instruction can name them. They do not need a login.
Put the people and machines on your farm into Intecrop once, so every instruction can pick them from a list.
Upload the supplier's invoice and let Intecrop fill in the rows — quantities, units and prices — for you to check.
Record when each block was done, how many tanks went out, the excess mixture and the weather — then publish, which takes the chemicals out of stock.
Enter a stock take: what you counted on the shelf becomes the balance.
See how much product and active ingredient went onto each block — and, if your role allows, what it cost.
Download the block census and every block's application record for a season, as a PDF to hand over or a spreadsheet to work in.
Add a manager, an advisor or anyone else to your farm by email address, with the role that fits their job.
See all your tags on the Tags page, add one, rename a value or a key, merge two tags into one, and delete a tag from everything at once.
Record stock that went from one of your stores to another as one move, so both stores agree on what moved and when.
See what you have been invoiced and what you owe, download your invoices and statement, and send proof of payment when a payment is overdue.
Record that a block has come out of the ground, and start a new block in its place when it is planted again — without losing the old block's history.
Send part or all of a delivery back, starting from the receipt it came in on, and let Intecrop work out the credit at the price you paid.
Enter the pre-harvest interval and re-entry interval for each product on each crop, one at a time or from a file.
Copy an earlier application's instruction into a new one — its operators, chemicals and blocks — and change only what is different this time.
Put a tag such as Buyer: Woolworths on one application or many at once, take it off again, and list only the applications that carry it.
Put a tag such as Use: Raisins on one block or many at once, take it off again, and list only the blocks that carry it.
Put a tag such as Programme: Foliar feed on one chemical or many at once, in every store at once, and take it off again.
What each field means and what the app does with it.
Nothing here yet.
Why the app is built the way it is.
How to decide whether something is another production unit on the same farm, or a farm of its own.
Why a cost is an average over a period rather than the price on the drum it came out of.
Why a season is a window over dates rather than something you create.
What each stage is for, what it locks, and at which stage stock moves.
Why you would tag a block, an application or a chemical, and what a tag does once it is on one.
Which of the three to choose when a block changes, and what each one does to the block's history.
Why the product list is shared between farms, why adding one is a request rather than a change, and how to tell where that request stands.
How a block's conditions are filled in, why a value can change once, and what to do when it says unavailable.
Are you sure you want to proceed?