A distributor’s customer can describe a repeat purchase in one sentence. Preparing it in Prophet 21 may require the rep to search account-specific item codes, check the supplying branch and explain why the old discount no longer applies.
Bourne can prepare that work around your Prophet 21 records. To make it useful, start with a real request and follow every interpretation through to the saved quote. The example below focuses on a customer alias and a requested repeat discount, two details that a straightforward copy-and-paste integration would miss.
Resolve the item, branch and requested discount
The customer writes: “Quote 200 of our usual anchors, customer code ANC-17. Ship from the branch that served our last job. Same discount if possible.”
Look up ANC-17 within that customer’s account. A different buyer may use the same code for another item. Once you identify the anchor, confirm whether 200 means pieces or packs and retrieve current pricing in that unit.
The previous sale identifies the branch and discount the customer remembers. Check current availability before choosing that branch again. “Same discount if possible” is a request for a concession; compare the current terms with the earlier ones and send the difference to the pricing owner if it needs approval.
Confirm the quote operations your installation supports
Epicor positions Prophet 21 for distribution operations. Your administrator or Epicor partner should confirm which interfaces your installed version supports before you scope quote creation.
Include account and item lookups, quote creation and the returned quote identifier in the integration acceptance test. Your Prophet 21 administrator should review the saved transaction.
Check the pack size after identifying the item
A correct customer-code match does not establish the selling unit. Ask the reviewer to confirm both. GS1’s GTIN Management Standard treats packaging quantity changes as an identification concern; use current packaging data rather than assuming a familiar product name means the same pack.
For ANC-17, keep the customer account and source quote behind the mapping. Then test similar shorthand from another account: a correction for one customer must not change how you interpret another customer’s code.
For customers that exchange structured orders, keep the customer’s unit code as well as the displayed description. UNECE Recommendation 20 supplies common unit-of-measure codes for trade, but your customer and Prophet 21 item still need an agreed conversion.
Treat “case,” “hundred” and “each” as different price bases. In a sample check, 500 pieces at $8 per hundred should extend to $40. Sending a quantity of 500 with a unit price of $8 would create a $4,000 line. Verify both the imported values and the resulting document; a successful integration response cannot detect the commercial mistake for you.
Test whether a customer correction carries over correctly
Include customer-specific aliases in your pilot acceptance tests. After correcting one example, test a later RFQ from the same account and a similar RFQ from a different account. Record both correct reuse and incorrect carryover.
Record corrections and review time. Include these inputs in your evaluation:
- Collect RFQs with customer and manufacturer part numbers.
- Provide past quote lines with customer, item, selling unit, and branch context.
- Include changed pack sizes and split-fulfillment examples.
- Have your Prophet 21 administrator confirm the account fields and actions the workflow may use.
Base your quoting capacity estimate on the time reviewers spend across that whole sample. Exact SKU matches will overstate the gain if customer aliases and split fulfillment account for much of the team’s workload.
Use Bourne for the work before quote entry
Choose Bourne when your Prophet 21 team spends its time resolving customer item codes, finding past project details and chasing approval for requested discounts. Bourne’s native Prophet 21 integration connects the approved result to the quote operations available in your account.
The review app can show the requested terms beside the current ones, so your rep sees the decision instead of repeating the research. Plan your Prophet 21 quoting workflow.
Frequently asked questions
Can we automate Prophet 21 quoting while reps keep using the ERP?
That can be the proposed workflow: prepare the request and place the result in the existing quoting process. Confirm the supported interface and where reps review exceptions before committing to the design.
Should we use customer or manufacturer part numbers for matching?
Keep both when available, together with the internal item. Customer numbers need account context; manufacturer references may still need a revision, unit or product specification.
Does Bourne connect to Prophet 21?
Bourne includes a native Prophet 21 integration. Confirm the version, records and transaction actions available in your account rather than relying on the Epicor name alone.
Further reading
UNECE: units of measure codes
Recommendation 20 provides standard codes for units used in international trade.
Arda Bulut
Arda Bulut is the co-founder and CTO of Bourne and HockeyStack. He leads engineering at Bourne, building the platform people use to create AI products, agents and automations.