On this page
- The short answer
- Where your business begins and ends
- Edible Oil vs Manufacturing and FMCG
- Map the commodity-to-market lifecycle
- CONTROL THE COMMITMENT
- A Sauda is not the invoice
- BOOKED QUANTITY ≠ RECEIVED QUANTITY
- Amendment and cancellation history
- Broker exposure
- Counterparty open position
- Weighted-average locked rate
- BOOKED RATE ≠ CURRENT MARKET RATE
- Sauda is not financial hedging
- GROSS WEIGHT ≠ NET MATERIAL
- Vehicle or tanker identity
- Match the inward to the Sauda
- CONTRACTED ≠ DELIVERED ≠ ACCEPTED
- Inward quality
- Deductions and allowances
- Accepted quantity or value
- Supplier settlement
- BULK OIL ≠ PACKED SKU
- FOLLOW THE OIL
- Tank inventory
- Tank transfer
- Tank capacity
- Weight, volume and density
- Tank commingling
- Crushing
- Refining
- Refining stages
- Stage-wise balance
- EXPLAIN THE RECOVERY
- STANDARD YIELD ≠ ACTUAL RECOVERY
- By-products
- Blending
- Blend formula and actual sources
- Blend genealogy
- Packing
- Packing output and loss
- Bulk-to-pack genealogy
- Full-tanker bulk sale
- Actual economics
- Job work
- After packing: the FMCG handoff
- ERP, weighbridge, plant, lab
- The difficult scenarios
- Standard or custom?
- Red flags
- Evaluation record
- What customer proof?
- Evidence: ANA Oils
- How exactllyERP fits
- Checklist
- Go Deeper
One company may crush oilseed. Another may buy crude oil and refine it. Some blend and pack refined oil. Some sell full tanker loads. Some operate mainly as packaged-oil distributors. Some use toll or job-work processing. Many combine several of these models.
That is why an ERP should not be judged simply by asking whether it supports purchase, production, tanks, batches or sales.
The buyer needs to know whether the system can preserve the original commodity commitment, actual delivered and accepted quantity, tank and batch identity, process recovery, bulk-to-pack conversion, commercial fulfilment and resulting cost/margin without reconstructing the story later.
The useful question is not “Does your ERP support Edible Oil?”
It is “Can you prove what we committed, what physically arrived or moved, what the oil became, where it is now, and what the transaction finally contributed?”
The short answer
An Edible Oil company should evaluate ERP by following the complete commodity-to-market chain.
A useful generic lifecycle is:
- market / negotiated rate
- Sauda / commodity contract
- counterparty / broker
- quantity + delivery window
- vehicle / tanker arrival
- weighbridge
- quality / accepted quantity
- contract fulfilment
- seed or crude-oil inventory
- tank / bulk storage
- crushing / extraction where applicable
- refining where applicable
- blending where applicable
- quality release
- refined-oil tank
- packing or bulk sale
- SKU / pack-size inventory
- warehouse / allocation
- dispatch / billing
- receivable / payable / settlement
- actual cost / margin
Not every Edible Oil business uses every stage.
The important test is whether the proposed ERP can connect:
- the original commodity commitment;
- agreed quantity and rate;
- counterparty and broker where applicable;
- fulfilled and open quantity;
- vehicle/tanker movement;
- gross, tare and net quantity;
- accepted quantity after quality where relevant;
- bulk/tank position;
- actual process input and output;
- by-products and losses;
- standard versus actual recovery;
- blending where relevant;
- bulk-to-pack conversion;
- packed or bulk fulfilment;
- and the resulting commercial position.
A feature list cannot prove that.
First identify where your Edible Oil business actually begins and ends
Before comparing ERP vendors, define the operating model or combination of models you actually use.
Possible models include:
These models can overlap.
A company may crush one oilseed, buy crude oil for another category, blend a third product and sell both bulk and packaged output.
Do not force the entire business into one “Edible Oil” process simply because a vendor has one standard demo.
Ask:
Where does our commercial commitment begin, where does physical custody change, and where does processing or packing materially change quantity, quality or value?
That answer should shape the evaluation.
What makes Edible Oil different from general Manufacturing and FMCG?
Manufacturing asks:
- what should be produced
- what material/process is required
- what actually happened
- what output resulted
- what it cost
- why it varied
FMCG asks:
- what stock is genuinely sellable
- what commercial rule applies
- what moved through the channel
- what remains unpaid or returned
- what the SKU finally contributed
Edible Oil adds another layer before and between both:
What quantity did we commercially commit at what rate?
What physical quantity actually arrived, moved or left after weighment?
Where is the bulk oil now?
What did each process stage recover, lose or create?
How did bulk material become a particular packed SKU or tanker dispatch?
That is why Edible Oil ERP evaluation should not simply combine a Manufacturing checklist and an FMCG checklist.
It should test commitment, physical quantity, bulk custody, recovery, conversion and commodity-to-margin traceability.
Map the complete commodity-to-market lifecycle before choosing software
Do not begin with the purchase order.
Begin with the real operating lifecycle.
At minimum, map the stages that apply to your business:
Then ask:
At which points can quantity, rate, ownership, accepted value, tank position, recovery, SKU output or commercial exposure change?
Those are the points the ERP evaluation must test.
CONTROL THE COMMITMENT
The first Edible Oil signature principle is:
CONTROL THE COMMITMENT
A commodity transaction may begin before the eventual inward receipt or sales invoice.
Depending on the business, the original commitment may include:
Confirmed exactllyERP Edible Oil capability includes recording these elements in purchase Sauda/commodity contracts and, where the business uses them, sales Sauda/commodity contracts.
The buyer should ask:
Can we reconstruct the original commercial commitment before looking at what was eventually received, dispatched or invoiced?
A Sauda is not the same thing as the later invoice
The commercial commitment may happen first.
Physical receipt, delivery and invoicing may happen later.
That means the system should preserve both:
what was booked
and:
what was actually fulfilled
Confirmed exactllyERP capability includes preserving the original agreed rate and fulfilling a single purchase Sauda through multiple inward receipts and a single sales Sauda through multiple dispatches where applicable.
The buyer should ask:
What did we originally commit, and how much of it has actually been fulfilled?
Do not treat a later purchase or sales invoice as if it were the original commodity agreement.
BOOKED QUANTITY ≠ RECEIVED QUANTITY
A single commodity commitment may be fulfilled in parts.
Confirmed exactllyERP capability includes visibility of:
- contracted quantity;
- fulfilled quantity;
- open/balance quantity;
- delivery schedule/window;
- fulfilment against that schedule.
The buyer should ask:
Before the next deal is booked, how much quantity is already committed but still open?
This is more useful than reviewing old purchase orders one by one.
Preserve amendment and cancellation history
Commercial commitments can change.
Confirmed exactllyERP capability includes contract amendment/cancellation while preserving the original and revised commercial history.
The buyer should ask:
If quantity, rate, delivery timing or another agreed term changes, can we still see the original commitment and the approved revision?
The historical commercial record should not disappear when the current contract state changes.
Broker exposure is different from supplier exposure
Not every Edible Oil business uses brokers.
Where brokers are used, management may need a separate view of:
- broker
- contracts
- committed quantity
- rate
- fulfilled quantity
- open quantity
- brokerage liability
Confirmed exactllyERP capability includes broker-wise open contract/exposure position and brokerage liability according to configured terms.
The buyer should ask:
Before booking another transaction through this broker, what quantity and commercial exposure is already open?
Counterparty open position should also remain visible
Confirmed exactllyERP capability includes counterparty/party-wise open commodity position.
The buyer should ask:
How much have we already committed to buy from or sell to this party, how much has been fulfilled and what remains open?
This should be available without manually consolidating multiple contracts.
Weighted-average locked rate can matter across several contracts
Confirmed exactllyERP capability includes calculation of weighted-average locked rate for relevant open or fulfilled commodity positions.
The buyer should ask:
Across the quantity already booked, what is our weighted commercial rate?
That is different from simply averaging contract rates without considering quantities.
BOOKED RATE ≠ CURRENT MARKET RATE
The original commodity rate should remain the original commodity rate.
Confirmed exactllyERP capability includes:
- recording/importing a current/reference market rate for commercial comparison;
- reporting booked/locked rate versus current/reference rate difference;
- preserving the original contract rate unchanged.
The buyer should ask:
What did we lock, what is the current reference rate, and what does the difference tell us?
Do not automatically describe that difference as realised profit or loss.
Commercial outcome also depends on fulfilment, accepted quantity, processing, charges, sale value and other actual costs.
Physical Sauda management is not financial hedging
This distinction must remain explicit.
Physical commodity contracts and financial derivatives are different capabilities.
exactllyERP supports physical Sauda/commodity commitment control and current/reference-rate comparison.
exactllyERP does not currently provide commodity futures/options or other financial hedge-position management, mark-to-market exposure, hedge settlement or hedge accounting.
The buyer should ask separately:
Do we need ERP to manage only physical commodity commitments, or do we also require derivative/hedge management?
Do not infer hedge functionality from Sauda Booking or market-rate comparison.
GROSS WEIGHT ≠ NET MATERIAL
A vehicle or tanker movement may involve:
- gross weight
- − tare weight
- = net material quantity
Confirmed exactllyERP capability includes capture of gross, tare and net weighbridge values linked to the relevant Sauda/contract and inward receipt.
The buyer should ask:
Which physical quantity actually fulfilled the contract?
The weighbridge record should not remain isolated from the commercial commitment.
Keep vehicle or tanker identity connected to the inward
Confirmed exactllyERP capability includes vehicle/tanker identification linked to the weighbridge and inward transaction.
The buyer should be able to ask:
Which vehicle or tanker delivered this quantity against this contract?
That connection matters for physical traceability and reconciliation.
Match the inward receipt to the original Sauda
Confirmed exactllyERP capability includes matching the inward receipt directly to the originating Sauda/commodity contract.
The buyer should test:
Receive one tanker against a multi-load Sauda. Which contract did it fulfil, and what quantity remains open afterwards?
The original commitment should remain visible from the inward record.
CONTRACTED QUANTITY ≠ DELIVERED QUANTITY ≠ ACCEPTED QUANTITY
These can be three different truths.
Confirmed exactllyERP capability includes identifying short/excess quantity between:
The buyer should ask:
What was promised, what physically arrived, and what did we finally accept for commercial settlement?
Do not assume these quantities are always identical.
Quality can affect accepted value at inward
Different oilseeds and edible oils can require different quality parameters.
Confirmed exactllyERP capability includes configurable inward quality parameters by seed/oil/material type and actual inward quality results linked to the specific receipt/batch.
The buyer should ask:
Which quality basis governed this receipt, what actual values were recorded and what commercial consequence followed?
Do not hard-code one universal parameter list.
Quality-based deductions and allowances should be governed
Confirmed exactllyERP capability includes quality-based procurement deductions/allowances according to configured commercial terms.
The buyer should ask:
If delivered quality differs from the agreed basis, how is the commercial adjustment calculated and approved?
This should be rule-driven rather than reconstructed after settlement.
Accepted commercial quantity or value should reflect approved adjustments
Confirmed exactllyERP capability includes accepted commercial quantity/value reflecting approved quality adjustment where required.
The buyer should distinguish:
- what physically arrived;
- what quality result was recorded;
- what was commercially accepted;
- what value is payable.
These are related but not necessarily identical.
Supplier settlement should close the inward commercial chain
Confirmed exactllyERP capability includes supplier settlement connected to:
- contract rate;
- accepted quantity;
- approved commercial adjustments.
The buyer should ask:
Can we explain the supplier payable from the original Sauda through actual accepted quantity and approved deductions or allowances?
That is the real close of the purchase-side commodity chain.
BULK OIL ≠ PACKED SKU
A company may simultaneously hold:
These are not the same inventory problem.
The buyer should ask:
How much oil do we have, in what state, in which tank or location, and how much has already become a packed SKU?
A single total “oil stock” figure can hide too much.
FOLLOW THE OIL
The second Edible Oil signature principle is:
FOLLOW THE OIL
Depending on the operating model, the physical chain may be:
- supplier / seed / crude oil
- vehicle/tanker
- weighbridge
- accepted inward batch
- tank
- crushing/refining/blending stage
- refined/blended tank
- packing run or tanker loading
- finished SKU / bulk dispatch
- customer
The buyer should ask:
Can we select one physical quantity and follow what happened to it without changing systems or reconstructing the story later?
Tank inventory should represent physical custody
Not every Edible Oil business operates tanks.
Where bulk-liquid storage matters, confirmed exactllyERP capability includes tank-wise inventory that can separately identify:
The buyer should ask:
Which tank holds what oil, how much, from which source and in what current status?
Tank transfer should preserve source context
Confirmed exactllyERP capability includes tank-to-tank transfers preserving:
- oil type;
- quantity;
- relevant batch/source identity.
The buyer should test:
Move bulk oil from Tank A to Tank B. Can we still explain where that quantity came from?
Transfer should not erase the source record.
Tank capacity and available quantity can influence the next movement
Confirmed exactllyERP capability includes monitoring tank capacity, minimum/reorder level and current available quantity where required.
The buyer should ask:
Before receiving or transferring another tanker, what capacity is genuinely available in the intended tank?
Do not imply every customer requires tank minimum/reorder logic.
Weight, volume and density should remain reconcilable
Confirmed exactllyERP capability includes relevant weight/volume/density handling in tank/bulk inventory while preserving the commercial/inventory quantity basis.
The buyer should ask:
Which quantity is physically measured, which quantity is commercially controlled, and what density/conversion basis connects them?
Do not assume every oil or process uses the same conversion basis.
Tank commingling requires an explicit genealogy rule
Commingling is more complex than ordinary transfer.
Multiple source batches may enter one tank and later be partially withdrawn.
Confirmed exactllyERP capability includes preserving/reconstructing the relevant source genealogy for commingled tank withdrawals using an assumed/calculated FIFO basis.
That boundary should remain explicit.
The buyer should ask:
If several source batches are commingled and we later withdraw part of the tank, what source genealogy does the system assign to the withdrawal?
For exactllyERP, that source attribution is calculated on FIFO basis.
Do not imply that FIFO reconstruction is a measured physical layer-by-layer identification of the liquid inside the tank.
Crushing should reconcile seed into all material outcomes
Where crushing applies, confirmed exactllyERP capability includes separately recording:
- oilseed input;
- crude-oil output;
- cake/meal or another relevant by-product;
- process loss.
The buyer should ask:
Where did the entire seed input go?
Do not evaluate extraction only by looking at oil output.
Refining should reconcile crude input into refined output and loss
Where refining applies, confirmed exactllyERP capability includes separately recording:
- crude-oil input;
- refined-oil output;
- relevant by-products;
- process loss.
The buyer should ask:
How much crude entered, what refined output resulted, what by-products were created and what process loss remains to be explained?
Refining stages should match the actual process
Confirmed exactllyERP capability includes configuring refining stages such as:
according to the actual process.
Do not imply every refinery uses every stage.
The buyer should ask:
At which stages do quantity, quality and cost materially change in our actual refinery?
Stage-wise input, output and loss should remain visible
Confirmed exactllyERP capability includes recording input/output/loss stage-wise through the configured crushing/refining process.
The buyer should ask:
At which stage did the quantity difference arise?
A final output percentage alone may not explain the process.
EXPLAIN THE RECOVERY
The third Edible Oil signature principle is:
EXPLAIN THE RECOVERY
Recovery is not just an output percentage.
It is an explanation of how material changed through the process.
Confirmed exactllyERP capability includes standard-versus-actual extraction/refining recovery comparison by batch and stage.
The buyer should ask:
What did we expect to recover, what did we actually recover and at which stage did the difference arise?
STANDARD YIELD ≠ ACTUAL RECOVERY
A crushing or refining batch may create:
The buyer should ask:
Can the system explain where the input quantity went — not merely calculate an output percentage?
Do not publish one universal Edible Oil recovery benchmark.
By-products should remain connected to their originating batch
Confirmed exactllyERP capability includes relevant by-products such as:
remaining linked to the originating batch.
These are examples, not universal outputs.
The buyer should ask:
Which secondary outputs have inventory or commercial value, and how do they affect the batch economics?
Blending creates another source-to-output relationship
Not every Edible Oil company blends oils.
Where blending applies, confirmed exactllyERP capability includes combining multiple source oils/batches into a defined blend batch.
The buyer should ask:
Which source oils formed this blend?
That relationship should remain visible after blending.
Record blend formula/ratio and actual source quantities
Confirmed exactllyERP capability includes recording:
- blend formula/ratio;
- actual source-oil quantities used.
The buyer should ask:
What blend was planned, and what source quantities were actually consumed?
Do not assume one universal blending basis.
Blend genealogy should work backward
Confirmed exactllyERP capability includes tracing the finished blend backward to all source oils/batches.
The buyer should test:
Take one finished blend batch and show every source oil/batch that contributed to it.
This should not depend on manually reconstructing tank movements.
Packing converts bulk inventory into commercial SKUs
A refined or blended oil source may feed several finished SKUs and pack sizes.
Confirmed exactllyERP capability includes packing runs recorded by:
- finished SKU;
- pack size;
- originating oil batch;
- packing batch/run;
- shift where required.
The buyer should ask:
Which bulk source fed this packing run, and which finished SKUs did it create?
Planned packing output should be compared with actual output
Confirmed exactllyERP capability includes planned-versus-actual packing output and separate packing loss/waste by run/batch.
The buyer should ask:
How much bulk oil entered packing, how many saleable packs resulted and what quantity remains as packing loss or balance?
Do not hide packing loss inside a general inventory adjustment.
Bulk-to-pack genealogy should work in both directions
Confirmed exactllyERP capability includes bulk-to-pack genealogy from packed finished-goods batch back to the refined/blended source batch or tank.
The buyer should test both directions.
Forward:
- refined/blended source
- packing run
- packed batch / SKU
- warehouse / customer
Backward:
- customer packed batch
- packing run
- refined/blended source
This closes the physical chain from bulk oil into marketable SKU.
A full-tanker sale should use the bulk inventory path
Some Edible Oil businesses sell complete tanker loads directly from bulk inventory.
Confirmed exactllyERP capability includes full-tanker bulk sales/dispatch directly from bulk/tank inventory while preserving:
- quantity;
- batch/source;
- customer;
- commercial-document traceability.
The buyer should ask:
Can a bulk tanker sale be fulfilled directly from bulk inventory without pretending that the product was first converted into a packaged SKU?
Bulk and packaged fulfilment should follow the appropriate inventory path.
Actual economics should survive the commodity-to-pack conversion
A useful economic chain may be:
- booked/acquisition basis
- accepted quantity
- processing cost
- recovery
- by-product effect
- packing cost
- finished SKU cost
- selling value
- applicable channel effects
- actual commercial result
Relevant confirmed Exactlly capabilities already include actual production costing, by-product treatment and net SKU commercial/margin analysis.
The Edible Oil-specific buyer question is:
Can the economic record remain connected from original commodity commitment through bulk processing and packing into the final sale?
Do not impose one universal margin formula.
Job work should preserve material ownership and recovery
Some Edible Oil companies use job-work or toll processing.
Relevant confirmed Exactlly Manufacturing capability includes:
- material issue;
- outstanding quantity;
- return reconciliation;
- processing cost.
The Edible Oil buyer should ask:
If seed or oil leaves our premises for processing, can we reconcile what quantity left, what came back, what by-products or loss resulted and what cost belongs to the job work?
Do not re-teach the entire Manufacturing job-work framework here.
Use it to test continuity of physical quantity and recovery.
Schemes, distribution, credit and collections still matter after packing
Once oil becomes packaged FMCG inventory, the existing FMCG buyer questions still apply where relevant:
The Edible Oil guide should not duplicate the complete FMCG guide.
Its distinctive centre remains:
commodity commitment → physical quantity → bulk custody → recovery → bulk/pack conversion → economics.
Decide what belongs in ERP, weighbridge, plant, lab and other connected systems
Not every Edible Oil function has to live in one application.
An operating environment may include:
The buyer should ask:
Which system owns the Sauda/physical contract?
Which system owns weighbridge quantity?
Which system owns accepted inward quantity?
Which system owns tank stock?
Which system owns crushing/refining batch execution?
Which system owns blend genealogy?
Which system owns packing output?
Which system owns actual cost and settlement?
What happens when an interface fails?
Do not assume one application should replace every specialist system.
The goal is one trustworthy operating and commercial record.
Make the vendor demonstrate the difficult Edible Oil scenarios
Do not allow the ERP demonstration to become a tour of Sauda masters, tank reports and production screens.
Give every shortlisted vendor the same difficult scenarios.
Record what is standard, configured, extended or custom
After every important Edible Oil scenario, classify how the proposed result is delivered.
The proposed product supports the requirement as part of its normal capability.
The result depends on masters, rules, workflow, quality parameters, stages, tank structure or other configurable behaviour.
Another application such as weighbridge, plant/MES, lab, market-rate feed or DMS forms part of the proposed solution.
Development is required specifically for the requirement.
The claim remains proposed until evidence is provided.
None of these labels is automatically good or bad.
The buyer needs to know what will actually exist in production.
Edible Oil ERP red flags
Sauda exists only in a spreadsheet
The original commodity commitment is outside the operating system.
Purchase or sales order is created later with no retained original commitment
The business cannot reconstruct what was originally agreed.
Contract rate is stored but open quantity is not
Commercial exposure is incomplete.
Partial receipts or dispatches do not reduce the open commitment correctly
The remaining position cannot be trusted.
Contract amendment overwrites the original
Commercial history is lost.
Broker position must be manually consolidated
Broker exposure is not operationally visible.
Weighted rate is manually calculated
Management cannot reliably understand aggregate booked position.
Current/reference rate overwrites the booked rate
The original commercial truth is lost.
Reference-rate difference is presented as realised profit
Commercial comparison is being mistaken for actual outcome.
Sauda is presented as hedge management
Physical contracts and financial derivatives are being confused.
Weighbridge values are retyped manually
Physical quantity can diverge from the machine record.
Gross/tare/net is disconnected from the contract
The load does not close against the commercial commitment.
Vehicle/tanker identity is lost after inward
Physical movement context is incomplete.
Contracted, delivered and accepted quantities are treated as identical
Short/excess and quality-adjustment effects disappear.
Inward quality result has no commercial consequence where it should
Settlement does not reflect agreed terms.
Supplier deduction is manually calculated later
Quality and commercial settlement are disconnected.
Bulk inventory is only a warehouse-level quantity
Physical tank custody is not visible.
Tank transfer loses source identity
Bulk genealogy breaks during internal movement.
Tank commingling is claimed without a defined source-allocation rule
Withdrawal genealogy is ambiguous.
FIFO-based commingling reconstruction is presented as measured physical identity
Calculated genealogy is being overstated.
Crushing records only oil output
Cake/meal and loss are missing from the material balance.
Refining records only finished output
The process cannot explain where crude input went.
Yield percentage exists without stage-wise input/output/loss
Recovery is a KPI rather than an explainable material balance.
By-products are posted as miscellaneous stock
Their connection to the originating batch and economics is lost.
Blend batch cannot identify source oils
The finished blend has no backward genealogy.
Packing converts bulk oil to SKUs without source genealogy
Bulk-to-pack traceability is broken.
Packing loss appears only as an inventory adjustment
The production record cannot explain conversion loss.
A full-tanker sale is forced through packaged-SKU logic
Bulk and packaged fulfilment are being conflated.
Actual SKU cost ignores recovery, by-products or packing effect
Commodity-to-margin economics are incomplete.
Job work breaks quantity/recovery reconciliation
Material ownership and recovery become uncertain outside the plant.
FMCG scheme detail overwhelms the Edible Oil evaluation
The guide is testing distribution rather than the distinctive commodity/bulk/process problem.
Customer proof is merely “an Edible Oil company uses our ERP”
The reference does not reduce uncertainty about Sauda, bulk custody, recovery or conversion.
A practical Edible Oil ERP evaluation record
For each critical workflow, record the evidence.
| Evaluation area | What the buyer should establish |
|---|---|
| Operating model | Where the business begins and ends |
| Purchase Sauda | What was committed to buy |
| Sales Sauda | What was committed to sell where applicable |
| Counterparty | Who the commercial commitment is with |
| Broker | Which intermediary applies where relevant |
| Booked quantity | What quantity is contractually committed |
| Booked rate | What original commercial rate was agreed |
| Booking date | When the commitment was made |
| Delivery window | When fulfilment is expected |
| Contract history | How amendments/cancellations are preserved |
| Fulfilled quantity | What quantity has actually closed against the contract |
| Open quantity | What remains outstanding |
| Broker exposure | What is open through each broker |
| Counterparty exposure | What is open with each party |
| Weighted locked rate | How multiple booked positions are combined |
| Reference market rate | What comparison rate is used |
| Booked vs reference | How the difference is reported without changing booked rate |
| Brokerage liability | How brokerage is calculated |
| Hedge requirement | Whether futures/options/hedge accounting are required |
| Weighbridge gross | What loaded gross weight is captured |
| Tare | What vehicle/tanker tare is captured |
| Net material | What net physical quantity results |
| Vehicle / tanker | Which physical movement belongs to the inward |
| Contract match | Which Sauda the receipt/dispatch fulfils |
| Delivered quantity | What physically arrived |
| Accepted quantity | What quantity is commercially accepted |
| Short/excess | How quantity difference is handled |
| Inward quality | Which parameters govern the receipt |
| Quality result | What actual values were recorded |
| Quality adjustment | What deduction/allowance applies |
| Accepted value | How approved adjustment affects commercial basis |
| Supplier settlement | How payable closes from contract to acceptance |
| Bulk-oil category | Crude/refined/buffer/other state |
| Tank | Where physical bulk stock is held |
| Tank transfer | How source/quantity survives movement |
| Tank capacity | How usable/available capacity is monitored where required |
| Dual-UOM / density | How weight/volume basis is reconciled |
| Tank commingling | How source attribution works after mixing |
| FIFO genealogy | How assumed/calculated source withdrawal is reconstructed |
| Crushing input | What oilseed quantity enters |
| Crushing output | What crude oil results |
| Crushing by-product | What cake/meal or other output results |
| Crushing loss | What difference remains |
| Refining input | What crude quantity enters |
| Refining output | What refined quantity results |
| Refining by-product | What secondary output results |
| Refining loss | What difference remains |
| Refining stages | Which actual stages apply |
| Stage-wise balance | Where input/output/loss changes |
| Standard recovery | What recovery was expected |
| Actual recovery | What actually occurred |
| Recovery variance | Where the difference arose |
| By-product genealogy | Which batch produced the by-product |
| Blend batch | Which sources form the blend |
| Blend formula/ratio | What combination was planned |
| Actual blend quantities | What sources were actually consumed |
| Blend genealogy | How finished blend traces to sources |
| Packing run | Which bulk source feeds packing |
| Finished SKU | What commercial SKU is produced |
| Pack size | Which pack format applies |
| Packing batch/run | Which run created the finished stock |
| Shift | Which shift applies where required |
| Planned pack output | What output was expected |
| Actual pack output | What output was produced |
| Packing loss | What conversion loss/waste occurred |
| Bulk-to-pack trace | How packed batch traces to oil source |
| Bulk tanker sale | How direct bulk fulfilment works |
| Packaged fulfilment | How packaged order is fulfilled |
| Actual cost | How commodity, process and packing cost connect |
| By-product economics | How secondary outputs affect economics |
| Margin | How resulting commercial position is derived |
| Job work | How external processing quantity/recovery is reconciled |
| System boundary | ERP/weighbridge/plant/lab/DMS ownership |
| Delivery method | Standard / configuration / extension / custom / not demonstrated |
| Follow-up | What evidence remains unresolved |
Do not turn this into a percentage score.
One unresolved commodity-position, weighbridge, recovery, bulk-custody or genealogy requirement can matter more than many minor feature matches.
What customer proof should an Edible Oil ERP vendor provide?
A useful customer reference is not simply another edible-oil company.
Ask for proof closest to the uncertainty you are trying to remove.
If your concern is Sauda control, ask:
Which customer can show the original commodity commitment, partial fulfilment and remaining open position?
If your concern is bulk handling, ask:
Which customer can show bulk/tanker inventory and the appropriate fulfilment path without pretending everything is packaged stock?
If your concern is job work, ask:
Which customer can reconcile material issued for processing with returned output and the financial record?
If your concern is distribution, ask:
Which customer operates packaged SKU / pack-size inventory across multiple warehouses and fulfilment flows?
If your concern is commodity-to-finance continuity, ask:
Which customer can show that the commercial commitment, operational fulfilment, invoicing, receivables/payables and management reporting remain connected?
Customer evidence should validate the difficult workflow.
Not decorate the proposal.
Relevant operating evidence: ANA Oils
ANA Oils provides the strongest current Exactlly proof for the distinctive Edible Oil operating chain.
Approved evidence includes:
- a ₹7,500 crore business context;
- 7+ year Exactlly relationship;
- intraday commodity-rate context;
- Sauda Booking;
- rate / quantity / counterparty;
- customer, broker and salesman credit controls;
- Head Office approval;
- full-tanker fulfilment where applicable;
- own-plant manufacturing;
- job work;
- multi-plant operations;
- multiple warehouses;
- bulk oil;
- packaged SKU / pack-size inventory;
- warehouse allocation;
- invoicing + e-way bill;
- distribution;
- finance / AR / AP;
- Banking API;
- MIS / management reporting.
The strongest proof role is:
COMMODITY COMMITMENT → OPERATIONS → FINANCE
ANA shows that a commodity-driven commercial commitment can remain connected to operational fulfilment and financial control in a real Edible Oil environment.
It should not be used to claim customer-confirmed proof of every stage-specific crushing/refining, tank-commingling or recovery capability in this guide.
Those capabilities are governed current exactllyERP product truth.
The customer story proves the connected Edible Oil operating environment.
The product demonstration must prove the buyer’s specific workflows.
How exactllyERP fits into this evaluation
exactllyERP should be evaluated against the same difficult Edible Oil scenarios.
Do not ask Exactlly only:
“Do you support Edible Oil?”
Bring the actual operating model.
Include:
- purchase Sauda process;
- sales Sauda process where applicable;
- counterparty/broker model;
- quantity and rate;
- delivery windows;
- amendment/cancellation process;
- open-position reporting;
- market/reference-rate source;
- brokerage terms;
- weighbridge process;
- vehicle/tanker process;
- accepted quantity;
- inward quality parameters;
- quality deductions/allowances;
- supplier settlement;
- tank structure;
- tank categories;
- tank transfers;
- commingling;
- FIFO genealogy basis;
- crushing process;
- refining process;
- actual stages;
- expected and actual recovery;
- by-products;
- blending;
- packing;
- bulk tanker sales;
- packaged fulfilment;
- job work;
- actual costing;
- connected-system boundaries.
Confirmed exactllyERP Edible Oil capabilities
Confirmed current Edible Oil capability includes:
- purchase Sauda/commodity contracts recording oilseed/oil type, counterparty, broker where applicable, quantity, agreed rate, booking date and delivery window;
- sales Sauda/commodity contracts recording quantity, rate, counterparty, broker and delivery terms where used;
- original agreed Sauda/contract rate locked and preserved;
- one purchase Sauda fulfilled through multiple inward receipts;
- one sales Sauda fulfilled through multiple dispatches where applicable;
- contracted, fulfilled and open/balance quantity visible;
- delivery schedule/window and fulfilment tracking;
- contract amendment/cancellation preserving original and revised commercial history;
- broker-wise open contract/exposure position;
- counterparty/party-wise open commodity position;
- weighted-average locked rate for relevant open/fulfilled positions;
- current/reference market rate recorded/imported for commercial comparison;
- booked/locked rate versus current/reference rate difference reported without changing the original contract rate;
- brokerage liability calculated against actual fulfilled quantity/value according to configured terms;
- gross, tare and net weighbridge values captured and linked to relevant Sauda/contract and inward receipt;
- vehicle/tanker identification linked to weighbridge/inward;
- inward receipt matched directly to originating Sauda/commodity contract;
- short/excess quantity between contracted, delivered and accepted quantity identified;
- configurable inward quality parameters by seed/oil/material type;
- actual inward quality results linked to the specific receipt/batch;
- quality-based procurement deductions/allowances calculated according to configured commercial terms;
- accepted commercial quantity/value reflecting approved quality adjustment where required;
- supplier settlement connected to contract rate, accepted quantity and approved commercial adjustments;
- tank-wise inventory separately identifying crude oil, refined oil, buffer/holding stock or other customer-defined oil categories;
- tank-to-tank transfers preserving oil type, quantity and relevant batch/source identity;
- tank capacity, minimum/reorder level and current available quantity maintained/monitored where required;
- tank/bulk inventory using relevant weight/volume/density handling while preserving commercial/inventory quantity basis;
- crushing batch separately recording oilseed input, crude-oil output, cake/meal or another relevant by-product and process loss;
- refining batch separately recording crude-oil input, refined-oil output, relevant by-products and process loss;
- refining stages such as degumming, neutralisation, bleaching, deodorisation, winterisation or other customer-defined stages configured according to the actual process;
- input/output/loss recorded stage-wise through the configured crushing/refining process;
- standard versus actual extraction/refining recovery compared by batch and stage;
- relevant by-products such as cake/meal, soapstock, acid oil or other customer-defined outputs linked to the originating batch;
- multiple source oils/batches blended into a defined blend batch;
- blend formula/ratio and actual source-oil quantities recorded;
- blend genealogy tracing finished blend backward to all source oils/batches;
- packing runs recorded by finished SKU, pack size, originating oil batch, packing batch/run and shift where required;
- planned versus actual packing output and packing loss/waste recorded separately by run/batch;
- bulk-to-pack genealogy tracing a packed finished-goods batch back to the refined/blended source batch or tank;
- full-tanker bulk sales/dispatch executed directly from bulk/tank inventory while preserving quantity, batch/source, customer and commercial-document traceability.
Confirmed advanced tank-commingling capability
When multiple source batches are commingled into one tank and later partially withdrawn, exactllyERP can preserve/reconstruct the relevant source genealogy using an assumed/calculated FIFO basis.
This is a governed calculation rule.
It should not be described as measured physical source-layer identity inside the tank.
One advanced capability not currently supported
exactllyERP does not currently provide:
commodity futures/options or other financial hedge-position management, mark-to-market exposure, hedge settlement or hedge accounting.
Physical Sauda/commodity commitment control and current/reference-rate comparison should not be presented as equivalent to hedge management.
Relevant confirmed broader Exactlly capabilities also apply, including:
- multi-plant production;
- multi-location inventory;
- job-work material issue/outstanding/return reconciliation and processing cost;
- actual production costing;
- standard-versus-actual costing;
- yield comparison;
- by-product handling;
- batch/lot traceability where applicable;
- quality hold/release;
- tank/drum/IBC or similar container inventory where required;
- partial issue preserving lot/balance;
- dual-UOM / density handling;
- packed SKU / pack-size inventory;
- stock allotment/reservation;
- distributor schemes;
- credit control;
- collections;
- returns;
- net SKU commercial/margin analysis;
- finance and receivables/payables;
- management reporting;
- Banking API where implemented.
These broader capabilities should remain separate from the Edible Oil-specific truth set.
The relevant questions remain:
What did we commit to buy or sell, at what rate and quantity?
Where is that material now — in transit, tank, process, packed stock or dispatch?
What did the input actually become, and what did that do to cost and margin?
Edible Oil ERP Evaluation Checklist
Operating model
Purchase Sauda
Sales Sauda
Contract fulfilment
Contract history
Broker / counterparty exposure
Market-rate comparison
Hedge requirement
Weighbridge
Contract-to-inward
Accepted quantity
Inward quality
Quality-based commercial adjustment
Supplier settlement
Bulk-oil categories
Tank inventory
Tank transfer
Dual UOM / density
Tank commingling
Crushing
Refining
Refining stages
Stage-wise balance
Recovery
By-products
Blending
Packing
Packing output / loss
Bulk-to-pack genealogy
Bulk tanker sale
Actual cost / margin
Job work
Distribution / FMCG handoff
Integration / coexistence
Vendor evidence
the buyer is evaluating ERP as the evidence system for a real commodity-to-oil-to-market operation rather than as a list of purchase, tank, production and sales features.