Who runs Prophet 21
Prophet 21 is the most widely deployed ERP across mid-market industrial and MRO distribution in North America, and the one most FrontBeacon prospects are already running.
Where the manual work actually is
P21 is good at holding an order once it exists. Getting the order into it is the bottleneck: EDI covers your largest twenty customers, the web store covers the ones who will use it, and the long tail — the ones who have emailed a PDF to the same address for eleven years — is keyed by hand.
How orders get into Prophet 21
There is more than one route in, and which one suits you depends on what your site already licenses and trusts. These are the routes worth knowing before any conversation about integration.
Scheduled Import Service Manager (SISM)
P21's native bulk order intake. A system drops files in an agreed location, SISM collects them on a schedule, moves each order from Submitted to Processing, and assigns a P21 order number. Epicor's own B2B Seller uses it, as do commerce connectors and third-party order tools. This is the route FrontBeacon targets: it is native, it needs no additional licence, and the file is inspectable before it is picked up.
Source: www.airdev.co
P21 Transaction API
Posts transactions, sales orders included, without driving the UI. It is a separately licensed add-on and the official documentation is thin, with most working knowledge living in community forums. Viable if you already hold the licence, and unnecessary if you do not.
Source: www.airdev.co
EDI 850
The native path for trading partners already set up for it. It is also the reason the problem exists: the customers worth an EDI project already have one, and the rest email PDFs.
Where FrontBeacon stops
FrontBeacon produces a file shaped for your SISM import location. Your reviewer approves the order on screen — beside the original PDF — and the file is written for collection. Because SISM is a scheduled file pickup rather than a live write, there is a reviewable artifact at every step and no direct connection into P21 from us.
- FrontBeacon is not an Epicor partner and is not listed in the Epicor ISV Solution Gallery.
- We do not drive the P21 UI, and we do not require your Transaction API licence.
Common questions
- Do we need the P21 API licence?
- No. FrontBeacon targets SISM, which is native to Prophet 21 and needs no additional licence. If you already hold the Transaction API licence that is another option, but it is not a prerequisite.
- How is this different from an EDI project?
- EDI requires each customer to adopt a format and maintain it. This requires nothing of your customer — they keep emailing the PDF they have always emailed. The change is on your side of the desk only.
- What happens when a line cannot be matched confidently?
- It blocks. The order does not become a file until a person resolves it. FrontBeacon will not default an unknown unit of measure to each, and will not pick between two plausible SKUs on your behalf.
Related
- Fastener distributorsEmailed purchase orders turned into reviewed sales orders for independent fastener distributors — with per-M and per-C quantities converted explicitly, not silently.
- Industrial and MRO distributorsOrder-entry automation for industrial and MRO distributors — broad catalogs, long-tail customers, and the emailed orders EDI never covered.
- PVF and plumbing distributorsEmailed purchase orders into your ERP for pipe, valve and fitting distributors — with spec, schedule and material detail kept on the line.
Running something else? See every ERP handoff.