We are currently using a pricing workflow where certain parts are assigned a price value of 0.0 and then displayed to users through the Label system as "Request Quote" rather than showing a numerical price. From the user interface perspective, this works well. Users browsing parts catalogs see the intended label and understand that pricing must be requested rather than being immediately available. However, we have identified a problem when an order is submitted and Documoto generates its automated order confirmation documentation and email attachments. The generated order confirmation does not appear to utilize the configured price label. Instead, it displays the underlying numeric value of 0.0 for those items. As a result, customers receive documentation showing parts with a price of 0.0, even though the catalog correctly displayed "Request Quote" during the ordering process. In our workflow, these items are not actually free. After receiving the order request, our team reviews the submission, determines the appropriate pricing, and then contacts the customer with the final quote. While this process itself works, the generated documentation creates several concerns: •Customers receive official order documentation showing a price of 0.0. •This can create confusion regarding the actual cost of the requested parts. •It may establish incorrect expectations before our team has had an opportunity to provide pricing. •It creates a poor customer experience by displaying information that does not match what was shown elsewhere in the platform. •In some situations, it could potentially create disputes or misunderstandings regarding pricing. Ideally, any location within Documoto that displays pricing information—including generated order confirmation emails, attached order documents, PDFs, and other customer-facing outputs—should respect the configured price label and display the assigned label rather than exposing the underlying 0.0 value.
