Oilseed Crush Plant Software: Custom Build or Off the Shelf
Buy. If you crush under roughly 1,000 tonnes a day, sell meal and oil largely on spot, and carry no renewable fuel documentation obligation, a grain accounting package such as AGRIS or Agvance plus your broker statements genuinely covers the arithmetic.
On this page
Buy. If you crush under roughly 1,000 tonnes a day, sell meal and oil largely on spot, and carry no renewable fuel documentation obligation, a grain accounting package such as AGRIS or Agvance plus your broker statements genuinely covers the arithmetic. Build when a daily crush margin has to be assembled from adjusted receipts, live yields and a hedge position drawn from one set of numbers.
What AGRIS, Agvance and the trading packages already handle
The software around a crush plant is not missing. It is scattered, and each piece is decent at its own job.
Grain accounting packages such as AGRIS and AgVantage from Cultura, or Agvance from Greenstone, do receiving properly. Scale tickets, grading on moisture, foreign material, damage and splits, a discount schedule, settlement, and a producer payable that your controller trusts. That is not a small thing and rebuilding it is rarely a good use of money. On the commercial side, a dedicated commodity trading and risk management package such as Agiblocks or Eka holds contracts, positions and mark to market with more rigour than any spreadsheet, and if your trading desk is the constraint that is where to spend first. Bushel handles grower facing contract and settlement visibility well.
On the plant floor, your historian is already collecting what you need. An AVEVA PI System or a Rockwell FactoryTalk historian holds tank levels, flows, temperatures and run states at a resolution nobody uses. Your laboratory information system holds oil content, protein, moisture and free fatty acid results.
Say the honest thing early. Most crush operations reading a build vs buy comparison should buy, and several should buy nothing at all. A single mechanical press plant selling meal to a local feed market and oil into spot, with no hedge and no renewable fuel customer, needs bookkeeping discipline rather than software. Buying a platform for that is a subscription looking for a problem.
Where every off the shelf option stops: the daily margin
Here is the workflow no package models, and it is the one that decides how the plant runs.
Your margin is beans in against meal, oil and hulls out, adjusted for what the hedge did. Every plant manager can recite that. Very few can produce the number for last Tuesday without three people and half a day, because the four components sit in systems with different owners and different close cycles. Receiving with its shrink and discounts is in grain accounting. Extraction performance is in the historian and the shift log. Meal and oil sales are in contracts, sometimes in a trading system, sometimes in a workbook. The futures position is with the commercial team or on a broker statement.
So the plant runs on a monthly figure that arrives weeks after it could have changed anything, and on instinct in between. Meanwhile the board crush moves daily with CBOT soybean, meal and oil futures, and the decisions that ought to respond to it, how hard to run and when to price, are being made on the instinct.
There is a second failure hiding inside this one, and it is the specific error we find most often. Yield calculations get run against delivered weight rather than the adjusted weight after moisture shrink and grade discounts. The dry matter you actually bought is not what the truck scale said. When extraction looks two points low, half the plants we have worked with are chasing a process problem that is an accounting problem, and the plant engineer spends a fortnight on it.
Then there is documentation. Oil going to a renewable diesel buyer carries obligations vegetable oil for a food customer never had: feedstock origin evidence, chain of custody under a scheme such as ISCC, and data supporting a carbon intensity claim. That evidence has to have been captured at receiving. You cannot retrofit origin to loads that arrived last quarter, and plants discover this the first time a buyer sends a document request.
The arithmetic: cost per tonne crushed versus the cost to build
Convert both options to cost per tonne crushed and the comparison stops being a debate.
Add your annual licence and maintenance across grain accounting, any trading system, the historian licences you are paying for and not using, and the reporting or business intelligence (BI) tool sitting on top. Divide by annual tonnes crushed. That is the buy side, and at any real throughput it is a small number per tonne, which is why nobody questions it.
Now the other column. Take the shrink and discount schedule applied by hand across thousands of loads and estimate the error in both directions, using the last audit or spot check you ran. Add the person day per week spent assembling the monthly number. Add the demurrage you paid last year on rail cars nobody was watching. Add one avoidable extraction drift that ran three weeks before anyone noticed. Divide all of that by the same tonnes.
The crossover, as a working rule, sits near 1,000 tonnes a day of continuous crush, or about 350,000 tonnes a year. Below that, the manual column stays small enough that a competent controller absorbs it and buying is correct. Above it, a tenth of a point of extraction and a half percent of settlement error are both worth more per year than the entire build, and they are only visible if the balance is computed daily against adjusted receipts. That is the crossover, and it is driven by throughput rather than by headcount.
What a custom build actually costs
From Digital Heroes delivery experience in commodity processing, a first release covering receiving with automated shrink and discounts, adjusted inventory, a daily mass balance built from historian data, and the crush margin calculation runs $80,000 to $160,000 across 12 to 18 weeks. A full plant platform adding purchase and sale contracts, loadout with quality certificates from actual results, position reporting including the hedge, sustainability documentation and rail management runs $200,000 to $500,000 phased over 8 to 14 months.
Budget data migration at 10 to 25 percent of the build on top. In this category the cost sits in historical receipts and contract history rather than in volume, and it is worth deciding early how many prior seasons you genuinely need inside the system rather than archived. Year two runs 15 to 20 percent of build cost annually: control system upgrades that move tag names, new certification scheme requirements, another purchaser's file format, and the enhancement work that follows once the plant starts trusting the daily number.
One sequencing rule saves more money than any negotiation. Do not build margin reporting before receiving and yield data are clean. A confident margin number computed from unreliable inputs is worse than no number, because people act on it.
The four situations where building wins
Four conditions move a crush operation across the line. Two together are usually decisive.
- Regulatory fit. You sell into renewable fuel markets, so feedstock origin, chain of custody under your certification scheme, and carbon intensity evidence have to attach to physical movements at the moment they happen. Multiple schemes running at once multiply this, because each defines mass balance differently, and no packaged plant system carries your particular combination.
- Scale economics. Past roughly 350,000 tonnes a year, small percentages become the whole argument. A tenth of a point of extraction across that volume outweighs the build, and you cannot manage what closes monthly with a plug figure.
- A workflow that is your competitive advantage. If you buy on basis and price into a moving board crush, the speed at which your commercial lead and your plant manager agree on one number is the business. Firms that argue about whose spreadsheet is right are slower than firms that do not, and that gap compounds every week.
- Integration sprawl across three or more systems. Scale and grading, the process historian, the laboratory system, contracts, the broker statement and the general ledger. Once five of those have to reconcile daily rather than monthly, the integration layer is the project and every other tool is a data source feeding it.
How to decide in a week
Skip the vendor demonstrations. Run this test.
On Monday, ask three people independently for the crush margin for a single specific day two weeks ago: your plant manager, your commercial lead and your controller. Give them until Wednesday and tell them not to talk to each other. On Wednesday, put the three answers side by side.
What you are measuring is the spread and the effort. If the three numbers agree within a rounding difference and each took under an hour, your process is stronger than most crush plants and you should buy the narrow thing you are missing, not a platform. If they disagree by more than the plant's typical daily margin, you have just priced the problem, because every operating decision made between those two dates was made inside that spread. If two of them used delivered weight rather than adjusted weight, you have found the specific defect this guide exists to name.
The next step is a paid discovery phase rather than a proposal. At Digital Heroes that means a signed product requirements document covering the receiving model, the mass balance definition, the margin calculation and the acceptance criteria, written before any code exists, by the named engineers who would do the work. You keep that document whether or not you build with us, and it is what makes a fixed quote hold. Contracting runs through our India LLP, US LLC or UK LTD entity so intellectual property assigns under your own law.
We are the wrong firm if you want trading advice, a certification body, or a control system integrator to touch the process network. We build the reporting and reconciliation layer above it, and any developer offering to automate your hedging decisions should be shown out.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In a survey of 579 supply chain professionals (July 31 to October 1, 2024), only 29% had built at least three of the five capabilities Gartner identifies as needed for future competitiveness (agility, resilience, regionalization, integrated ecosystems, and enterprise-wide strategy). Source: Gartner (2025) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Criteo's Global Commerce Review found retail apps convert at 18% versus 4% on mobile web (roughly 4.5x), and travel apps convert at 20% versus 6% on mobile web (about 3.3x). Source: Criteo (2017) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
Frequently asked questions
How long does implementation take without interrupting the crush?
A first release ships in 12 to 18 weeks and the plant runs throughout, because the work begins at receiving and can be captured alongside the existing process rather than replacing it. The largest schedule risk is pulling process and tank data out of an older control system. Get that assessed in the first fortnight rather than assuming a clean interface exists, since it decides whether the mass balance arrives on time.
Who owns the code and the plant data if an agency builds this?
You own the repository, the cloud accounts and every byte of production and settlement history, with the right to hire another firm, agreed before kickoff. At Digital Heroes the client owns the code from the first commit. When a system produces the margin and position numbers your commercial decisions run on, needing somebody else's permission to change a calculation is an unacceptable dependency to accept for a licence discount.
Can the system show our hedge position without touching trading decisions?
Yes, and that boundary should be written into the scope. The report shows physical inventory and open contracts by commodity and delivery period, with the futures position imported from your broker or trading system, so the net exposure appears as one picture from one set of source data. It reconciles, it does not decide. Most disagreements between commercial and plant teams disappear once both argue from the same numbers.
What happens if the mass balance does not close?
It will not close, and a system that assumes otherwise was built by someone who has not worked in a plant. The correct behaviour is to separate measurement variance from unexplained loss, present both as figures to investigate, and never absorb the difference into a plug. Ask any developer this question before signing. The answer tells you within a minute whether they have delivered in process manufacturing or only read about it.
Do we need this if we already have a commodity trading system?
Probably not the full platform. If your trading package already produces a reliable daily position and your only gap is plant yield, that is a much narrower and cheaper project, often a receiving and mass balance layer that feeds the position you already trust. Build the wider system when the gap runs both ways, meaning the trading view and the plant view disagree and nobody can settle it from source data.
What is the difference between delivered weight and adjusted weight?
Delivered weight is what the truck scale recorded. Adjusted weight is what remains after moisture shrink and grade discounts are applied, and it represents the dry matter you actually bought and paid for. Yield and extraction must be computed on adjusted weight. Using delivered weight makes an accounting difference look like a process fault, which is the most common and most expensive modelling error in oilseed processing software.
Can we defer rail car management to a later phase?
Yes, if truck volume dominates your loadout today. Rail brings car placement and release timing, constructive placement rules and demurrage exposure that accrues quietly, so it deserves its own workstream rather than being assumed into a general logistics module. Many plants find rail visibility pays for itself in avoided demurrage alone, which makes it a strong phase two rather than a reason to delay release one.
What documentation do renewable diesel buyers actually ask for?
Depending on market and buyer, expect feedstock origin evidence, sustainability certification such as ISCC, chain of custody through the plant, and data supporting a carbon intensity claim, with specifics confirmed by your compliance adviser because programmes differ and change. The operational point is timing rather than content. Origin evidence has to be captured at receiving, and software should also warn before a supplier declaration expires rather than after a load has arrived against it.
Should we build one plant first or all of them?
One plant, and pick the one with the cleanest instrumentation rather than the largest throughput. Multiple sites multiply certification scope, tag mapping and reconciliation rules, and each of those is a place where a first release stalls. Once a single plant has run a full quarter on a daily margin nobody disputes, rolling the second site out is largely configuration and data mapping rather than design work.
How do we know the daily margin number can be trusted?
Prove it before you rely on it. Run the new calculation in parallel with your existing monthly close for two full months and reconcile the difference line by line, treating every unexplained gap as a defect rather than as noise. Plants that skip this step get a number that people quietly stop believing after the first surprise, and rebuilding that credibility costs far more than the two months would have.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
How long does custom ERP development take?
Plan on 3 to 4 months for the first working module and 6 to 12 months for a full multi-module rollout. In Digital Heroes delivery experience the schedule risk is data migration and integration testing, not feature coding, so we stage go-lives module by module instead of one big-bang launch.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
Will a custom ERP scale as we grow from 50 to 500 employees?
Yes, if it is designed for that from the start, which mostly means clean database design, permissions that handle new departments, and modules that stay separable. Adding users to software you own costs nothing in licenses, the opposite of the per-seat scaling penalty on NetSuite or Dynamics. What does need budget as you grow is new modules and integrations, so keep a small standing development arrangement rather than restarting a vendor search every two years.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Camille.
Office Manager · New York · New-york · 7 posts on the site
Published · Last updated .
