Ayyra

Connecting Ayyra to your ERP

Ayyra reads four groups of fields from the system you already run, read-only, and never writes back. Through a direct connection, a scheduled export, or our own API.

Works with 10+ major ERPs

What Ayyra needs from your ERP

Four things, and nothing else. If your ERP can report them, Ayyra can work:

  • Sales lines, with the date, the depot and the quantity.
  • Stock on hand, broken down by depot.
  • Batches and their expiry or sell-by dates.
  • The principal or supplier each line belongs to.

The connection is read-only

Ayyra asks for read access and nothing more. It does not post an order, adjust a stock figure or change a price, so connecting it cannot break anything your team depends on.

That is usually the question IT asks first, and it is the reason a connection can normally be approved without a change-control process.

Three ways to connect

Which one suits you depends on what your ERP exposes and what your IT team prefers:

  • A direct read against the ERP's own interface, where it has one. Nothing to schedule and nothing to maintain.
  • A scheduled export your ERP already produces, dropped where Ayyra can pick it up. This is how most teams start.
  • Ayyra Connect, our API, when you want to push the data yourself or pull Ayyra's results into your own screens.

If your team runs on exports

That is fine, and it is common. A weekly extract with the four field groups above is enough for Ayyra to run the check. You do not need to replace a working process to get the list.

What it takes to set up

A conversation with whoever owns the ERP, read credentials or a scheduled export, and a confirmation of how your depots and units are named so Ayyra reads them the way your team does.

There is nothing to migrate and no second system for your team to type into. Orders are booked exactly as they are today.

Not sure your ERP can do this?

Tell us what you run and roughly how many lines and depots you have, and we will say plainly whether Ayyra can read it.