# Estimates in KillerConversions 1.2.6

Install and activate the Pro add-on, then start with its simple estimate template. Replace the sample currency and prices before publishing. An estimate is guidance, not payment collection, tax calculation or a final invoice.

1. Add a number question for quantity. Give it useful minimum, maximum and step limits.
2. Open Add pricing when unused, or Estimate pricing when already configured. Enable pricing and add a quantity row with its label, quantity question and unit price.
3. Add fixed extras tied to a selected choice or optional checkbox. Only visible, validated answers contribute.
4. Try a normal order, zero, maximum quantity, every extra and hidden-question cases. The published browser total is a preview; the server calculates the accepted total.
5. Publish and submit an example. Compare the saved entry, configured notification and print-friendly summary with your expected result.

For example, 2 hours × USD45.00 plus a selected USD25.00 extra produces USD115.00. Quantities support three decimal places and at most 1,000. Monetary inputs use two decimal places. Each quantity line rounds half-up to the nearest minor unit, then the lines are added. Negative or malformed amounts are rejected. Only configured currency labels are used; no exchange-rate conversion occurs.

Pro adds base and minimum charges, pricing tiers, conditional extras, saved expected-total examples and a price-change comparison before publishing. Volume pricing uses the reached tier’s unit price for the whole quantity. Graduated pricing charges each band separately. For example, ten units at 10.00 then further units at 8.00 means 12 units cost 116.00 under graduated pricing; a volume tier at 10 units with price 8.00 means 12 units cost 96.00. Choose and test the intended model.

Use saved examples at tier boundaries and immediately above/below them. A failed expected-total example blocks publication until you correct the prices or deliberately correct an outdated expected amount. Pro's legacy formula engine remains available for existing forms and supports only bounded numbers, field references and arithmetic operators; it never executes arbitrary code.

Accepted entries retain relevant inputs, currency, pricing revision, itemisation and total. Later price edits do not rewrite old estimates. Pro can generate a branded PDF from those stored values. Files, internal staff notes and remote resources are not embedded. See the application guide for PDF text/size limits.

Print the summary or inspect the saved entry if an email is missing. WordPress mail acceptance is not proof that a recipient received it. Estimates do not require newsletter consent; optional visitor confirmation has a separate choice.

Hosting requirement: itemised estimates use 64-bit PHP integers. Free text validation works without PHP mbstring; Pro PDF generation requires mbstring. This estimate display model uses two decimal places for every configured three-letter currency; it does not implement currency settlement or collect payments.