How to Handle Edge-Case Jobs Without Letting Them Slip Through

Most quoting workflows are built for standard jobs. Parts that fit your machine, use materials you stock, and fall within the quantities your pricing formula was designed for.

Edge cases break these workflows in two specific ways. A part gets built in the wrong orientation because the constraint wasn't carried through from quoting to the floor. Or a customer receives an instant price on a job that actually needs a human to look at it first, and your team is committed to a number that doesn't hold up.

Phasio's build orientation constraints and review-required pricing gate are designed for exactly these situations.

GETTING STARTED

Both features sit in your process and quoting configuration. Orientation constraints are enabled per organisation under Settings > Organisation > General in the Manufacturing Constraints section. Review-required is configured directly in your pricing equations and also fires automatically when an equation produces a broken result.

Orientation constraints are available on Pro and Factory Floor plans. Full documentation for both features is here: https://docs.phas.io/

WHAT CHANGES FROM DAY ONE

Lock a part's orientation at quoting and it stays locked through to production. When a part needs to be built in a specific orientation to preserve tolerances, surface finish, or structural integrity, you can set that constraint directly from the part configurer in your quote or order. Drag the rotation gizmo to the correct position, confirm, and a fixed orientation icon appears on the part card. From that point on, the constraint is visible everywhere the part appears: in the order detail, on production groups, and on traveller sheets, so anyone handling the job downstream sees it without having to ask.

Customers can also lock orientation from your storefront by selecting "Use Original Orientation," which preserves the axis from their uploaded CAD file. Useful for parts where the customer already knows how they need the part to come out. If you're using the Dyndrite, 4D_Additive, or AMIS Pro nesting integrations, orientation constraints travel with the file via CAMSPEC export, so the nesting software packs the build respecting them automatically.

Flag non-standard jobs for review before the customer sees a price. The review-required gate lets your pricing equation hold a part back when it falls outside your normal parameters. The customer sees a "price under review" message and the checkout button is disabled until your team reviews the job and sets a price manually.

You trigger the gate in your pricing equation by passing reviewRequired: true to the done() function. Common conditions include parts that exceed your machine dimensions, quantities above a certain threshold, materials that require manual pricing such as Inconel, Ti-6Al-4V, or Carbon PEEK, production times beyond a certain number of hours, or unsupported material and color combinations. The gate also fires automatically if your equation produces a falsy, negative, or NaN result, so customers will never see a zero or broken price regardless of what the equation does with an unusual input.

Once your team reviews the flagged parts and sets a price, the customer can proceed to checkout as normal.

WHY IT MATTERS

The cost of getting an edge-case job wrong falls in two places. On the factory floor, a part built in the wrong orientation means scrap, rework, and a missed deadline. In the quoting flow, an automatically generated price on a job outside your normal parameters can commit you to a number that doesn't hold up once your team actually looks at the job.

Orientation constraints prevent the first by carrying the correct build orientation through every step of the workflow. Review-required pricing prevents the second by intercepting non-standard jobs before the customer sees a price, giving your team the space to assess the job without any pressure already applied.

Together they let you run self-serve quoting for the jobs that fit your standard parameters while handling the exceptions deliberately, without those exceptions slipping through unchecked. The storefront stays open and frictionless for most jobs. The edge cases get the attention they need.