Sync construction cost-item prices with Alfie only after a web review

What the source actually says

Alfie's current capability map treats sync_kostenpost_prices as a medium-risk, web-only operation. It can be governed in application context, but it is not a WhatsApp or voice execution claim. This page does not turn that source into an automatic conclusion; it translates the verified boundary into a construction workflow that can still stop on uncertainty.

The practical value comes from applying the boundary consistently to every relevant person, document and project rather than remembering it only when an exception appears.

Data to capture before action

The primary source makes several boundaries explicit: 1. the action belongs to the operations family; 2. cost-item components and supplier prices can affect later calculations; 3. the web-only rule applies to review and import-related cost actions; 4. organisation permissions and confirmation still govern execution. Keep the official page with the operational rule so a later reviewer can see which wording and date supported the decision.

Record both the source value and the normalised value used by the workflow. Preserve later corrections as additions so the original evidence remains understandable.

A usable decision route

Turn the rule into a repeatable sequence: 1. identify the supplier evidence and effective date; 2. show old and proposed component prices; 3. calculate impact on open estimates without silently changing them; 4. confirm the selected cost items in the web interface. Give every step an owner, a timestamp and the relevant project or counterparty, rather than storing only the final status.

Before any external message, payment, status change or import, show the affected entity, amounts, dates and consequences. Require a fresh confirmation when those inputs change.

Where the workflow can fail

The most important failures appear when context or timing is lost: 1. overwriting negotiated project prices; 2. mixing gross, net and tier prices; 3. describing a registered action as an autonomous market-price feed. Use a visible exception state instead of guessing. A blocked item should explain what evidence is missing and who can resolve it.

Test at least one normal case, one ambiguous case and one late correction. The safe outcome for missing evidence is a question or escalation, not a confident default.

Control and ownership

Assign one authorised owner, keep the source, date, inputs and decision in one record, and send exceptions to a qualified adviser. Software can structure evidence, but it does not replace legal, tax or employment advice. Alfie belongs in this flow as Enfin's governed execution layer: business context, permissions, preview and confirmation surround the action. A model may structure information without receiving independent authority to decide.

Review the procedure when the official source, contract, channel or product capability changes. Track prevented errors as well as speed so governance produces visible value.

Official or primary guidance: Official or primary guidance.

Explore Enfin, review pricing, or discuss your workflow.