The platform
Apex layers on the ERP you already run.
Apex does not ask you to move your catalog, your customers or your ledger. It reads them from the ERP into one foundation your company owns, runs quoting, pricing, orders, production and billing on top, and writes each result back to the ERP first, where your finance team already works.
The layers
Five layers, and the ERP stays at the bottom.
Each layer does one job. The ERP holds the posted record. The raw layer keeps the ERP's records exactly as they arrived. The one commerce model is what every tool reads. The tools do the work, and nothing consequential leaves without a person in the Approval Queue and a line in the audit.
- Raw records
- Kept verbatim and append-only, with a new version only when the ERP's content changes.
- One model
- Customers, items, prices, stock, orders and invoices, shared by every Ferrata product the company uses.
- Audit
- Every change written in its own transaction, with who made it and when.
- 05Approval Queue and auditEvery write waits for a person; every change recorded3 waiting
- 04Apex’s tools
- 03One commerce modelCustomers · items · prices · stock · orders · invoices48,210 rows
- 02Raw ERP recordsKept verbatim, versioned only when the ERP changes them61,904 records
- 01Your ERPSAP · NetSuite · Dynamics 365 · Rillet · the system of record
How it runs
Read, model, run, write back.
The same four steps whichever tool you start with, so the second tool you switch on reads the records the first one brought down.
- 01
Read
Customers, items, price lists, stock, orders and invoices come down from the ERP on a schedule, page by page.
- 02
Model
Each record is kept raw, then mapped into the one commerce model with its ERP identity carried on the row.
- 03
Run
Quotes, RFQs, price lists, sales orders, production and billing run on that model, with prices and costs calculated by code.
- 04
Write back
Sales orders, A/R invoices, credit notes and journals go to the ERP first, through one outbox, and are read back to confirm.
Who holds the record
The ERP wins, and you see it when it does.
The ERP is the record
Stock, prices, customers and orders default to the ERP as system of record, object by object.
Conflicts raise a warning
When an edit in Apex disagrees with the ERP, Apex shows the warning and the ERP's value holds.
Standalone when there is no ERP
A company without an ERP runs items, stock and invoices in Apex itself, on the same model.
One foundation
Add a second Ferrata product later and it reads the same records. Nothing is copied or mapped twice.
FAQ
Platform, run end to end.
What does Apex read from our ERP?
Customers and their addresses, items with their units, price lists and special prices, stock by location, quotations, sales orders, deliveries, invoices and journal entries. Each object is kept raw exactly as the ERP holds it, then mapped into the one commerce model the tools read.
What does Apex write back, and how?
Sales orders, A/R invoices, credit notes, journal entries and new customers, each only after a person approves it. Every write goes through one outbox: it is claimed once, the ERP is read before anything is written, and the result is read back to confirm it landed as written. On SAP Business One this runs today; on NetSuite and Dynamics 365 the same contract is built and checked on your own account when your instance is deployed.
What happens when Apex and the ERP disagree?
The ERP wins by default, object by object, and you see a warning. If a price edited in Apex conflicts with the price the ERP sends down, Apex keeps the ERP's value and shows you both, so nothing is overwritten silently in either direction.
Can we use Apex without an ERP?
Yes. A company without an ERP runs its items, stock, quotes, orders and invoices in Apex itself, on the same commerce model. When it adds an ERP later, the ERP becomes the record and Apex maps to it rather than starting over.
What happens when we add a second Ferrata product?
It reads the same foundation. Customers, items, orders and invoices are already there, so the second product switches on its own tools and rules without a second connection to the ERP or a second copy of the data.
Related in Apex
- IntegrationsWhat Apex reads and writes, by ERP.View
- One commerce modelGoods, services and plans, on one set of records.View
- Deployment optionsHosted, your VPC, on-prem or air-gapped.View
- Your data stays yoursPrices, costs and margins, private to you.View
- CPQConfigure, price and quote from the items and price lists already in your ERP.View
See Apex work on your own quote to cash.
Thirty minutes on one workflow, with your own quotes, orders or invoices. You leave with a view of where Apex fits, and an honest answer if the sequencing is wrong and you should fix something else first.
Your pricing, approval and billing rules are your advantage, and they stay yours. Apex is configured to the way you sell, make and bill. You are not handing over a playbook or fitting into a template.