ERP integration

Epicor Prophet 21

Also covers P21.

The integration is very doable and the hard part is never the API. It is deciding which system owns each piece of data.

Prophet 21 runs the operations of a lot of distributors, and when those distributors sell online the two systems have to agree about products, pricing, stock and orders.

We have been building and maintaining that connection since 2018. Below is what the work actually involves rather than what a datasheet says.

Reviewed August 22, 2026.

Tell us what you need Compare all platforms

What it is good at

P21 already holds the truth
Customer-specific pricing, contract terms and real availability live in the ERP. Once the storefront reads them rather than guessing, the whole quoting problem simplifies.
Order sync removes rekeying
Web orders land in P21 as orders. That is the single change that most often pays for the project, because somebody is currently retyping them.
The data model is stable
P21 does not move underneath you the way a SaaS platform can. An integration built carefully stays working.

Where it falls short

Deciding what owns what is the real project

Product descriptions, images, categories and web-only attributes usually should not live in the ERP, and pricing and stock usually should. Getting that boundary wrong is what makes integrations fragile.

Wrong for:
Teams hoping to skip the data-ownership conversation and just sync everything.
What helps:
Draw the boundary explicitly before any code, one field at a time. It is a day of arguing that saves months.

Real-time pricing is a performance problem

Customer-specific price and availability per line item means calling the ERP during browsing, and the ERP was not built to be a web backend.

Wrong for:
Stores expecting live ERP calls on every page with no caching strategy.
What helps:
Cache aggressively with sensible invalidation, and reserve live calls for the moments that need to be exact.

Every installation is customised

Two P21 installations at two distributors will differ in fields, conventions and business rules. Experience transfers; the mapping does not.

Wrong for:
Anyone expecting an off-the-shelf connector to work unmodified.
What helps:
Budget discovery as its own phase. We have never had one where discovery was wasted.

Who should choose it

Right for

  • Distributors already running Prophet 21 as their system of record
  • Businesses where pricing is contractual and per customer
  • Teams currently rekeying web orders into the ERP by hand

Wrong for

  • Businesses whose catalog and pricing are simple enough not to need it
  • Teams unwilling to decide which system owns which data

Our record with it

Hours
86
Clients
3
Since
2018

Real, named, multi-year work: product sync, order sync and guest checkout against live P21 installations.

How we approach integrations

Questions about Epicor Prophet 21

Can Prophet 21 integrate with Adobe Commerce or Shopify?

Yes, both. The platform matters less than the integration design: what syncs, in which direction, how often, and which system wins when they disagree.

What is the hardest part of a P21 integration?

Deciding which system owns each piece of data, and handling customer-specific pricing without making every page wait on the ERP.

Is there an off-the-shelf P21 connector?

Connectors exist and every P21 installation differs in fields and conventions, so expect mapping and customisation work regardless of where you start.

Keep comparing

Ask AI about Epicor Prophet 21

ChatGPT Claude Gemini Perplexity Meta AI

Start your project

Tell us what you're building.

Answer a few quick questions about your store and what's holding you back, and we'll come to the call already knowing your setup and where we'd start. We build ecommerce and custom web apps for B2B manufacturers, distributors, and marketplaces, with deep Adobe Commerce and Magento expertise.

See our work

0%