How does Ella handle a price mismatch between the PO and the ERP / pricelist?

Ella applies a clear price hierarchy: it first checks for a contract price specific to that customer–SKU combination in the ERP, then falls back to the customer's assigned pricelist.

If the final price disagrees with the PO, Ella flags it on the draft order with both prices visible side-by-side and a link to the exact location on the source PO where the PO price was found. Margin issues get caught upstream, not after the order ships.

» What the rep sees

The draft order line shows:

• ERP/Pricelist Price: The price Ella will use if the order is submitted as-is
• PO Price: What the buyer sent
• A direct link back to the source PO so the rep can verify the buyer's intent before acting

» What the rep can do

The rep has three options before submitting:

• Accept: Keep the ERP/pricelist price. The order submits with the correct price and the discrepancy is logged.
• Override: Manually enter a different price on that line. The override is flagged on the order for auditability.
• Escalate: Hold the order and route it to an admin or pricing team before submission. Useful when the discrepancy is large or the customer has a pending contract renegotiation.

No order with a flagged price discrepancy can slip through unreviewed; the rep must make an active choice before submission.

» Things to keep in mind

• Price conflicts are caught at draft stage, before the order reaches the ERP. This prevents margin issues from being discovered after the order ships.
• The override and the original PO price are both stored on the order record, so there is always a clear audit trail if a pricing dispute comes up later.