StreamEdgeSolutions

API & Integrations · Connections

ERP Integration Service

Connect your ERP to the systems around it, once we have proved it can be connected

Buy now

From$1,499USD one-off

One payment. Work starts once we have confirmed your requirements.

The four questions this page answers

  1. 1

    What you buy

    A one-off remote project connecting the ERP your business runs on to another system, so figures stop being exported and re-typed between them. Whether it can be done at all depends entirely on what your ERP exposes, which is why a paid feasibility review comes first and is the honest part of this product.

  2. 2

    What you get

    5 deliverables, listed in full below

    • A written feasibility report on what your ERP exposes and on what terms
    • A documented field mapping and system-of-record decision
    • One working integration flow between the ERP and one other system
    + 2 more
  3. 3

    How it is delivered

    Remote Setup

    Carried out remotely by our team. Nothing is posted and no one visits.

    REMOTE SERVICE

  4. 4

    How long it takes

    Feasibility review in 1–2 weeks; the integration 3–6 weeks after it, where the review says it is possible

    Measured from the point everything under “what we need from you” is with us, not from the moment you pay.

Your system connected to an external system through an integration layer — illustrative concept, not a screenshot of a client system
Your system connected to an external system through an integration layer. Illustrative interface concept — not a screenshot of a client deployment.

What is this, in plain English?

A one-off remote project connecting the ERP your business runs on to another system, so figures stop being exported and re-typed between them. Whether it can be done at all depends entirely on what your ERP exposes, which is why a paid feasibility review comes first and is the honest part of this product.

ERP integration is the area where suppliers most often promise first and discover later. Some ERPs publish a documented API and the work is ordinary. Others expose nothing but a nightly file export, a database the licence forbids you to read, or an interface module the vendor sells separately. We review your specific installation and version before any development, report plainly what is possible, and where the answer is that the job cannot be done this way, we say so and stop.

The problem it solves

Your ERP holds the authoritative numbers, and every other system in the business is fed from it by somebody exporting a file and re-typing the contents into something else.

If that does not describe you, this is probably the wrong product. Tell us and we will point you at a better fit rather than sell you the nearest one.

What you get

The concrete things that exist at the end and that you own.

5 deliverables

  • A written feasibility report on what your ERP exposes and on what terms
  • A documented field mapping and system-of-record decision
  • One working integration flow between the ERP and one other system
  • An exceptions queue and failure alerting
  • Technical documentation for whoever maintains it next

What's included

The work covered by the figure in the buy box, at no extra cost.

  • Feasibility review of one ERP installation
  • One integration flow to one other system
  • Field mapping and system-of-record documentation
  • Queuing, retry and idempotent processing
  • Exceptions queue and failure alerting
  • Parallel-run verification before go-live

Not seeing something you expected? Check what you are not buying before you order.

What does it do?

Everything listed here is delivered as part of this product. Nothing on this list is aspirational.

  • A paid feasibility review of your specific ERP, its version and its licence terms
  • A written statement of what the ERP genuinely exposes, and what it does not
  • One integration flow built between the ERP and one other system
  • Field mapping and a system-of-record decision agreed in writing before development
  • Queuing and retry, so an ERP batch window does not lose records
  • An exceptions queue for records the ERP rejects
  • Failure alerting and a run log for diagnosis

How it works

The delivery sequence from order to handover.

  1. 1

    Feasibility review, done first and paid for

    We examine your ERP’s version, its API or export capability, and the licence terms governing access to its data. This is the deliverable that decides whether anything else is possible.

  2. 2

    Report honestly

    You get a written answer: a full API integration, a limited file-based one, or that it cannot be done this way at all. Where the answer is no, we stop and settle under the refund policy rather than building something that cannot work.

  3. 3

    Agree the mapping

    Field by field, including which system is authoritative and what happens to records with no home on the other side.

  4. 4

    Build against a test company

    Development runs against a test or copy company file, never against your live ERP data.

  5. 5

    Parallel run

    One period is run both the old way and the new way and the two are compared, before anyone relies on it.

  6. 6

    Go live with exceptions

    Records the ERP rejects are queued for a person, never silently dropped, and failures raise an alert.

Delivery & fulfilment

Stream Edge Solutions ships nothing. Every package on this site is carried out and handed over remotely — this is exactly what happens after you order.

REMOTE SERVICEHow this is delivered
  1. 1We confirm requirementsWe read what you sent with the order, come back in writing with anything missing, and agree the scope before any chargeable work starts.
  2. 2We build and configure remotelySetup, configuration and testing are done by our team over a remote connection — on your systems or on ours, whichever the package specifies.
  3. 3We hand it overYou receive the working setup, the credentials, the documentation and a walkthrough. Everything built for you is yours at handover.

Carried out remotely by our team. Nothing is posted and no one visits. Typical turnaround: Feasibility review in 1–2 weeks; the integration 3–6 weeks after it, where the review says it is possible.

Delivery method
Remote Setup
Expected delivery time
Feasibility review in 1–2 weeks; the integration 3–6 weeks after it, where the review says it is possible
Measured from the point everything under “what we need from you” is with us — not from the moment you pay.

Full detail of how work is handed over, what happens if requirements are outstanding and how order records are kept is in the Delivery & Fulfilment Policy.

What we need from you

Nothing starts until these are in place, and the turnaround above is measured from that point — not from the moment you pay.

  • Your ERP name, version and hosting arrangement, plus the licence terms covering access to its data
  • An account and API credentials issued to your business by the ERP vendor or your implementer
  • A test or copy company file for development, where one can be produced
  • A decision-maker who can settle which system is authoritative for each field
  • Acceptance that feasibility is decided by what the ERP vendor exposes, not by us

Who this is for

  • Manufacturers and distributors running an ERP alongside other tools
  • Businesses whose website and ERP hold the same stock figures separately
  • Finance teams re-keying ERP figures into reporting spreadsheets
  • Companies told by another supplier that their ERP "cannot integrate"
  • Organisations on an older on-premises ERP version

Business needs this addresses: Improve operations, Integrate systems

What's not included

Just as plainly as the list above: the things this package is not.

  • ERP licence, module and user fees, which you pay your ERP vendor directly, including any interface or API module they sell separately
  • Work your ERP cannot support. If the feasibility review finds no usable route we report that and cancel or rescope under the refund policy, rather than building a fragile workaround
  • Reading an ERP database directly where the vendor’s licence forbids it, which we will not do even where it is technically possible
  • Changes inside the ERP itself, its customisations or its business logic
  • ERP implementation, configuration or consultancy, which belongs to the vendor or your implementer
  • Any partner, reseller or certified status with an ERP vendor, which we do not hold and do not claim

Anything outside the scope above is quoted separately, in writing, before it is carried out. Nothing is added to your bill without your agreement.

FAQs

What if our ERP has no usable API?

Then the honest answer is that the job cannot be done that way, and the feasibility review exists to reach it before you have paid for development. Some ERPs offer only a scheduled file export, which supports a one-way batch integration but not live two-way sync. Where nothing usable exists at all we say so, hand over the written finding, and settle under the refund policy.

Our ERP vendor sells an interface module. Do we still need you?

Possibly not, and we will say so if their module does what you need. Where a vendor charges for API access, that fee is yours and is paid to them directly. We build against what your licence entitles you to use, and we cannot unlock a capability you have not bought.

Can you read the ERP database directly?

Usually we will not, even where it is technically possible. Many ERP licences forbid it, direct reads break on the vendor’s next upgrade, and writes made that way can corrupt data the application assumes it controls. If no supported route exists, that is a real finding rather than an invitation to go around it.

Why is this priced "from"?

Because the range is genuinely wide: a modern cloud ERP with a documented API is ordinary work, while a fifteen-year-old on-premises installation may not be integrable at all. The figure covers the feasibility review and one straightforward flow. Anything beyond that is quoted in writing after the review, and you are free to stop there.

Refund & cancellation

What happens if you change your mind, and what happens to money already paid.

Cooling-off before work starts
You have 7 days after ordering to cancel while work has not yet begun. Up to 25% may be retained to cover scoping and scheduling already carried out.
Work already done
Once delivery has started, refunds are assessed against the work completed and the deliverables already handed over — the list under “what you get” above is what that assessment is made against. Approved refunds are processed within 14 days.
If we cannot deliver what is described here
You are refunded. The scope on this page is the scope we are held to, which is exactly why the exclusions above are stated before you buy rather than after.

The full terms, item type by item type, are in the Refund & Cancellation Policy. How the work reaches you is covered by the Delivery & Fulfilment Policy.

Not sure this is the right product?

We would rather point you at the right thing than sell you the nearest one. Ask us before you buy — no obligation.

Ask a questionRequest a custom quote

Related products

Others that solve nearby problems, in case this is not quite the right fit.

Or see all 12 in API & Integrations.

Contact us