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.
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.
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.
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.
Pull open POs by vendor and expected receipt date. Update PO quantities and create new POs to trigger replenishment from your product.
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.
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.
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.
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).
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.
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.
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.
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.
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.
© 2025 Askel.ai. All rights reserved.