Skip to content
Outrich Data

Data type

License your ERP records for AI training

ERP data can often be licensed for AI training once parties and prices are masked, because the records describe transactions more than people. Outrich Data is a direct buyer and deals with the operating company itself. It checks supplier, customer and software terms, replaces identifiers with placeholders, and pays you for a licensed copy that you approve in writing.

What counts as erp data

An ERP is the ledger of what your company bought, made, stored, moved and sold. Its tables hold purchase orders, goods receipts, bills of materials, production orders, inventory movements, sales orders, shipments, journal entries and the master data that ties them together: items, units of measure, warehouses and cost centers.

This page covers the business records themselves. The step-by-step audit trail of who clicked what is covered under workflow logs. An ERP tenant you run on behalf of a client, such as a third-party logistics provider holding a customer's stock records, contains that client's data and is excluded.

Why AI labs want it

Public tabular data is small, clean and disconnected. An ERP is large, messy and relational. One sales order links to a customer, items, a price list, a pick, a shipment, an invoice and a payment. AI labs working on models that reason over tables and databases need real schemas with that kind of linkage, including the duplicates and miscoded rows.

The records also contain planning decisions. A planner chose a reorder quantity, a buyer split an order across two suppliers, a scheduler moved a job. The data shows the situation before the decision and the result after it. Labs use that for forecasting, planning and anomaly detection, and for evaluations with a known answer.

Removed before licensing

What comes out first.

  • Customer and supplier names, addresses and tax IDs, replaced with stable placeholders
  • Unit prices, costs and margins, bucketed or scaled where they are sensitive
  • Bank account and payment details in vendor and customer master records
  • Employee names and IDs on approvals, timesheets and expense lines
  • Payroll and benefits tables, excluded in full
  • Free-text memo and description fields that name people or deals
  • Unreleased financial results of a public company

Data title search

What gets checked.

  • Supplier agreements. Negotiated pricing and terms are often confidential under the supply contract, which is why prices are masked or dropped.
  • Customer contracts. Order and shipment records can fall under customer NDAs and DPAs even after names are replaced.
  • ERP vendor license. Your transaction data is generally yours, but some agreements restrict disclosing the vendor's data model or documentation. Check before exporting schema details.
  • Securities law. A public company, or a supplier to one, should confirm with counsel that no material non-public information leaves in the dataset.
  • Lender and investor covenants. Some credit agreements restrict disclosure of financial records or transfers of assets outside the ordinary course.
  • Personal data. Sole-proprietor suppliers and individual customers are people. GDPR and CCPA can apply to their records.

Who signsThe CFO or COO sponsors it, since the records span finance and operations. The general counsel approves the license and the ERP administrator or head of IT runs the extract.

Value

What moves the price of erp data.

FactorEffect on value
Linked documentsOrder, receipt, shipment, invoice and payment records that join cleanly are generally worth more than isolated tables.
Years of historySeveral seasons of demand, supply and price movement support forecasting work that a short extract cannot.
Master data qualityConsistent item, unit and location coding reduces the cleanup a lab would otherwise have to do.
Operational varietyReturns, backorders, substitutions and write-offs make the data more instructive than a record of perfect orders.
A data dictionaryField definitions and custom-field notes shorten review and raise interest.

Industries where this is common

Questions

Licensing erp data: what companies ask.

Would a buyer be able to see what we pay our suppliers?
Not if prices are treated as sensitive, which is the default. Costs and prices can be removed, banded or multiplied by a constant so ratios and trends survive while real figures do not. Supplier names are replaced with placeholders. You approve the method.
Our ERP is heavily customized. Does that hurt?
Usually not. Custom fields and tables are part of what makes real systems hard, and that is useful to a lab. What helps is a short data dictionary explaining what each custom field means. The free schema inferrer on this site can draft one in your browser.
Is the general ledger included?
Only if you choose to include it. A company can offer operational records such as orders and inventory and hold back the ledger. Where journals are included, account balances can be scaled and payroll entries are excluded.
We are a subsidiary. Who has to agree?
That depends on your group structure, intercompany agreements and financing documents. A parent, a lender or a board may need to consent. Outrich Data asks about this during the rights review, and your counsel confirms who must sign.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc