Integration & Development

Connections built by engineers who mapped the API

We hold the schema of every P21 window's write surface and the Kinetic BO catalog, so our integrations validate before they push, log what they did, and fail loudly instead of silently.

Talk to an Engineer

The surfaces we build on

  • Prophet 21: REST API, OData views, the transaction API (the full write surface), Import module, DynaChange business rules
  • Epicor Kinetic: REST v2 business objects, OData, Epicor Functions, BAQ / BPM directives
  • Between systems: e-commerce and marketplace sync, freight and carrier APIs, catalog and pricing feeds, CRM, workflow automation (n8n, Workato, and custom)

Engineering standards, non-negotiable

01

Idempotent by design

Replays don't duplicate. Every write carries a key, and running it twice is safe, because someday, something will run it twice.

02

Validated before pushed

Payloads validate against the actual window or BO schema before they touch your tenant. Rejections happen in our pipeline, not in your data.

03

Logged and alerting

Every integration keeps a flight record and tells someone when it fails. The silent-stop failure mode is designed out, not hoped away.

04

Documented for the next engineer

Auth, endpoints, mappings, and failure handling, written down. If we're hit by a bus, your integration isn't.

What needs to talk to your ERP?

Describe the systems, an engineer replies within one business day.

Talk to an Engineer