Skip to main content

Feature Request: Mandatory Cost/Selling Price & Prohibit 0.00

Customer requests a feature to make 'Cost' and 'Selling Price' fields mandatory for all product types. The primary goal is to prevent users from entering '0.00' as a placeholder, ensuring actual values are provided. Currently, this validation is only in place for specific product types where a missing value would cause a PSA sync error.

1 comment

Log in to comment and vote

Comments1

  • Aqua Snowflake

    •

    Oct 29

    FEATURE REQUEST BRIEF

    Summary

    The customer needs to enforce cost price entry on hardware line items during quote creation to prevent €0 cost values from syncing to their PSA, which skews margin analysis. Currently, account managers can leave cost price blank on hardware products, causing distorted margin calculations downstream when items sync with zero cost but positive selling price.

    Background

    The customer uses Salesbuildr to create quotes with mixed line item types: consulting hours (which legitimately don't require cost price) and hardware (which must have cost price for accurate margin tracking). Hardware cost prices should come from distributor feeds, but for non-catalog items or when distributor data is incomplete, account managers must enter cost manually. Today, if cost price is omitted on hardware, a €0 value syncs to their PSA (Autotask), where margin analysis shows distorted percentages (e.g., 100% margin when cost is €0 and selling price is €100). This makes it impossible to accurately track hardware profitability.

    What Was Investigated

    Workarounds explored and their limitations:

    • Approval rules: Can enforce minimum margins or maximum discounts but cannot prevent €0 cost entries or distinguish between product types.

    • Distributor auto-population: Fills cost only for catalog items; non-catalog hardware items still require manual entry.

    • Custom fields with required toggle: Can enforce custom data points but does not apply to the standard Cost Price field itself.

    None of these address the root issue: there is no mechanism to require cost price specifically on hardware line items within a quote.

    The Gap

    Salesbuildr lacks a way to make cost price mandatory on individual line items during quote creation. The Cost Price field is optional by default, and there is no conditional enforcement (e.g., "require cost price only for products in the hardware category"). This allows €0 cost values to be saved and synced to downstream systems, breaking margin analysis workflows.

    Requested Feature

    • Add a required field toggle for Cost Price at the quote line item level, either globally or scoped to specific product categories or types.

    • When enabled, prevent quote line item save until Cost Price is populated with a non-zero value.

    • Optionally, allow configuration to apply the requirement to specific product categories (e.g., hardware) while exempting others (e.g., services/consulting).

    • Display a validation error at line item entry time, not after sync.

    Why This Matters

    Inaccurate cost data in the PSA breaks financial reporting and makes it impossible to track true product margins. This affects pricing strategy, profitability analysis, and accountability. Other MSPs using mixed-service quoting models likely face the same issue when account managers lack discipline around data entry.

    Proposed Priority

    Low. This is a data governance issue specific to workflows where cost price is sometimes optional. It can be mitigated with process discipline or approval rule validation, and the feature request is novel (first time requested). However, prioritize discovery to confirm if other customers have similar margin tracking needs.