Read-only by default
The only thing Distrify writes back is an order. Nothing else in your ERP is touched unless you explicitly ask for it.
Distrify is a layer in front of your ERP, your business system, not a replacement for it. It reads what the ERP already knows, publishes it, and writes orders back in the format the ERP expects.
Every integration project that fails does so for the same reason: it created a second place where the truth might live. Distrify is built to never be that second place. Stock, prices and customers belong to the ERP; Distrify reads them, presents them and hands orders back.
That constraint is what makes the first version arrive in days. There is no migration, no cutover weekend, and no period where two systems disagree about what is in the warehouse.
proALPHA calls Distrify from the Integration Workbench. Days for the first use case, built by their proalpha partner.
Open 02ALPHAPLAN calls Distrify over its REST API, a live data connection. Days for the first use case, built by their own team.
Open 03abas calls Distrify from abas Connect or an ESDK app. Days for the first use case, built by their team or abas partner.
Open 04Distrify gets registered as an API, a live data connection, inside Infor OS. One registration, then it is available everywhere, built by their infor administrator.
Open 05Sage X3 calls Distrify with its built in REST client. Days for the first use case, built by their sage partner or it.
Open 06An extension calls Distrify, or Power Automate does it with no code. Days with a developer, hours without one, built by their partner, or nobody.
Open 07A C/AL codeunit calls Distrify, or middleware does it without touching NAV. Days with their NAV partner, built by their nav partner, or nobody.
Open 08A B1if scenario calls Distrify and writes the answer back. Weeks with their partner, built by their sap business one partner.
Open 09One endpoint, three ways in. At least one always fits. Hours for the no-code route, built by their team, or nobody.
OpenA REST API if there is one, an SFTP drop, a scheduled Excel export, or a read-only database view. The oldest system we have connected exports a fixed-width text file overnight, and that is enough.
The import copilot matches columns, flags the values that do not look like the others, and stores the mapping so every subsequent file runs unattended.
Changes are diffed against the current catalog. What changed is published; what did not is left alone, so a channel is never rewritten wholesale for a handful of updates.
An order placed on any channel is posted to the ERP in its own format, with the customer, terms and part numbers the ERP expects, so nothing downstream has to change.
The only thing Distrify writes back is an order. Nothing else in your ERP is touched unless you explicitly ask for it.
Distrify holds a published projection of your data, not an authority over it. Disconnect it and the ERP is unchanged.
Operated by Automates UG in Germany, with customer and pricing data held in the EU.
Your catalog, prices and customers are never used to train a shared model.
Thirty minutes on your own parts: send us a price list and we show it running live across every channel.
We reply within one working day. No newsletter, no drip campaign.