Review-required gate
Flag a quote line from your pricing equation so the customer can't see its price or check out until you approve the quote.
The review-required gate lets your pricing equation hold a part back for your attention before anything is shown to the customer. While it is active, the price is hidden on the storefront and the customer cannot check out until you approve the order for purchase. A line priced from catalog pricing tiers for that customer ignores the review flag, so the gate never holds it.
Use it for parts outside your normal operating range: oversized geometry, unusually large files, exotic materials or edge-case material combinations, unusually high quantities, or anything you want to price manually before committing.
How it works
- Your equation calls
done({ price, reviewRequired: true }), or passes any expression that evaluates totrue. A price that is 0, negative, or not a number sets the flag automatically. - The customer sees a price review message instead of the line's price, and checkout is blocked.
- In Phasio, the part shows an orange warning icon with the tooltip "The part was flagged for review by your pricing algorithm." The quote shows a red alert, "The parts in this order cannot be purchased due to manufacturing or payment constraints.", with the reason "There are parts with prices pending manufacturer review".
- You review the part, adjust its price if needed, and click Approve for Purchase. The customer can now see the prices and check out.
Your equation still runs to completion. The internally calculated price is visible to your team.
What the customer sees
The storefront shows a price review message instead of the price of each flagged line, and the customer cannot check out. In a customer's storefront catalogue, a part whose price needs review is listed without a price, and an assembly total that includes such a part is hidden. A fixed unit price you set yourself still shows.
Review a flagged quote
- Open the quote. Each flagged part shows the orange warning icon, and the quote shows the red alert.
- To change a part's price, open the quote's ··· menu and click Edit. Click the Modify Pricing icon on the part, then adjust its variables or switch on Override total price?. Click Save.
- When the prices are right, click Approve for Purchase in the alert. The customer can now see the prices and check out.
A manual price does not lift the gate. Approve for Purchase works on the whole order, not on one part, and it bypasses every purchasability check for the order, not only the review flag. Approving does not clear the review flag either: the flag and the orange icon stay on the part until a recalculation no longer sets it.
Quotes and orders you create in Phasio bypass these checks from the start, so the gate mainly affects storefront quotes.
What happens to the calculated price
When reviewRequired is true, your equation's price argument is still stored internally. In the part's Modify Pricing dialog you'll see:
- All
variable()fields (print time, machine, support volume, etc.) with their calculated values as placeholders - Override total price? to set the line total manually
There is no per-part approval. When the prices are right, click Approve for Purchase on the quote. Typing a manual price alone leaves the flag on.
Set the flag in your equation
Pass reviewRequired to done(), either as the third argument or in the object form:
done(price) // no review
done(price, duration) // no review, with duration
done(price, duration, reviewRequired) // reviewRequired is a boolean expression
done({ price: calculatedPrice, reviewRequired }) // review flag, duration from workflow.durationThe flag is available in process (Level 1) and post-process (Level 2) equations. An order-level equation has no done() call, so it cannot set the flag.
To set the review flag without a duration, use the object form. done(price, 0, true) sets the duration to 0 hours: an explicit 0 replaces workflow.duration, so the dispatch date uses only the lead time buffer.
Automatic triggering
The gate also fires automatically if the computed price is falsy, negative, or NaN - for example, if a required material.variables key is missing and the formula produces an unexpected result.
Customers see a price review message instead of a zero or negative price. A Level 2 equation that throws is different: the selected post-process adds 0 and does not set the flag. See When an equation fails.
Patterns
Part exceeds machine dimensions
const { width, length, height } = specification
const MAX_X = 340 // mm — adjust to your machine
const MAX_Y = 340
const MAX_Z = 580
const reviewRequired = width > MAX_X || length > MAX_Y || height > MAX_Z
done({ price: unitPrice, reviewRequired })Price out of expected range
const reviewRequired = unitPrice > 1000
done({ price: unitPrice, reviewRequired })Useful as a sanity check: if your equation produces an unexpectedly high price, catch it before the customer sees it.
Material requires manual pricing
const MANUAL_MATERIALS = ['Inconel 625', 'Ti-6Al-4V', 'Carbon PEEK']
const reviewRequired = MANUAL_MATERIALS.includes(specification.material.name)
done({ price: unitPrice, reviewRequired })Quantity too high
const reviewRequired = requisition.quantity > 500
done({ price: unitPrice, reviewRequired })Production time too long
const totalHours = round(buildHours + setupHours, 1)
const reviewRequired = totalHours > 120
done(unitPrice, totalHours, reviewRequired)Unsupported material / colour combination
const isUnsupported = specification.material.name === 'TPU' && specification.color === 'White'
done({ price: computeBasePrice(), reviewRequired: isUnsupported })In a post-process equation
const handlingFee = variable('1: Handling fee', 2)
const finishFee = processPricing.price * variable('2: % of part price', 0.15)
const finalUnitPrice = variable('3: Override unit price', round(handlingFee + finishFee, 2))
const reviewRequired = finalUnitPrice > 500
done(finalUnitPrice, 2, reviewRequired)Fully manual quoting (always review)
// This process is never auto-priced — every order goes to manual review
done({ price: 0, reviewRequired: true })Useful for exotic materials or bespoke services where no formula can reliably produce a price.
Combining multiple conditions
const { length, width, height, volume, minBoundingBoxVolume, minWallThickness } = specification
const stockVolume = minBoundingBoxVolume ?? length * width * height // can be null
const oversized = Math.max(length, width, height) > 300
const highRemoval = (stockVolume - volume) / stockVolume > 0.90
const openMesh = !revision.watertight
const thinWall = minWallThickness !== null && minWallThickness < 0.8 // null without wall thickness analysis
const reviewRequired = oversized || highRemoval || openMesh || thinWall
done(unitPrice, printTimeHours, reviewRequired)Each condition is independent. The gate fires if any of them is true.
Last updated on
Order-level pricing
Add fees, discounts and shipping to an order based on the whole cart with an order-level equation that runs once per order.
Process examples
Complete pricing equations for powder bed, FDM, large format FDM, SLA/DLP, metal LPBF, ceramics, CNC machining and vacuum casting, with the questions to answer before you build your own.