How the price sits against your inventory

Twelve months from signature, annual payment in advance against invoice with 14 days' payment terms. After that it renews for a year, cancellable with three months' notice.

The exit until day 90 is a clause of its own in the contract, not in the general terms. An email is enough, and nine months of the annual price are refunded within 14 days. If your IT delivers the export later than day 10, every date moves by those days — the decision date included.

No. The formula is the price, the same for every customer. What moves is the item count, and the first run counts it.

A trial on fifty items produces a plausible curve, not an effect. The first run calculates across all items and validates the result against last year. In exchange you carry the risk for three months instead of twelve.

Four files from your ERP: item master with MRP data, movements over 36 months, order history with goods receipt dates, open orders and requirements. Your criticality list, if you have one. Your IT gets an export specification with tables and fields for your ERP, plus a 20-minute briefing. The same export is needed monthly after that — your IT sets it up once as a recurring job.

As a parameter file with reorder point, safety stock, and min/max level per item, which your ERP imports as master data. SAP with MRP type VB, proALPHA, Infor LN, and Dynamics read exactly these fields. No interface, no project.

PartsOS is operated exclusively in Germany (ISO 27001-certified data centers, AWS eu-central-1). All data is encrypted both in transit (TLS 1.2+) and at rest (AES-256). There is no transfer of data to third countries without a separate agreement. You remain the data controller and retain control over your data (with options for export and deletion upon termination of the contract).

We calculate the parameters from two years of your history and validate them against the third, which never went into the model. For that year we replay your demand twice: once with the parameters from your ERP, once with ours — both using the real lead times from your goods receipts. Out of that come service level (the share of demand quantity served immediately from stock) and inventory in euros, for each variant. What the comparison does not capture is your planning team's manual interventions. That is why every item carries its reasoning, so your planner can hold it against their experience.

Then it is on page 1. You exit by day 90 and have a validated statement about your parameters for the price of three months.

Nothing new. One run a month, the quarterly review of the effect in the real warehouse, and a recount of the items once a year. The formula from the contract also applies on renewal.

After the first run, the review list: the items we flag because they move the most inventory or service level. Then monthly, reviewing the changes, approving or rejecting them, and loading the approved file into the ERP — in SAP as mass maintenance via MM17, and we supply the instructions. One-off: switching items with an automatically calculated reorder point (SAP VM) to VB, so SAP does not overwrite our values. We supply that list. Whatever your planning team rejects stays as it is.