01 / backbone
Kinetic is the ledger
Jobs, parts, available-to-promise, pricing, order management. The authoritative record the business is run on.
The real problem
Kinetic runs the plant. The store runs the customer. The work is the space between.
Jobs, parts, available-to-promise and pricing on one side, dealer and distributor self-serve on the other. The middle is where commerce breaks.
02 / front door
Shopify is self-serve
Where dealers and distributors place repeat orders without a phone call, a rep, or a faxed PO.
03 / the gap
The middle is where it breaks
Duplicate customers. Orders written twice. Pricing that drifts. Silent failures at month-end close.
Our position
Epicor ships no Shopify connector at all, so the manufacturing data model is left to a generic mapping tool. We built a product around that gap, and Epicor Kinetic plugs in as a mapped REST and BAQ adapter.
How we build it
One direction for master data. Both directions for orders.
Customers, parts, available-to-promise inventory and price tiers are read out of Kinetic and pushed to Shopify. The storefront never writes to the ledger. Orders are the only thing that travels both ways.
System of record
Epicor Kinetic
read · never overwritten
The platform
Makro Middleware.
map · reconcile · audit
The storefront
Shopify Plus B2B
where buyers self-serve
Master data: Kinetic → Makro Middleware → Shopify, one way
Orders: Shopify → Kinetic, status returns
REST API v2 · OData v4Build on v2, with an API key on every call. v2 respects existing Kinetic user and data permissions, where v1 ignores menu security. V2 always, v1 is for legacy.handshake
BAQ read surfacesBusiness Activity Queries are the recommended read and extract surface. Available-to-promise, price tiers and revisions are pulled as shaped BAQ results, never raw on-hand.Kinetic → MK
Epicor FunctionsCustom server logic exposed as one REST endpoint. The whole order write chain collapses into a single idempotent, atomic, server-side call that returns the new OrderNum.Shopify ↕ Kinetic
BPM directive eventingKinetic has no native webhook, so real-time is engineered. A BPM Method or Data Directive calls an Epicor Function that makes an outbound REST POST, with BAQ polling as fallback.Kinetic → MK
OAuth 2.0 · client-credentialsServer-to-server auth against the Epicor IdP on a ServerToServer client. A machine identity, not a borrowed password. On native on-prem, a bearer token from the token resource.handshake
The console
This is not a connector. It is something you operate.
Every sync, every failure, every reconciliation is visible. This is the same Makro Middleware console your team would watch in production. Move through the views.
console.makro.agency / granite-peak-manufacturing / sync
live
Sync Monitor
Sync Monitor
Dead Letter Queue
Observability
Entity Key Map
Schedules
Order Relations
Records / 24h ▲
48,210
across 9 entities
Queue depth
3 pending
2 retrying · 1 review
Avg latency
1.2s
event → Shopify
Last reconcile
04:00
0 drift detected
Activitylive · last 60s
Throughputrecords / hr
In queue
3
of 48,210 processed
Auto-retrying
2
transient · rate-limit
Needs review
1
permanent
Resolved / 24h
41
38 auto · 3 manual
Dead Letter Queuenothing is dropped in silence
| Time | Entity | Error class | Attempts | Next | Action |
|---|---|---|---|---|---|
| 08:13:04 | order · OrderNum 10288 | PERMANENT · validation | 3 / 3 | held | Inspect |
| 07:55:22 | customer · CUST-00910 | TRANSIENT · timeout | 2 / 5 | 09:50 | Retry now |
| 06:40:11 | part · PN-44120 | RATE_LIMIT · license | 1 / 5 | paced | Inspect |
Sync volume7-day · records
Circuit breakersper endpoint
Kinetic · REST v2last trip · never
closedShopify · Admin APIlast trip · 3d ago
closedAvalara · AvaTaxlast trip · never
closedUptime · 90 dayserror rate 0.03%
customer · Granite Peak Westentity_key_map
kinetic CustNumCUST-004182
CustIDGPW-YARD
shopify gidgid://shopify/Company/61…
checksuma91f… unchanged
versionv17
→ decision: SKIP · already in sync
Every record carries three identities at once. The middleware reads this row before every write and decides create, update, or skip.
Kinetic has no idempotency key and no Shopify-external-ID column, so the middleware owns the map: Shopify GID against CustNum, OrderNum and PartNum. This is what stops duplicate customers and double-posted orders before they reach your ledger.
Change detection runs on the stored checksum, so a catalog of 50,000 parts with 12 real edits syncs 12 records, not 50,000.
Active schedules
7
all workflows enabled
Runs today
96
0 failures
Next run
09:46
available-to-promise
Nightly batch
01:00
DMT · 48,210 records
Workflowstenant · granite-peak
Part delta syncBAQ · watermarkedevery 15 min✓ 09:38 · 142 recordsnext 09:53Run now
Available-to-promisePartAlloc BAQevery 5 min✓ 09:41 · 3 partsnext 09:46Run now
Price tiersResolvePrice functionhourly✓ 09:00 · 1,204 rowsnext 10:00Run now
CustomersCustomerSvc · deltaevery 15 min✓ 09:40 · 6 recordsnext 09:55Run now
Order status returnKinetic → Shopifyevery 5 min✓ 09:42 · 11 ordersnext 09:47Run now
Full catalog batchDMT bulk loadnightly · 01:00✓ 01:00 · 48,210 recordsnext 01:00Run now
Daily reconciliationboth systems vs key mapdaily · 04:00✓ 04:00 · 0 driftnext 04:00Run now
Shopify order#1042
gidgid://shopify/Order/57…
companyGranite Peak West
line 1PN-99320 × 12
line 2PN-44120 × 4
total$8,420.00
#1042↔OrderNum 77231✓
gid://Company/88…↔CUST-004182✓
PN-99320 × 12↔99320 · qty 12✓
PN-44120 × 4↔44120 · qty 4✓
$8,420.00↔8,420.00 USD✓
entity key map · every id matched before write
Kinetic sales orderOrderNum 77231
OrderNum77231
CustNumCUST-004182
line 199320 · qty 12
line 244120 · qty 4
statusconfirmed
Order journey#1042 → OrderNum 77231 · 5s end to end
09:42:04webhook received→
09:42:04HMAC ✓ · dedup ✓→
09:42:05transformed→
09:42:06Epicor Function→
09:42:09OrderNum 77231 confirmed→
09:42:09status → Shopify
drag, scroll, or use the tabs
Inside the platform
Feature by feature.
Ten engineered subsystems, one shared dataset. The same platform that runs in production for NetSuite, mapped to the Epicor Kinetic surface.
01 / 10
When a record fails
Integrations are judged by how they fail. Follow one failed record.
An order write to Kinetic fails on a license-concurrency penalty. It is classified before it is retried, and nothing disappears into a log file. Colour carries the verdict: amber is sorted, teal paces, red is held, green replays.
01
It arrives
An order write to Kinetic fails on a license-concurrency penalty. Instead of disappearing into a log, it enters the pipeline.
captured→ 02
It gets classified
Every failure is sorted before anything is retried, so a bad record never loops forever.
classified→ 03
Rate-limit paces
The license penalty routes to a paced lane that reuses one session and bounds concurrency, automatically, until the burst clears.
retrying→ 04
Permanent is held
A validation failure routes straight to the dead-letter queue for review. It is never retried blindly, and a duplicate OrderNum is never written.
→ 05
You replay it
Fix the cause, replay from the queue. A daily reconciliation pass catches anything the live path missed.
replayed · reconciledThe failure modes no vendor page admits
Where generic connectors fail on the Kinetic data model.
Epicor ships no first-party Shopify connector, so every route is a generic mapping tool against a manufacturing data model. These are the points where job-based inventory, the price matrix and the customization layer break a fixed-mapping connector. A custom middleware layer is built to handle all of them, explicitly.
No native connector at all
Epicor Commerce Connect (ECC) is built on Magento Community Edition and never mentions Shopify. Every Shopify route is third-party or custom. The real choice is a packaged connector versus purpose-built middleware, not a connector versus a build.
→ build on Kinetic REST v2, BAQs and Epicor FunctionsJob-based inventory overselling
Kinetic does not store an available-to-sell number, it is derived. Available equals OnHandQty minus AllocatedQty, and in a shop it depends on job status. Publish on-hand and you sell stock already committed to open production jobs.
→ available-to-promise from a BAQ, per warehouseNo resolved-price endpoint
Reading the Part returns a unit price that ignores customer and customer-group lists, and no documented endpoint returns a single resolved customer price. The price is a layered, stacking cube that only evaluates at order-line entry.
→ wrap the pricing engine in a function, pre-compute B2B listsBOM & configure-to-order mapping
The Kinetic part master carries revisions, BOMs, UOM conversions and configure-to-order structures that do not map to Shopify's flat product and variant model. The data model, not the API call, is where these projects succeed or fail.
→ map the part master and job structure before any endpointThe GetList drops UD fields trap
A UD field surfaces as a …_c field on full-row reads once the data model is regenerated, but GetList deliberately drops it. Build sync on GetList and Shopify receives blank custom attributes.
Two incompatible rate limiters
Epicor has no app-level rate limiting and no 429. The throttle is Web Service license concurrency, a 20-second penalty per call on a shared license. Shopify's side is the opposite, a hard 429 with Retry-After. One backoff policy cannot serve both.
→ self-throttle Kinetic, honor 429 on ShopifyNo atomic transaction in iPaaS
Writing a Kinetic order is a multi-call dataset dance, each row carrying a RowMod flag. A recipe-based iPaaS runs these sequentially with partial-write risk, and the Jitterbit connector has no native Epicor Function activity at all.
→ one Epicor Function POST, all-or-nothing server-sideNo idempotency, dedupe it yourself
Kinetic has no idempotency key. OrderNum is server-assigned on every create, so a retried POST writes a second sales order, and there is no native Shopify external-ID column on the standard tables.
→ dedupe on the Shopify order ID before create, own the ID mapClaims you can check
What you will hear, and what the docs actually say.
Every reality below is verified against a primary Epicor source, a named vendor doc, or attributed practitioner consensus. This is the difference between a team that read the marketing and a team that shipped against the documentation.
01
The claim"Epicor has a native Shopify connector, just turn it on."
The realityThere is no first-party Epicor to Shopify connector. Epicor Commerce (formerly Commerce Connect / ECC) is built on Magento Community Edition and never mentions Shopify. Every Shopify route is third-party or custom. The real choice is a packaged connector versus purpose-built middleware, not a connector versus a build.
02
The claim"Just sync stock on hand and you're good."
The realityKinetic does not store an available-to-sell number, it is derived. Available equals
OnHandQty − AllocatedQty, and in a manufacturing shop available-to-sell depends on job status. Publish on-hand and you sell stock already hard-allocated to open jobs. The correct feed is a BAQ computing availability per warehouse from PartAlloc / PartBin.03
The claim"Read the customer's price from the REST API and sync it."
The realityNo documented endpoint returns a single resolved customer price. Reading the
Part returns a unit price that does not account for customer or customer-group lists. Price is a layered cube (part base, base list, group list, customer list, quantity break, percentage discount) that stacks and only evaluates at order-line entry. Wrap the pricing engine in an Epicor Function and pre-compute B2B price lists.04
The claim"Run cart-time tax through Epicor so the ERP is authoritative."
The realityEpicor's tax calc is flag-gated and synchronous to Avalara's cloud: set the calc flag, set RowMod, call MasterUpdate, which fires a server-mediated round-trip to AvaTax and back. On the checkout path that is three serial network legs per cart change against an ERP with no rate limiting. Quote tax in Shopify against the same Avalara account, settle in Epicor and reconcile deltas.
05
The claim"Build the integration on Epicor's REST API, any version is fine."
The realityBuild on REST v2, not v1. v2 (OData v4) requires an API key and respects existing ERP user and data permissions; on v1, menu security is completely ignored. Practitioner consensus is blunt: "V2 always, v1 is for legacy." It matters commercially because the Epicor-blessed iPaaS (Jitterbit) is REST v1 only.
06
The claim"Epicor has a per-minute rate limit you tune retries against."
The realityEpicor has no application-level rate limiting and issues no 429. The real throttle is Web Service license concurrency: exhaust the dedicated licenses and Epicor assigns a shared license with a 20-second penalty per Business Object call, and response times double, then double again. Self-throttle, reuse one session per burst, and size the license count to peak load. Shopify's side is the opposite, a hard 429 with Retry-After.
07
The claim"Epicor pushes real-time events to Shopify via webhooks."
The realityKinetic has no native webhook or publish-subscribe registry. Real-time Kinetic to Shopify is built from a BPM Method or Data Directive to an Epicor Function to an outbound REST POST, or by BAQ polling. Shopify webhooks handle the inbound direction; the outbound direction is something you engineer, not subscribe to.
08
The claim"Retry a failed order safely, Epicor dedupes it."
The realityKinetic has no idempotency key.
OrderNum is server-assigned on every create, so a retried POST creates a second sales order, and there is no native Shopify external-ID column. The middleware must own idempotency (dedupe on the Shopify order ID before create, then persist the returned OrderNum) and own the ID map.09
The claim"An iPaaS connector wraps your order in one atomic transaction."
The realityWriting a Kinetic order is a multi-call dataset dance (
GetNewOrderHed → ChangeCustomer → ChangePartNum → MasterUpdate), each row carrying a RowMod flag. A recipe-based iPaaS runs these sequentially with partial-write risk, and the Jitterbit connector has no native Epicor Function activity at all. The clean pattern is one Epicor Function POST that collapses the chain server-side into an all-or-nothing transaction.10
The claim"Custom fields just appear in the API automatically."
The realityMostly, with one trap that silently ships blank data. A UD field surfaces as a
…_c field on full-row reads (GetRows) once the data model is regenerated, but is deliberately absent from GetList. Build sync on GetList and Shopify receives blank custom attributes. Use GetRows or a BAQ. Adding a UD field is an ERP change, not a connector toggle.11
The claim"BOMs and configure-to-order map straight into Shopify variants."
The realityKinetic's part master carries revisions, BOMs, UOM conversions and configure-to-order structures that do not map to Shopify's flat product and variant model out of the box. For CTO and BOM-linked products the part master and job structure must be mapped before any REST endpoint is wired. This is the manufacturing depth generic connectors skip.
12
The claim"OAuth client-credentials works on any Epicor, it's standard."
The realityOnly on Epicor Cloud / IdP, not native on-prem. The modern server-to-server path is OAuth 2.0 client-credentials against the Epicor IdP with an admin-provisioned ServerToServer client; on-prem falls back to a bearer token from the token resource. Either way REST v2 still requires the API-key header on every call, and these are admin-only, discovery-phase dependencies.
13
The claim"Access Scope locks the integration user down, one switch and you're safe."
The realityAccess Scope is necessary but not sufficient. Certain core security services remain callable regardless of scope, and Basic credentials still permit fat-client login even with a scope assigned. Least privilege takes five independent layers: Integration-Account flag, no-access security groups, a tight Access Scope, REST v1 disabled, and scoped data and company permissions.
14
The claim"Off-the-shelf connectors handle reliability, that's what you pay for."
The realityThe market does not publicly document the two facts that most determine reliability: which REST version it hits, and whether it calls Functions for atomic transactions. The recurring failures (silent divergence, duplicates, concurrent-inventory conflicts, partial writes, SKU mismatch) are reliability failures, not feature gaps, solved by the same primitives: durable queue, idempotency, bounded retry, replay and reconciliation.
The decision guide
Three ways to connect Epicor Kinetic and Shopify, and why there is no native option.
There is no first-party Epicor Shopify connector, so there are three real paths: no native option (Epicor Commerce Connect targets Magento, not Shopify), a third-party iPaaS or packaged connector, or a custom integration built on Kinetic's OData v4 REST API and Shopify's Admin API. The right choice depends on order volume, job-based inventory, B2B complexity and how customized the Kinetic install is. Note that Kinetic, Prophet 21 and ECC are different Epicor products: confirm which one you run before scoping.
Option 01
No native connector (ECC = Magento)
Epicor Commerce Connect is Epicor's commerce product, but it targets Epicor's own storefront and Magento / Adobe Commerce, not Shopify. There is nothing to turn on for Shopify.
- platformMagento Community, not Shopify
- shopifynot supported, ever
- disambiguateKinetic vs P21 vs ECC differ
- realityevery Shopify route is custom
Right for nobody on Shopify, the option exists only to rule it out.
Option 02
iPaaS & packaged connectors
Subscription middleware and packaged tiles: Celigo, Boomi, MuleSoft, Commercient SYNC, StarfishETL, Codeless, and the Epicor-blessed Jitterbit / Workato.
- mappingsconfigurable, template-bound
- jitterbitREST v1 only, no Functions
- writessequential recipes, partial-write risk
- pricingannual fee, grows with volume
Right for standard multi-system sync where the manufacturing logic fits a fixed-mapping template.
Option 03 our build
Custom middleware
Built around your exact part master, job-based inventory and B2B logic, owned by you, operated with a support agreement. Where manufacturers and distributors end up.
- readBAQs · write Epicor Functions
- tenancysingle-tenant, isolated per client
- recovery7 failure classes, DLQ, replay
- scopeATP, BOM/CTO, price matrix native
Right for job-based inventory, configure-to-order and BOM products, the stacking price matrix, BPM-customized installs, or non-standard fulfillment a fixed-mapping connector cannot model.
How long it takes
Timeline by scope, not a contact-us wall.
An Epicor Kinetic ⇄ Shopify Plus build lands in one of three bands depending on B2B complexity, the part master depth, and how many of the break points above are in play.
Band 01 · foundation
6–8
single site · standard catalog
- Customers, parts and inventory one way, Kinetic to Shopify
- Orders both ways through one Epicor Function, idempotent
- Available-to-promise from a BAQ, overselling prevention
- Dead-letter queue, daily reconciliation, the console
Band 02 · B2B
8–12
Shopify Plus B2B · price tiers
- Everything in foundation, plus the resolved price cube
- Customer price tiers to per-company Shopify B2B price lists
- Avalara tax handoff at the Shopify edge, settled in Epicor
- BPM approval workflows and credit holds respected
Band 03 · manufacturing
12–16+
BOM / configure-to-order · multi-plant
- Everything in B2B, plus BOM and configure-to-order mapping
- Part-master revisions and UOM conversions to variants
- Multi-plant available-to-promise, Site to Shopify Location
- BPM directive eventing for real-time, custom UD fields
Cost · scoped per build
We price an Epicor Kinetic integration as an engineering engagement: a build with a support agreement, not a per-record meter or a platform seat that renews forever. For context, the industry reports an 8 to 14 week scope and iPaaS at roughly $40,000 to $80,000 setup plus monthly fees, cited as industry-reported context, never as our quote. Your exact figure is scoped to the band and the break points in play, and we put it in writing before anything starts.
Security posture
Built to pass your IT review, and your Epicor admin's questions.
Credentials never in plain config
Epicor and Shopify secrets are held as encrypted fields, isolated per tenant and rotatable without downtime. The OAuth client secret and API key never sit in plaintext, anywhere.
Inbound traffic is verified
Every Shopify webhook is HMAC-verified before it is trusted, then deduplicated by event id, so a replayed webhook cannot create a second order.
Least-privilege access to Kinetic
OAuth 2.0 client-credentials against the Epicor IdP on Cloud (a ServerToServer client) or a bearer token on on-prem, an API key on every v2 call, and a dedicated least-privilege service user, never an admin login.
Everything is on the record
An append-only audit trail logs every operation, source-tagged, so you can prove what happened during month-end close.
Frequently asked questions
Where Kinetic integrations get hard, and where we land.
The details that separate a team that read the docs from a team that shipped against them. Open any one.
01How do you integrate Epicor Kinetic with Shopify?+
There are three paths: a Shopify app connector, a third-party iPaaS (Commercient SYNC, Celigo, Boomi, MuleSoft), or a custom integration built on Epicor Kinetic's OData v4 REST API and Shopify's Admin API. For manufacturers and distributors, a custom integration gives the control needed to handle job-based inventory, BPM approval workflows, and B2B price tiers that off-the-shelf connectors flatten.
02Does Epicor Kinetic have a native Shopify connector?+
No. Epicor Commerce Connect (ECC) is Epicor's commerce product but it targets Epicor's own storefront and Magento/Adobe Commerce, not Shopify. For Shopify you use middleware or a custom build.
03Does Epicor Kinetic have an API for Shopify integration?+
Yes. Epicor Kinetic exposes an OData v4–compliant REST API covering every business object, BAQ, process, report, and Epicor Function. It authenticates with API keys and access scopes and respects existing Kinetic user and data permissions.
04How does inventory sync work between Epicor Kinetic and Shopify?+
It must publish available-to-promise quantities, not raw on-hand stock. In Kinetic, available-to-sell quantity depends on job status, so stock committed to open production jobs must be excluded before it reaches Shopify. Connectors that sync raw on-hand counts oversell.
05Can Epicor Kinetic drive Shopify Plus B2B pricing?+
Yes. Customer price tiers maintained in Kinetic map to Shopify Plus B2B catalog price lists, so dealer and wholesale accounts automatically see their correct contract pricing, with Kinetic as the single source of truth.
06What's the difference between Epicor Kinetic and Epicor ERP 10 (or Prophet 21) for integration?+
Kinetic is the current name for the product formerly called Epicor ERP (Epicor 10); Kinetic integrations use the REST API while ERP 10 often relies on BPM connections. Prophet 21 (P21) is a different Epicor ERP for wholesale distribution with its own data model, so confirm the version before scoping.
07Do you handle configure-to-order / BOM products from Kinetic in Shopify?+
Yes. The Kinetic part master and job/BOM structure are mapped before any REST endpoint is wired, because for CTO and BOM-linked products the data model, not the API call, determines whether the integration holds.
08What do you need from our team?+
Three things: an admin-provisioned IdP client and API key for a dedicated least-privilege service user, access to a sandbox or pilot Kinetic environment, and your Epicor functional lead in the entity-mapping workshops. Your Epicor partner is welcome in every session. We would rather they ask hard questions early.
09Will this survive our Epicor upgrades and our customizations?+
Yes. A customized Kinetic still integrates cleanly: UD fields ride the same record payload as …_c fields, and BAQs and Epicor Functions are auto-exposed over REST and OData v4, so we read your customizations generically. The one trap is
GetList, which deliberately drops UD fields, so we build on GetRows or a BAQ. Adding a UD field is an ERP change to scope into the plan, not a connector toggle.10Will rollout touch our production ledger?+
Not until you decide it does. Master data syncs are read-only against Kinetic. Order writes go to a pilot environment first, then through a parallel run with daily reconciliation. Production posting starts when the reconciliation report says zero drift and you sign off, and the audit trail covers every record from day one.
The framework underneath
A proven platform. Epicor Kinetic is the next mapped adapter.
Every ERP sits behind the same contract: authenticate, fetch master data, push orders, validate, report. The sync engine, mapping layer, error handling and Shopify integration never change when a new system plugs in. NetSuite runs on that framework in production today. Epicor Kinetic is a registered target on the same platform, its path mapped to REST v2, BAQs and Epicor Functions.
We say this plainly: the credibility is a real platform and a precisely mapped Kinetic path, not a decade of Kinetic traffic. That distinction is exactly what your architect can verify, which is why we lead with it.
adapter contractbase.ts
01authenticate()OAuth 2.0 · API key
02fetchMasterData()REST v2 / BAQ
03pushOrder()Epicor Function · idempotent
04validate()schema check
05report()audit + status
NS
NetSuite
SuiteQL · token auth · saved search
EK
Epicor Kinetic
Kinetic · REST · BAQ
D3
Dynamics 365 F&O · BC · Sage · Infor
OData / REST adapters
Proof and outcomes
Claims you can check.
$100K+ / yr
Clarius · NetSuite + Salesforce + Shopify PlusCapability proof, on NetSuite, not Epicor. We built a unified account page integrating Clarius' NetSuite ERP, Salesforce CRM and Shopify Plus into a single view of customer information, orders and invoices, and used Shopify Flow automation feeding order data into NetSuite to keep the platforms in sync. It is proof Makro runs real ERP to Shopify Plus middleware in production. The Epicor Kinetic path is the mapped extension of that same platform.
1,756
Automated tests across 139 suites, run on every change. No code reaches your production data without passing them.
85%
Coverage gate enforced before any deploy.
39
End-to-end browser tests, across Chromium, Firefox and WebKit.
7
Failure classes, each with its own pre-decided policy.
0
Credentials stored in plaintext, anywhere, ever.
Bring your Epicor architect and your renewal quote. We will walk the platform, not a deck.
A real conversation about your Kinetic environment, your part master, and the three sharp questions you already have.