How to add a mobile app to Epicor Prophet 21
Short answer
Decide first what Epicor's own mobile and RF options already cover, then build a thin mobile front end over the P21 middleware APIs for the gaps: barcode scanning, bin transfers, cycle counts, will-call and outside sales lookups. Keep business logic in P21, handle poor connectivity with a local queue, and run everything behind your VPN or reverse proxy.
Distribution is a mobile business. Pickers walk the warehouse, drivers deliver, outside sales visit job sites, and counter staff look things up while standing in an aisle. P21 is a desktop-centric ERP, so these people either carry paper, share a few terminals, or rely on a handful of Epicor mobile and wireless tools that may not fit how you work.
Before building anything, inventory what you already own. Epicor has offered wireless warehouse capabilities and mobile modules for sales and inventory, and the right answer may be to license or configure those. A custom app makes sense for specific workflows: a lookup that mirrors how your branch operates, a customer-facing delivery capture, or a task that mixes P21 with other systems.
This page is about that custom layer: what to expose from P21, how to design for scanners and bad Wi-Fi, and how to avoid creating a second source of truth.
What teams use it for
Bin-to-bin transfers and putaway
Scan an item and a location, confirm quantity, and post an inventory transfer, with validation against location rules.
Cycle counts
Present count tasks by zone, capture scanned counts, and submit variances for supervisor approval before adjustment.
Pick confirmation
Show the pick ticket, require scans for items and lots or serials, and report short picks immediately to inside sales.
Outside sales lookup
Show customer-specific price, branch availability, open orders and last purchases for a salesperson at a job site.
Delivery capture
Record signature, photo and exceptions at drop-off and attach them to the invoice or shipment.
Receiving
Scan inbound packing slips or items against the PO, enter received counts, and flag overages and damages.
Epicor Prophet 21 integration surface
- P21 middleware services (REST and related transaction endpoints, depending on version) for reading items, locations, orders and customers, and for posting inventory and shipment transactions.
- Epicor wireless and mobile modules, which may already handle receiving, picking and counting; assess these before custom development.
- SQL Server read access for fast lookups such as item location quantities and open pick tickets (inv_loc, oe_line style tables, verified locally). Do not write to tables directly.
- Barcode and label configuration in P21 (item IDs, UPC, vendor and customer part numbers, bin labels) which determines what a scan can resolve.
- Authentication options: P21 user credentials passed to the middleware, or a service account with your own user layer. Choose deliberately, since it affects audit and licensing.
How it works
- 1
Map workflows and devices
List the five to ten tasks that matter, who does them and on what hardware: rugged Android scanners, iOS phones, or tablets. Pick one platform first.
- 2
Check native options
Confirm with Epicor or your reseller what your licence already includes for wireless warehouse and mobile sales before writing code.
- 3
Build an API facade
Put a small backend between the app and P21 that exposes task-shaped endpoints such as get pick, confirm pick and submit count. It validates, caches and keeps P21 internal.
- 4
Design for the floor
Large touch targets, scanner-first input through keyboard wedge or intents, fast confirmation sounds, and minimal typing.
- 5
Handle offline
Queue transactions locally with idempotency keys and replay them in order when connectivity returns, showing clear pending status.
- 6
Authenticate
Use single sign-on or a device login mapped to a P21 user, enforce device enrolment through MDM, and expire sessions on shared devices.
- 7
Pilot and expand
Run one workflow in one warehouse zone, compare error rates with the previous method, then expand.
Example flows
Cycle count by zone
Trigger: A supervisor releases a count for aisle C.
- The app downloads the bins and expected quantities.
- The counter scans each bin and item and enters the count.
- Variances above a threshold require a recount.
- Confirmed counts are submitted for supervisor approval and then adjusted in P21.
Result: Counts are completed faster and adjustments have a clear approval trail.
Short pick escalation
Trigger: A picker finds fewer units than the ticket requires.
- The picker enters the actual quantity.
- The backend checks other locations for the item.
- It suggests the next bin or alerts inside sales.
- The pick is partially confirmed and the exception is logged.
Result: Shortages surface in minutes rather than at the shipping dock.
Delivery proof
Trigger: A driver arrives at a job site.
- The driver opens the stop and scans the order tag.
- The customer signs and a photo is taken.
- The app uploads when connected and attaches the proof to the invoice.
Result: Delivery disputes are resolved from stored proof.
Keeping data on-prem
The app only needs to reach your backend, which in turn reaches P21 inside your network. Expose the backend through a VPN, an MDM-managed per-app VPN, or a hardened reverse proxy with device certificates. Warehouse Wi-Fi coverage is often the real constraint, so plan access point coverage and test dead zones before blaming the software. If you want voice or natural-language features such as asking the device where an item is, run the model on a local server and return only answers to the device. Do not put P21 database credentials on devices under any circumstances.
Security checklist
- Never store ERP credentials on the device; use short-lived tokens issued by your backend.
- Enrol devices with MDM, enforce screen lock and remote wipe, and disable the app on lost devices.
- Validate every transaction server-side against P21 rules; assume the client can be tampered with.
- Use idempotency keys so retries after a dropped connection do not double post.
- Log device, user and location for each transaction to support audits.
Ways to get it done
Epicor wireless or mobile modules
Effort: Configuration and training over weeks, plus licence cost.
Best first stop for standard receiving, picking and counting if licensed and compatible with your processes.
Custom app on the P21 APIs
Effort: Typically two to five months for a few well-chosen workflows.
For workflows that differ from standard, or where you need a modern interface on mixed devices.
Partner such as Netray
Effort: A pilot for one workflow, then incremental additions.
When you want the app backed by private AI for lookup and exception handling, and kept entirely on your network.
Pitfalls
- !Writing directly to P21 tables from the backend bypasses business rules and breaks upgrades.
- !Underestimating Wi-Fi and scanner hardware issues; test on the floor, not at a desk.
- !Letting the app invent its own item or location logic that differs from P21 creates reconciliation work.
- !Forgetting lot and serial handling until late, which reshapes the pick and receive flows.
- !Skipping offline design leads to duplicate or lost transactions in weak coverage areas.
Frequently asked questions
Does Prophet 21 have a mobile app?
Epicor has offered mobile and wireless warehouse capabilities for P21, and availability varies by version and licence. Check what you own before building. A custom app is mainly for workflows the standard tools do not cover or for a different user experience.
Can the app work offline?
Yes, but design it deliberately. Cache reference data such as items and locations, queue transactions with unique keys, and sync in order when connected. Some actions, like checking live availability, cannot be fully offline and should say so clearly.
What devices work best?
Rugged Android scanners with built-in barcode engines are common in warehouses, since they offer fast scanning and durable hardware. Phones and tablets suit outside sales and delivery. Pick based on environment and total cost, and standardise models for support.
How do we handle user licences?
Licensing depends on how the app authenticates and which P21 services it calls. Ask Epicor or your reseller how API and middleware usage is counted for your contract before choosing a shared service account versus per-user logins.
Can we add AI features to the app?
Yes, for example asking where an item is or summarising a customer before a visit. Keep the model on your side, give it read-only tools over P21, and show the user the source so they can trust or correct the answer.
Want Mobile app working on your Epicor Prophet 21?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment