Treat part identity, pricing, availability, and reservation as separate decisions—even when they appear together on a quote.
Begin with the item relationship
A repair center description, supplier catalog number, and ERP item code may refer to the same part without using the same text. Establish a controlled mapping and keep uncertain matches visible. Include the unit of measure, pack quantity, and location where those change how a part is ordered or issued. Technical compatibility still needs an approved equipment reference; a commercial item match is not approval for a substitute.
Choose the owner of price and cost
A supplier cost, an internal standard cost, and a customer selling price serve different purposes. Decide which values the service price book should read and which remain controlled by the ERP or commercial team. Identify effective dates, customer-specific arrangements, and who may approve an exception. Avoid a broad two-way update that lets an edited quote silently overwrite the master item price.
Distinguish stock from a commitment
A stock quantity can be a useful planning input, but it may be old or include material that another job needs. Define the meaning of the availability value and show its refresh context where necessary. A reservation or purchase decision is a separate action with an owner. The service planner should know whether a part is merely listed, checked as available, allocated, or awaiting confirmation.
Keep quote revisions reproducible
When a repair quote is issued, preserve the relevant item, unit, quantity, and price information with that revision. A later price-book update should not make the original customer offer impossible to explain. If the scope changes, retain the revised approval separately. Link the resulting job to the accepted version so repair center instructions and eventual billing refer to the same commercial agreement.
Assess the actual ERP environment
Business Central provides REST API services, while Epicor describes an SDK for Prophet 21 extensibility. These are starting points for technical assessment, not proof that every desired field is exposed in a customer’s installation. Review customizations, access, endpoint coverage, and any required implementation work. A read-only customer and item lookup can establish useful shared context before more consequential purchasing or inventory actions are considered.
Use awkward cases in the first review
Test a pack sold as individual units, a superseded item, a customer-specific price, an unavailable part, and an approved quote created before a rate change. Ask the estimator and parts coordinator to explain the result together. If they cannot tell which record is authoritative, refine the mapping first. The goal is a price book that supports a defensible quote, not just a successful transfer of fields.
A working checklist
- Supplier, business, and ERP identifiers mapped
- Cost and selling-price ownership defined
- Availability distinguished from reservation
- Issued quote values and approvals remain traceable
Source references: Microsoft: Business Central REST API overview · Epicor: Prophet 21 technology and SDK. Provider references describe their interfaces. Maxwrk connections are scoped and validated for each customer; no prebuilt connector is implied.
An operational planning perspective. Equipment-specific decisions and service procedures remain with qualified personnel and the customer’s approved process.