Compare supplier prices for one construction item with Alfie using source dates
Compare equivalent units, validity, tiers and delivery context before turning supplier-price data into a purchasing decision.
The lowest visible number is not necessarily the lowest usable purchase price. Package sizes, dated catalogues, quantity tiers and delivery conditions can make two supplier options incomparable.
Verify the source, identity and current state
The current Alfie product page positions Alfie as a governed execution layer where context, permissions and confirmations work together. Current application source registers compare_artikel_supplier_prices; it is classified as low-risk comparison. This page does not promise an external integration, autonomous outcome or availability beyond what the source supports.
Turn the request into one bounded decision
Resolve the article, required quantity and delivery context. Normalise units, show source date, validity, tier and supplier status, and flag missing values instead of ranking them as zero.
Keep evidence and separate the next actions
Keep the comparison as evidence for a human purchasing decision. It must not change the preferred supplier, update a purchase price, place an order or rewrite an estimate without another authorised action.
Test exceptions before daily use
Test a missing identifier, two records with the same name, insufficient permissions, stale source data and a temporarily unavailable system. Alfie should stop with a focused question or a proposal that has not executed. Keep the original request, selected record, relevant source fields, user, timestamp and confirmation without copying more personal or payment data than needed.
Repeat the check when the party, amount, scope, schedule, recipient or document version changes. An earlier result is context, not automatic permission. Define who can correct an error, who must be informed and when the exception is genuinely closed.
Make the result readable to a colleague who did not prepare the record. They should see which facts were established, what uncertainty remains and which action was executed or blocked. Free text can explain the evidence, but it does not replace identity, source or confirmation.
Before rollout, rehearse correction as well as success. Record how the team finds an incorrect selection, which dependent records need review and who may confirm the repair. This keeps one mistake bounded to its record instead of copying it into a schedule, quote, purchase decision or invoice.
Connect preparation to governed execution
Enfin connects the customer, supplier, quote, project, task, item, cost item and invoice in one construction record. Alfie can prepare information and propose an action within available permissions; an authorised user confirms consequential actions. Explore Enfin, compare pricing or discuss your workflow.
Sync construction cost-item prices with Alfie only after a web review
Review supplier evidence, effective dates, components and estimate impact before Alfie synchronises construction cost-item prices on the web.
Create a construction item with Alfie after checking supplier-reference duplicates
Verify name, unit, VAT, purchase source and existing references before a reusable construction item enters estimates and purchasing.
Approve an invoice inbox item with Alfie after project, amount and duplicate checks
Approving an incoming invoice is a financial decision, not a document-processing shortcut. An AI layer can collect evidence and prepare the decision, but it…