Configure lead times
How to configure and manage lead times and their pricing in Phasio
Lead times are defined on the workspace level, and are uniformly available across all of your processes and post-processes. As such all lead times will be available for selection through your storefront.
You can configure these under Settings > Manufacturing > Lead Times.
Each lead time is associated with a duration buffer, which we use when calculating an estimated dispatch date at the point a customer places an order through your storefront. You can think of this as a grace-period to begin production on a requisition.
Add a lead time
- Open Settings > Manufacturing > Lead Times.
- Click New Lead Time.
- In the Add new Lead Time dialog, enter:
- Name: the name customers see, for example
Standard. - Buffer: the buffer in whole hours.
- Auto selected: switch this on for the lead time that the storefront selects for new parts.
- Name: the name customers see, for example
- Click Add.
The table lists each lead time with its Name, Duration Buffer, and Auto selected setting. To change a lead time, click its Edit icon, change the fields in the dialog that opens, and click Update. To remove it, click its Delete icon.
If no lead time has Auto selected switched on, parts added on the storefront have no lead time, so requisition.leadTime is null in your equations. Parts added in Phasio get the Auto selected lead time, or the first active lead time if none is auto selected.
Multiplier adjusted pricing
You can customise the unit price of a requisition directly within your process and post-process equations, through introspecting the requisition.leadTime?.name property that is available to you. requisition.leadTime is null when the part has no lead time, so always use ?. and a default case. Without them, the equation fails or the price becomes NaN.
Here's an exemplar primitive implementation of lead-time adjusted pricing:
function getLeadTimeMultiplier() {
switch (requisition.leadTime?.name) { // leadTime can be null
case 'Economy':
return 0.8
case 'Standard':
return 1
case 'Expedited':
return 1.2
default:
return 1 // no lead time, or a name not listed here
}
}
done(unitPrice * getLeadTimeMultiplier())Quantity adjusted pricing
In the above example, we've adjusted the unit price of a part by an arbitrary pricing multiplier based on the selected lead time for this requisition.
The flexibility of defining your lead time pricing directly within your equations, as opposed to using a general pricing multiplier defined on the lead time itself, is that you have the flexibility to make these adjustments in pricing based on things such as selected quantity, and geometric properties such as part volume.
Here's an exemplar of quantity adjusted lead time pricing:
function getLeadTimeMultiplier() {
switch (requisition.leadTime?.name) { // leadTime can be null
case 'Economy':
return requisition.quantity > 1000 ? 0.95 : 0.8
case 'Standard':
return requisition.quantity > 1000 ? 1.1 : 1
case 'Expedited':
return requisition.quantity > 1000 ? 1.5 : 1.2
default:
return 1 // no lead time, or a name not listed here
}
}
done(unitPrice * getLeadTimeMultiplier())Last updated on