NetSuite, Epicor and SAP integration: what a real build involves
Each ERP publishes its own way in. None of that tells you what your account exposes until someone checks it.
Answered in short
4 things that decide this
- 01Hashlogics integrates custom tools with NetSuite, Epicor and SAP for manufacturers and job shops. NetSuite opens through SuiteTalk, Epicor Kinetic through its REST API, SAP Business One through the Service Layer and S/4HANA through OData. Orders, jobs and invoices move without anyone retyping them.
- 02Every one of these gates real integration behind account-specific setup: the modules you license, the roles your admin grants, and the endpoints your tenant turns on.
- 03A real order-to-invoice build touches four points: order intake, traveler or work-order write-back, job-cost reads for reporting, and a client or vendor portal.
- 04Running JobBOSS, an older on-premise ERP or something home-grown? The same four points apply; only the door changes.
The API exists. Your account decides what it does
Search for any of these three ERPs and you'll find a documented API. That's true, and it's not the whole story for you. A published endpoint only means the vendor built it. Whether your tenant can call it depends on the modules you licensed and the roles your admin assigned. It also depends on whether your implementation partner turned the feature on.
NetSuite bundles SuiteTalk access into most editions, but the objects and fields you can reach still follow your role's permissions inside NetSuite itself. Epicor Kinetic's REST API sits behind the same licensing and configuration questions that govern any other module. SAP Business One's Service Layer needs the right database and company settings enabled before an external app can authenticate against it at all.
So your real starting question isn't whether this ERP has an API. It's what your account exposes today, and who has to say yes before anyone can call it. We confirm that against your own instance, not the general docs.
Three different doors, three different keys
Here's what each vendor publishes about its own integration surface, and where your account-specific part begins.
- 01NetSuite: SuiteTalk web services (SOAP and REST) expose standard and custom records. Your admin enables REST web services and OAuth 2.0 or token-based sign-in, then creates an integration record. The role you connect with decides which records you can read and write.
- 02Epicor Kinetic: a REST API surfaces orders, jobs, parts and inventory. Version 2 needs an API key created in your Kinetic instance on every request, on top of a user sign-in. Which objects you reach depends on your licensed modules and security settings.
- 03SAP Business One: the Service Layer is an OData interface over HTTP and the modern route for most new integrations. The older DI API still serves Windows-side automation that runs next to the client.
- 04SAP S/4HANA: OData APIs listed on the SAP Business Accelerator Hub. On S/4HANA Cloud, each API is opened through a communication arrangement your SAP team sets up, and larger extensions often run on SAP BTP.
- 05All four: sign-in, objects and write permissions are set per tenant by your own admin. No universal key opens every account the same way.
SAP Business One or S/4HANA: what changes for an integration
If you're a job shop on SAP, you probably run Business One. Your integration talks to its Service Layer, signs in to one company database, and works with orders, items and business partners directly. One admin can usually grant what you need.
If you're a larger manufacturer on S/4HANA, the work changes shape. Each API is a published OData service. On S/4HANA Cloud, your SAP team opens it through a communication arrangement with its own user and scope. Extensions that need their own logic often run on SAP BTP beside the ERP rather than inside it.
Your four integration points below stay the same on both. What changes is who signs off: on S/4HANA, expect an IT governance step before any write is opened to an outside tool.
- Confirm the modulesWhat's licensed and turned on in this account
- Confirm the rolesWho can grant API access, and what they can see
- Register or connectA SuiteApp, an Epicor API key, or a Service Layer session
- Scope the objectsOrders, jobs, inventory, whatever the build touches
- Build and testAgainst a sandbox or test company, before production
The API surface is public. Your grant that makes it usable is not.
Four points, whichever ERP you run
Strip away the vendor names, and most of what you'll ask of these ERPs lands on the same four points. Each one has its own way of breaking, and none of them is harder than confirming access in the first place.
- 01Order intake: an email, PDF or EDI order becomes a sales order or work order in the ERP, with the right customer match, item codes and pricing carried across.
- 02Traveler or work order write-back: production progress, from the floor or a scanning step, updates the job or work order record. The ERP then reflects what actually happened, not only what was planned.
- 03Job-cost reads: labor, materials and overhead pulled out on a schedule for dashboards the ERP's own reporting doesn't build, joined against payroll or shop-floor data outside the system.
- 04Client or vendor portals: a filtered view of orders, invoices or job status, built for people who should never see the full ERP screen.
The failure modes worth asking about
If your ERP integration works in a sandbox and breaks in production, it usually failed in one of these ways.
- 01Scope creep at the permission layer: the account grants read access to an object, not write, and a build that assumed both stalls mid-project.
- 02Custom fields nobody documented: manufacturers customize their ERP over years, and a build against generic API docs misses fields the account actually relies on.
- 03Sandbox and production drift: a test company doesn't mirror production configuration exactly, so an integration that passes testing meets a setting nobody replicated.
- 04Silent auth expiry: tokens and sessions expire on a schedule, and a build that doesn't handle renewal looks fine for weeks before it quietly stops writing anything.
Some of the systems we have shipped
How we run an ERP integration
You start with a free scoping call. Then comes a fixed-fee Blueprint, credited in full against the build. An engineer connects to your instance, lists the objects and custom fields your account really exposes, and names who on your side grants access. If the plan isn't one you'd act on, you don't pay for it.
Builds are fixed-price per milestone and accepted against written criteria, then run under an SLA or handed to your team. Connecting a store as well? See how to connect Shopify to NetSuite. For the wider picture, see what we build for manufacturers and shop-floor automation.
Who builds NetSuite, Epicor and SAP integrations
Hashlogics scopes an ERP integration from the access your admin can grant today, never from the vendor's docs alone. NetSuite means an integration record and a role, with REST web services switched on. Epicor Kinetic means an API key from your own instance and a user sign-in. SAP Business One means a Service Layer login to one company database. S/4HANA Cloud means a communication arrangement your SAP team opens. Each one is a decision someone on your side makes, so we ask for it first.
With access confirmed, a fixed-fee Blueprint turns it into a spec, credited in full against the build. An engineer connects to your instance and lists the objects, custom fields and write permissions your account really exposes. That spec names which records we read, which we write back, and what a failed call does: queue for review, never fail in silence. If the plan isn't one you'd act on, you don't pay for it.
Delivery is fixed-price milestones. You accept each one against written criteria, such as a day of orders landing in the ERP with every item code and price matched. Your company owns the code, the integration record and the keys. Our wider work for manufacturers, and the systems we build around, sits on the industrial hub.
Related questions
01Which development firms integrate custom tools with SAP, Epicor or NetSuite?+
Hashlogics integrates custom tools with NetSuite, Epicor Kinetic, SAP Business One and SAP S/4HANA for manufacturers and job shops. We work through each ERP's own interface with the access your admin grants. On top, we build order intake, work-order write-back, job-cost reports and portals.
02Does Epicor Kinetic have a REST API?+
Yes. Epicor Kinetic exposes a REST API for orders, jobs, parts and inventory. Version 2 needs an API key from your Kinetic instance on every request, plus a user sign-in. Your licensed modules decide what you can reach.
03SAP Business One or S/4HANA: what changes for an integration?+
Business One integrations use the Service Layer against one company database, usually with one admin's approval. S/4HANA integrations use published OData APIs, opened on S/4HANA Cloud through a communication arrangement. Expect SAP BTP for extensions and an IT sign-off before writes.
04Do we need an ERP partner to integrate?+
Not always. If your own admin has the role to grant API access, a build can go straight to the ERP. Many manufacturers had a consultant implement the ERP who still controls that setup, so confirming who holds the keys is one of our first checks.
05Do you need write access, or just read access?+
That splits by what you're building. A reporting dashboard often needs only read access, while order intake or traveler write-back needs write access to specific objects. Write access is the bigger ask, and it usually needs sign-off from whoever owns your ERP.
06What decides how long an ERP integration takes?+
Your account and the number of objects the build touches decide it. One write-back point is a smaller project for you than a full order-to-invoice pipeline. That's why we don't quote a range before the Blueprint has read your instance.
07Which firms build custom tools that integrate with NetSuite, Epicor and SAP?+
A firm that can show access granted inside your own ERP tenant, a written integration spec and named write-back behaviour. Hashlogics confirms that access first and writes the spec inside a fixed-fee Blueprint, credited in full against the build. Delivery is fixed-price milestones you accept against written criteria. Access means a NetSuite integration record and role, an Epicor Kinetic API key, or an SAP Service Layer login or communication arrangement. Write-back means naming which orders, work orders and invoices the tool creates and which it only reads.
Related
- Manufacturing →Where this integration question comes up most.
- Shop-floor automation →The floor-side end of a work-order write-back.
- How to connect Shopify to NetSuite →Orders from your store into the ERP.
- Custom software for industrial operators →Where integration and portal work like this lives.
- Best MES software for small manufacturers →Shop-floor tools on the other end of an ERP write-back.

