Epicor Prophet 21 logo

Epicor Prophet 21

ERP & FinanceService accountLive

Epicor Prophet 21 is the dominant ERP for wholesale distributors, running purchasing, inventory, pricing, and customer accounts for thousands of distribution businesses across North America. It runs on a per-customer host URL and exposes data through a REST API secured by OAuth 2.0 client credentials.

What you can do

Read and write sales orders

Pull open, acknowledged, and shipped sales orders by customer, date range, or order number. Create new orders and update line items including pricing overrides and requested ship dates.

Sync customer master records

Read and update customer accounts including contact details, credit limits, pricing tiers, and assigned territory reps. Create new customer records from your product's onboarding flow.

Query inventory availability

Check on-hand quantities, allocated stock, and backorder status by item and warehouse location. Askel handles multi-warehouse distribution setups so your product can show accurate availability across all stocking locations.

Read and write purchase orders

Pull open POs by vendor and expected receipt date. Update PO quantities and create new POs to trigger replenishment from your product.

Sync vendor and item master data

Read vendor records, item master data, and pricing matrices. Askel normalizes P21's pricing tier structure into flat price lists your product can display or act on.

Track shipments and receipts

Read shipment confirmations, carrier tracking numbers, and warehouse receipts as they are posted. Use this data to update order status in your product without polling the full order list.

Sample use case

Syncing P21 order status into a distributor's customer portal

Ridgepoint Supply sells industrial fasteners and runs their business on Prophet 21. They use your B2B customer portal product to let buyers check order status and reorder. When an order ships in P21, Ridgepoint's buyers expect to see tracking information inside the portal within the hour.

  1. 1

    Register the OAuth client in P21

    Ridgepoint's P21 admin opens the OAuth configuration screen inside Prophet 21's admin console and creates a new client for Askel. They note the client ID and client secret generated by P21, as well as their P21 host URL (ridgepoint.prophet21cloud.com).

  2. 2

    Enter credentials in Askel

    Ridgepoint's admin pastes the P21 host, client ID, and client secret into the Askel setup screen inside your portal product. Askel calls /oauth/token on Ridgepoint's host using the client_credentials grant and confirms it receives a valid Bearer token.

  3. 3

    Schema discovery

    Askel reads the available P21 endpoints and discovers the SalesOrder, Customer, Inventory, and Shipment objects along with any custom fields Ridgepoint has added to their P21 configuration. Your CS team sees a field mapping draft within minutes.

  4. 4

    Map and validate

    A few custom pricing fields need manual mapping. A CS rep reviews Askel's suggestions with Ridgepoint's operations manager and runs a dry-run against 50 recent orders to confirm the order status and tracking data lands correctly in the portal.

  5. 5

    Go live

    The hourly sync is enabled. When P21 posts a shipment confirmation, Askel pulls the updated order status and carrier tracking number and writes them into Ridgepoint's portal so buyers see real-time shipment data without calling their sales rep.

Authentication

Service account

The customer's P21 admin registers an OAuth client in Prophet 21's admin console and provides the generated client ID, client secret, and P21 host URL to Askel. Askel mints a Bearer token by calling the client_credentials grant against /oauth/token on the customer's host and refreshes it automatically before expiry. No user passwords are stored.

Data flow

How Askel sits between your product and the customer's system

Data flow between Customer's Prophet 21 tenant, Askel, and Your productCustomer's Prophet 21 tenantAPI endpointAskelauth · mapping · driftYour productyour backend
Sales OrdersCustomersInventoryPurchase OrdersVendorsShipments

FAQ for Epicor Prophet 21

Does this work with both cloud-hosted and on-premises P21 deployments?+
Yes. Askel uses the host URL the customer provides, so it works with P21 Cloud, P21 hosted by a third-party data center, and on-premises installations that are accessible from the internet. For on-prem deployments behind a firewall, the customer typically sets up a reverse proxy or VPN tunnel so Askel can reach the P21 host.
Which P21 API version does Askel use?+
Askel targets the P21 REST API (available from version 2020.1 onward). If a customer is on an older version that only exposes the SOAP endpoints, Askel will note this during the connection test and the integration will not be available until the customer upgrades or enables the REST layer.
What OAuth scopes or permissions does the P21 client need?+
Askel needs read access to the SalesOrder, Customer, Item, Vendor, Inventory, and Shipment endpoints, and write access to SalesOrder and PurchaseOrder if your product creates or updates those records. The P21 admin assigns endpoint permissions to the OAuth client during registration inside the P21 admin console.
What happens if the customer changes their P21 host URL or rotates the client secret?+
Askel will immediately stop receiving valid tokens and surface a connection error in your product's integration dashboard. The customer's admin can update the host or credentials in the Askel setup screen without losing the existing field mappings, and the integration resumes on the next scheduled run.
Ready to ship integrations faster?customers faster?implementations faster?
Join onboarding teams delivering integrations without the engineering queue,
catching drift before it breaks, and hitting go-live dates.
Security & Compliance
ISO 27001 Certified
GDPR Compliant

© 2025 Askel.ai. All rights reserved.