ERP integration: how RevPrice talks to the system you already run
Every price RevPrice calculates starts from the cost already sitting in the ERP, and goes back to it once approved. This page explains both directions.
What changes from one operation to the next is not the calculation: it is where the data comes in and where it goes out. Before talking about method, it helps to separate what RevPrice reads from what it writes back.
What RevPrice reads from the ERP
These are the figures a price is made of, and they already live in the system the company buys, sells and invoices with.
- Cost of each receipt
- The acquisition cost of every incoming invoice, with freight, the taxes on that invoice and supplier rebates. It ages between two purchases, which is why a price calculated once is wrong the second time.
- Item registration
- What decides the tax on the sale: the tax classification code, the item regime and the destination state of the operation. Without sound registration, the rate applied is the one on file, not the one owed.
- Sales already made
- What left the shelf, at what price and through which channel. That is what makes it possible to compare the margin the rule calculated with the margin the operation actually earned.
- Product structure
- In manufacturing, the bill of materials: every component with the quantity that goes into one unit, the expected process loss and the time spent at each work centre.
What RevPrice writes back to the ERP
Reading cost is half the job. The other half is the approved price going back to the system that publishes prices.
- The approved price
- A price that cleared the margin rule and the approval goes back to the ERP to be published. That is where the point of sale, the shelf label and the customer price list are fed from.
- One price list
- Back office, checkout and shelf read the same price because it comes out of the ERP, and not out of a parallel spreadsheet kept beside it. Where labels are electronic, the path is the same.
- Who, when and why
- Every price change keeps the person who approved it, the date and the reason. That record stays in RevPrice, and what reaches the ERP is the decision already made.
How the exchange happens
The path depends on what the source ERP hands over. Which one applies to your operation is settled by the technical assessment, before rollout starts.
Through the ERP interface
When the source system exposes an interface of its own, reading the cost and writing the price back both go through it, with no file in between.
Through a purpose-built connector
When the ERP is custom built or exposes no interface, the integration team develops the connector for that system. It is the path for companies running software of their own.
Which of the two, and how often
That is what the technical assessment answers, with the source ERP in front of it: where the exchange happens, how often it runs and what changes when the system is upgraded.
The cadence on record is the one for reading cost: it follows the incoming invoice rather than a fixed hour of the day — when cost moves, the suggested price moves with it. How often each sync runs is settled during rollout.
One price figure sits in neither the ERP nor the purchase invoice: the competitor's. RevScan is what reads it, under competitor price monitoring, and the result leaves as Excel, as CSV or through an API into the ERP and the BI tool.
Which ERPs RevPrice integrates with
It is the first question anyone evaluating asks, and the honest answer is that a list does not answer it.
Revema Tech publishes no list of certified ERPs. What is on record is the method: when the source system exposes an interface, the integration goes through it; when it does not, the integration team develops the connector for that system. The deciding question is not whether your ERP is on a list — it is what it hands over as cost and as registration.
For a named ERP, the answer comes in writing out of the technical assessment: it looks at the source system and at the state of the registration, and that is where the timeline to the first batch of products going live comes from. With the integration in place and clean registration, that timeline is counted in weeks; with incomplete registration, cleaning it becomes the first stage of the project.
What the technical assessment settles
- Where the exchange happens in that ERP: its own interface, a connector or a file.
- The direction of each figure: what RevPrice reads and what it writes back.
- How often each sync runs, and what changes when the system is upgraded.
- What has to be ready on the ERP side: sound cost and sound registration.
How much each of those points weighs changes with the operation, which is why a price is not formed the same way in retail, distribution and manufacturing.
Anyone still building the shortlist criteria will find the full set under how to choose pricing software, where ERP integration is one of the items — and where the same question is asked from the buyer's side.
Questions about ERP integration
The doubts that come up during the technical assessment, answered with what Revema Tech has on record.
Is there a list of ERPs certified for RevPrice?
None is published. RevPrice was built to integrate with the ERP systems used in the market, and for custom systems the integration team develops purpose-built connectors. The answer for a named ERP comes in writing from the technical assessment, not from a list on the website.
Does the integration run one way or both ways?
Both ways. RevPrice reads the receipt cost, the item registration and the sales from the ERP, calculates the price under the company rules and writes the approved price back, which is what publishes at the point of sale and prints the label. Invoicing, stock and the till remain the job of the ERP.
Which figures leave the ERP for RevPrice?
The acquisition cost of every incoming invoice, with freight and taxes; the item registration, which decides the rate on the sale; the sales already made, to compare calculated margin against earned margin; and, in manufacturing, the product structure with components, process loss and time at each work centre.
How often is cost refreshed?
Reading cost follows the incoming invoice: when the cost of an item moves, its suggested price moves with it, with nobody reopening a file. How often each sync runs is defined during rollout, because it depends on what the source ERP hands over and how frequently it does so.
What has to be ready on the ERP side before starting?
Sound cost and sound registration, which is what the calculation works on. With the integration in place and clean registration, the first batch of products usually goes live within weeks; with incomplete registration, cleaning it becomes the first stage of the project, ahead of any new price.
Does competitor monitoring feed the ERP as well?
It does, by a different route. RevScan reads the price a competitor advertises and hands the result over as Excel or CSV, through an API into the ERP and the BI tool, or straight into the price analysis inside the platform. It is data from outside the company, so it does not come from the ERP.
Bring your ERP to the conversation
The integration team looks at the source system and the state of the registration, and answers in writing with the method, the direction of each figure and the timeline to the first batch.